This paper discusses how with EA and eaDocX business rules can be managed as a strategic resource and integrated into your project documentation. Enterprise Architect allows you to
Enterprise Architect allows you to capture Business Rules in a range of styles, from simple statements which are just special kinds of Requirement, all the way to executable, verifiable logical statements.
The presentation describes how Ian used EA in a large multi national project , and in the process "did less work, had more fun and became (a bit) famous".
This is the second presentation given by Ian at the European EA User Group event in London on Wednesday May 15th 2013. He also presented it in Ottawa at the North American/Canadian EA User Group meeting on May 1st 2013.
This White Paper looks at ways to transform our project documents, helping readers to find and use information that is relevant to them.
In both Waterfall and Agile developments,
excellent documents can improve project quality and give new insights. New document capabilities allow authors to create high quality, accurate and targeted documents, and allow readers to navigate their way through them in an intuitive way.
By storing information in EA, and using eaDocX, approaches are described that can bring our project communications into the 21st Century. Documents which:
- contain only content which is relevant to the reader
- provide a range of presentation styles
- engage and hold the reader's attention
- guide the reader as to where they should concentrate their attention
- give the reader freedom to navigate the document’s contents as they wish
This sample just shows you what the various kinds of Word paragraph style are which are defined for this document.
It will show:
- Table header, text, bullet and number list styles
- Inline normal, bullet and numbered bullet styles
It shows how you can make use of these Word paragraph styles to improve the appearance and readabilty of your documents.
The BulletList script takes each Element which is passed from eaDocX, and creates a simple bulleted list of the names of the elements. It will work for
any kind of element, so you might use this multiple times, for all the element types which you'd like to print as bullets.
It doesn't make use of any Word paragraph styles, for the formatted output might look a bit strange.
This final Bullet List example uses a Word Paragraph style: the one which you have chosen in you document for the Inline Bullet style. You can
specify this in the eaDocX Options and Settings, Under Inline Settings.
This means the output will look more like other bullet lists which eaDocX generates, those which appear in the 'Notes' field of any element.
This is an example of the type of complexity for which you might use an eaDocX Script.
What we want to do is calculate the 'importance' of a Requirement, based on how many people want it, and how
much they want it. We have decided to link Requirements to Actors using a stereotyped Dependency, with a stereotype of "High", "Medium", "Low" or nothing.
The importance is then calculated - by the script - as (3 x Number of 'High' Dependencies) + (1 x number of 'Medium' Dependencies).
This is then printed in a table, with Importance values of > 10 being highlighted in red, 5-10 in yellow.
This script shows how you can use Scripting to both apply calculations to your eaDocX documents, and control the output formatting as well.
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.