Skip to end of metadata
Go to start of metadata

Requirements management is one of the main tasks in system engineering process. Requirements could come from the system environment. That's why the first step is to define the system environment and the requirements coming from it. A system could be connected to several kinds of other external systems.

Those external systems could have an impact on our system, or could exchange inputs/outputs with it. They are consequently divided in two categories: stakeholders and enabling systems.

To define this environment, we will consider our system as a "black box", defining enabling systems and stakeholders as well as requirements coming to the system from its environment.

Define systems, enabling systems and Stakeholders

To define the system, enabling systems and stakeholders, we work in the view "2.1. Define requirements".

Define System

We start creating our system. In our example, the system is the "Laptop".



Define Enabling Systems

Enabling system are external systems with functional links with our system. We will therefore create an enabling system in our example, which we will name "Mouse".


Define Stakeholders

Stakeholder is a person or a contributor of our system.

Resulting View

Creating those objects will allow you to have a view looking like :



Capture external requirements

Once we've defined the external perimeter of our system, we can now define requirements coming from the enabling systems and stakeholders.

Define stakeholders Requirements

The capture of stakeholder requirements is done in the same view:  "2.1. Define requirements".


  • Then give a name to this new requirement. Given name for our example will be "User needs a correct internet connection".

Define enabling system Requirements

The capture of requirements is done in the same view : "2.1. Define requirements".


  • Afterwards, name this new requirement. The name given for our example will be "The mouse has to be supplied by the Laptop".
  • No labels