Requirements Planning & Management Chapter 5 Points to review: Introduction Structure Requirement Packages Create Business Domain Model Analyze User Requirements Analyze Functional Requirements Analyze QoS Requirements Determine Assumptions and Constraints Determine Requirement Attributes Document Requirements

Points to review:

Introduction

Structure Requirement Packages

Create Business Domain Model

Analyze User Requirements

Analyze Functional Requirements

Analyze QoS Requirements

Determine Assumptions and Constraints

Determine Requirement Attributes

Document Requirements

Chapter 5: Requirement Analysis & Documentation Points to review: Introduction Structure Requirement Packages Create Business Domain Model Analyze User Requirements Analyze Functional Requirements Analyze QoS Requirements Determine Assumptions and Constraints Determine Requirement Attributes Document Requirements Validate Requirements Verify Requirements Data and Behavioral Models Process/Flow Models Usage Models Issues and Tasks List Chapters: Section 5.1 – 5.9 (Pg 182 – 207) Section 5.10 – 5.12 (Pg 207 – 227) Section 5.13 – 5.14.2 (Pg 228 – 249) Section 5.14.3 – 5.15 Pg. 250 - 265)

Points to review:

Introduction

Structure Requirement Packages

Create Business Domain Model

Analyze User Requirements

Analyze Functional Requirements

Analyze QoS Requirements

Determine Assumptions and Constraints

Determine Requirement Attributes

Document Requirements

Validate Requirements

Verify Requirements

Data and Behavioral Models

Process/Flow Models

Usage Models

Issues and Tasks List

BABOK Chapter 3: Requirement Analysis & Documentation Introduction

5.1 - Introduction Knowledge Area Definition and Scope Requirements analysis and documentation describes how stakeholder needs are analyzed, structured and specified for use in the design and implementation of a solution. The objective is to: Define the characteristics of an acceptable solution Adequately describe an acceptable solution to the business problem Provide a clear understanding of how to design and implement it.

Knowledge Area Definition and Scope

Requirements analysis and documentation describes how stakeholder needs are analyzed, structured and specified for use in the design and implementation of a solution. The objective is to:

Define the characteristics of an acceptable solution

Adequately describe an acceptable solution to the business problem

Provide a clear understanding of how to design and implement it.

5.1 – Introduction The primary focus of this knowledge area is to develop the analysis models and determine the gaps in the information provided by the stakeholders. Input Project scope Planning documentation Goals and Objectives Output Fully specified requirements

The primary focus of this knowledge area is to develop the

analysis models and determine the gaps in the

information provided by the stakeholders.

Input

Project scope

Planning documentation

Goals and Objectives

Output

Fully specified requirements

5.1 – Introduction Activities Structure the requirements Create a business model domain Analyze user requirements Analyze quality of service requirements Determine assumptions and constraints Determine requirement attributes Document requirements Validate requirements Verify requirements

Activities

Structure the requirements

Create a business model domain

Analyze user requirements

Analyze quality of service requirements

Determine assumptions and constraints

Determine requirement attributes

Document requirements

Validate requirements

Verify requirements

BABOK Section 3.2 (Pg 66) Activity 1 – Structure Requirements Package

5.2 - Structure Requirements Package Purpose : To refine the problem boundary and solution scope definitions developed in Enterprise Analysis. Predecessor Problem Domain Scope Output from Elicitation KA

Purpose :

To refine the problem boundary and solution scope definitions developed in Enterprise Analysis.

Predecessor

Problem Domain Scope

Output from Elicitation KA

5.2 - Structure Requirements Package Process and Elements Define the Solution Boundary Actors System Time Structure Solution Definition Techniques Goal Decomposition: Breakdown of goals into objectives Feature List Decomposition: Decomposition of services provided by the solution Functional Decomposition: Breakdown high level functions into processes and sub-processes

Process and Elements

Define the Solution Boundary

Actors

System

Time

Structure Solution Definition

Techniques

Goal Decomposition: Breakdown of goals into objectives

Feature List Decomposition: Decomposition of services provided by the solution

Functional Decomposition: Breakdown high level functions into processes and sub-processes

BABOK Section 3.2 (Pg 66) Activity 2 – Create Business Domain Model

5.3 - Create Business Domain Model Purpose To describe the current and future state of the enterprise. To get a good understanding of the current as-is of the enterprise Predecessors Output for Elicitation KA

Purpose

