Question

The benefit of textual requirement over diagram is that a textual requirement can often be easier to understand, presenting clear views of the structure and relationships of functional requirements.
State True or False.

Answer 1

Answer:

The objective of this activity is to identify stakeholder requirements. Stakeholder requirements are fundamentally statements reflecting stakeholder needs. System requirements differ in that they specify what the system will do and how well it must do it. There is a need to demonstrate traceability between these sets of requirements but they differ both in context and in their degree of precision.

Generally speaking, stakeholders may be (although are not necessarily) domain experts but are not usually system engineering experts. Most stakeholders will be comfortable communicating requirements via text and few will be capable of using more formal languages, such as activity or state diagrams. The good news is that scenarios—captured in sequence diagrams—are easily taught to nontechnical stakeholders and serve as a valuable tool for capturing any requirements.

This chapter will discuss the identification of stakeholder needs, and capturing them as textual requirements and scenarios on sequence diagrams. Requirements will be clustered into coherent sets called use cases. A great deal of what we talk about here applies equally well to system requirements, the topic of the next chapter; however, for system requirements, we will also perform more rigorous analysis that goes well beyond the initial capture of stakeholder needs.