Chp 3 - Requirements Engineering Process

Question 2

What generic activities are common to all RE processes?

Answer 2

1. Requirements Elicitation
2. Requirements Documentation
3. Requirements Validation & Negotiation,
4. Requiremens Management

Question 3

What is Requirements Engineering Process?

Answer 3

1. The process used for RE vary widely depending on the domain, environment, process and organization

Question 4

Name the five RE process steps shown in the generic model.

Answer 4

1. Feasibility study
2. Requirements Elicitation;
3. Requirements Documentation
4. Requirements Validation & Ngotiation 5. Requirements Management

Question 5

What is a feasibility study?

Answer 5

Assessment of a project’s practicality

Reveal whether a project/plan is feasible

Question 6

List the four types of feasibility study.

Answer 6

1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Schedule Feasibility

Question 7

List out 6 Questions for people will ask in Feasibility Study

Answer 7

1. What if the system wasn’t implemented?
2. What are current process problems
3. How will the proposed system help
4. What will be the integration problems
5. Is new technology needed? What skills
6. What facilities must be supported by the proposed system?

Question 8

What is requirements elicitation?

Answer 8

Working with customers to find out services that system should provide and system operational constraints

Question 9

Who are Requirements Elicitation stakeholders? ( 3 )

Answer 9

1. End‑users
2. Managers
3. Maintenance Engineers
4. Domain Experts

Question 10

Name the four requirements elicitation activities.

Answer 10

1. Requirements Discovery
2. Requirements Classification & Organisation
3. Requirements Prioritisation & Negotiation
4. Requirements Specification

Question 11

What does Requirements Discovery do?

Answer 11

1. Interact with stakeholders to discover requirements

Question 12

What does Requirements Classification & Organization do?

Answer 12

1. Group related requiremetns and organises them into coherent clusters

Question 13

What does Requirements Prioritisation and Negotiation do?

Answer 13

1. Prioritising Requirements and Resolving Requirements Conflicts

Question 14

What does Requirements Specification do?

Answer 14

1. Requirements are documented and input into the next round of the spiral

Question 15

List out 5 problems during Requirements Elicitation

Answer 15

1. Stakeholders don’t know what they really want.
2. Stakeholders express requirements in their own terms.
3. Different stakeholders may have conflicting requirements.
4. Organisational and political factors may influence the system requirements.
5. The requirements change during the analysis process. New stakeholders may emerge and the business environment
   change.

Question 16

What are four RE discovery techniques?

Answer 16

1. Interview
2. Scenarios
3. Use Cases
4. Ethnography

Question 17

How are requirements discovered?

Answer 17

1. Meet with stakeholders
2. Identify their roles

Question 18

What questions that Interview asked?

Answer 18

Questions to stakeholders about the system that they use and the system to be developed

Question 19

List out 2 types of Interview

Answer 19

1. Structured Interview
2. Unstructured Interview

Question 20

What is a structured interview?

Answer 20

A pre‑defined set of questions answered by stakeholders

Question 21

What is an unstructured interview?

Answer 21

No pre‑defined agenda; explores a range of stakeholder issues

Question 22

What are scenarios?

Answer 22

1. Real-life examples of how a system can be used

Question 23

What does scenario include? ( 5 )

Answer 23

1. A description of the starting situation
2. A description of the normal flow of events
3. A description of what can go wrong
4. Information about other concurrent activities
5. A description of the state when the scenario finishes.

Question 24

What is a Use Cases?

Answer 24

Scenarios identifying actors and their system interactions

Question 25

Which diagram adds detail to use cases?

Answer 25

Activity diagram showing event‑processing activities

Question 26

What is ethnography in RE?

Answer 26

Observational techniques which lets analyst immersion in work environment to discover implicit system requirements

Question 27

What does Ethnography helps discover?

Answer 27

1. Implicit System Requirements

Question 28

List out 2 types of Requirements that Ethnography is effective for discover

Answer 28

1. Derived from the way which people actually work 2. Derived from cooperation and awareness of other people's activities

Question 29

What is requirements validation?

Answer 29

1. Checking that requirements actually define what the customer really wants ## Footnote Overlap with requirements analysis as it is concerned with finding problems with the requirements

Question 30

Why fix requirements early?

Answer 30

To avoid costly rework of design and code

Question 31

What cost is greather than repairing design and coding errors?

Answer 31

1. Cost of fixing requirements

Question 32

What does the change to the requirements means that?

Answer 32

1. System Design and Implementation must be change 2. System must be retested

Question 33

What does validity checks ensure?

Answer 33

Ensure requirements fulfil stakeholder needs

Question 34

What does consistency checks ensure?

Answer 34

Ensure requirements do not conflict with each other

Question 35

What does completeness checks ensure?

Answer 35

Ensure all functions and constraints are defined

Question 36

What does realism checks ensure?

Answer 36

Ensure requirements can be implemented with current technology

Question 37

What does verifiability checks ensure?

Answer 37

Ensure requirements are testable via written test sets

Question 38

Name three requirements validation techniques.

Answer 38

1. Reviews 2. Prototyping 3. Test‑case generation

Question 39

What is requirements management?

Answer 39

Managing requirement changes during elicitation and system development

Question 40

List out 3 reasons why Requirements Management is inevitable

Answer 40

1. The business and technical environment of the system changes after installation 2. The people who pay for the system and the users of the system are rarely the same people. 3. Large system usually have a diverse user community, with many users having different requirements.

Question 41

What is requirement identification?

Answer 41

Assigning unique IDs to each requirement for traceability

Question 42

What are traceability policies for Requirements Management Planning?

Answer 42

Define relationships among requirements and design elements

Question 43

What is tools support in Requirements Management Planning?

Answer 43

Use of specialist tools, spreadsheets or databases for RE data ## Footnote Requirement Management involves the processing of large amounts of information

Question 44

What is the change management process?

Answer 44

Activities that impacts and costs of requirement changes

Question 45

What is problem analysis & change specification?

Answer 45

Identify requirement problems or specify required changes

Question 46

What is change analysis & costing?

Answer 46

Assess the effect and cost of proposed changes

Question 47

What is change implementation?

Answer 47

Modify requirements document, design, and code per approved changes

Question 48

What are enduring requirements?

Answer 48

Stable requirements from core stakeholder activities

Question 49

What are volatile requirements?

Answer 49

,Requirements that change during development or use

Question 50

Define mutable requirements.

Answer 50

Requirements changing due to environmental shifts

Question 51

Define emergent requirements.

Answer 51

Requirements emerging as customer understanding develops

Question 52

Define consequential requirements.

Answer 52

Requirements resulting from introducing the computer system

Question 53

Define compatibility requirements.

Answer 53

Requirements depending on existing systems or business processes