To describe the current and future state of the enterprise.

To get a good understanding of the current as-is of the enterprise

Predecessors

Output for Elicitation KA

5.3 - Create Business Domain Model Process and Elements Domain and User variation Multiple work units perform the same function Multiples users perform the same work Resolution Document inconsistencies in current business model Determine if standardization is needed

Process and Elements

Domain and User variation

Multiple work units perform the same function

Multiples users perform the same work

Resolution

Document inconsistencies in current business model

Determine if standardization is needed

BABOK Section 3.2 (Pg 66) Activity 3 – Analyze User Requirements

5.4 - Analyze User Requirements Purpose To capture and describe requirements that affect a particular user or user group. To insure that the needs of individual stakeholder groups are addressed by a solution. Process Describe users or user groups Describe how users of a solution will interact with it. Describe how a product will meet the needs of different customer groups. Determine whether to develop different requirement for different group of users

Purpose

To capture and describe requirements that affect a particular user or user group.

To insure that the needs of individual stakeholder groups are addressed by a solution.

Process

Describe users or user groups

Describe how users of a solution will interact with it.

Describe how a product will meet the needs of different customer groups.

Determine whether to develop different requirement for different group of users

BABOK Section 3.2 (Pg 66) Activity 4 – Analyze Functional Requirements

5.5 Activity: Analyze Functional Requirements Purpose To describe the desired behavior of a solution. Process Textual Documentation Matrix Documentation Diagrams Models Related Tasks

Purpose

To describe the desired behavior of a solution.

Process

Textual Documentation

Matrix Documentation

Diagrams

Models

Related Tasks

BABOK Section 3.2 (Pg 66) Activity 5 – Analyze QoS Requirements

5.6 Activity: Analyze QoS Requirements Purpose To describe attributes of the system or system environment. Process Describe environmental Requirements Describe interface requirements Create a glossary Describe operational requirements Consider privacy requirements Describe quality requirements Describe safety requirements Describe security requirements Describe Training requirements

Purpose

To describe attributes of the system or system environment.

Process

Describe environmental Requirements

Describe interface requirements

Create a glossary

Describe operational requirements

Consider privacy requirements

Describe quality requirements

Describe safety requirements

Describe security requirements

Describe Training requirements

BABOK Section 3.2 (Pg 66) Activity 6 – Determine Assumptions and Constraints

5.7 Activity: Determine Assumptions and Constraints Purpose To describe non-functional aspect of the problem domain but will impact the design of the solution. Process Describe Business Constraints Describe Technical Constraints Describe Assumptions

Purpose

To describe non-functional aspect of the problem domain but will impact the design of the solution.

Process

Describe Business Constraints

Describe Technical Constraints

Describe Assumptions

BABOK Section 3.2 (Pg 66) Activity 7 – Determine Requirement Attributes

5.8 Activity: Determine Requirement Attributes Purpose To provide information about the requirement. Process Pay attention to cues during elicitation Document attributes Determine the values of the required attribute

Purpose

To provide information about the requirement.

Process

Pay attention to cues during elicitation

Document attributes

Determine the values of the required attribute

BABOK Section 3.2 (Pg 66) Activity 8 – Document Requirements

5.9 - Document Requirements Purpose To create requirement document. Process Analyze your audience Select document format Write your requirement

Purpose

To create requirement document.

Process

Analyze your audience

Select document format

Write your requirement

BABOK Section 3.2 (Pg 66) Activity 9 – Validate Requirements

5.10 Validate Requirements Purpose - To ensure that the stated requirements correctly and fully implement the business requirements as defined during Enterprise Analysis. Description - To be added in later drafts… (IIBA work-in-progress)

Purpose - To ensure that the stated requirements correctly and fully implement the business requirements as defined during Enterprise Analysis.

Description - To be added in later drafts… (IIBA work-in-progress)

BABOK Section 3.2 (Pg 66) Activity 10 – Verify Requirements

5.11 Verify Requirements Purpose To ensure that requirements are defined clearly enough to allow solution design and implementation to begin. Process Bump requirements against requirement rules Benefits No duplicates Requirement are feasible Can be implement in current release Can be used to conduct further analysis

Purpose

To ensure that requirements are defined clearly enough to allow solution design and implementation to begin.

Process

Bump requirements against requirement rules

Benefits

No duplicates

Requirement are feasible

Can be implement in current release

Can be used to conduct further analysis

5.11 Verify Requirements

