Storyboarding and Game Design SBG, MBG620 Full Sail University

Slides:



Advertisements
Similar presentations
Design by Contract.
Advertisements

Use-Cases.
Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer.
Use Case Diagrams Damian Gordon.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Use Case & Use Case Diagram
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
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.
Extending the Requirements Model - techniques for detailing use cases
Information System Engineering
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Ch 12: Object-Oriented Analysis
CS3773 Software Engineering Lecture 03 UML Use Cases.
Interaction Diagrams Activity Diagram State Machine Diagram
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Use Case Modeling.
USE Case Model.
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.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
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
Faculty of Computer & Information
Black Box Testing Techniques Chapter 7. Black Box Testing Techniques Prepared by: Kris C. Calpotura, CoE, MSME, MIT  Introduction Introduction  Equivalence.
Behavioral Modeling: Sequence and Communication Diagrams Copyright © 2009 John Wiley & Sons, Inc. Copyright © 2005 Pearson Education Copyright © 2009 Kannan.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
1 Use Case Modeling Reference: RUP Doc. Use Case Example 2.
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.
1 Structuring Systems Requirements Use Case Description and Diagrams.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
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.
UML (Unified Modeling Language)
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
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 Case Study and Use Cases for Case Study Lecture # 28.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Use Case Analysis Chapter 6.
Contents What is “RUP?” What are Requirement Types
Using Use Case Diagrams
Paul Ammann & Jeff Offutt
CMPE 280 Web UI Design and Development August 29 Class Meeting
Use Case Modeling - II Lecture # 27.
ATM OO Design and Implementation Case Study
Use Cases Discuss the what and how of use cases: Basics Benefits
Chapter 5 유스케이스 개요 Introduction to Use Cases
Recall The Team Skills Analyzing the Problem (with 5 steps)
Dynamic Modeling of Banking System Case Study - I
Use Case Model.
Object-Oriented Static Modeling of the Banking System - I
Exercices & Corrections Week 3
Use Case Modeling - techniques for detailing use cases
Concepts, Specifications, and Diagrams
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Paul Ammann & Jeff Offutt
Chapter 9 Use Cases.
Object Oriented Analysis and Design
Use Cases 1.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Using Use Case Diagrams
Seminar 2 Design of Informatics Systems
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Object-Oriented Software Engineering
Use Case Modeling Part of the unified modeling language (U M L)
Information Systems Engineering
Presentation transcript:

Storyboarding and Game Design SBG, MBG620 Full Sail University Use Case Storyboarding and Game Design SBG, MBG620 Full Sail University

What’s a use case? Presents a high-level story Describing the interactions between the users and the system. How an end user interacts with the system under specific set of circumstances Depicts the system from the end user point’s of view

Use case representations Can be represented: Narrative text Outline of tasks or interactions A template based description Diagram representation

How to build a Use Case? First step: Define the set of actors Different people or devices that use the system External to the system Have one or more goals when using the system Two types: Primary actors: Work directly and frequently with the system Interact with the system to achieve required system functions Secondary actors: Help the primary actor to complete his task

How to build a Use Case? (cont.) Answer the following questions to define the actors: Who are the primary users of the system? Who are the secondary users of the system? Are there any other (external) systems that interact with the system? Does any of the actors have multiple roles? Are there any other entities that use the system’s output?

How to build a Use Case? (cont.) Second step: build the use case Pick one of the end-users Define the different actions that the user can do. Each action corresponds to one use case. For each use case: Define the preconditions Define the course of events to perform the action Define the course of events if an exception happens

Use Case Template Use Case: Name of use case Primary actor: Goal in context: Brief description of the use case Preconditions: Any conditions that must be true before the use case can be started Trigger: Event that initiates the use case Post conditions: the state of the system after the execution of the use case. Scenario: Detailed description of the actor’s actions and the system responses. Exceptions: Detailed description of error conditions that could occur as well as the system responses in these cases.

Example of Use Case Use Case: Withdraw cash Primary actor: Customer Goal in context: Brief description of the use case Preconditions: Customer has active account Customer has a debit card Trigger: Event that initiates the use case Post conditions: Customer receives cash Account balance is reduced by the amount of the withdrawal Scenario: Customer inserts debit card Customer enters PIN number System validates if customer has a valid account with the bank Customer chooses the required account Checking/Savings Customer selects the amount to withdraw Customer confirms the amount to withdraw Customer receives money System ejects the debit card Exceptions: Customer enters an invalid PIN number System displays a message to the customer to re-enter his PIN Customer enters correct PIN Customer selects an amount higher than the available balance System displays a message to the customer informing him that he does not have sufficient funds System displays a message to the customer to re-enter a new amount Customer enters a lower amount

Use Case Diagram A diagram presenting how: Actors relate to use cases. Use cases relate to use cases Built in early stages of development Presents a high level view of the system Gives an overview of the system Specifying the system requirements Validating the system’s architecture

Elements of use case diagram Actors Use case or Process Task to be performed Is presented by a verb Each actor is linked to a use case Relationships/Links Association Generalization Child/parent relations Include One use case incorporates the functionality of another use case Extend One use case extends the behavior of another use case

How to build a use case diagram? Determine the main system functionalities use cases/tasks to be performed Use verbs The functions should be in ovals Determine the actors of the system Connect the actors to the use cases Specify the type of relationships (include, extend, etc)

Example of Use Case Diagram

Additional links http://www.agilemodeling.com/artifacts/useCaseDiagram.htm http://msdn.microsoft.com/en-us/library/dd409432.aspx http://www.tutorialspoint.com/uml/uml_use_case_diagram.htm