Built-in Profile - Business Analysis Outline
|
Previous Top Next |
EA Element
|
Formatting Style
|
Notes
|
|
Requirement
|
|
Table
|
Prints the Alias, Name and Priority
|
Actor
|
|
Table
|
Prints the Actor name, detail and a link to the use cases which the actor uses
|
Use Case
|
|
Table
|
Print the Use Case reference (Alias), Name, Description and a link to the actors who use the use case.
Using EA to hold details of which Actors use which use cases means the use case text doesn't need to hold a list of actors which is manually maintained.
|
Class
|
|
Inline
|
These might be used in a conceptual model during analysis
|
Attribute
|
|
Table
|
Attributes of classes
|
<<process>> Activity
|
|
Inline
|
For this example, business processes are given this stereotype, so we can control the formatting. They are formatted as Inline, because we've chosen to print their diagram, and sub-Activities
|
Activity
|
|
Table
|
The lowest-level parts of the business process. OK to print these in a table, as they have no sub-elements.
We also print the previous and next activities, to show how related element details can be used.
|
ActivityPartition
|
|
Table
|
This is what EA calls the swimlanes which are used in business process diagrams. Renamed to 'Team' in this example.
|
Decision
|
|
Table
|
Shows where decisions are being made in the business process flow. Quite a low level of detail. Also shows previous & next activities
|
EA Element
|
Formatting Style
|
Notes
|
|
Document Information
|
|
Table
|
Allows for printing the Document Information table about when and from where the document was generated
|
Term
|
|
Table
|
Use when printing a glossary
|
Issue
|
|
Table
|
Good for annotating use cases or requirements with issues as they arise during the analysis process
|
Package
|
|
Inline
|
Required for eaDocX to create the basic heading structure
|