Technique: 5.12 - Data and Behavior Models

5.12.1 - BUSINESS RULES Purpose : To provide a formal structure for the identification, documentation and maintenance of business rules Key Elements : Captured as textual statement 5 types of Business rules: Term, Fact, Derivation, Assertion, Action Enabler Decision tables/trees are used to capture Business Rules

Purpose :

To provide a formal structure for the identification, documentation and maintenance of business rules

Key Elements :

Captured as textual statement

5 types of Business rules: Term, Fact, Derivation, Assertion, Action Enabler

Decision tables/trees are used to capture Business Rules

5.12.2 - CLASS MODEL Purpose : To show the entities relevant to the solution, along with each entity's internal structure and relationships with other entities Key Elements : Characteristic are distinguished via: Attributes: Information recorded about a class Operations: What a class can do

Purpose :

To show the entities relevant to the solution, along with each entity's internal structure and relationships with other entities

Key Elements :

Characteristic are distinguished via:

Attributes: Information recorded about a class

Operations: What a class can do

5.12.3 - CRUD MATRIX Purpose To define different levels of access rights to data stored within a software solution Key Element 5 level of access rights Create: instantiate new instances of data element Read: view all data stored in data element Update: change data stored in data element Delete: delete instance of data element List: view instances of data element but not internal data

Purpose

To define different levels of access rights to data stored within a software solution

Key Element

5 level of access rights

Create: instantiate new instances of data element

Read: view all data stored in data element

Update: change data stored in data element

Delete: delete instance of data element

List: view instances of data element but not internal data

5.12.4 - DATA DICTIONARY Purpose A data dictionary defines the data that is recorded or used by an organization Key Element Primitive Data Elements: smallest unit of information about a data. Such as: Name, Aliases, Value/Meanings, Description…etc Composite Data Elements: combination of different primitive data elements.

Purpose

A data dictionary defines the data that is recorded or used by an organization

Key Element

Primitive Data Elements: smallest unit of information about a data. Such as: Name, Aliases, Value/Meanings, Description…etc

Composite Data Elements: combination of different primitive data elements.

5.12.5 - DATA TRANSFORMATION AND MAPPING Purpose Used on projects such as data warehousing that require use of existing business data records to ensures that the historical data records are consistent with the new business solutions needs Key Element High level data model Data business rule Data cleansing plan Environment plan Business data categories Source & target record naming conventions

Purpose

Used on projects such as data warehousing that require use of existing business data records to ensures that the historical data records are consistent with the new business solutions needs

Key Element

High level data model

Data business rule

Data cleansing plan

Environment plan

Business data categories

Source & target record naming conventions

5.12.6 - ENTITY RELATIONSHIP DIAGRAMS Purpose Useful in describing the structure of the business itself, and many of the business rules by which it is governed. To communicate data requirements to business area experts. Key Elements Entities Attributes Unique Identifiers Relationships

Purpose

Useful in describing the structure of the business itself, and many of the business rules by which it is governed.

To communicate data requirements to business area experts.

Key Elements

Entities

Attributes

Unique Identifiers

Relationships

5.12.7 - METADATA DEFINITION Purpose Helps the Business Analyst to explain the context in which the data is used. Key Element Data about data Captured within the system

Purpose

Helps the Business Analyst to explain the context in which the data is used.

Key Element

Data about data

Captured within the system

BABOK Section 3.3 (Pg 83) Technique: 5.13 – Process Flow Models

5.13 – Process Flow Models Techniques Data & Behavior Models Process Flow Models Usage Models Process Flow Models Activity Diagram Data Flow Diagram Event Identification Flowchart Sequence Diagram State Machine Diagram Workflow Models

Techniques

Data & Behavior Models

Process Flow Models

Usage Models

Process Flow Models

Activity Diagram

Data Flow Diagram

Event Identification

Flowchart

Sequence Diagram

State Machine Diagram

Workflow Models

5.13 – Process Flow Models Techniques Data & Behavior Models Process Flow Models Usage Models Usage Models Prototyping Storyboards/Screen Flows Use Case Description Use Case Diagram User Interface Designs User Profiles User Stories

Techniques

Data & Behavior Models

Process Flow Models

Usage Models

Usage Models

Prototyping

Storyboards/Screen Flows

Use Case Description

Use Case Diagram

User Interface Designs

User Profiles

User Stories

