Documentation Flashcards
What is Requirements documentation?
- Specification of collections of requirments
Advantages with requirments documented?
- Requirments is elicated and can be hard for stakeholders to memorize
- Documentation is shaed to all participants in project
- Legal binding for costumer to agree on the devedlopment
- Improve communication, less subject interpreations
- Someone can take over the job if someone left
Diffrence with agile and plan-driven documentation?
Agil = less documentation, it keep going through project
plan-driven = Written and structured documents
What is documented?
- Info of stakeholders
- Summary of techniques
- Requirments of FQL
- reached agreements
- Goals of the system
- Priorities of requirments
what is specified requirments?
Lär dig!
When documented requirments that complies with specification rules defined by a RE appraoch.
When does the documentation phase starts?
With elication, and keep going with negotiation, validation and requirments mangement/change
What is documented and how?
- Artefacts
3 main types are :
1. Goal (DESIRED STATE) OF THE SYSTEM
2.Scenarios = EXAPMLES OF SYSTEM USAGE
3. Solution oriented requirments (system requirments) - FUNCUNALITY AND QULAITY FOR SOFTWARE SYSTEM
What is documented and how?
- System requirments
- Functional requirments: define servives/behaviour of the system
ex: if the computer gets hacked, the security departments should get a notis - Quality requirment : define wulaity of the system or function. ex : system should not fail more than 3 times/year
- Constraints: define organizational or technological limitations of how the system should be developed ex:
Organizational: The technichan is only allowed to restart the system due to policy A.
Technological: The system must be developed using lastest Java programming language
Qulality requirments (list)
GÖR!! LÄR 3 om dagen
- vad är quality requirments?
–
Quality Criteria for singel Requirement
3 om dagen - lära sig!
ACCUCCFT
- Complete: no missing information – the requirement must completely describe the
functionality (or quality, constraint) it specifies. - Traceable: the requirement’s origin, realization (evolution) and relation to other
requirements can be traced. - Correct: the requirement is confirmed as needed/necessary, by stakeholders.
- Unambiguous: the requirement has a single valid interpretation.
- Comprehensible: the requirement’s content is understandable to stakeholders.
- Consistent: statements within the requirement do not contradict/deny each other.
- Verifiable: the requirement can be tested or checked in the implemented system.
- Feasible: the requirement is possible to implement given the organizational, legal,
financial or technical constraints. - Up-to-date: the requirement describes the current/actual status of the system.
- Atomic: one requirement artefact describes a single, coherent fact.
Acceptance Criteria
What is that??
Rules for checking the correctness of a
development artefact, such as:
- a requirement artifact,
- requirements specification,
-prototype/system,
Requirements Attributes
1. WHY that?
2. examples
3. An attribute is define by:
- Because large amount of information is accumulated during the RE
process, the information needs to be well organized and structured.
An attribute is defined by type, value, and range of
(valid) values. Some common attribute types for a requirement are:
- Unique identification (for unique referral to a requirement)
- Type of requirements (functional, quality requirement, constraint)
- Source of the requirement (stakeholder(s), document, system…)
- Status (in writing, drafted, completed, agreed, etc)
- Unique identification (for unique referral to a requirement)
Languages for Requirements
3 diffrent languages
- Informal . natural langauage
- Semi-formal - when the requirement is expressed in a structured and/or restricted form of
a natural language, using vocabularies, glossaries, or syntactic patterns;
§ when text and modeling are combined (UML is an example). - Formal : when the requirement is expressed in a formally defined
language – such language is expressed using models, symbols and
formulas which precisely specify syntactic and semantic relations to
one another (Z language is one example):
Which languages is most common to write requirments?
- NL
Example: ”when a person tries to register a patient, the information from
ID card is used”; “this app should enable a sound when turning pages”…
+ Universal, no practice and tools
- vaguness of terms, interpreations diffrent, clumpsy fpr detailed specfications
Semi-formal Langauge Requirements
have techniques for reducing the diffrent interpreations of requirment in NL, they are
- Controlled langugage - defines for a specific domain a special (syntax) and terms for restricted grammar. (ex user story)
+ Expressen less amigious than NL with simple grammar and structured syntax
+ easier to read
- Modelling language - model-based requirements (conceptual models,
use cases, etc.)
+provide more compact descriptions than NL; they are
less ambiguous than NL; but they require knowledge of modelling. When
the requirement is expressed by means of models it typically describes a
single perspective (data, or functionality, etc.)
