---

1. Wait momentarily then browse the narrative on the right hand side to get the gist of the Function Requirement Definition.

2. Note the narrative immediately to the left. This is the 'vision' interpretition drawn up by the systems engineer and subsequently agreed by the stakeholders. It is written in a way that allows requirements to be globally understood, defined and tested.

3. Study the list of requirements to the left. Note the requirement types (Requirement, Target and Constraint).

4. Note the first 4 requirements are checked (verified) and submit the form.

5. This model uses approximately 120 unique dataflows, classified by subsystem, to seamlessly capture IT process event metrics. Observe the 2 types of dataflows transmitted by 'Function Requirement Definition' before acknowledging the notification.

6. Click OK and repeat the above sequence for 'Performance Requirement Definition' and Resource Requirement Definition.