Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Analysis

No description
by

Thien Phan

on 27 February 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Analysis

USE CASE ANALYSIS
Why use cases?
Analysis Phase
Develop use cases
-Describe all the tasks that users need to perform with the system

-Clarify the users’ required interactions with the system

-Reveal most functional requirements of the new system

-Identify exceptions, special cases, and error handling requirements in the new system

Develop requirements definition
Apply requirements analysis strategies
Use requirements elicitation techniques
What is a use case?
When?
When we are re-engineering processes or making any changes to business processes that will significantly alter the way people work
How to create?
-Using elicitation techniques (interview and JAD)

-It requires practice to write a meaningful and complete use case

-A set of activities performed on a step of an overall process to produce some output results

-The level of detail depends on the project team
Building Use Cases
As-Is Systems
Focuses on current systems
To-Be Systems
Focuses on desired systems
Identify use cases
Identify major steps within each use cases
Identify elements within steps
Confirm the use case
Find out events, tasks that are important for this business
For each case, find out
Triggers
Materials
Responses
Outcome
Write down these information above with the event names as identifier
For each major case,
Identify the cases
Preconditions can help defining the starting point
User and analyst should work together
Write down steps in order from first to last
The process of obtaining lawn chemicals
Trigger: A Lawn Chemical Applicator (LCA) needs a chemical for a job
Focus on the real needs for the new system, not what the users wanted the system to do

Users may not know what is possible for the system
Users don't understand the capabilities or limitations of technology
Users don't understand the difference between what they need and what they want

Elements of a use case
Basic information
Name & number (ex. UC-2)

Priority

Actor/user role

External trigger/temporal trigger
Validate that each use case is correct and complete
Preconditions & Postconditions
Identify the inputs and outputs
Track the flow of the steps
Make sure nothing is omitted
Preconditions define the state the system must be in before the use case commences, postcondition afterwards

Ex. In order to request a chemical, he must be authenticated, his training and credentials must be up to date

Sets boundaries

Define the final products of the use case

Ex. The Lawn Chemical Case is stored
Normal Course & Alternative Course
"Happy Path" - what happens when everything goes smoothly

Describing what an outsider could observe while watching the user and system interact
The Summary Area
Summary of inputs and outputs
Inputs needed for the completion of the use case
Sources of each input
Outputs as the result each step
Destination of each output
Use case is correct
Review steps, inputs and outputs
Final result is consistent with results defined for the use case
Reenact the use case
Role-play use case
Make sure inputs can produce the outputs and desired results
For each step, identify the triggers and its inputs and outputs
Exceptions
Should describe any error conditions or exceptions that may occur as the use case steps are performed

Potential errors that could lead to an unsuccessful result

Should ask the user for special situations or possible errors

To prevent crashes during testing and implementation
Summary inputs & outputs
Final section of a use case summarizes major inputs & outputs along with the source and destinations

This includes all possible inputs & outputs not just the normal course
Additional use case issues
Frequency of use

Business rules

Special requirements

Assumptions

Notes and issues
Questions
Summary
Identify major steps within each use cases
Breaks it down into smaller manageable parts

Potential reusability (authentification)

Use case writing team (Programming perspective, business rules, familiar with the system)
Identify use cases
Use Case Format
Example was fully dressed because it is essential

"The LCA specifies the desired lawn chemical" - left open to interpret, correct perspective during the analysis phase

User representatives are not closely engaged with the development team throughout the project

Collaborating remote teams need a detailed, shared understanding of the user requirements
Revise Functional Requirement Based on Use Cases
Better understanding of the system
Functional requirement may be modified
Gives potential paths in case certain conditions are fulfilled
Chapter 4:
Use Cases
Group 9

Gong Chen
Selim Ozyalcin
Thien Phan
Chris Sta. Romana
Full transcript