Using the glossary must be obligatory:All involved personnel must beobliged to exclusively use the terms and term definitions as they havebeen defined in the glossary.
Subscribe to view the full document.
4.8Summary47The glossary should contain the sources of the terms:In order to be ableto resolve questions and problems at any time during the course of theproject, it must be possible to determine the source of a term.The stakeholders should agree upon the glossary:Only stakeholders canreliably validate the operational definitions for their respective projectcontext. Each definition should be validated by the stakeholders ortheir representatives. In addition, the individual term definitions in theglossary should be explicitly approved. This approval signals that therespective term is correct and its use is obligatory.The entries in the glossary should have a consistent structure:All entriesin the glossary must be structured in the same way. In order to supporta consistent documentation, it is advisable to use a template for glos-sary definitions. In addition to the definition and the meaning of aterm, the template should specify possible synonyms and homonyms. To reduce the effort of aligning terms with one another, it is advisable tostart with the creation of the glossary early on in the project.4.8SummaryThe documentation of requirements plays a central role in requirementsengineering. As the amount of requirements is often vast, it is very impor-tant to clearly structure the requirements so that personnel not involvedwith the project also understand them. Also, looking up and changingrequirements is simplified and accelerated in this way. This makes meetingthe quality criteria for requirements documents much easier. Usingcustomized documentation structures has proven to be suitable for thatpurpose. These are completed by inserting project-specific requirementswritten in natural language in conjunction with conceptual requirementsmodels.
Subscribe to view the full document.
495Documenting Requirements in Natural LanguageElicited requirements for the system to be developed are frequently docu-mented using natural language. Natural language has the advantage that it(allegedly) does not require preparation time in order to be read andunderstood by stakeholders [Robertson and Robertson 2006]. In addition,natural language is universal in the sense that it can be used to describe anycircumstances. However, there are some problems associated with the useof natural language for requirements documentation. 5.1Effects of Natural LanguageSubjective perceptionAs natural language is inherently ambiguous and statements in natural lan-guage can often be interpreted in multiple ways, it is necessary to place spe-cial emphasis on potential ambiguities in such statements to satisfy the cri-terion of unambiguousness. Requirements are defined and read by peoplewith different knowledge, different social backgrounds, and different expe-riences. The diversity among the people involved in the development proc-
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 )