In (software) the technology a requirement (frequently English requirement) is a statement about one characteristic which can be being been fulfilling or achievement of a product, a system or a process which can be furnished. Requirements are summarized in a work statement, were usually not documented can in the reality in addition, in almost arbitrary other documents to be found have, or.
The requirement definition follows after the step of the requirement analysis and represents thus the second step during a development process, on which the complete following development develops. Therefore enormously importantly sufficient project time for it is to be taken into account: Each error that is made here to provide necessarily for the correction a multiple of the time, which costs it, a prudent requirement definition.
In developed the requirement document in such a way with the customer must the tasks, which the one which can be developed is to solve the system from hardware and/or software, which goals of the development project which can be achieved as well as the circle of users for that is developed the system, to be held.
The requirement document (consent), come out in such a way from the requirement definition, is basis for the software Design.
Also in Germany one uses gladly English term the requirements and calls the associated activities requirements management and requirement engineering.
Requirement engineering (RH) is methodically supported setting up of requirements by means of analysis of the problem definition. The tasks of the RH are determination (English elicitation), analysis, completion, documentation and quality assurance. For the determination of the requirements it applies to find out, which "the correct" are to asking Stakeholder (it project-took part).
Requirement management (RM) covers requirement engineering as well as measures as the control, a check and administration of requirements, thus risk management, change management and conversion management.
These definitions, which see requirement management as generic term, consider from the past to the realizations that problems with requirements result mostly from management lacking of requirements. It matured in the meantime the realization the fact that alone setting up of requirements is not sufficient but for the realization of a product or a system the large process of the requirement management is necessary.
RH uses the natural speech, if necessary a formalized natural speech with reduced vocabulary and firm sentence constructions, for the representation the so-called requirements Templates. Those likewise strengthens used artificial languages for modelling like e.g. UML or Message Sequence Charts (MSC) facilitate a formulation of the requirements in many situations.
Requirements may be described with requirements engineering not only statements about desired characteristics make, but must parallel to it criteria, examined like these characteristics can (acceptance criteria). These often also criteria called cases of test serve not only the quality assurance of the product, but completely substantially the quality of the requirements themselves, since providing an acceptance criterion forces to an immediate contentwise examination of the requirement.
We found here 5 articles.
R» Requirement (computer science)» Requirement analysis » Requirement management » Requirement profile » Requirements |
We found here 6 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback