Please enable JavaScript.
Coggle requires JavaScript to display documents.
SOFTWARE ENGINEERING (requirement validaion) (principles of requirements…
SOFTWARE ENGINEERING
(requirement validaion)
risk of non-validated requirements
conflicts not resolved
late error detection at during acceptance
client stop trusting supplier
schedule n budget overrun
subsequent error in planning,architecture,design,test,implementation
quality aspects of requirements
(aspects must be validated)
content
goal - Avoid development based on false information, that is the development of something that is not needed
search for shortcomings
completeness
consistency
correctness
traceability
verifiability
necessity
agreement
goal - Avoid some stakeholders disagree with documented requirements
search for shortcomings
agreed
agreed after changes
conflicts resolved
documentation
goal - Avoid information gaps or the violation of agreed documentation guidelines
search for shortcomings
conformity
understandability
unambiguity
principles of requirements validation
1.involvement of the correct stakeholders
indpndnt of auditors
involve external one when internal lack expertise
2.separating d identification and the correction of errors
focus on error identification increases detection rate
avoidance error correction decreases unproductive actvty
3.validation from diff views
client,developers,auditor views
4.adequate change of documentation type
play out strength,compensate weakness
transcribe from one into another frm helps identifying error
5.construction of dev artifacts
simultaneous activities of developers n testers
6.repeated validation
revadilate constantly in heavily changing environment
validation of requirement
reviewing doc
early in dev stage using prototypes
during dev stage using periodical s/w increments
typical defects found during requirements check; corrective actions
incorrect requirements
contradictory requirements
unrealistic requirements
superfluous requirements
typical defects found during requirement doc validation
table has empty cells
language defects exist
few or none q requirments
requirement validation teknik
statik teknik
reviews
teknik
ispection
walkthrough
audit/commenting
informal review
validation can b performed by anyone y fhm content/needs to process it
principle
4eyes see more than 2(lgi2 if dia org x involve in producing d checked item)
early error detection(smntra blh removed at low cost)
matching of diff notation
dynamic teknik
prototypes
simulation