Creating your first requirements

Creating your first requirement containers

After creating a project for your Scope Manager project and deploying the ScopeManager and ScopeAdmin MDACs, you are now ready to create your first Scope elements.

In our example, we are going to start by creating some requirement containers and requirements. However, it should be noted that the procedures for creating goal containers and goals, or business rule containers and business rules, are almost identical to those used to create requirement containers and requirements. All you have to do is click on the correct icon.

To create the requirement containers that will structure your future requirements, carry out the steps shown in the screenshot below.

Creating your first requirement container

Steps:

1. In the tab of the explorer, click on the root requirement container.

2. Click on the "Create a requirement container" icon.

3. Enter a name for your new requirement container (in our example, "User requirements").

Continue by creating the "Elevator system requirements" requirement container.

Note: To create a goal container or a business container, the procedure is exactly the same, simply click on the icon to create a goal container and the icon to create a business rule container.

Defining your new requirement containers

Requirement containers can be further defined by adding descriptions and associating property sets. Both these operations are carried out in the dedicated "Requirement container edition" window shown below.

Defining your first requirement container

Steps:

1. In the tab of the explorer, click on the newly-created "User requirements" requirement container. The "Requirement container edition" window then appears.

2. In this window, click on the arrow on the right-hand side of the "Type" field to display the list of available property sets, and select the property set you wish to implement. The property sets which appear in this list are those provided by default, along with any other property sets you may have defined.

3. In the "Description" field, enter a description for the requirement container (in our example, "This requirement container groups together all the requirements of the user in the context of the elevator system Scope Manager project").

4. If you wish to enter specific values for the properties automatically associated with your new requirement container, these can be directly entered in the right-hand zone of the window.

5. Click on "OK" to confirm.

Continue by defining the "Elevator system requirements" requirement container with the "Functionality" property set and the following description:

· "This requirement container groups together all the requirements of the elevator system itself in the context of the elevator system Scope Manager project".

Note 1: According to the property set selected, the default properties and their associated values displayed on the right-hand side of the window vary. All future requirements created within a requirement container for which a property set has been implemented will then use these properties. For more information on properties and property sets, please see "Introducing requirement properties".

Note 2: To define properties for a goal container or a business rule container, the procedure is exactly the same – simply double-click on the goal container or business rule container to open the dedicated edition window and proceed in the same way.

Opening a Scope editor

To open a new Scope editor on a container element (requirement container, goal container or business rule container), simply carry out the following steps:

1. In the tab of the explorer, right-click on the container element for which you want to open a Scope editor.

2. Run the "MDA Components/Scope Manager/Open a Scope editor" command. The new editor then opens in the work view window.

Creating your first requirements

Requirements, which are created inside requirement containers, can be created either in the tab of the explorer through the "Create a requirement" icon, or directly in the Scope editor through the "New requirement" command.

Creating your first requirement

Steps:

1. In the tab of the explorer, select the "User requirements" requirement container.

2. Click on the "Create a requirement" icon.

3. Enter a name for your new requirement (in our example, "Change floor").

A new requirement can also be created through the "New requirement" command, available by right-clicking in the Scope editor.

Continue by creating the following requirements:

· In the "User requirements" requirement container, the "Be informed" and "Give orders" requirements.

· In the "Elevator system requirements" requirement container, the "Transport user", "Inform user" and "Manage problems" requirements.

Note: The procedure for creating new goals inside a goal container or new business rules inside a business rule container is very similar. Simply select the container element of your choice and either click on the relevant icon in the explorer, or else use the "New goal" or "New business rule" commands in the dedicated Scope editor.

Defining your new requirements

Requirements can be further defined by adding descriptions, which will be used when generating Scope Manager documentation. These descriptions are added in the dedicated "Requirement edition" window below.

Defining your first requirement

Steps:

1. In the tab of the explorer, click on the newly-created "Change floor" requirement. The "Requirement edition" window then appears.

2. In the "Description" field, enter a description for the requirement (in our example, "The user must be able to go up or down to another floor").

3. If you wish to enter specific values for the properties automatically associated with your new requirement, these can be directly entered in the right-hand zone of the window (values can also be assigned to properties in the editors).

4. Click on "OK" to confirm.

Descriptions can also be added to requirements by directly clicking on the "Description" field in the Scope editor and entering the description.

Continue by entering the following descriptions for the requirements you have just created:

o "Be informed": The user must be able to find out information on the current state of the elevator system.

o "Give orders": The user must be able to give orders to the elevator system.

o "Transport user": The elevator system must be able to take the user to the floor of his choice.

o "Inform user": The elevator system must be able to communicate certain information to the user.

o "Manage problems": The elevator system must be able to handle potential problems (for example, excess weight in the cabin or a power cut to the system).

Note: To define properties for a goal or a business rule, the procedure is exactly the same – simply double-click on the goal or business rule to open the dedicated edition window and proceed in the same way.