America's Team FC, Prospectus, Funding, Proposal, Revenue and Forecast
Copyright © 2005 Hyundai Team 1 Intelligent Traffic Forecast System Hyundai Team 2005.09.13.
-
Upload
reginald-merritt -
Category
Documents
-
view
213 -
download
0
Transcript of Copyright © 2005 Hyundai Team 1 Intelligent Traffic Forecast System Hyundai Team 2005.09.13.
Copyright © 2005 Hyundai Team 1
Intelligent Traffic Forecast System
Hyundai Team
2005.09.13
Copyright © 2005 Hyundai Team 2
Contents
Introduction Context Diagram layout Find Actors Find Use Cases Adapting Use case Diagram Describe How Actors & Use Cases Interact Making Instance Scenario Of Use Cases Possible Weakness In Capturing Requirement Review: What Did Concern Us
Copyright © 2005 Hyundai Team 3
Introduction
Intelligent Traffic Forecast System predicts the traffic flow and finds the best way.
Roundabout way
National highway
Express Way
Which way is the best on Chuseok holiday this year?
Copyright © 2005 Hyundai Team 4
Context Diagram layout
ITFS(Intelligent Traffic Forecast System )
User
Weather Informati
on Provider
Navigation System
Traffic DB
Request for Optimal path
Display Optimal path Last 5
years traffic information
various paths from departure to arrival
Weather
information
Request for traffic
Request for path
Copyright © 2005 Hyundai Team 5
Find Actors User - A person who requests for the optimal path and gives a priority
- A user is either PC user or mobile user by the access environment
Navigation System- a legacy system that provides the various paths
Traffic DB - an external database of the last 5 years traffic information.
Weather Information Provider- a legacy system that provides current weather information
Copyright © 2005 Hyundai Team 6
Find Use Cases
Validate Identification Gather Weather Information Set Priority Request For Optimal Path Analyze The Optimal Path Inquire About The Various Paths Calculate The Average Traffic Create Log
Copyright © 2005 Hyundai Team 7
Adapting Use case Diagram
Intelligent Traffic Forecast System
Gather weather informationWeather Service Provider
Create log
Analyze the optimal path
Navigation System
Inquire about the various paths
<<include>>
Traffic DBCalculate the average traffic
<<include>>Set priority
Request for optimal path
<<extend>>
<<extend>>
<<include>>
<<include>>
Validate identification
User
Validate identificationfor Mobile user
Mobile user
Validate identificationfor PC user
PC user
Copyright © 2005 Hyundai Team 8
Describe How Actors & Use Cases Interact
Use Case name Request for optimal path
Unique use Case ID UC-105
Primary actor(s) User
Brief description User submits the request for the optimal path in time. If there is, weather and priority setting information also can be input data. After the use case gets all of the request information, it invokes the included use case, ‘Analyze the optimal path’ and ‘create log’. After it gets the optimal path, the system displays the result of calculation to the user screen.
Preconditions Success in the security check
Flow of events 1. User completes the online request for the optimal path by inputting the locations of departure and arrival.
2. Preparation for calculating the optimal path. ……. …….
Copyright © 2005 Hyundai Team 9
Making Instance Scenario Of Use Cases
Happy Case:
System can find the similar condition in the past traffic database.
But...
Unhappy Case:
System can’t find the similar condition ..
Needs to find the most similar case.
Copyright © 2005 Hyundai Team 10
Possible Weakness In Capturing Requirement
Security Problem If we don’t identify the “validate identification” use case,
we can’t find this problem.
System capacity
Response time per user at peak
How many users the system can support?
How much data the database can handle?
Copyright © 2005 Hyundai Team 11
Review: What did concern us
What is the most important thing when we define the scope of use cases?
Easy to read and understand.
Clear to trace and find the defects.
Do not overlap or omit the functions of use cases .
Which is the more efficient way merging use cases or dividing them into included use cases?
To have more readability, we divide the use cases into included
use cases.
To adjust the granularity of use cases, we can merge or divide the
use cases .
Copyright © 2005 Hyundai Team 12
Q & A