Sept 200491.3913 Ron McFadyen1 Include Relationship UC1:Process Sale … Main Success Scenario … 7. Customer pays and System handles payment. … Extensions.

Slides:

Advertisements

Similar presentations

Object-Oriented Analysis and Design Evolutionary Requirements.

Advertisements

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:

Stimulate 2005 Instructor: Luz M. Quiroga University of Hawaii Information and Computer Science / Library and information Science POST.

Use Case & Use Case Diagram

Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.

Information System Engineering

Assignment I, part 1. Groups of three students. Specify one as group leader. group names to TA and me. Create an object-oriented conceptualization.

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.

Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.

As analysis proceeds, you recognize

September Ron McFadyen1 design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before.

January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.

Sequence Diagram Objects are represented horizontally across the top of the diagram Each object has a lifeline some exist before and/or after some are.

Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.

Jan Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box Actors.

Jan Ron McFadyen1 Consider a simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase.

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of.

Fall 2009ACS-3913 Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,

Jan R. McFadyen1 Use Case development As analysis proceeds, you recognize commonality amongst the Use Cases that you will abstract out into.

Fall 2009ACS Ron McFadyen1 The context maintains an instance of a concrete state subclass State Pattern Each subclass (concrete state) implements.

Use Case Modelling.

Jan R McFadyen1 Use Cases Widely used. Not just an OO technique. Diagramming defined in UML Each Use Case will meet one or more user goals;

Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,

Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.

Sept Ron McFadyen1 Extend Relationship.

CENTURY 21 ACCOUNTING © Thomson/South-Western LESSON 4-1 Preparing a Chart of Accounts.

IS0514 Lecture Week 3 Use Case Modelling.

Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.

1.  Modeling the context of a system  Modeling the requirements of a system 2.

Software Engineering 1 Object-oriented Analysis and Design Chap 30 Relating Use Cases.

Use Case Modeling Scenarios, Actors and Use cases Use case Relationships > and > Use case Generalization Writing use cases formally Choosing System Boundary.

Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.

SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.

CENTURY 21 ACCOUNTING © Thomson/South-Western LESSON 12-1 Posting to An Accounts Payable Ledger.

Kyung Hee University System Functional Model OOSD 담당조교 석사과정 이정환.

Chapter 9 Applying UML and Patterns -Craig Larman

1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.

Learning Objectives Understand the Business – LO1 Distinguish among service, merchandising, and manufacturing operations. – LO2 Explain common principles.

Sept Ron McFadyen1 Class Diagram Begins as a conceptual or analysis class model and evolves to a design class model Used throughout the development.

Business Analysis with For PG MDI, Gurgaon Kamna Malik, Ph.D.

CENTURY 21 ACCOUNTING © 2009 South-Western, Cengage Learning LESSON 4-1 Preparing a Chart of Accounts.

January Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, Implement the ProductSpecification and Payment classes in any OO.

Five Types of Payment Systems Cash Checking Transfer Credit Card Stored Value Accumulating Balance.

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.

MAN 470 – Berk TUNCALI 1. What is Cash Management? It is the process of forecasting, collecting, disbursing, investing and planning for the cash a company.

January Ron McFadyen1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain of interest.

Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.

PRESENTATION ON USE CASE. Use Case Modeling Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is.

22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.

Understanding Requirements

UML (Unified Modeling Language)

Node-Tree Diagram (Level 1-2 Work-Breakdown-Structure) (Perform Personal Financial Management) Manage Investment Portfolio Manage Cash Manage Checking.

Information flow Diagram. Information Flow The following diagram illustrates the information flow within typical manufacturing and wholesaling organisation.

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.

Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,

Jan Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,

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.

Use Case Modeling - II Lecture # 27.

Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.

Use Case Model Use case diagram.

UML Use Case Diagrams.

Auburn University COMP 2710 Software Construction Use Case Analysis and Exercises (Part 2) Dr. Xiao Qin Auburn University.

© 2014 Cengage Learning. All Rights Reserved.

Relating Use Cases popo.

IS0514 Lecture Week 3 Use Case Modelling.

Use Case Model Use case diagram – Part 2.

Page 37 Figure 2.3, with attributes excluded

Presentation transcript:

Sept Ron McFadyen1 Include Relationship UC1:Process Sale … Main Success Scenario … 7. Customer pays and System handles payment. … Extensions or alternate flows: 7a. Paying by cash … 7b. Paying by credit: include Handle Credit Payment 7c. Paying by check: include Handle Check Payment

Sept Ron McFadyen2 Include Relationship In the UML diagram Process Sale Handle Check Payment Handle Credit Payment > Process Sale has a dependency on Handle Check Payment, and another dependency on Handle Credit Payment The dashed lines and the stick arrowhead are the correct way to depict dependencies

Sept Ron McFadyen3 Include Relationship Suppose a Purchase order system has two use cases Place Order and Track Order and both contain customer validation. Customer validation could be factored out, resulting in: Validate Customer > Track Order Place Order Customer

Sept Ron McFadyen4 Include Relationship Suppose ATM is a base use case and contains: 1.Show advertisement of the day 2.Include identify customer 3.Include validate account 4.… Validate Account > Identify customer Customer ATM session

Sept Ron McFadyen5 Extend Relationship

Sept Ron McFadyen6 Extend Relationship The extend relationship is typically used for optional behaviour Extend is used to separate optional from mandatory behaviour; extend is used to distinguish variants in behaviour Under a specified condition the base use case is extended with the behaviour specified in the addition use case. We say the addition use case is dependent on the base use case (note the directed line in the drawing)

Sept Ron McFadyen7 Extend Relationship Process Sale collects the payment from the customer. Suppose payment via a gift certificate is considered an exceptional case. See Figure 25.3 > Handle Gift Certificate Payment Cashier Payment, if the Customer presents a gift certificate Process Sale Extension Points: Payment

Sept Ron McFadyen8 Extend Relationship Process Sale declares/states “Payment” is an extension point, but Process Sale does not know anything else: the condition, the name of the other addition use case. (see page 389) > Handle Gift Certificate Payment Cashier Payment, if the Customer presents a gift certificate Process Sale Extension Points: Payment