Copyright © 2005 Hyundai Team 1 Intelligent Traffic Forecast System Hyundai Team 2005.09.13.

Slides:

Advertisements

Similar presentations

Writing Good Use Cases - Instructor Notes

Advertisements

OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.

CMSC 345, Version 9/07 S. Mitchell Use Cases Concepts, Specifications, and Diagrams.

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:

Requirements Specification and Management

Chapters 7 & 9 System Scope

OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.

Use Cases Elizabeth Bigelow CS C 9/15/2000.

Documenting Requirements using Use Case Diagrams

Object Oriented Analysis Process

Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.

Use Case Modeling.

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.

Copyright © 2014 Pearson Education, Inc. 1 It's what you learn after you know it all that counts. John Wooden Key Terms and Review (Chapter 6) Enhancing.

Air Traffic Control System Team #3. Introduction The purpose of air-traffic control is to assure safe separation between en-route aircraft and the safe.

Chapter 7 Structuring System Process Requirements

Chapter 3 Object-Oriented Analysis of Library Management System(LMS)

[ §6 : 1 ] 6. Basic Methods II Overview 6.1 Models 6.2 Taxonomy 6.3 Finite State Model 6.4 State Transition Model 6.5 Dataflow Model 6.6 User Manual.

Chapter 7: The Object-Oriented Approach to Requirements

SharePoint 2010 Business Intelligence Module 6: Analysis Services.

Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.

RUP Requirements RUP Artifacts and Deliverables

Project Analysis Course ( ) Week 2 Activities.

Analysis Modeling (cont’d) CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides.

Free Mini Course: Applying SysML with MagicDraw

Object-Oriented Analysis - Instructor Notes

State Diagrams / System Sequence Diagrams (SSDs)

® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.

SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.

Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.

Chapter 3 Object-Oriented Analysis. Requirements Analysis A requirement is a feature of the system Requirements analysis seeks to assess and specify the.

Use Cases 1. Last week  Introduction to software engineering  How is it different from traditional engineering?  Introduction to specification  Operational.

Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.

Submitted By: Memon Khurshed (Group Leader) Hamed Abdollahpur

Developing an Algorithm

OOSE Use Case. Requirement Functional: –Features, capabilities, and security Non Functional: –Usability: Human factors, help, and documentation –Reliability:

UML-1 3. Capturing Requirements and Use Case Model.

Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 40 Observing.

Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.

PRJ566 System Sequence Diagrams.  A system sequence diagram …. Illustrates input and output events related to the system under discussion.  Larman,

UML-1 8. Capturing Requirements and Use Case Model.

1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.

A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.

Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.

1. Agenda Introduction Problem Restate Project Progression Use Case Narratives UML Use Case Diagram Data Flow Diagrams Functional Requirements Prototype.

Use Case Model Use case diagram.

Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.

(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0

QA and Testing. QA Activity Processes monitoring Standards compliance monitoring Software testing Infrastructure testing Documentation testing Usability.

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright.

Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.

1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.

Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.

Library Online Resource Analysis (LORA) System Introduction Electronic information resources and databases have become an essential part of library collections.

CSC480 Software Engineering Lecture 7 September 16, 2002.

Network Monitoring Through Mobile (MOBTOP) Developed By : Akanksha Jain. (102199) Shikha Arora (101319) Team Name: Beans Course: CS532 Guided By:Prof.

© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.

1 TCS Internal MyBank MyBank. 2 Content  Introduction  Data Flow Diagram  Class Diagram  Use case Diagram  Application Layouts.

Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.

Advanced Higher Computing Science

WHAT IS A Context Diagram?

BTS430 Systems Analysis and Design using UML

Use Case Model Use case diagram.

UML Use Case Diagrams.

Concepts, Specifications, and Diagrams

IMPORTANT NOTICE TO STUDENTS:

واسط كاربري هوشمند Intelligent User Interface

Use Case Modeling.

Use Case Modeling Part of the unified modeling language (U M L)

Requirements “Content Guide”

Presentation transcript:

Copyright © 2005 Hyundai Team 1 Intelligent Traffic Forecast System Hyundai Team

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 Information 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

Copyright © 2005 Hyundai Team 8 Describe How Actors & Use Cases Interact Use Case nameRequest for optimal path Unique use Case IDUC-105 Primary actor(s)User Brief descriptionUser 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. PreconditionsSuccess in the security check Flow of events1.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