Requirements

In this module, the requirements analysis is explained step-by step.

Add requirement

Requirements are either added here, or end up here after being added via the PDF Connector. All the Requirements that have the status 'Proposal' are displayed here and information can be added to them. After the status of the requirement is set to 'Final', it is moved to 'Step 1: Assign Responsibilities; .

Note: the basic configuration requires that a requirement has a type. If it does not have a type it will not be visible in Step 1. If this feature is not desired, it can be changed by one of our consultants.

Requirements Analysis

The requirements analysis consists of three steps. In the first step, responsible disciplines and persons are selected. And in the second step the objects and activities are assigned to the requirements or checked if they were already asigned. The third step focuses on the content. First the verification phase is selected, and finally the responsible person will indicate whether the requirements are clear or what else needs to happen to them.

Step 1: Assign Responsibilities

Step 1a: For Requirements Manager(s): Assign Discipline

This step is only visible fot the requirements manager. He has propose a discipline to each requirement. The proposed requirement will end up in step 1a: Accept assignment to Discipline. It is also possible to select requirements which are informational for a Discipline. The requirements that are selected to have an information discipline, will end up in a different table on the 'My Requirements' page. Selecting informational Disciplines is optional.

Step 1a: Accept assignment to Discipline

This step is visible for everyone. After selecting a discipline in a select box, a table shows in which the requirement can be accepted or rejected. If the requirement is rejected it is required to fill in a motivation for disapproval. The requirements manager can then review the rejected requirements and link them to another discipline. Here also informational Disciplines for the Requirements can be selected. See the explanation at Step 1a: For Requirements Manager(s): Assign Discipline.

Step 1b: Assign Responsibles

After again selecting a discipline, all the requirements for which the proposals were accepted are shown. Now the person(s) responsible is selected by selecting a function. A function describles the role that a person takes in the project. Here also informational Responsibles for the Requirements can be selected. It works the same as the informational Disciples. See the explanation at Step 1a: For Requirements Manager(s): Assign Discipline.

Summary: All accepted Requirements

This page gives a summary of all the accepted requirements.

Step 2: Assign to Objects and Activities

In Step 2 the connections between requirements (accepted by discipline and assigned to a person) and the Objects and Activities are maintained. A discipline or responsible function can be selected and after the 'Search' button is pressed, a table is shown.

For each requirement in the table, relationships with objects and/or activities can be created or deleted.

Step 3: Content Analysis

Step 3a: Relevance of Requirements

In Step 3a, the phase of verification of a certain requirement is selected. It is possible to select a discipline or a responsible function (not mandatory). After clicking on the 'Search' button, the table is shown.


At the top of the page (see the picture above) an instruction and a button are shown.

The instructions:

Select in the table below your discipline and function. Per requirement, two buttons are shown in the column that is the 3rd on the right: 'V' and 'X'. If a requirement is relevant for the current phase, select the button 'V'. The current phase is then filled in the second last column. If a requirement should not anymore marked as relevant for this phase, press the button 'X' to undo the selection. The checkboxes in the last column are not meant to be used!

Note: The current phase is set in the system and can be changed by our consultants if necessary.

The button that is highlighted in green below can be used to select multiple requirements at once and apply the current phase to them. After pressing the button, all the requirements that are shown in the table below (that do not have a phase yet) will be selected and receive the current phase as their verification phase.

Step 3b: Content Analysis

Here it is also possible to make a selection based on a discipline and/or function. Furthermore, there are several options to add change the status or add in information regarding the content:

  • New clarification (Toelichting). A clarification can be added that explains the requirement. This information can come from another party or can be internally agreed upon.

  • Unclear (X). If a requirement needs to be further explained, because it is unclear what is meant, this button has to be clicked.

  • To decompose (o). This button is clicked when the requirement is to general to be used and it needs to be made more specific.

  • Clear with assumption (>). If a requirement is specified, but it could be ambiguous, please select this option and give an assumtion.

  • Clear (>>). The requirement is clear without any doubt.

Summary: All clear Requirements which have a phase

This table summarizes exactly its title; all requirements which have a phase.

Step 3b: (Check): All unclear / to decompose Requirements

All 'unclear' and 'to decompose' Requirements are shown in this step. In each table 'Log info' is displayed that is automatically generated. Unclear requirements can be clarified by pressing the '<' button. To decompose requirements can get the status 'clear' after pressing the '<' button, but mostly these requirements will be split up in several more specific requirements.

Parent topic: Relatics