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