Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.

Slides:



Advertisements
Similar presentations
Requirements Diagrams With UML Models
Advertisements

Use Case Diagrams.
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
Systems Analysis and Design in a Changing World, Fourth Edition
Physics for Scientists & Engineers, 3rd Edition
© 2005 Prentice Hall8-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
9-1 © Prentice Hall, 2004 Chapter 9, Part II: System Behavior - Interactions (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Electric Charge and Electric Field
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
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 Diagram.
Unified Modeling Language
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
Pfleeger and Atlee, Software Engineering: Theory and PracticePage 4.1 © 2006 Pearson/Prentice Hall Sidebar 4.1 Why Are Requirements Important? Top factors.
CS 360 Lecture 6.  A model is a simplification of reality  We build models to better understand the system being developed.  We build models of complex.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
DFDs vs. Use Case Modeling COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
9-1 © Prentice Hall, 2004 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Departments in Business Business Name 1 Business Name 2.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
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.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Systems Analysis and Design in a Changing World, Fourth Edition
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design,
Use Cases and Use Case Diagrams Reporter: 陳雅萍. Outline Use cases, actors Organizing use cases Modeling the behavior of an element Use case diagrams Common.
USE CASE Pertemuan 7 Matakuliah: Konsep object-oriented Tahun: 2009.
 What to do if you want to build a new house? › Buy a bunch of wood and nails and start immediately. › Or, put some blueprints to follow, and plan of.
Session 5 Object Model Development. OOAD with UML / Session 5 / 2 of 19 Review A class icon is a rectangle with three sections within it An object is.
Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
System modeling and the Unified Modeling Language (UML) CS
UML CSE 470 : Software Engineering. Unified Modeling Language UML is a modeling language to express and design documents, software –Particularly useful.
UML CSE 470 : Software Engineering. Unified Modeling Language UML is a modeling language to express and design documents, software –Particularly useful.
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.
Unified Modeling Language Tutorial
Lec-5 : Use Case Diagrams
UML Modeling Sequence diagram
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
Object-Oriented Systems Analysis and Design Using UML
Start at 17th March 2012 end at 31th March 2012
Introduction to UML Introduction to UML Shiyuan Jin September,23,2002
COP 4331 Recitation #2 University of Central Florida
Unified Modeling Language
Princess Nourah bint Abdulrahman University
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4th edition, Prentice Hall, Hans Van Vliet, Software Engineering:
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
COP 4331 Recitation #1 University of Central Florida
Unified Modeling Language
Unified Modeling Language
COP 4331 Recitation #1 University of Central Florida
What is a Relationship Map?
Appendix A Object-Oriented Analysis and Design
Software design and architecture
COP 4331 Recitation #1.
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014

Use Case Diagrams

 Depicts observable, user-initiated functions in terms of interactions of the system and its environment  Describes the relationship between “actors” and use cases  An actor is something that interacts with the system Actors

 A use case represents some action that takes place within the system  Represents a major required functionality of the system  Use cases are not meant to model all tasks that the system provides  They specify user views of essential system behavior Login

 Additionally: ◦ A large rectangle box denotes the system boundary ◦ A line between an actor and use case denotes that the actor participates in the use case Student Login

 > ◦ A use case includes the functionality described in the previous one ◦ Represented by a directed arrow having a dotted shaft, labeled with > Check Fines > Pay Fines

 > ◦ A use case may include the functionality described in another use case Borrow Item > Find Item

 Shari Lawrence Pfleeger and Joanne M. Atlee, "Software Engineering: Theory and Practice", 4th Edition, Prentice Hall, Prepared/modified by  Kia Manoochehri ◦  Gurkan Solmaz ◦