Requirement Quiz 1 CAB1483

Which of the following statements describes work that is not part of the (core) work of a software engineer?

• To understand the problem domain of a software system to-be-developed

• To define/evolve the architecture of a software system

• To design and develop program cod

• To invent a new programming language

Why is requirements elicitation difficult?

• Because there doesn’t exist a suitable UML notation for requirements elicitation

• Because it is difficult to identify the relevant stakeholders, and, once identified, the stakeholders have difficulties describing what they want/need

• Because requirements can change over time

• Because stakeholders don’t understand use cases

Which of the following statements about project stakeholders is NOT true?

• Different stakeholders may have different expectations regarding the planned solution and the Business Analyst should find a common understanding of the purpose of a solution.

• Identification of all the stakeholders is important, as each of them can provide own needs and limitations related to a planned solution

• Identification of all the stakeholders is important, as it determines the initial scope and requirements of the system.

• Stakeholders who are not owners or operators of business processes being a part of the final solution should have assigned lower priority as their requirements are less important

Which of the following statements correctly explains reasons for organizing requirements?

• Organizing requirements helps to define the structure of requirements and the scope boundaries

• Organizing requirements supports quality assurance as it make the requirements model more clear and complete.

• Organizing requirements is necessary to ensure that all requirements have been collected.

• Organizing requirements supports project planning and allows maintaining traceability.

You are focusing your elicitation activities on gathering transition requirements. Which technique may provide the best opportunity for this activity?

• Prototype

• Focus Group

• Interface Analysis

• Observation

Requirements are defined

• From a high-to-low level detail

• To the lowest possible level of detail

• To the level dictated by the sponsor

• To whatever detail is needed to achieve action and understanding

An input represents which of the following

• Feedback from a structured walkthrough

• A component of a business rule

• Information and precondition necessary for a task to begin

• Managerial assessment of BA performance

In customer driven projects, requirements

• Are sketchy and informal

• Are structured following a particular approach

• Have specification that comes in a customer presentation

• Rely on consultant for advice on features

The framework describing requirement engineering consists of

• The concern of understanding the problem

• The concern of formally describing a problem

• The concern of attaining an agreement on the nature of the problem

• All of the above

Which of the following is not included in the Software Requirement Specification (SRS)

• Functional requirements

• Non-functional requirements

• Goals of implementation

• User manual