Scenario-based elements

Class-based elements
Generic elements Build analysis model
State Diagram Behavioral elements
DFD Flow-oriented elements
Requirements Analysis &
Prioritizing Requirements
Negotiation
Conflict and conflict resolution
Negotiating requirements
requirements risk

application domain
first which requirements problem to be solved
4 components of requirements
subsequent deliver business
elicitation
dropped processes
collaborate with the the needs and constraints
customers of the stakeholders
M - MUST have this. a statement of need and
Prioritizing feasibility
S - SHOULD have
Requirements statement of scope for the
this if at all possible.
E.g.: MoSCoW method to group requirements into system
C - COULD have this if
it does not affect (Coley Consulting, 2008) several priority categories Prioritization scale stakeholders who participated
anything else. in requirements elicitation
W - WON'T have this system’s technical environment
time but WOULD like Elicitation Work Products a list of requirements
Techniques
in the future and the domain
Requirements Elicitation constraints
QFD
estimated the benefit, Semi-quantitative Analytical scenarios that provide
penalty, cost and risk Approach into the use of the
system
prototypes developed

Why is it difficult to understand Problems of volatility

what the customer wants Christel and Kang (1992) Problems of scope
Problems of Understanding
Interviews
Traditional Surveys
Observations
Elicitation Techniques Iterative Prototyping
Joint Application Design (JAD)
Modern Rapid Application Development (RAD)
Quality Function Deployment
A process of discussing the conflicts in the (QFD)
requirements and finding resolutions to the RE Process (module 3) part
2
identified conflicts
based on technical and
organizational needs.
political
factors
personalities Negotiating
discussion sessions in meeting technique Requirements
Recognize that it’s not a competition
Map out a strategy
Listen actively
Focus on the other party’s interests Negotiating Guidelines
Don’t let it get personal
Be creative – think out of the box conflicts,
Be ready to commit and move on In any set of requirements overlaps
omissions.
Developer and stakeholders
discuss and resolve the
Conflict & Conflict
problems
Resoultion
different stakeholders different requirements
have
priorities.

interaction
Technique to counter matrix.
a probability that some
adverse circumstance will (Sommerville, 2007)
occur defined risk
Technical
performance Identify
safety and security Requirements Risk
probability
Analyze
effects
Mitigate