Sharing your EA models with new users - EA users or non-EA users - is a great way to share the knowledge which those models contain.

But's it not as simple as giving them access to EA. Or even access to some other, web-based tool which lets them see into EA. We need to think about

  1. what's in the model and how it's organised,
  2. who needs ot access it and what we want them to do, and finally,
  3. create an experience for those users which will let them actually do what we need them to do

This workshop is a single-customer workshop, because you'll be working on your own model - or maybe a copy of it, just to be safe.

You'll get practical help on what to do, then be try out the techniques on a model which you understand.

Agenda:

Session   Activity Deliverables
1 Organising your model

- Looking at your package structure

- Techniques for tidying-up diagrams

- Assessing your meta-model - what element types and stereotypes do you use, and what connectors.

- proposed new package structure

- standards & action plan for tidying-up diagrams

- view of your meta model, and a plan to make it consistent

 

2 Audience and Action

- who might beneft from getting access to your models ?

- what would you like them to DO once they can access them? Just read, or read and comment, or give their formal approval?

- matrix of people, actions, and the parts of your models they need to access

- sets the agenda for the next session, where we prepare the model for them to access

3 Curation

- learn some techniques for presenting information to users in new ways, so they can make the contribution you need

- practice these on some of your own models

- plan for adding new curated diagrams 

- plan for adding new types of information presentation

4 Implementation  Finally, we'll look at some the tools which are available to let you deliver all this - web-based Ea tools, tools within EA intself, and other EA-related tools

- implementation tasks

- list of actions

The course is a full day, run onsite on your premises, so that the team can acces your models.

Our instructor will need to see these models, so we are happy to sign a reasonable non-disclosure agreement before we start the workshop.

Maximum delegates - 12

Skill level required - Proficient EA user. Able to navigate around EA, create diagrams, do basic modelling tasks. 

Knowledge Curation with EA (workshop)

Duration

1 day

Cost

£1200 plus £35 per delegate and instructor expenses

Delegates

Maximum of 12

Prerequisites

Knowledge of Enterprise Architect

 

Modelling has changed how complex IT projects are analysed and designed. Models can join-up the skills and knowledge of lots of different people. But our experiences of managing projects and creating models tells us that there is often a disconnect between the language, background, and sometimes even the objectives of PMs and modellers.

Modellers are focused on their key Project deliverables...

  • Architectiure
  • Requirements Managaement
  • Process Management
  • User Stories and Use Cases
  • Design

Project Managers care about these Project deliverables too, but they are also concerned with:

  • Benefits management
  • Stakeholder Management
  • Risk and Issue Management
  • Configuration Management
  • Reporting.

This intensive 2-day workshop will pull your PMs and Modellers closer together, by concentrating on the overlapping concerns of both groups. We’ll create a language which they both can share, as well as creating an action plan. And we do this in a unique way. The workshop is facilitated by an experienced Project Manager AND an experienced modeller. In this way we build a bridge between these two areas of expertise, so that the Modellers change what they do to support the Project Managers, and the PMs know what the model can deliver. Bridging the gap, to make everyone more successful

 

Topic  
Introduction

Develop a simple vision of how your projects could work when this is all done. What will success look like?.

Choose a Project

Either the project you’re working on, or, if you haven’t yet chosen one, identify one where modelling will make a visible difference

Understand the art of the possible

Discover what models are good at, and what not. Clue: they are usually poor at doing pure Project Management! And compare this with what you’re currently doing. Looking from the modellers and PM perspectives

What can we do differently?

Explore what  Project Managers need, and how modellers can help deliver that — agreeing what and how the models  can be changed simply to deliver …

Minimum Value Model (MVM)

What is the least amount of modelling we can do to deliver value to the project? This isn’t the full vision: it’s just the first step towards it

Action Plan and Outputs

Agreed success criteria for candidate project (s)

Prioritised list of pain points and actions

Tailored modelling recommendations for your MVM 

Project Governance impacts: Milestones/key stages, impacted processes, easy wins

Plan for implementation

 

 Delivering Projects with EA

Duration

2 days

Cost

£4800 plus £70 per delegate and instructor expenses

Delegates

Maximum of 12

Prerequisites

Knowledge of Enterprise Architect

 

This course explores how to analyse, capture and manage requirements in EA.

With examples and exercises to reinforce the concepts.
 
 
Topic Details

Introduction

Mandatory on all courses. Just introduces the course and the approach

Writing Good Requirements

We will look at the 9 criteria for individual requirements, and 8 criteria for a set of requirements. Then using exercises we will uncover common pitfalls and identify strategies for  avoiding them

Requirements Management in EA

Using the results of the exercises completed in the morning, we will explore how EA supports requirements management, and identify techniques, hints and tips to make our analysis clear and, where appropriate, re-useful. (NB this session assumes delegates already have some familiarity with the Enterprise Architect UI and navigation.)

Creating Requirements

We will explore how to create and edit requirements using the Enterprise Architect Specification Manager. How to link requirements to other things including using relationship matrices and diagrams. The use of colours.

Managing Requirements

Making bulk edits (e.g. for changing status values). Using validation rules. Baselining and Audit in EA. 

Importing Requirements

We’ll look at the options available: including native EA import capabilities, writing bespoke import scripts, eaDocX/eaXL and other approaches.

Publishing Requirements

We will look at the native EA ‘out of the box’ capabilities as well as other tools to assist in review and approval of your requirements

Customising EA for Requirements Management

Including Element naming and numbering and Level numbering

 

EA in a Day: Requirements Management

Duration

1 day

Cost

£1200 plus £35 per delegate and instructor expenses

Delegates

Maximum of 12

Prerequisites

Knowledge of UML
(from e.g. UML for Business Analysts)

 

This course explores how to analyse and capture details of Use Cases in EA using Structured Scenarios, which make structuring your Use Cases simple and fast.

With examples and exercises to reinforce the concepts.
 
 
Topic Details

Introduction

Mandatory on all courses. Just introduces the course and the approach

What is a Use Case?

Putting UCs in context: relationship to User Stories, Scenarios, Task Analysis

Getting to the Goal

Expected and Alternate paths, and Exceptions. How much detail is enough? Partly and fully dressed UCs. Granularity

Extras

Adding Non-Functional Requirements (NFRs) and Actors, UC writing guidelines, how can UCs go wrong?

Use Case Diagrams

What to include: UCs, Actors, system boundaries.  UC Activity Diagrams. All using UML Notation.

Adding Detail

Actor inheritance, Includes and Extends,  Dealing with time,  Use Cases and Test Cases

Modelling Use Cases in EA

Using the results of the exercises completed in the morning, we will explore how Use Cases are implemented in EA, model our UCs and discover hints and tips to make our analysis clear. (NB this session assumes delegates already have some familiarity with the Enterprise Architect UI and navigation) 

 

EA in a Day: Use Cases

Duration

1 day

Cost

£1200 plus £35 per delegate and instructor expenses

Delegates

Maximum of 12

Prerequisites

Familiarity with Enterprise Architect  UI and navigation.

 

If your project is about to start using EA, then it makes sense to begin by pulling-in as much existing knowledge as you can. No point in re-inventing things your organization or industry already knows about.

Each time we have helped projects to do this, the knowledge they have harvested has been different, but we’ve noticed that some common ideas have emerged. This 1-day workshop lets you benefit from all those other projects, and gets you off to a flying start.

This workshop helps organisations evaluate what types of data can be harvested, structure and organise models for successful data import, understand impacts and strategies for managing data governance and then choose the best way(s) to do it.

 
 
Topic Details

Introduction

Mandatory on all courses. Just introduces the course and the approach

What’s your approach? 

Big bang or incremental

What would you like to harvest?

This is where any discussion on harvesting should start: what’s your project trying to do, and how could a well-populated model help that project go faster, cheaper, and with better quality? This will then help us to create a target list of existing knowledge which we’ll try to find

What’s available?

The amount and types of knowledge available will affect how we decide to approach the problem

Analyzing information for harvesting

What’s its meta-model? When knowledge is pulled into EA, it needs to become something. It’s not just text & diagrams. It might be some Requirements, a set of Industry-standard processes, or some test case results. In each case, we need to work out where this new knowledge will fit with what you know already, and how to plan to develop your model in future.

EA can also help you to produce knowledge you can use in new ways. For example, you could pull-in the design of an existing database, then use EA to reverse engineer that back into a domain model. These techniques can give really useful insights into how other projects have approach problems similar to yours

Governance

Please don’t yawn. Governance may be dull, but it gets more interesting when, for example, you base your project on some harvested processes, and those processes change between when you harvest them, and when your project goes live. So your project fails. Now are you interested in Governance? In this section, which may be quite short, we’ll just think about how we manage harvested knowledge

Mechanics of Harvesting

This is the meaty part, where we actually get our hands on some existing information, and pull it into EA in a variety of ways. We look at Built in EA functions, Functions in eaDocX/eaXL, Bespoke EA import scripts and contract harvesting.

 

EA in a Day: Knowledge Harvesting (workshop)

Duration

1 day

Cost

£1200 plus £35 per delegate and instructor expenses

Delegates

Maximum of 12

Prerequisites

Knowledge of EA