Requirements Basics: Writing Requirements correctly

Textual requirements are often ambiguous or imprecisely written. This poses a significant project risk and makes verification and validation of the product harder. With better requirements you reduce these risks, use your requirements more efficiently and create a solid basis for communication among everyone involved in the project.

Content:

• Properties of language
• Basic linguistic principles
• Language in the requirements engineering process
• A set of linguistic rules for writing requirements
• Writing and reviewing requirements using an example project

Your benefit:

You appreciate the importance of good requirements for development and testing. You write requirements that are clear, unambiguous and testable. This gives you objective assessment criteria for identifying defects and teaches you methods and techniques for formulating requirements. As a result, you raise the quality of your documents, communicate more easily and precisely with your customers and subcontractors, and improve the success of your projects with simple means.

Target audience:

Requirements managers, (technical) project leaders, quality assurers, development engineers, test engineers

Required prior knowledge:

A basic understanding of the processes in requirements engineering and management