4) Documentation of Requirements

Question 1

What is the goal of documentation of requirements?

Answer 1

The goal is to ensure that the current state of knowledge is secured, and that anyone can obtain an overview at any time.

Question 2

Please name the 4 steps for the documentation of requirements.

Answer 2

• Determine the purpose and target group
• Selection of the detail level and documentation form
• Documentation of requirements
• Checking whether the documentation still fits the purpose and target group

Question 3

What are the typical risks in the practical handling of documentation of requirements?

Answer 3

• Stakeholders who do not admit that they don’t understand the documentation form used.
• The danger that important and possible not yet agreed upon requirements are hidden in large documents and are overlooked during the audit.

Question 4

Course Question!

Please name the characteristics of each specification level.

Answer 4

1) Visions: rough descriptions including goals, visions of products, and product.
2) Use cases and user stories: more detailed descriptions.
3) User requirements: concepts, acceptance, criteria, and test cases.
4) Detailed user requirements: interface descriptions and test cases.

Question 5

List the 4 typical elements of requirements documents.

Answer 5

• Project vision
• Overview Level
• Detailed Requirements
• Glossary

Question 6

Please define the project vision in requirements documents.

Answer 6

At the beginning of a project, the client’s specifications and requirements must be determined, documented, and agreed upon.

Formulating the project vision in text helps the project team to develop a common understanding of the project vision and communicate with stakeholders. The project vision is an introduction and guide to the content of the document, as well as an anchor and pick-up point for workshops and meetings with stakeholders. It can be used to check whether the contant and form still fits the purpose and target group.

Question 7

Explain the role of the overview level in requirements documentation.

Answer 7

The overview level is used for the technical and functional classification of the application. You should be able to obtain a general overview of the main system functions, technical interfaces, users, and classifications in the system landscape.

Question 8

What elements should be considered in the overview level?

Answer 8

• Location of the system in the business process landscape.
• Brief description of the most important system functions so that the reader can gain an overview of the individual system functions.
• Embedding of the system in the IT landscape of the organization, so it is possible to classify the system compared to other IT systems.
• Technical interfaces to other systems, so all involved parties are aware of the technical dependencies.
• Brief description of the roles that will be actively involved in the project, so it is clear which stakeholders must be involved.

Question 9

What forms of documentation can be used to record requirements?

Answer 9

• text
• bullet lists
• tables
• functional models
• references to external documents
• screenshots or prototypes

Question 10

Please give tips on how we can build a glossary.

Answer 10

• sort the defined terms alphabetically
• define technical terms to be used in the requirements
• define verbs to prevent misunderstandings if they are not defined in the specification
• describe adjectives, such as fast
• use legally binding verbs and explain their meaning
• define requirements related to roles by describing tasks and responsibilities

Question 11

Course Question!

Please name the 4 elements that make up a requirement documentation.

Answer 11

1) Project vision
2) Overview level
3) Detailed requirements
4) Glossary