Reasons for the documentation during the life cycle

This preview shows page 52 - 54 out of 182 pages.

Reasons for the documentation During the life cycle of a requirements document, many people are trusted with the documentation. During communication, the documentation has a goal-oriented and supporting role. The main reasons for documenting requirements are as follows: Central role of requirements Requirements are the basis of the system development. Requirements of any kind influence the analysis, design, implementation, and test phases directly and indirectly. The quality of a requirement or of a requirements document has a strong impact on the progress of the project and therefore on its success. Definition 4-1: Requirements Document / Requirements Specification A requirements specification is a systematically represented collection of requirements, typically for a system or component, that satisfies given criteria.
Image of page 52

Subscribe to view the full document.

34 4 Documenting Requirements Legal relevance Requirements have a legal relevance. Requirements are legally binding for the contractor and the client, and the client can sue for their fulfill- ment. Documenting the requirements can help to quickly overcome legal conflicts between two or more parties. Complexity Requirements documents are complex. Systems that possess thousands of requirements that in turn have complex interdependencies on multi- ple layers are not unheard of in practice. Without suitable documenta- tion, keeping on top of things can become very difficult for anyone involved. Accessibility Requirements must be accessible to all involved parties. Projects undergo certain “development” as time goes by—with regard to the subject as well as the staff. When requirements can be permanently accessed, uncertainty and obscurities can be avoided and staff that has recently joined the project can quickly get up to speed. Another argument for a good documentation, supportive of the project, is that employees almost never share the same understanding of a subject matter. Therefore, requirements should be documented in a way that they meet the quality demands of all involved. 4.2 Types of Documentation Requirements for a system can be documented in three different perspec- tives. In practice, natural language as well as conceptual models are used to this end, or oftentimes, an advantageous combination of both is employed. 4.2.1 The Three Perspectives of Requirements Requirements for a system can be documented in three different perspec- tives onto the system to be developed: Data perspective Data perspective: In the data perspective, a static-structural perspective on the requirements of the system is adopted. For example, the struc- ture of input and output data as well as static-structural aspects of usage and dependency relations of the system and the system context can be documented (e.g., the services of an external system).
Image of page 53
Image of page 54

What students are saying

  • Left Quote Icon

    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.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    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.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    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.

    Student Picture

    Jill 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 )
Answers in as fast as 15 minutes