Scribd
Upload
66 views5 pages

DFP40182 Lab Activity 2 SRD

Uploaded by

Izzul Muazzam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
66 views5 pages

DFP40182 Lab Activity 2 SRD

Uploaded by

Izzul Muazzam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

DFP40182 : SOFTWARE REQUIREMENT & DESIGN

LAB ACTIVITY 2:
Requirement Elicitation & Analysis
Duration: 2 hours

Activity 2A:

Based on your reading of the article provided, please


answer the following questions:

1. Give the definition about Requirement Elicitation and


Analysis.
Activity discovering requirement

2. Who are stakeholders when you are doing elicitation?

Stakeholders are the people from whom we first elicit


requirements, and then from whom we obtain the input
necessary during requirements analysis and negotiation, and
then who will finally accept the system into service.

CHAPTER 2: REQUIREMENT ENGINEERING Page 1


DFP40182 : SOFTWARE REQUIREMENT & DESIGN

3. State 4 main process of requirements elicitation and


analysis.
1. Requirements discovery

2. Requirement specification

3. Requirement prioritization and negotiation

4. Requirement classification and organization

4. From the description below, state one of the main processes


in Requirements Elicitation & Analysis

“It’s the process of interacting with, and gathering the


requirements from, the stakeholders about the required
system and the existing system (if exist).It can be done
using some techniques, like interviews, scenarios,
prototypes, etc, which help the stockholders to understand
what the system will be like. ”

-Requirement discovery

5. State THREE reasons why gathering and understanding the


requirements is a difficult process?

That’s because stakeholders may not know what exactly they want the software to do, or they

may give unrealistic requirements. They may give different requirements, which will result in

conflict between the requirements, so we have to discover and resolve these conflicts. Also,

there might be some factors that influence the stakeholder’s decision, like, for example,

managers at a company or professors at the university want to take full control over the

management system.

CHAPTER 2: REQUIREMENT ENGINEERING Page 2


DFP40182 : SOFTWARE REQUIREMENT & DESIGN

6. Name each of the symbols below:

User Lending Service

7. There are few techniques can be used to gather the


requirements. State these techniques:

 Interview users
 Study analogous systems
 Examine suggestions and problem reports
 Study improvements made by users
 Conduct a brainstorming session
 Work in the target environment
 Talk to support teams
 Look for unintended uses
 Demonstrate prototypes to stakeholders

CHAPTER 2: REQUIREMENT ENGINEERING Page 3


DFP40182 : SOFTWARE REQUIREMENT & DESIGN

8. Explain what did you understand about the Requirement


Classification & Organization.
The goal of this activity is to organize the various components of a system into their
corresponding requirements. This will help us identify the most appropriate architectural design pattern.

9. Describe your understanding about Requirement


Prioritization & Negotiation.
This activity is focused on finding and resolving conflict through negotiation. It helps you
prioritize the requirements and negotiate with the various stakeholder groups to reach a solution that is
beneficial for everyone.

CHAPTER 2: REQUIREMENT ENGINEERING Page 4


DFP40182 : SOFTWARE REQUIREMENT & DESIGN

How Requirement Prioritization


Step 1 - Understand the purpose and strategy for prioritization

Step 2 - List the customer needs

Step 3 - List the requirement

Step 4 - Facilitate the rating of the need

Step 5 - Determine technical

CHAPTER 2: REQUIREMENT ENGINEERING Page 5

You might also like