Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirement Documentation, :red_flag:1 - Coggle Diagram
Requirement Documentation
intro
what should be documented
Requirement
goal
scenario
Context Information
RE Context
Development context
Additional information
minutes of meeting
decisions taken
Format
textual
natural language
structured text
model-based
data perspective
behavior perspective
combined
conceptual models with annotations
text with models
Definition
a document in req engineering serves a specific purpose, differ in terms of content,format and quality
Reason
basis for system development
legal reference
keep overview
accessibility for team/stakeholder
purpose of doc
elicitation
creativity workshop
questionnaire for iv
negotiation
argumentations
supporting the comparison
management
minutes of meeting
management report
validation/verification
proof of safety features
scenarios for validation
non RE activities
input for successive system development acitivities
contractual document
Req doc VS req spec
req spec more strict doc of req and additional information
spec doc demands
content
format
quality
type of req spec doc
stakeholder requirement specification (StRS)
system requirement specification (SyRS)
Software requirement specification (SRS)
Lastenheft (client)
Pflichtenheft (contractor)
SRS structure
Introduction
References
Specific Requirement
Verification
Appendices
Acceptance Criteria
defines verifiable and measurable condition for accepting a developing artefact
implemented system will be verified against its specified requirements
types
acceptance criteria for requirement
acceptance criteria for the implemented system
single requirement
conditions a single requirement must meet in order to be accepted
refine quality criteria as well as documentation guideline
checklists for validation and verification
requirement specifications
requirement specification as a whole is accepted
refine quality criteria as well as general documentation guideline
Ambiguity
meaning
the quality/state of being ambiguous especially in meaning
uncertainty
reason
Underspecified requirement
missing details
vegueness
Defective specified requirement
use different words that sound alike
how to avoid
glossaries
collection of technical terms
define specific meaning
example that explain the terms
benefit
avoid different interpretation
avoid misunderstanding
syntactic requirement patterns
syntactic structure for documenting requirement in natural language an defines the meaning of keywords used in pattern
requirement template
a building plan for the syntactical structure of an individual requirement
procedure
determine legal obligation(shall,should,will)
determine the core of the requirement (process verb) ie print
characterize the activity of the system
insert objects ie print what
determine logical and temporal conditions
cause of error using natural language
nominalization (eg transmission, input, booking, acceptance, subject)
noun without reference index (eg the user,the message, the data)
universal quantifiers (eg each,every,never,always,each time,all,some,none)
incomplete specified conditions (eg if, in case, whether, depending on)
incompletely specified process verbs (passive voice, unclear who enter login data, where and how its done
:red_flag:1