Prev Next

Introduction to Requirement Modeling

Requirement engineering is one of the most important disciplines in the system lifecycle and, when done well, it will set the foundation for a successful project or program of work, ultimately ensuring that great value is delivered to the users and other stakeholders. Enterprise Architect is a sophisticated and intuitive platform for developing and managing Requirements gleaned from modeling stakeholders and visions, business cases, business drivers and capabilities to detailed Functional and Non-functional Requirements. Requirements can be prioritized, traced and tracked, and changes can be recorded, baselined, versioned and audited. 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, either directly on the local system or though Pro Cloud Services.

How it Will Help You

You will typically come to the topic of Requirement Engineering with some existing knowledge or experience, even if it is something that has been learnt in lectures or by on the job training, or perhaps by using a different tool. You will benefit by understanding the product features and the tools that are available to develop and manage Requirements in Enterprise Architect, and this will enable you to be more productive both when working alone and as a member of a team.

Who Will Benefit?

Anyone involved in the development or management of Requirements, whether at a strategic level, a business value level or a system development level, will benefit from reading this information. This includes a wide range of roles including Strategic Thinkers, Business and Requirements Analysts, Enterprise, Business, Technical and Solution Architects, Project and Program Managers, Developers, Test Designers and User Experience Designers.

What You Will Learn

This topic will teach you how to use the powerful features of Enterprise Architect to develop and manage Requirements, to create documentation and to work collaboratively as a member of a team using a formal or informal system life cycle process or standard.

Overview of the Documentation

Subject area


See also

Meet the Requirement Tools

Lists the key tools that are used for developing and managing Requirements, including a picture of each tool in action, where to find the tool, how to use it and how to become proficient in using the tool. There are a large number of additional useful tools that are described in the last topic, Additional Requirement Tools.

Meet the Requirement Tools

Requirement Overview

Puts Requirement Engineering in context by defining what Requirements are, the different levels of Requirement, characteristics of good Requirements and the business context of Requirements. The information also includes the concept of a Requirement diagram that readers coming from text based tools might not be familiar with, and how to create and view requirements in Enterprise Architect.

Requirements Overview

Requirement Development

Discusses the activities and tasks associated with discovering, evaluating, recording, documenting and validating the Requirements. The topic is conveniently divided into four sub-topics - Elicitation, Analysis, Specification and Validation - and identifies a wide range of features that can be used, from Mind Mapping diagrams for recording information in elicitation workshops, to the Specification Manager for creating Requirements, to Test Cases for validating them.

Requirements Development

Requirement Management

Describes the activities needed to maintain a set of Requirements that represent an accord or agreement between the project team and the customer. It includes composing hierarchies of Requirements, tracing other elements back to Requirements, and tracking the properties of Requirements including Status, Priority, and Difficulty. It also describes managing changing Requirements, Volatility and assessing the impact of changing Requirements.

Requirements Management

Requirement Documentation

Describes how formal and informal Requirement Documentation can be generated directly from Enterprise Architect using a series of predefined and extensible templates. This includes Glossaries, Data Dictionaries, Use Case Reports and Documents such as a System Requirements Specification.

Requirements Documentation

Requirement Processes and Standards

Puts the usage of Enterprise Architect's Requirement tools in the context of System and Requirement processes and standards. The topic describes how flexible the tools are and how they can be used with any process or standard.

Requirement Processes and Standards

Additional Requirement Tools

Lists a series of additional tools that can be used for Requirement Engineering, including a picture of each tool in action, where to find the tool, how to use it and how to become proficient in using the tool. There are a number of key tools that are the most important tools for Requirement Engineering that are described in the first topic, entitled Meet the Requirement Tools.

Additional Requirement Tools