Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
46 views

Lab 3

The document describes an experiment to identify various requirement development activities like elicitation, analysis, specification, validation and management for given scenarios. It explains that requirements must be clearly understood through proper elicitation and analysis, then specified and verified. The procedure is to study a tutorial on software requirements and identify which activities - like elicitation, analysis, specification or validation - are associated with each scenario like conducting a survey, preparing requirements documents, or making changes upon a client's request.

Uploaded by

Devanshi Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
46 views

Lab 3

The document describes an experiment to identify various requirement development activities like elicitation, analysis, specification, validation and management for given scenarios. It explains that requirements must be clearly understood through proper elicitation and analysis, then specified and verified. The procedure is to study a tutorial on software requirements and identify which activities - like elicitation, analysis, specification or validation - are associated with each scenario like conducting a survey, preparing requirements documents, or making changes upon a client's request.

Uploaded by

Devanshi Gupta
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

EXPERIMENT - 3

Aim:
To identify the various requirement development activities viz. elicitation, analysis, specification,
validation and management for the given scenarios.

Tools/Apparatus: None

Theory:
Requirement engineering produces a specification of what a system should do. The intention of
requirement engineering is to provide a clear definition of requirement of the systems. This phase is a
very important phase because, if the customer requirements are not clearly understood, the ambiguity
can get into the other phase of the development. To avoid such issues, requirement has to be elicited
using the right elicitation techniques, to be analyzed effectively, specified clearly and verified
thoroughly.

All activities are collectively termed as requirement development activities.

Procedure:
1) Study the tutorial paper “Software Requirements.pdf”.
2) Identify the requirement development activities associated with each of the
following scenarios.
a) Joe is creating an online survey questionnaire for requesting user feedback
on the desired features of the application to be developed.
b) Mark is preparing a formal document which includes all of the desired
features identified by the survey.
c) Jack identified an incomplete requirement statement.
d) Jones is identifying all security related requirement and separating them
from the performance related requirements.
e) Merlin a team member is sent to client to observe the business case and
collect typical user requirements.
f) Leo is team member is working on requirement and ensuring that
requirement collected should not be vague and unclear.
g) Lee is conducting a facilitated meeting with the stakeholder to capture the
requirements.
h) Amit a team member is distributing questionnaires to stack holder for
gathering user requirements.
i) Client requests a change in the current user interface to team leader.

Scenario Requirement Development Activities


a)
b)
c)
d)
e)
f)
g)
h)
i)

You might also like