Task: Identify System Goals
Define the purpose of the system and the over-arching functionality it has to fulfill.
Disciplines: Requirements
Relationships
Parent Practices
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs
      Steps
      Gather Information

      Use different techniques to make gathering requirements easier. Face-to-face meetings with stakeholders are the most effective way to understand stakeholder needs and to gather and validate requirements, but you must prepare in order for these meetings to run efficiently.

      Be prepared by gathering and reviewing information related to the problem domain, problem statement, business environment and key stakeholders. Most of this information must be available in the vision. Also review the existing requirements repository for stakeholder requests.

      Identify top-level system goals
      The first step is to use the acquired information to identify the most important, top-level system goals. These are usually abstract descriptions of the overall purpose of the system.
      Refine top-level system goals to more granular goals
      Break down the top-level goals to smaller goals that contribute to reaching the top-level goals. Denote relationships between top-level and sub-goals and document the refinements made.
      Identify obstacles that can hinder the system from reaching its goals
      Think of environmental, regulatory, or technical obstacles that might prevent certain goals from being reached. Document the obstacles and their relationship to the individual goals.
      Identify assumptions about the environment and the system
      Identify the implicit assumptions that you make when thinking about goals and obstacles. Do you expect a certain user behaviour? Do you assume that certain economic incentives are in place? Do you assume high quality of information? Document these assumptions and the possible impact if they turn out to be false.
      Key Considerations
      If an existing requirements document, such as a technical vision or appropriate business documents are available, they can be used as a starting point for the definition of the system goals.