How do you take advantage of Use Cases in Enterprise Architect?
How can you link Use Cases and scenarios to formal requirements for improved traceability?
How to leverage your Use Cases to drive other downstream activities like testing and modeling?
Use Case Analysis is a well established technique to identify and improve system requirements. This webinar will examine how Enterprise Architect can model the proposed functionality of a new system using Use Cases and Requirements.
In this webinar you will learn how to:
| Example Model: | Shuttle-Launch-Use-Case.eap |  |
Enterprise Architect 12.1, Build 1229.
Enterprise Architect provides an in-built Learning Center with a step-by-step guide to help you get started.
The UML Tutorial on the Sparx Systems website can help provide a technical overview of the 13 UML diagrams supported by Enterprise Architect.
You may care to examine the following Community Site video that introduces diagram creation and building a Use Case.
http://community.sparxsystems.com/tutorials/951-exploring-enterprise-architect-through-video-part-4
Please refer to the Help topic Agile Requirement Processes. The Community Site also refers to the Agile Business Analyst.
Automatic. Items that appear in the Glossary are automatically highlighted when they are used in text fields in Enterprise Architect.
Yes, you can easily export Enterprise Architect's glossary to a Word, RTF or PDF document. You can learn how to do this from the Help topic System Document Templates. See the Glossary section.
The Glossary is stored in Enterprise Architect's model repository, within the table: t_glossary.
Glossary definitions are not stored or displayed in the Project Browser. To access the Glossary, use the Project menu, or the keyboard shortcut, Alt+2.
Yes, through the Automation Interface or via the table in the model repository, t_glossary. For more information on using the Automation Information to access the Glossary, see the Help topic Term Class.
Yes. It is possible to undertake an XML import of Glossary terms.
The related Import process covers Glossary terms in the exported XML format. For an alternative using an Excel import see: Community Site article Simple VBA Excel to EA importer.
Yes.
For more information, see the Help topic Using the Image Manager.
It is also possible to download an image library from the Sparx Systems website.
No. This is not supported.
A Use Case scenario is intended to be a simple scenario conveying a single alternate flow. Where there is more complex detail involving multiple alternate flows, then it is best depicted using an Extend connection to the alternate Use Case and placing the nested Alternate scenario in this extended Use Case.
No.
Use the in-built diagram generation to create an Activity diagram.
Yes. You can automatically create a Realization relationship between a Use Case and a Requirement. Simply drag the Requirement from the Project Browser onto a Use Case diagram. If the relationship already exits, Enterprise Architect will automatically add the dependency relationship where it already exists.
You also have the option of placing a Requirement or a Use Case onto a blank diagram and using Insert All Related Elements command to build an appropriate Dependency diagram.
A realization connector shows that the source element implements, or realizes, the destination element. Dependency connectors model a much broader range of relationships between elements. Once you create a Dependency you can further refine its meaning by applying a specialized stereotype.
For more detailed explanations, please refer to the Help topics Dependency and Realization.
Yes.
When you have created a structured scenario, you can generate any of these diagrams from it:
For more information, please refer to the Help topic Generate Diagrams.
The values in the 'Uses', 'Results' and 'State' columns, whilst optional, are significant if you want to generate a diagram from the specification.
Result: Indicates the result or outcome of completing this step. This information is often quite valuable for testing purposes to ensure accurate and timely results are being produced.
State: The name of the State that the system enters, as a result of completing a particular step in the scenario. This information is typically used to create a State machine so Business Analysts can identify the contributing factors that cause State Change within a system.
Yes, the Structured Scenario Editor was available in Enterprise Architect 11.
It was first introduced in Enterprise Architect 8, however the Structured Scenario Editor has undergone many enhancements since its inception.
Yes. The scope of this is very open. It is commonly a Realization or Dependency relationship to a Requirement, Feature or another element elsewhere in the model.
Yes. For more information, please refer to the previous webinar on Model-Driven Use Case Analysis with Structured Scenarios.
Yes. You can link to functional and non-functional requirements on a single line.
