Dr.

Muhammad Ali Memon

Mr.Kamran Dahri
Suhail Khaled
 Someone always performs the role of
requirements analyst on every software
project.

 Business Analysts
 Systems Analyst
 Requirements Engineer
 Requirements Manager
 Analyst.
Role of an Analyst
 The analyst

◦ is a translator of others' perspectives into a

requirements specification
◦ is a reflector of information back to other
stakeholders.

◦ helps stakeholders find the difference between

what they say they want and what they really need.
Primary Responsibility

 gather
 analyze
 document
 validate

needs of the project stakeholders.

 The Analyst's Tasks
 Define business requirements
 Identify project stakeholders and user classes
 Elicit requirements
Interviews Facilitated requirements Document analysis
workshops
Surveys Customer site visits Business process
analysis
Work flow and task Event lists Competitive product
analysis analysis
Reverse engineering Retrospectives performed
of existing systems on the previous project
Essential Analyst Skills
 Listening skills
 Interviewing and questioning skills
 Analytical skills
 Facilitation skills
 Observational skills
 Writing skills
Essential Analyst Skills

 Organizational skills
 Modelling skills
 Interpersonal skills
 Creativity
Essential Analyst Knowledge
 Sound understanding of

◦ Project Management
◦ Risk Management
◦ Quality Engineering
◦ Product Management Concepts
◦ Application Domain Knowledge
Overview
 Vision and scope issues must be resolved

before the detailed functional requirements

can be fully specified.
 A statement of the project's scope and

limitations helps greatly with discussions of

proposed features and target releases.
 The vision and scope also provide a reference

for making decisions about proposed

requirement changes and enhancements.
Defining the Vision

 The product vision aligns all stakeholders in a

common direction.

 The vision describes what the product is

about and what it eventually could become.
Defining the Scope
 The project scope identifies what portion of

the ultimate long-term product vision the

current project will address.
 The statement of scope draws the boundary

between what's in and what's out.

 The details of a project's scope are

represented by the requirements baseline

that the team defines for that project.
Vision and Scope Document
1. Business Requirements
 Primary benefits that the new system will

provide to its sponsors, buyers, and users.

1.1 Background
 Summarize the rationale and context for the

new product.
 Provide a general description of the history or

situation that led to the decision to build this

product.
1.2 Business Opportunity
 Describe the market opportunity that exists or the
business problem that is being solved. Describe the
market in which a commercial product will be
competing or the environment in which an
information system will be used.
 This may include a brief comparative evaluation of
existing products and potential solutions, indicating
why the proposed product is attractive. Identify the
problems that cannot currently be solved without the
product, and how the product fits in with market
trends or corporate strategic directions
1.3 Business Objectives and Success Criteria

 So this section should focus on the value provided

to the business. This could include estimates of
revenue or cost savings, return on investment
analysis, or target release dates.

 Describe the factors that are likely to have the

greatest impact on achieving that success. Include
things within the direct control of the
organization, as well as external factors
1.4 Customer or Market Needs

 Describe the needs of typical customers or of

the target market segment, including needs
that current products or information systems
do not meet.
 Present the problems that customers

currently encounter that the new product will

address and provide examples of how
customers would use the product.
1.5 Business Risks
 Summarize the major business risks associated
with developing—or not developing—this
product.
 Risk categories include marketplace competition,
timing issues, user acceptance, implementation
issues, and possible negative impacts on the
business.
 Estimate the potential loss from each risk, the
likelihood of it occurring, and your ability to
control it.
 Identify any potential mitigation actions.
2. Vision of the Solution

 Establishes a strategic vision for the system

that will achieve the business objectives.
 Provides the context for making decisions

throughout the course of the product's life.

 Should not include detailed functional

requirements or project planning information.

2.1 Vision Statement

 Write a concise vision statement that summarizes the

long-term purpose and intent of the new product.
 The vision statement should reflect a balanced view
that will satisfy the needs of diverse stakeholders.

 It can be somewhat idealistic but should be grounded

