You want to design a requirements document to suit people who will work with the document in further phases of the development process. Sort the following sentences into CORRECT and INCORRECT combinations of role and requirements characteristics.

A company (a customer) wants to have an information system to support its tender preparation process. The management hires your company to specify and develop or buy a system. You are the requirements engineer responsible for the project. During initial discussions with different representatives of the customer, you find: (1) partly you do not understand the customer's terminology, (2) the representatives do not use a consistent terminology, and (3) the main contact person (at the customer) described his ideas by telling you the expected interactions between specialists and information system in form of different flows of user actions and system reactions. Which of the followings are particularly well suited to elicit and document the requirements in this case?

For the choice of notations for the documentation of functional requirements, stakeholders should be able to read the notation used.

For the choice of notations for the documentation of functional requirements, the UML diagrams have to be applied in projects with object-oriented development.

Different notations should be used depending on the kind of requirement to ensure optimal understandability.

A graphical notation like the UML should be highly preferred as it is easier to understand.

Requirements documentation has a goal-oriented and supporting role. Which of the followings is NOT a reason for documenting requirements?

Functional requirements can be classified into perspectives. Which of the followings is one of the perspectives of functional requirements?

Requirements of the behavioral perspective describe the reaction of the system to events in the system context.

The data perspective describes data flows in and out of the system.

Requirements of the functional perspective define the data manipulations by the system.

The behavioral perspective describes the execution of functions processing input and output data.

The ISO/IEC/IEEE 29148:2011 standard defines a reference structure for requirements documents. Which of the following is NOT the advantage of using a reference structure?

Requirements documents serve as the basis for many activities during the project life cycle. Which one of the following tasks is NOT based on the requirements documents?

The requirements engineer needs to check that a single requirement fulfills the following quality criteria EXCEPT

Which of the following entities are NOT contained in a glossary?

A glossary can help to minimize conflicts due to different understandings of terminology.

Responsibility for maintaining the glossary can be shared between requirements engineers and stakeholders.

The glossary should be managed centrally.

Everyone in the project must use the glossary.

Stakeholders are not required to agree on all the terms in the glossary.

Compiling the glossary should follow after the elicitation of the functional requirements.