MODULE 1

Question 1

MODULE 1

Answer 1

Requirements Engineering

Question 2

Course Learning Outccome

Answer 2

Evaluate software requirements and
appraise the processes involved in
discovering and documenting these
requirements.

Question 3

TOPIC LEARNING OUTCOMES

Answer 3

1. Evaluate the concepts of user and system requirements and why these requirements should be written in different ways.
2. Value the differences between functional and nonfunctional software requirements.
3. Appraise the main requirements engineering activities of elicitation, analysis, and validation, and the
   relationships between these activities.
4. Weigh why requirements management is necessary and how it supports other requirements engineering activities.

Question 4

Topics covered

Answer 4

Functional and non-functional requirements
Requirements engineering processes
Requirements elicitation
Requirements specification
Requirements validation
Requirements change

Question 5

The process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed.

Answer 5

Requirements engineering

Question 6

the descriptions of the system services and constraints that are generated during the requirements engineering process.

Answer 6

System requirements

Question 7

It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.

Answer 7

requirement

This is inevitable as requirements may serve a dual function

May be the basis for a bid for a contract - therefore must be open to
interpretation;

May be the basis for the contract itself -
therefore must be defined in detail;

Both these statements may be called
requirements.

Question 8

“If a company wishes to let a contract for a large software development project, it must define its needs in a sufficiently abstract way that a solution is not pre-defined. The requirements must be written so that several contractors can bid for the contract, offering, perhaps, different ways of meeting the client organization’s needs. Once a contract has been awarded, the contractor must write a system definition for the client in more detail so that the client understands and can validate what the software will do. Both of these documents may be called the requirements document for the system.”

Answer 8

Requirements abstraction (Davis)

Question 9

Types of requirement

Answer 9

User requirements
System requirements

Question 10

Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers.

Answer 10

User requirements

Question 11

A structured document setting out detailed descriptions of the system’s functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.

Answer 11

System requirements

Question 12

User and system requirements

Answer 12

see page 10

Question 13

Readers of different types of requirements specification

Answer 13

see page 11

Question 14

Any person or organization who is affected by the system in some way and so who has a legitimate interest

Answer 14

System stakeholders

Question 15

Stakeholder types

Answer 15

End users
System managers
System owners
External stakeholders

Question 16

Stakeholders in the Mentcare system

Answer 16

• Patients whose information is recorded in the system.
• Doctors who are responsible for assessing and treating patients.
• Nurses who coordinate the consultations with doctors and administer some treatments.
• Medical receptionists who manage patients’ appointments.
• IT staff who are responsible for installing and maintaining the system.