Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirement Documentation (serves a specific purpose, depending on their…
Requirement Documentation
(serves a specific purpose, depending on their purpose)
importance of documentation
1.common reference
2.Support training of new employees
3.preserve expert knowledge
4.persistence
What should be documented
1.Context Information
2.Additional Information
3.Requirement
Representation format
Textual
1.Natural language text
2.Structured Text
3.Templates
Model Based
1.Data Perspective
2.Behavior perspective
3.Functional Perspective
Combined
1.Conceptual with note
2.Text with models
Purpose of documentation
1.Elicitation
=Input for creativity workshop
2.Negotiation
=Supporting the comparison of conflicting viewpoint
3.Management
=Management report
4.Validation
=Input for verification activities
5.Non RE activities
=Support for the derivation of test cases
Typical type of requirement specification
1.Stakeholders requirement specification
2.System requirement specification
3.Software requirement specification
4.Lastenheft(definition of system vision
5.Pflichtenheft(detail of the vision and system goals)
Acceptance Criteria
(define verifiable and measurable condition for accepting a development artefact
Acceptance Criteria for requirement
Single requirement
1.Define the condition a single requirement must meet
2.Refine quality criteria for single requirement as well as documentation guideliness
Requirement Specification
1.define condition under which a requirement specification as a whole is accepted
2.Can include acceptance criteria
Acceptance criteria for implemented system
Realization of single function and qualities
1.define criteria the realization of a single functional
2.support the uncovering of potential defects in the requirement itself
realization of entire system
1.define the conditions under which the client will accept the system
2.may be based on acceptance criteria for single requirements.
AMBIGUITIES IN Natural Language REQUIREMENTS
is when the meaning of a word, phrase, or sentence is uncertain. There could be more than one meaning
Avoid ambiguities terms because
1.Will lead to confusion, wasted effort and rework
2.Unclear and not sharp
TECHNIQUES FOR AVOIDING AMBIGUITY
Glossaries
an alphabetical list of words relating to a specific subject, text, or dialect, with explanations; a brief dictionary.
Help to reduce following risk
1.Different stakeholders do not know the meaning of a term and interpret the term differently.
2.Avoid misunderstanding
3.Different interpretations exist but are not known
Content of glossaries
1.Synonym
2.Homonyms
3.Context-specific technical terms
4.Abbreviations and acronyms
5.Everyday concepts that have a special meaning in the given context
Syntactic requirement patterns
Requirement template for functional requirement
Procedure to use template
Determine legal obligation (shall, should, will)
Determine the core of the requirement (process verb) i.e. print
Characterize the activity of the system
Insert objects i.e. print what
Determine logical and temporal conditions