Systematic requirements management pays off

The success of IT projects stands and falls with requirements management. The CHAOS Report 2015 of the Standish Group shows that only 29% of IT projects go as planned. 52% are in the balance, and 19% fail. One of the most frequent problems is insufficient requirements management.

Systematic requirements management also pays off in terms of budget: correcting errors during the specifications phase is significantly cheaper than correcting them later during operation.

TÜViT has been supporting customers over the entire product life cycle: from determining the requirements, up to their analysis, documentation and validation up to management for more than 15 years.


Objective of requirements management

Contracts for development and operating tasks are typically awarded to suppliers. Much of the project success stands and falls with whether suppliers receive clear, consistent specifications and implement them as agreed. Through systematic requirements management (from the initiation and early stages of a project to its implementation), the project can continuously monitor and control the quality and functionality of a system.

Our procedure

  1. We first identify the relevant stakeholders. Here we include the future users, technical specialists, and the IT department.
  2. Together with the stakeholders, we create business process models that serve as the basis for the functional and non-functional requirements.
  3. We coordinate the communication process between the various parties involved.
  4. We provide support in the preparation of requirement specifications, ensuring an unambiguous and clear formulation of requirements. Alongside the traditional use of specifications to describe requirements, we use agile methods, such as the formulation of user stories.
  5. TÜViT also continues to support you during the operational phase, when there is typically no further project organization available. We ensure that new requirements or changes, i.e. change requests, are consistently updated in the requirements documents.

Standards and methods

Depending on the project, various methods are applied to determine the requirements:

  • document analysis
  • interviews
  • questionnaires
  • brainstorming
  • workshops

In defining the methods used for documenting requirements, various aspects must be taken into consideration, e.g. previous experience of the individuals or the scope of the project. Methods used include, for instance:

  • business process modeling
  • use cases, activity diagrams, class diagrams, UML models
  • wording templates

We also make sure that the tools being used for requirements management or modelling meet the specific project requirements .

Our services at a glance

  • development of organization-specific processes and methods for the requirements analysis and the management of requirements
  • planning of requirements analysis and management in the project, including the preparation of convention manuals
  • performance of the requirements analysis in the project, including the preparation of business process models, concepts and requirement specifications suitable for use in the invitation to tender
  • requirements management during the project phase and beyond
  • consulting on and use of tools e.g. ARIS, Enterprise Architect, inStep, eclipse and various open-source UML tools

Your benefits at a glance

  • our specialists have all relevant certifications, e.g. IREB® CPRE or ARIS Business Architect
  • neutral moderation of the requirements definition process
  • comprehensible and clear requirements
  • standardized documentation
  • requirements management makes extensive requirements easy to use, and ensures greater transparency and traceability in IT projects
  • the complexity of the IT systems can be controlled effectively through a systematic requirements management

Project example

Federal Institute for Research on Building, Urban Affairs and Spatial Development (BBSR)

TÜViT has been supporting the project “Integrated Spatial Information System (IRIS)” since 2011. In a first step, IRIS consolidates the dispersed regional statistical data inventories of the BBSR into a central data storage (IRIS I). In future, IRIS will form the technical basis for information provided by the BBSR to various buyers.

In the first project stage, TÜViT supported the actual situation analysis and created the basic concept. After the decision on the project progress, TÜViT supported the creation of the technical specifications for the IRIS I phase. During the implementation phase, TÜViT ensured a systematic requirements management