Lecture 16 9/11/15. Reminder - Semester 1 Continuous Assessment  In lab MS Excel Exam  Thursday 19 th November  Group 1 4-5pm - A to L  Group 2 5-6pm.

Slides:



Advertisements
Similar presentations
Use Case Diagrams.
Advertisements

Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
Use Case Diagrams Damian Gordon.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Using SUCD to Describe Use Cases ECE 621. Authoring Styles Many authoring styles exist Tailored for specific domains  Real-Time systems  Safety critical.
Use Case & Use Case Diagram
Advanced Data Modeling
Software Development Theory Slideshows By Mark Kelly Edited and Modified by Mr Hem Use Cases UML Use-case actors relaxing.
Information System Engineering
Use Case Modeling CIS 4800 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College Copyright © 2009 John Wiley & Sons, Inc. Copyright.
Chapter 6 Advanced Data Modelling
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.
Intro to Systems Requirements COMP1007 © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Systems Requirements Use-Cases.
Documenting Requirements using Use Case Diagrams
Class Diagram & Object Diagram
Use Case Modelling.
Use Cases Chapter 4. After Scenarios Find all the use cases in the scenario that specifies all possible instances of how to report a fire –Ex: “Report.
Modelling classes Drawing a Class Diagram. Class diagram First pick the classes –Choose relevant nouns, which have attributes and operations. Find the.
IS0514 Lecture Week 3 Use Case Modelling.
Software Engineering 1 Object-oriented Analysis and Design Chap 30 Relating Use Cases.
Managing Changing Requirements: Structure the Use Case Model PowerPoint Presentation derived from IBM/Rational course Mastering Requirements Management.
Intro: Use Case and Use Case Diagram Documentation.
Object-Oriented Modeling
Interaction Modeling. Introduction (1) Third leg of the modeling tripod. It describes interaction within a system. The class model describes the objects.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 10: Structure the Use-Case Model.
Microsoft ® Office Access ® 2007 Training Build a database I: Design tables for a new Access database ICT Staff Development presents:
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Presented by Kathy Castleberry Health Services & Training Manager INCA Head Start 11/19/12.
Use Cases 7/09. lnot part of the system lrepresents roles a user can play lrepresents a human, a machine or another system lactively exchanges information.
Interaction Modeling Extracted from textbook:
1 Structuring Systems Requirements Use Case Description and Diagrams.
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
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.
Adv. Use cases Actor generalization – general and special actors Use case generalization – general and special use cases Include and extend relationships.
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.
Use cases Week Use‐case diagram 2 – Depicts the interactions between the system and external systems and users. – Graphically describes who will.
Unit-3 Identifying use cases Object Analysis Classification
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
UML (Unified Modeling Language)
Introduction to Active Directory
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
Access Specifier. Anything declared public can be accessed from anywhere. Anything declared private cannot be seen outside of its class. When a member.
Use Case Diagram Lecture # 1. Use Case Diagram Use-cases are descriptions of the functionality of a system from a user perspective.  Depict the behaviour.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Observation Skills Helping Assess Children’s Behaviour.
Use Case Diagrams-2. Relationships between Use Cases 2 1. Generalization - use cases that are specialized versions of other use cases. 2. Include - use.
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
1 After the scenarios are formulated Find all the use cases in the scenario Describe each of these use cases in more detail Participating actors Describe.
Belton Lane Primary school. A BASIC OUTLINE What is Tapestry? Tapestry is an on-line system which allows us to create an individual Learning journey for.
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
Use Cases. 2 A use case... –Specifies the behavior of a system or some subset of a system. –Is a system-level function. –Does not indicative how the specified.
Auburn University COMP 2710 Software Construction Use Case Analysis – Examples and Exercises Dr. Xiao Qin Auburn University.
Topic 2: binary Trees COMP2003J: Data Structures and Algorithms 2
Use Case Modeling - II Lecture # 27.
Chapter 8 Advanced Interaction Modeling
SYSC System Analysis and Design
Auburn University COMP 2710 Software Construction Use Case Analysis and Exercises (Part 2) Dr. Xiao Qin Auburn University.
Interface.
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Object Oriented Analysis and Design
Use Cases.
Relating Use Cases popo.
IS0514 Lecture Week 3 Use Case Modelling.
Using Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Interaction Modeling Extracted from textbook:
Information System Design
Presentation transcript:

Lecture 16 9/11/15

Reminder - Semester 1 Continuous Assessment  In lab MS Excel Exam  Thursday 19 th November  Group 1 4-5pm - A to L  Group 2 5-6pm – M to Z

More practice Which actor initiates the entering of an order? The clerk.

More practice Which actor responds to an order being entered? The accounts system.

More practice Is the Accounts System actor a human? No, it’s an information system.

More practice Who starts off the getting of an address? The accounts system.

More practice Can the Accounts System cancel an order? No.

More practice Who is the passive actor during order entry? The accounts system.

More practice Who is the primary actor during order entry? The clerk.

“Includes” – aka “Uses Association”  The includes relationship occurs when you are describing your use cases and notice that some of them have common subflows  To avoid describing a subflow more than once in several use cases, you can extract the common subflow and make it a use case of its own  The new use case can then be included (used) by other use cases

More on Include  The relationships among the other use cases and this new extracted use case is an “includes relationship”  The includes relationship helps us avoid redundancy by allowing a use case to be shared  A base use case is dependent on the included use case(s); without it/them the base use case is incomplete

“Extends” relationship  the extends relationship means that one use case is similar to another use case but does a bit more or is more specialized  the base use case (the use case that is extended) is extended with additional behaviour by the extending use case  the extensions can be seen as optional functionality added to the base use case

UCD Example – Include and Extend Use Case Generalization Actor Generalization

Use Case Generalization  A parent use case may be specialized into one or more child use cases that represent more specific forms of the parent.  A child inherits all structure, behaviour, and relationships of the parent.  Children of the same parent are all specializations of the parent.  In an Order Management system, the use cases Phone Order and Internet Order share a lot in structure and behaviour.  A general use case Place Order is defined where that structure and common behaviour is defined.  The abstract use case Place Order need not be complete in itself, but it provides a general behavioural framework that the child use cases can then make complete.

Reminder – Actor Generalization  In the context of use case modeling the actor generalization refers to the relationship which can exist between two actors and which shows that one actor (descendant) inherits the role and properties of another actor (ancestor).  The generalization relationship also implies that the descendant actor can use all the use cases that have been defined for its ancestor.  When it comes to air travel, both a "Business Traveler" and a "Tourist" are "Passengers".  The fact that they are passengers allow them to have common behavior such as "Buy Ticket" but the fact that they are separate actors implies they can also have differences.  The "Business Traveler" might be able to "Redeem Business Miles" while the "Tourist" cannot.