Unified Modeling Language

Slides:



Advertisements
Similar presentations
Requirements Diagrams With UML Models
Advertisements

Use Case Diagrams.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Systems Analysis and Design 8th Edition
Tutorial 2. What is a UML Use Case Diagram? Use case diagrams model the functionality of a system using actors and use cases. Use cases are services or.
Department of Computing
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
THE OBJECT-ORIENTED DESIGN WORKFLOW UML2 Sequence Diagrams.
Documenting Requirements using Use Case Diagrams
Use Case Systems Analysis & DesignUse Case1 Use case refers to A system’s behavior (functionality) A set of activities that produce some output.
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
Use Case Modeling.
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Unified Modeling Language
Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.
High-Level Design With Sequence Diagrams COMP314 (based on original slides by Mark Hall)
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Systems Analysis & Design 7 th Edition Chapter 5.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
1 Structuring Systems Requirements Use Case Description and Diagrams.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
An Introduction to the Unified Modeling Language
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Drawing System Sequence Diagrams
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.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
4-1 © Prentice Hall, 2007 Topic 4: Structuring Systems Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey.
Chapter 3: Introducing the UML
 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.
Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.
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.
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
1 Use Cases Object-Oriented Modeling and Design with UML (Second Edition) Blaha & Rumbaugh Sections 7.1, 8.1.
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.
CompSci 280 S Introduction to Software Development
Business Process and Functional Modeling
Welcome to M301 P2 Software Systems & their Development
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases
Lec-5 : Use Case Diagrams
Analyzing system processes: Use Case Diagram 2/2
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
Start at 17th March 2012 end at 31th March 2012
Sequence Diagrams.
COP 4331 Recitation #2 University of Central Florida
Unified Modeling Language
Sequence Diagrams Lecture 6.
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4th edition, Prentice Hall, Hans Van Vliet, Software Engineering:
COP 4331 Recitation #1 University of Central Florida
Unified Modeling Language
COP 4331 Recitation #1 University of Central Florida
WHAT IS A Use Case Diagram?
INFS 6225 Object Oriented Systems Analysis & Design
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
Software Design Lecture : 15.
Use Case Model Use case diagram – Part 2.
Software design and architecture
Chapter 5.
CIS 375 Bruce R. Maxim UM-Dearborn
COP 4331 Recitation #1.
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Unified Modeling Language Use Case Diagrams

Use Case Diagram 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

Use Case Diagram Logs in 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 Should be a verb Logs in

Use Case Diagram Logs in 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 Logs in Student

Use Case Diagram <<include>> A use case includes the functionality described in the previous one Represented by a directed arrow having a dotted shaft, labeled with <<include>> Check Fines Pay Fines <<include>> To Pay Fines we require to Check Fines

Use Case Diagram <<extend>> A use case may include the functionality described in another use case Borrow Item Find Item <<extend>> To Borrow Item we may need to Find Item

Finally, To draw a use case diagram: Think of following items: Actors Use cases (Actions) Triggers Goals Failed conclusion Extensions Etc. The relation between use cases Include Exclude

Finally, To draw a use case diagram: For actors: Give meaningful relevant names Put primary actors to the left side Actors does not interact with each other Put inheriting actors below the parent For use case: Names begin with a verb Names are descriptive Put actions in logical order Place included use case to the right of the invoking use case Place inheriting use case below parent use case

References Shari Lawrence Pfleeger and Joanne M. Atlee, "Software Engineering: Theory and Practice", 4th Edition, Prentice Hall, 2010. Prepared/modified by Kia Manoochehri kiam@knights.ucf.edu Gurkan Solmaz gsolmaz@knights.ucf.edu Safa Bacanli sbacanli@cs.ucf.edu Neda Hajiakhoond hajiakhoond@knights.ucf.edu