Tài liệu Module 5: Analyzing Information: Use Cases and Usage Scenarios doc

Module 5: Analyzing Information: Use
Cases and Usage Scenarios


THIS PAGE LEFT INTENTIONALLY BLANK

Module 1: Course
Overview
Module 4: Gathering
Information
Module 5: Analyzing
Information: Use Cases
and Usage Scenarios
Module 6: Analyzing
Information: Rationalizing
Information
Module 7: Presenting
Information
Gathering and Analyzing
Business Requirements
Module 2: Identifying
Business Processes,
Challenges, and Vision
Module 3:
Characteristics of
Information
Transitioning
to Analysis
Use Cases
Usage Scenarios

Review
Module 5: Analyzing
Information: Use Cases
and Usage Scenarios
Module 5: Analyzing Information: Use Cases and Usage Scenarios 103



!
!!
!

Overview
"
Transitioning to Analysis
"
Use Cases
"
Usage Scenarios
"
Review
In this module...
In this module...


In this module, you transition from the process of gathering information to the
process of analyzing information. When you gather and analyze business and
user requirements at work, the process is iterative. As you analyze information,
you will most likely find that you need to gather additional information. The
number of iterations that you conduct depends on the business challenge and

other factors, such as time limits imposed by stakeholders.
First, you will look at the relationship between gathering and analyzing
business and user requirements. Then you will learn how to develop use cases
and usage scenarios.
After completing this module, you will be able to:
"
Describe a process for synthesizing information.
"
Explain the concepts of use cases and usage scenarios.
"
Create use cases.
"
Create usage scenarios.

Slide Objective
To provide an overview of
the module topics and
objectives.
104 Module 5: Analyzing Information: Use Cases and Usage Scenarios



!
!!
!

Transitioning to Analysis
"
Requirements and Wants
"

Synthesizing Gathered Information
"
Activity 5.1: Transitioning from Gathering to Analyzing
Information


In this section, you will look at the transition from gathering information about
the business challenge to analyzing the information so that you can determine
business and user requirements and wants. Then you will learn about a general
process for synthesizing information.
In Activity 5.1, you will participate in a class discussion relating your own
experiences to the process of gathering and analyzing requirements and wants
in the Ferguson and Bardell, Inc. case study.
Slide Objective
To provide an overview of
the topics and activity in this
section.
Module 5: Analyzing Information: Use Cases and Usage Scenarios 105



Requirements and Wants
"
Synthesize the gathered information
"
Determine requirements
$
What the product must do
"
Constraints

$
What parameters the product must work within
"
Determine wants
$
What would be nice for the product to do
"
Organize and prioritize requirements and wants


When you have finished gathering information, you will have a large amount of
information that you need to sift through to determine what information is most
relevant to the business challenge. You need to synthesize the information to
create a detailed description of the current state.
The information that you gather from different sources will include
requirements and wants from the business and user perspectives. The
requirements indicate what the product or solution needs to do to solve the
business challenge as derived from the business and user perspectives. The
wants indicate what stakeholders and users would like to see in the final
product or solution. You need to distinguish between requirements and wants
when you synthesize the information from both the business and user
perspectives.
The requirements and wants will eventually define the features of the final
solution. At this stage, you will only describe, organize, and prioritize the
requirements and wants. Later, in the process of developing the product, the
development team will determine the features of the product.
Some requirements indicate aspects of the business, applications, information,
or technologies that may constrain the final business solution. The final
business solution must conform to these factors because they are deemed
unchangeable. For example, a business may have a particular network

configuration that cannot be changed in the near future. The network may have
certain bandwidth limitations that affect how the development team will need to
design the final solution. As you synthesize the information, you need to
document these constraints clearly so that the development team will design a
product that conforms to the enterprise architecture of the business.
Slide Objective
To summarize the previous
course material and
transition to the next phase
of the course by focusing on
analyzing information for
requirements.
Lead-in
As you synthesize
information, you should use
the business and user
perspectives to determine
the requirements and wants,
as well as identify
constraints in the business
environment.
Delivery Tip
Reinforce to students that
requirements and wants are
not necessarily at odds with
each other. Users and
stakeholders have a core
understanding of what is
required to improve the
business. They also have

desires for features or
capabilities that they know
might not make it into a first
or second release of a
product.
106 Module 5: Analyzing Information: Use Cases and Usage Scenarios



As you analyze the information that you have gathered, verify that you have
enough information to indicate the current state of the business and product
requirements, including:
"
The security needs.
"
The support structures for the solution and their characteristics.
"
Planned changes in the business that could affect the product design.
"
The performance that the users expect or that the business needs to remain
competitive.
"
The existing applications, such as legacy systems, that will need to interact
with the new product.
"
How the existing business processes affect the solution.

As you synthesize and analyze the information, you can determine any gaps
that exist in the information that you collected, and if necessary, gather
additional information.

When the development team actually develops the final product, it will need to
take the product requirements into account. The team will also need to
document the effects that the new product may have on the existing
environment in terms of new requirements for the business, such as support,
maintenance, and extensibility issues. The new requirements must also adhere
to the constraints that you documented during analysis.
Module 5: Analyzing Information: Use Cases and Usage Scenarios 107



Synthesizing Gathered Information
"
Validate all information from observations and
interviews
"
Create information models to capture
$
Context
$
Workflow process
$
Task sequence
$
Physical environment
"
Share information with all team members


You should discuss your findings at a debriefing session with other team
members. At the debriefing session, you will present your findings, diagrams,

and notes to each other. Comments from members of the project team help to
interpret the results, and the session helps the team to better understand the
users.
Involve as many team members as possible in the debriefing session, especially
those from development, testing, user education, and logistics management.
Team members will contribute different perspectives to the session and walk
away from these debriefings with information that is important to them. During
this session, the different team members should suggest any information that is
missing that you need to research.
As you analyze the information, you develop information models that describe
the current state and provide the following information.
Item Description

Context Cultural norms, policies, procedures, rules, regulations, and
standards that constrain and support the business and user.
Workflow
process
Communication and coordination of many work processes and
activities.
Process Collection of activities that yield a result, product, or service,
usually a continuous operation.
Activity Collection of tasks within a particular process.
Task sequence Detailed steps for discrete activities.
Task Series of steps associated with a particular role and activity.
Step Smallest level of action that cannot be decomposed any further.
Physical
environment
Geographic and workspace layout, tangibles, and information
artifacts that affect and support work.

Slide Objective
To explain a general
process for synthesizing
information.
Lead-in
When you synthesize
information, you break it
down into models that
indicate what the final
product must do.
108 Module 5: Analyzing Information: Use Cases and Usage Scenarios



Activity 5.1: Transitioning from Gathering to Analyzing Information


In this activity, you will compare your experience in a development project
with the process described in this section. You will also review the results of
your work from the activities in Module 4 in relation to business and user
requirements and wants.
After completing this activity, you will be able to:
"
Describe a process for synthesizing information.
"
Evaluate the information collected in the Ferguson and Bardell, Inc. case
study in terms of requirements and wants.

Slide Objective
To explain the activity.