Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAP 10 (REQUIREMENT MGT) (STAKEHOLDER INTEREST (MGT (vision and goals…
CHAP 10 (REQUIREMENT MGT)
ATTRIBUTE
structuring
ensuring consistency (dependencies)
identification
An ID is
a key attribute of a requirement.
a mean for referencing the requirement.
a mandatory attribute .
explicitly assigned.
uniquely assigned and never modified.
valid for the entire life cycle of the product.
progress and state control
SCHEME
Specific properties of the project
Constraint
Domain rules
Constraints of the development process
TYPICAL
Identifier
Name
Description
Source
Stability
Risk
Priority
ADDITIONAL
Version
Author
Legal obligation
Kano model type
Benefit
Loss
Effort
Risk
Status (regarding content, validation, agreement)
Requirement Type (functionality, quality, constraint)
Requirement kind (high level, detailed requriement)
Acceptance criteria
Release
TYPE OF VIEW ON RE
selected view (subset of att values,selected by diff criteria)
condensed view (condensed information,selected by diff criteria)
STAKEHOLDER INTEREST
MGT (vision and goals,progress report)
USER (functionality,fulfullment of needs)
QUALITY DEPARTMENT(define metrics,complete artifact)
LEGAL DEPARTMENT(norms,standards)
PROJECT MANAGER (effects,change wish)
6.CLIENT (progress report,acceptance criteria)
7.ARCHITECT(non functional re,structure of system architecture)
DEVELOPER(standards,guideline)
GENERATE VIEW
Establishing the necessary views
Definition of Reports
Determine the requirements attributes
Create the reports
Publish the reports
RE PRIORITIZATION (Classical prioritization with low, middle, high priority.
Prioritization using Kano model)
WATERFALL APPROACH (change management process after the requirements approval)
ITERATION APPROACH (allocation of requirements to releases according to vision)
METHODS
Determining prioritization criteria
Choosing the stakeholder for prioritizing
Determining the requirements to be prioritized
Establish prioritization techniques
Prioritizing
TECHNIQUE
1.Single-Criterion Classification, IEEE Std. 830-1998 (importance of realization)
Mandatory
Optional
Nice-to-have
2.Primarily used in procurement projects, for evaluation. KANO CLASSIFICTION
Dissatifiers
Satisfiers
Delighters
3.Used in projects with great innovation, for release planning.
4.RANKING(Everybody create the ranking order of the requirements)
5.Top-Ten Technique(Everybody has a poin )
MATRIX 1/1 @ 2/2
Traceability classification of relations
Pre-RS-Traceability
Post-RS-Traceability
Traceability between requirements
ADVANTAGE
Simplification of Verification
Identification of system gold plating
Identification of requirements gold plating
Progress monitoring
1/2
Change management
Maintenance
Reuse
Accountability
2/2
REPRESENTATION OF RE TRACEABILITY
Text based references
Hyperlinks
Trace matrices
Trace graph
CHANGE MGT
Changes compared to a baseline are triggered by change requests
Reasons for change request
Change of the user wishes
Legal changes
New technology
ELEMENT (Needed information from the applicant &
Management information)
Change frequency(high/low)
Classification of incoming change requests
Corrective requirement change
Adaptive requirement change
Exceptional change (hot fix)
Measurements for requirements
Quality of requirements documents and processes can be analyzed based on
Error founds
Attributes
Traces
Changes
Typical measurements include
1.Requirements change rates
2.Requirements errors