correctness of the specification can only be verified if the criterion ofunderstandability is met.Consistent:[IEEE Std. 830-1998] Requirements must be consistentwith regard to all other requirements, i.e., the requirements must notcontradict one another, regardless of their level of detail or documenta-tion type. In addition, a requirement must be formulated in a way thatallows for consistency with itself, i.e., the requirement may not contra-dict itself.Verifiable:[IEEE Std. 830-1998] A requirement must be described in away that allows for verification. That means that tests or measurementscan be carried out that provide evidence of the functionality demandedby the requirement.Realizable:It must be possible to implement each requirement giventhe organizational, legal, technical, or financial constraints. This meansthat a member of the development team ought to be involved in ratingthe goals and requirements so that he can show the technical limits ofthe implementation of a particular requirement. In addition, the costsfor the implementation must be incorporated into the rating. Occa-sionally, stakeholders withdraw a requirement if the costs for its reali-zation become apparent. Traceable:[IEEE Std. 830-1998] A requirement is traceable if its originas well as realization and its relation to other documents can beretraced. This can be done by means of unique requirement identifiers.
Subscribe to view the full document.
4.7Glossary45Using these unique identifiers, requirements that are derived fromother requirements on a different level of the specification can be con-nected. For example, a system goal can be traced through all levels ofabstraction, from design to implementation and test. Details can befound in section 8.4.Complete:[IEEE Std. 830-1998] Each individual requirement mustcompletely describe the functionality it specifies. Requirements thatare yet incomplete must be specially marked, for example by inserting“tbd” (“to be determined”) into the respective text field or by setting acorresponding status. These markings can then be systematicallysearched for and missing information can be amended accordingly.Understandability:Requirements must be comprehensible to eachstakeholder. Therefore, the type of requirements documentation (seesection 4.2) can vary significantly, depending on the developmentphase (and therefore, depending on the involved staff). In require-ments engineering, it is important to strictly define the terms used. Fundamental principles of understandabilityAlong with quality criteria for requirements, there are two fundamentalrules that enhance the readability of requirements:Short sentences and short paragraphs:As human short-term memory isvery limited, circumstances that belong together should be describedin no more than seven sentences.
As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.
Temple University Fox School of Business ‘17, Course Hero Intern
I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.
University of Pennsylvania ‘17, Course Hero Intern
The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.
Tulane University ‘16, Course Hero Intern
Ask Expert Tutors
You can ask 0 bonus questions
You can ask 0 questions (0 expire soon)
You can ask 0 questions
(will expire )