Do you need to capture, manage and trace project requirements?
Do you have requirements stored in text documents, spreadsheets or other formats that inhibit traceability and analysis?
Enterprise Architect provides powerful tools for requirements management and activities associated with discovering, evaluating, recording, validating and reporting on your project requirements.
In this webinar you will learn how to:
| Example Model: | shuttle-launch-use-case-extended.eap |  |
| Whitepaper 1: | requirements-engineering.pdf | |
| Whitepaper 2: | time-aware-modeling.pdf | |
Enterprise Architect 13 Beta. Build 1301.
Registered Users can download the Enterprise Architect 13 Beta installer from the following page:
http://www.sparxsystems.com/ea13
Registered Users will be notified via the Forum when Enterprise Architect 13 is officially released.
Yes. Sparx Systems has a global network of authorized Enterprise Architect Trainers and Consultants that offer a full range of products and services to support you in your activities.
For more information or to contact a partner, please refer to our Partners and Services webpage:
http://www.sparxsystems.com/partners/index.html
Yes. Sparx Systems has a comprehensive library of webinars available to the public.
Previous webinars are available for viewing at:
http://www.sparxsystems.com/webinars
Yes. Some of the webinars are also available on the Sparx Systems YouTube site:
https://www.youtube.com/user/SparxSystems
The Enterprise Architect 13 release page outlines some of the exciting features and benefits that may be of interest to new and existing customers. Please refer to the release page for more information:
http://www.sparxsystems.com/ea13
The Enterprise Architect 13 User Guide also provides a comprehensive range of resources to help get you started.
Yes. I have used Auto Naming to ensure consistency in the names of requirements as they are created. You can add pre and post fix details to any requirement.
See the Help Guide for more information about Auto Naming and Auto Counters .
Yes. There is improved support for Linux and Mac OS under Enterprise Architect 13.
The Specification Manager, Charts, Custom UML Types, Requirement Diagrams and Requirement Checklists are all available in Enterprise Architect 12.1
Tagged Values were available in Enterprise Architect in 12.1, however the ability to filter based on tagged values is new to Enterprise Architect 13. The new Ribbon Interface, including the ability to search for tools and commands was introduced in Enterprise Architect 13. Time Aware Models and Cloning capabilities are new features available in Enterprise Architect 13, that were designed to help people understand how models evolve over time.
These details have not been finalized.
When Enterprise Architect 13 is officially released, a detailed break down will appear on the Compare Editions Page.
Yes. You can create and retrieve requirements from a Cloud repository. Please refer to the Help Guide to learn how to set up OSLC Requirements Management.
You may also care to review the webinar on Cloud Services to better understand how OSLC works in Enterprise Architect.
http://www.sparxsystems.com/resources/webinar/model-repository/cloud/introduction/introduction-cloud-services.html
Yes. Enterprise Architect has a purpose built User Story element that can be used to create a story. It is possible to link the User Story element to any number of other elements including business Goals, Objectives high level stakeholder requirements and detailed requirements resulting from grooming the story, constraints and more. To learn more, view the following webinar on Model Driven Use Case Analysis with Structured Scenarios:
For additional information on User Stories, please refer to the following Help Topic:
http://sparxsystems.com/enterprise_architect_user_guide/13.0/business_analysis_tools/tools_ba_user_story.html
There are many options for creating new requirements. The webinar illustrated how to create a new Requirement using the Specification Mangager. Another common method is to drag a Requirement Element from the Toolbox onto a Diagram or into a selected Package.
For more information on creating a requirement, see the Help topic:
http://sparxsystems.com/enterprise_architect_user_guide/13.0/model_domains/creatingrequirements.html
You might use Phase to represent the phase of the project, whereas Version captures the version of the requirement itself. Sparx Systems does not dictate a methodology, and many companies may vary their usage to suit their individual needs. Some companies may even use the Glossary to further define terms such as Version and Phase.
Yes. You can create your own Tagged Values to represent more than one Status.
For more information on creating a custom Status value, please refer to the Help Topic on
Status Types.
Yes. This can be achieved using Tagged Values.
Yes. You can trace changes using a combination of Baselines, Auditing and Time Aware Models.
Auditing is a project-level feature that model administrators can use to record model changes in Enterprise Architect. To learn more about how auditing can trace a change of requirement state, refer to the Help Guide on:
Auditing.
Enterprise Architect has a comprehensive and powerful built in Compare (diff) utility, which enables you to explore what has changed within a model over time.Enterprise Architect provides a facility to 'Baseline' (snapshot) a model branch at a particular point in time for later comparison with the current Package state. Baselines can be used in conjunction with Time Aware modeling to see how the state of Requirement changes over time, clearly identifying any changes that occur to that State. For more information, refer to the Help Topic on:
Baselines.
Yes, Enterprise Architect can Trace from a Use Case to a non Functional Requirement. Traceability helps to identify the way a given requirement or process has been implemented in a system, enabling you to follow the path of dependencies from the initial request, through a modeled solution and up to the deployed physical system or process. For more information, please refer to the webinar on
Traceability.
The Requirements Checklist is a convenient element that acts as a tally to indicate whether a Requirement complies with a set of predefined measures. The Checklist element can be assigned to any Requirement and the measures can be updated directly in the diagram.
For more information, refer to the Requirements Checklist section of Help Guide.
The Requirements Checklist element is available from the Requirements Toolbox. Simply drag the Requirements Checklist onto a diagram and draw a connector between the Checklist and the desired Requirement. The Checklist helps to ensure that a requirement follows a set of best practice guidelines.
Where to find the requirements Checklist Elements:
Toolbox | More Tools... | Requirements | Extended Requirements Page | Requirements Checklist
No. It was available in a previous version of Enterprise Architect.
Yes. It is possible to customize a Requirements Checklist. You can add additonal list items with ease. The Checklist details are stored in a Tagged Value field of type Memo called: "Checklist". You can modify this XML statement to list many other other options or alter the existing set of options.
For more information, please refer to the Help Topic on the
Requirements Checklist.
The values of the Requirements Checklist are available via the Memo tag. You can use the Enterprise Architect Object Model to make changes to the Tagged Value Class.
For more information, please refer to the Help Guide on:
The TaggedValue Class in relation to Automation.
Yes.
In addition to a requirements Checklist, there is also a generic checklist that can be associated with any model element.
Yes. You can edit and review SysML requirements using the Specification Manager.
To learn more about the Specification Manager, please refer to the following page:
http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/specification_usage.html
The SysML Requirement type include the Tagged Values: ID and Text. You can use these, however they are displayed in the Tagged Value window.
An alternative option is to use the Element.Alias (ID) Element.Notes (text). These Alias and Notes and Tagged Values can be displayed in the diagram by selecting Diagram Properties (F5) | Element tab.
The Alias is set in F5 | Diagram > [x] use Element Alias.
A point to consider is that Auto numbering supports the Element Alias, however it is not supported for a SysML ID Tagged Value.
Registered users can download the Enterprise Architect installer directly from:
http://www.sparxsystems.com/securedownloads/EA130_Reg.msi
To learn more about Enterprise Architect 13 visit the release page:
www.sparxsystems.com/ea13
Yes. When installing a newer version of Enterprise Architect, any existing Enterprise Architect installation will automatically be uninstalled. As a workaround to run multiple parallel versions of EA on your system, copy the directory where EA is currently installed before upgrading.
Ensure that you create a copy of the existing EA directory before installing Enterprise Architect 13. On Windows, it is typically found at:
C:\Program Files (x86)\Sparx Systems\EA
Running the EA.exe from this copied directory will allow you to continue using your previous version of Enterprise Architect while having Enterprise Architect 13 as your 'primary' installation.
Read our Version Control whitepaper to learn best practice information in relation to version control in Enterprise Architect. For additional information, you may also refer to the Help Topic on using
Version Control.
Diagram Filters are available to all users of a model.
Yes. Diagram Filters can be applied to any type of diagram within Enterprise Architect.
Diagram Filters can be applied to all diagrams.