in the realities of existing or anticipated markets,
enterprise architectures, corporate strategic
directions, and resource limitations.
2.1 Vision Statement

 For [target customer]

 Who [statement of the need or opportunity]

 The [product name]

 Is [a product category]

 That [key benefit, compelling reason to buy or use]

 Unlike [primary competitive alternative, current system, or current

business process],

 Our product [statement of primary differentiation and advantages of

new product].
2.1 Vision Statement

 For scientists who need to request containers of chemicals, the

Chemical Tracking System is an information system that will
provide a single point of access to the chemical stockroom and
to vendors. The system will store the location of every chemical
container within the company, the quantity of material remaining
in it, and the complete history of each container's locations and
usage. This system will save the company 25 percent on
chemical costs in the first year of use by allowing the company to
fully exploit chemicals that are already available within the
company, dispose of fewer partially used or expired containers,
and use a single standard chemical purchasing process. Unlike
the current manual ordering processes, our product will generate
all reports required to comply with federal and state government
regulations that require the reporting of chemical usage, storage,
and disposal.
2.2 Major Features

 Name or number each of the new product's

major features or user capabilities in a
unique, persistent way, emphasizing those
features that distinguish it from previous or
competing products.
2.3 Assumptions and Dependencies

 Record any assumptions that the stakeholders

made when conceiving the project and writing
this vision and scope document.

 Record major dependencies the project has on

external factors outside its control. These could
include pending industry standards or
government regulations, other projects, third-
party suppliers, or development partners.
3. Scope and Limitations

 State both what the system is and what it is

not.
 The project scope defines the concept and

range of the proposed solution. The

limitations itemize certain capabilities that
the product will not include.
 The scope and limitations help to establish

realistic stakeholder expectations.

3.1 Scope of Initial Release

 Summarize the major features that are

planned for inclusion in the initial release of
the product.
 Describe the quality characteristics that will

let the product provide the intended benefits

to its various user classes.
3.2 Scope of Subsequent Releases

 If you envision a staged evolution of the

product, indicate which features will be
deferred and the desired timing of later
releases.
 Subsequent releases let you implement

additional use cases and features and enrich

the capabilities of the initial use cases and
features .
3.3 Limitations and Exclusions

 Defining the boundary between what's in and

what's out is a way to manage scope creep
and customer expectations.
 List any product capabilities or characteristics

that a stakeholder might anticipate but that

are not planned for inclusion in the product
or in a specific release.
4. Business Context

 Summarizes some of the project's business

issues, including profiles of major
stakeholder categories and management's
priorities for the project
4.1 Stakeholder Profiles

 Stakeholders are the individuals, groups, or

organizations who are actively involved in a
project, are affected by its outcome, or are
able to influence its outcome.
 The stakeholder profiles describe different

categories of customers and other key

stakeholders for this project.
4.2 Project Priorities
 Fit the five dimensions of a software project:
features, quality, schedule, cost, and staff
 A constraint: A limiting factor within which the
project manager must operate
 A driver: A significant success objective with
limited flexibility for adjustment
 A degree of freedom: A factor that the project
manager has some latitude to adjust and balance
against the other dimensions
4.3 Operating Environment

 Describe the environment in which the

system will be used and define the vital
availability, reliability, performance, and
integrity requirements.
 This information will significantly influence

the definition of the system's architecture,

which is the first—and often the most
important—design step.
Overview
 A project that lacks a clearly defined and

well-communicated direction invites disaster.

 Project participants can unwittingly work at

cross-purposes if they have different

objectives and priorities.
 The stakeholders will never agree on the

requirements if they lack a common

understanding of the business objectives for
the product.
Conflicting Business Requirements
 Business requirements collected from multiple

sources might conflict.

 Project Sponsor’s role to resolve conflicts among

various business stakeholders

 As more stakeholders are identified and more

constituencies with competing interests climb

aboard, the risk of scope creep increases.
 Resolving such issues is often a political and

power struggle, which lies outside the scope of

this book.