2.3 Examples: Ski resort information system

Slides:



Advertisements
Similar presentations
Cultural Heritage in REGional NETworks REGNET E-SHOP.
Advertisements

Context Diagram Yong Choi BPA CSUB.
Chapter 4: Requirements Engineering
BANKING SYSTEM Software Requirements Document CEN Advanced Software Engineering Fall Term
Information System Analysis
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
09/04/2015Unit 2 (b) Back-Office processes Unit 2 Assessment Criteria (b) 10 marks.
Use Case & Use Case Diagram
Karolina Muszyńska Based on:
USE CASE – ATM EXAMPLE Actors: ATM Customer ATM Operator Use Cases: The customer can withdraw funds from a checking or savings account query the balance.
SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.
Information System Engineering
UML and Systems Analysis MIS3502: Application Integration and Evaluation David Schuff
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Assignment I, part 1. Groups of three students. Specify one as group leader. group names to TA and me. Create an object-oriented conceptualization.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
SwE 313 Case Study Registration System.
Aspect-Oriented Software Development (236601) 1 Home Assignment (what, where and when)
{ How to Use An ATM A simple tutorial to teach how to use ATM Machines.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Regal Web Booking Engine Group Booking User Guide.
Quiz 1. Who is the guru of Extreme Programming?
Use Cases 2 ENGR ♯10 Peter Andreae
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Online Goods and Services. Topics Online Shops and Physical Goods Online Shops and Physical Goods Booking Systems Banking Education and Training Gaming.
MintTrack By Jeff Titus Christopher C. Wilkins Stephen Krach Pablo BajoLaso.
Examples of TPS 1 In this section, we examine the: components of a TPS the examples of real-time transaction processing batch transaction processing.
Team ELL System Requirements Ladakeysha Thomas Elizabeth Waldo LaWanda Warren Brandon Williams.
Glenn David Blank Computer Science & Engineering Department Lehigh University, Bethlehem, PA, USA With support from the National Science Foundation (Grants.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
CS212: Object Oriented Analysis and Design Lecture 4: Objects and Classes - I.
ICT IGCSE.  Understand a wide range of work-related ICT applications and their effects, including applications in libraries (such as records of books.
Copyright © 2007, Oracle. All rights reserved. Managing Concurrent Requests.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Faculty of Computer & Information Software Engineering Third year
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
SFWR ENG 3KO4 Software Development for Computer/Electrical Engineering Fall 2009 Instructor: Dr. Kamran Sartipi Software Requirement Specification (SRS)
Payroll System Bank System Any bank(s) to which direct deposit transactions are sent. Employee A person that works for the company that owns and operates.
Faculty of Computer & Information
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Scenario A scenario is a sequence of steps describing an interaction between a user and a system. Use case is a set of scenarios tied together by a common.
(14-2) UML Instructor - Andrew O’Fallon CptS 122 (December 2, 2015) Washington State University.
Information Systems Engineering Activity Diagram 1.
GOALS BUSINESS MATH© Thomson/South-WesternLesson 3.2Slide 1 3.2Electronic Banking Record electronic banking transactions Find account balance when banking.
How Your Customers Will Pay Online & by Phone
1.7.2.G1 © Family Economics & Financial Education – Revised May 2005 – Financial Institutions Unit – Electronic Banking Funded by a grant from Take Charge.
Lecture Outline Monday 23 rd February (Week 4) 3 – 3:10pm Review of Requirements Eng. and use cases 3:10 – 3:40pm Exercise on Use Case 3:40-4:40 Class.
Chapter 3: Software Design –Use case Diagram Nouf Alghanmi.
UC Diagram & Scenario RKPL C & D. Using Use Case Diagram Use case diagrams are used to visualize, specify, construct, and document the (intended) behavior.
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
1 Case Study and Use Cases for Case Study Lecture # 28.
Introduction What would our society be like now if we did not have ATm’s? Not able to access money when we urgently want it. You will have to go to the.
Using Use Case Diagrams
Use Case Modeling - II Lecture # 27.
Object-Oriented Static Modeling of the Banking System - I
Outline 1. Exercise on use case diagram
Exercices & Corrections Week 3
UML Use Case Diagrams.
Concepts, Specifications, and Diagrams
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Using Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Real-Time Structured Analysis and Design Technique (RSTAD)
Presentation transcript:

2.3 Examples: Ski resort information system Users should be able to query weather and snow condition forecasts for a date they enter. The system should allow to book single or double rooms at the resort hotel “Skier’s Luck” online (with credit card). Visitors should be able to book one-day beginners courses on snowboards. There is only one course a day. The max. size of a course is 8 persons. The resort offers special courses for kids. In order to built courses with kids of same age, the customer has to enter the kid’s age. Canceling of course or room bookings are only possible up to 10 days ahead. CPSC 333: Foundations of Software Engineering J. Denzinger

CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (1)! << includes >> stereotype in actor associations CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (2)! Associations between actors Unnamed associations between use cases CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (3)! System no use case! Name relations! CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (4)! Wrong understanding of the <<extends>> stereotype CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (5)! Diagram moves main functionality outside the system CPSC 333: Foundations of Software Engineering J. Denzinger

Errors you should prevent (6)! Data structures instead of functions as use cases, e.g. date, age, database relations not named CPSC 333: Foundations of Software Engineering J. Denzinger

Example Use Case Diagram Query weather&snow forecast <<include>> Book room Enter personal info Visitor Book SB course <<include>> <<extend>> (Enter kid’s age) Cancel course Book kids’ SB course Cancel room CPSC 333: Foundations of Software Engineering J. Denzinger

Use Case (1) Use Case: Query weather&snow forecast Precond: - Main flow: Visitor enters date Weather & snow forecast for local region is displayed for specified date CPSC 333: Foundations of Software Engineering J. Denzinger

Use Case (2) Use Case: Book SB course Precond: - Main flow: Visitor enters date Include (Enter personal info) (Enter kid’s age) Store reservation Confirm reservation to Visitor Exceptional flow: If number of course participants for specified date > 8, then tell visitor so and let him choose another date CPSC 333: Foundations of Software Engineering J. Denzinger

Use Case (3) Use Case: Book kids’ SB course Precond: SB course is for a kid Main flow: Enter kid’s age Store reservation Confirm reservation to Visitor Exceptional flow: If course for specified date is adult course, then tell visitor so and let him choose another date. If course for specified date is kids’ course, and the specified age is outside the course’s age range, then tell visitor so and let him choose another date. CPSC 333: Foundations of Software Engineering J. Denzinger

Example: literature reference management system Storage and retrieval of references, e.g. Title: The unified modeling language user guide Authors: G. Booch, J. Rumbaugh, I Jacobson Publisher: Addison Wesley Publication year: 1998 Small exercise: Draw a Use Case Diagram (at least two use cases) Describe use cases (at least one) Title: Software engineering in the Internet age Authors: F. Maurer, G. Kaiser Publisher: IEEE Publication year: 1998 Journal: IEEE Internet Computing Magazine Volume: 2 Issue: 5 CPSC 333: Foundations of Software Engineering J. Denzinger

Use Case Diagram: literature reference management Add reference Remove reference User Search for reference List references CPSC 333: Foundations of Software Engineering J. Denzinger

Event flow: List references Precondition: user has selected “list references” functionality. The system prompts the user to select the device: printer or file. The system prompts the user to select the print order: by name or by title. The use case finishes with the system printing the list on the requested device. CPSC 333: Foundations of Software Engineering J. Denzinger

Event flow: Add reference Precondition: user has selected “add new reference” functionality. The system prompts the user to select if he/she wants to add a normal reference or a book. The system prompts the user to enter title, author, and publisher of the reference (Add journal paper) (Except-1). The user is notified that the reference has been successfully added. Except-1: The reference already exists. The user can re-enter the data or terminate the use case. CPSC 333: Foundations of Software Engineering J. Denzinger

Use case: Add journal paper Add journal paper: If the paper is a journal, then the system additionally asks for the journal’s name, the volume number and the issue number. Add reference <<extend>> Add journal paper CPSC 333: Foundations of Software Engineering J. Denzinger

Exercises Develop use case diagram and textual use case descriptions for: an elevator (1 elevator, n floors) a telephone (with number memory) an e-mail system CPSC 333: Foundations of Software Engineering J. Denzinger

enter and exit through a door Elevator -- Use Case 1 elevator, n floors press an elevator button press a floor button User Elevator enter and exit through a door CPSC 333: Foundations of Software Engineering J. Denzinger

Small Test: Bank account manager System has to run on an automated teller machine. User must be able to deposit checks into the account. User must be able to draw money from the account. User should be able to query the balance of his/her account. The user should get a receipt for a transaction on request. The transaction type (withdrawal or deposit), the transaction date, the account number, the amount, and the new balance should be visible on the receipt. After each transaction the new balance should be displayed to the user. CPSC 333: Foundations of Software Engineering J. Denzinger

Example: bank account manager Use case for withdrawal Use case for depositing Use case for balance query Small Test: Draw a Use Case Diagram (Organize use cases) Describe use cases “include”-relationship: Use case for entering the pin number and comparing the pin number on the card with the entered pin number Use case for printing the receipt CPSC 333: Foundations of Software Engineering J. Denzinger