5.13.1 – Activity Diagram Purpose To graphically represent the flow of a sequence of activities and the logic that controls the flow Key Elements Activities Sequence Start point End point Branches Merges Forks Joins Responsibilities

Purpose

To graphically represent the flow of a sequence of activities and the logic that controls the flow

Key Elements

Activities

Sequence

Start point

End point

Branches

Merges

Forks

Joins

Responsibilities

5.13.2 – Data Flow Diagram (DFD) Purpose To shop how information is input, processed, stored, and output from a system Key Elements External Entities Data Store Data Process Data Flow

Purpose

To shop how information is input, processed, stored, and output from a system

Key Elements

External Entities

Data Store

Data Process

Data Flow

5.13.3 – Event Identification Purpose To facilitate the discovery of processes of a system Key Elements External Event Temporal Events Internal Events

Purpose

To facilitate the discovery of processes of a system

Key Elements

External Event

Temporal Events

Internal Events

5.13.4 – Flowchart Purpose To graphically represent the flow of a sequence of activities and the logic that controls the flow Key Elements Activity Sequential Flow Start Point End Point Branches Merges Forks Joins

Purpose

To graphically represent the flow of a sequence of activities and the logic that controls the flow

Key Elements

Activity

Sequential Flow

Start Point

End Point

Branches

Merges

Forks

Joins

5.13.5 – Sequence Diagram Purpose To model logic of usage scenarios Key Elements Objects Passive Active Messages Lifeline

Purpose

To model logic of usage scenarios

Key Elements

Objects

Passive

Active

Messages

Lifeline

5.13.6 – State Machine Diagram Purpose To specify a sequence of state that an object goes through during its lifetime Key Elements States Transitions Events

Purpose

To specify a sequence of state that an object goes through during its lifetime

Key Elements

States

Transitions

Events

5.13.7 – Workflow Models Purpose To document how work processes are carried out To find opportunities for process improvement Key Elements Activities/Tasks Sequential Flows Decision Points Parallel Flows Swim-lanes Terminal

Purpose

To document how work processes are carried out

To find opportunities for process improvement

Key Elements

Activities/Tasks

Sequential Flows

Decision Points

Parallel Flows

Swim-lanes

Terminal

5.14.1 – Prototyping Purpose All more realistic visual representation of user interaction with a system Key Elements Shell Documentation for Development

Purpose

All more realistic visual representation of user interaction with a system

Key Elements

Shell

Documentation for Development

5.14.2 – Storyboards/Screen Flows Purpose Provide an early mock-up of proposed business solution functionality Key Elements Screen Shots Modeling

Purpose

Provide an early mock-up of proposed business solution functionality

Key Elements

Screen Shots

Modeling

5.14.3 Use Case Descriptions Purpose To gain agreement between project stakeholder on what behavior they expect from the system Key Elements Name Actors Precondition Flow of Events Post Conditions Extension Points Special Requirements

Purpose

To gain agreement between project stakeholder on what behavior they expect from the system

Key Elements

Name

Actors

Precondition

Flow of Events

Post Conditions

Extension Points

Special Requirements

5.14.4 Use Case Diagram Purpose Used to provide agreement on project scope for BA and Business Stakeholders Used by all project stakeholders to get an understanding of components of the problem space. Key Elements Actor Association Boundary Use Case

Purpose

Used to provide agreement on project scope for BA and Business Stakeholders

Used by all project stakeholders to get an understanding of components of the problem space.

Key Elements

Actor

Association

Boundary

Use Case

5.14.5 User Interface Designs Purpose To gain agreement on user’s goal when using the system Key Elements User profiles or classes Element of discussion Organization standards Modeling standards

Purpose

To gain agreement on user’s goal when using the system

Key Elements

User profiles or classes

Element of discussion

Organization standards

Modeling standards

5.14.6 User Profiles Purpose To highlight differences in user groups that require different interfaces Key Elements User Types User Attributes Techniques Elicitations Revised user types

Purpose

To highlight differences in user groups that require different interfaces

Key Elements

User Types

User Attributes

Techniques

Elicitations

Revised user types

5.14.7 User Stories Purpose To get an agreement on key features To gain time estimates to accomplish coding for a feature Key Elements Story Card Description Estimates Priority Unique ID Constraints Business Rules

Purpose

To get an agreement on key features

To gain time estimates to accomplish coding for a feature

Key Elements

Story Card

Description

Estimates

Priority

Unique ID

Constraints

Business Rules