Prev Next

Requirement Models

Requirement Engineering is one of the most important disciplines in the system lifecycle and has a documented impact on the success of projects. Enterprise Architect is a sophisticated and intuitive platform for developing and managing Requirements gleaned from modeling stakeholders and visions, and regardless of the domain, the size of the project or the method being followed, Enterprise Architect provides tools that make it easy to manage the largest of Requirement repositories in complex projects.

Analysts can work together via a collaborative platform with role based Security, Discussions, the Library window, Model Mail and a range of other tools to encourage best practice and productivity.

Requirement Development

Requirement Development consists of all the activities and tasks associated with discovering, evaluating, recording, documenting and validating the Requirements for a particular project. Requirements are discovered, analyzed, specified and verified. Enterprise Architect has a wide range of tools and features to assist the Analyst as they develop Requirements. The centerpiece for Requirement Development is the Specification Manager, through which the Requirement Analyst can enter, view and manage Requirements in textual form as if in a spreadsheet. Requirement properties such as Status, Priority and Author can be edited in-line, and filters can be applied to restrict the display to particular requirements.

Defining requirements using the Specification Manager in Sparx Systems Enterprise Architect.

The Specification Manager can be used in conjunction with a platform of other tools such as diagrams, the Traceability window and the Element Discussions facility.

An example in Enterprise Architect of requirements grouped into hierarchies for decomposing a high level requirement.

Requirement Management

Requirement Management comprises the activities to maintain a set of Requirements that represent an accord or agreement between the project team and the customer. It also has a focus on ensuring that the Requirements are acceptable to the design and development teams, and that they are sufficiently specific to be implemented into working business, software or hardware systems.

Status chart - a Requirements Management Tool used in Sparx Systems Enterprise Architect.

Requirement Documentation

A number of documents are commonly produced as part of the Requirement engineering discipline such as the Software (System) Requirements Specification and Use Case Reports and these can be generated automatically from a Requirement Model using built-in templates. In addition a wide range of other documents can be produced using built-in or customized templates.

Outputting a requirements document to a PDF file in Sparx Systems Enterprise Architect.

Requirement Processes and Standards

Enterprise Architect is an open platform that supports any Requirement engineering process. The tool has a rich feature set and is highly configurable, and its flexible design means that whatever method is being used you will find features to help. So whether the team is using Formal Requirements, Use Cases, User Stories or Story-Boards in any combination, Enterprise Architect can be used to develop, manage and document the Requirements. The implementation of the UML extension mechanisms means that any type of Requirement can be created and managed using built-in types or by using stereotyped elements and Tagged Values.

A User Story as a stereotyped Use Case modeled in Sparx Systems Enterprise Architect