Scribd
Upload
86 views2 pages

Software Requirements-3

The document discusses different stages of requirements engineering: First, inception involves asking initial questions to understand stakeholders, goals, and benefits. Next, elicitation aims to gain a deeper problem understanding and allow customers to voice perceptions through collaborative gathering and quality function deployment. Then, elaboration expands and refines gathered information by developing use cases, classes, and diagrams. Finally, negotiation reconciles customer wants with feasibility by prioritizing, identifying risks, estimating efforts, and iteratively modifying requirements for mutual satisfaction.

Uploaded by

Kazi Dip
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
86 views2 pages

Software Requirements-3

The document discusses different stages of requirements engineering: First, inception involves asking initial questions to understand stakeholders, goals, and benefits. Next, elicitation aims to gain a deeper problem understanding and allow customers to voice perceptions through collaborative gathering and quality function deployment. Then, elaboration expands and refines gathered information by developing use cases, classes, and diagrams. Finally, negotiation reconciles customer wants with feasibility by prioritizing, identifying risks, estimating efforts, and iteratively modifying requirements for mutual satisfaction.

Uploaded by

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

In inception a set of questions is being asked:

First set of questions Next set of questions Final set of questions

These questions focus on the These questions enable the These questions focus on
customer, other stakeholders, requirements engineer to gain a the effectiveness of the
the overall goals, and the better understanding of the communication activity itself
benefits problem and allow the customer to
voice his or her perceptions about
a solution
• Who is behind the request for this • How would you characterize • Are you the right person to answer
work? "good" output that would be these questions? Are your answers
• Who will use the solution? generated by a successful solution? "official"?
• What will be the economic benefit • What problem(s) will this solution • Are my questions relevant to the
of a successful solution? address? problem that you have?
• Is there another source for the • Can you show me (or describe) the • Am I asking too many questions?
solution that you need? business environment in which the • Can anyone else provide additional
solution will be used? information?
• Will special performance issues or • Should I be asking you anything
constraints affect the way the else?
solution is approached?

Elicitation Task
● Eliciting requirements is difficult because of
○ Problems of scope in identifying the boundaries of the system or specifying too much
technical detail rather than overall system objectives
○ Problems of understanding what is wanted, what the problem domain is, and what
the computing environment can handle (Information that is believed to be "obvious"
is often omitted)
○ Problems of volatility because the requirements change over time

● Elicitation may be accomplished through two activities


○ Collaborative requirements gathering
○ Quality function deployment

Elaboration Task
● During elaboration, the software engineer takes the information obtained during inception
and elicitation and begins to expand and refine it
● Elaboration focuses on developing a refined technical model of software functions, features,
and constraints
● It is an analysis modeling task
○ Use cases are developed
○ Domain classes are identified along with their attributes and relationships
○ State machine diagrams are used to capture the life on an object
○ ERD, Data Flow Diagram, CFD are developed
● The end result is an analysis model that defines the functional, informational, and behavioral
domains of the problem

Negotiation Task
■ During negotiation, the software engineer reconciles the conflicts between what the
customer wants and what can be achieved given limited business resources
■ Requirements are ranked (i.e., prioritized) by the customers, users, and other stakeholders
■ Risks associated with each requirement are identified and analyzed
■ Rough guesses of development effort are made and used to assess the impact of each
requirement on project cost and delivery time
■ Using an iterative approach, requirements are eliminated, combined and/or modified so that
each party achieves some measure of satisfaction

Negotiation skills

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy