Christopher McSpiritt

Domains

• Domains are an area undergoing analysis

Solutions

• A solution is a set of changes to the current state of an organization that are made in order to enable the organization to meet a business need, solve a problem, or take advantage of an opportunity.
• Examples of solutions and solution components include software applications, web services, business processes, the business rules that govern that process, an information technology application, a revised organizational structure, outsourcing, insourcing, redefining job roles, or any other method of creating a capability needed by an organization.
• Business analysis helps organization define the optimal solution for their needs, given the set of constraints (including time, budget, regulations, and others) under which that organization operates.

Requirements

• Condition or capability needed by a stakeholder to solve a problem or achieve an objective.
• A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents.
• One of the key objectives of business analysis is to ensure that requirements are visible to and understood by all stakeholders.
• A requirement may describe the current of future state of any aspect of the enterprise.
  • Requirements Classification Scheme
  • Business Requirements
    • Higher level statements of the goals, objectives, or needs of the enterprise.
    • Describe why a project has been initiated, the objectives the project will achieve, and the metrics that will be used to measure its success.
    • They are developed and defined through enterprise analysis.
  • Stakeholder Requirements
    • Statements of the needs of a particular stakeholder or class of stakeholders.
    • They describe the needs that a given stakeholder has and how that stakeholder will interact with the solution.
    • Stakeholder requirements serve as a bridge between business requirements and the various classes of solution requirements.
    • They are developed and refined through requirements analysis.
  • Solution Requirements
    • Describe the characteristics of a solution that meet business requirements and stakeholder requirements.
    • They are developed and defined through requirements analysis.
    • They are frequently divided into sub-categories:
      • Functional Requirements
        • Describe the behavior and information that the solution will manage
        • Describe the capabilities the solution will be able to perform in terms of behavior or operations
        • Non-functional requirements
          • Capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective.
          • Also knows as quality or supplementary requirements
          • Often include requirements related to capacity, speed, security, availability, and the information architecture and presentation of the user interface.
  • Transition Requirements
    • Describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state, but that will not be needed once that transition is complete.
    • They are differentiated because they are always temporary and cannot be developed until both an existing and new solution are defined.
    • They typically cover data conversion from existing systems, skill gaps that must be addressed, and other related changes to reach the desired future state.
    • They are developed through solution assessment and validation.