Defining Requirements

The discovery team formulates requirements to describe new functions or features that are to be implemented.

Prerequisites

  • You have modeled and analyzed your business processes.

  • You have documented the application landscape.

  • In a fit / gap analysis of your business processes, you have identified the need to implement new functions or features or to change existing functions or features.

Context

In Focused Build, you can create requirements from within the Solution Documentation by adding them to business processes or process steps. For this purpose, you use the Requirements Management application, a user interface for documenting and assigning requirements.

If you have not yet modeled your business processes and only start with a list of requirements, you can create the requirements directly in Requirements Management. Later, you can use this app to assign the requirements to the structure elements of the Solution Documentation.

Architect Mode

In the architect mode, architects can enter the project and wave that is relevant for a requirement. You can activate the architect mode in the Customizing (IMG).

Creating Requirements from Within the Solution Documentation

Prerequisites

  • You have already modeled your business processes in the Solution Documentation.

Procedure

  1. In the Solution Documentation, in the Design Branch, select the business process or process step related to your requirement.
  2. In the attributes pane, at Related Documents, choose Requirements.

    The Requirements Management application opens in a separate browser window.

  3. In Requirements Management, choose Requirement. In the menu, choose Create New Requirement.
  4. Specify the header data, such as title, priority, and requirement owner, and requirements team, and add a description for the requirement.
    You can also specify the following:

    • Specify the category of the requirement and the classification of the work packages for the requirement.

    • Select a solution. By default, the selection is blank (no solution assigned). You can later search for requirements that have no solution assigned and change the assignment.

    • Specify the requirement as local.

    • Enter value points or effort points. Value and effort points can be used for the release planning. For example, if the estimated value is high and the estimated effort is low, you can give the requirement a higher priority.

    • Maintain customizable text or numeric fields and flags. The fields can be:

      • provided with self-defined value helps

      • filtered, sorted, and saved in user-specific views

  5. Save your settings. You have the following saving options:

    • Choose (Save) to keep the Create new requirement window open and send the requirement for approval (set the requirement's status to To be Approved).

    • Choose (Save and New) to close the Create new requirement window and create another requirement.