SYSTEMSDESIGNANALYSIS 1 OO: Chapter 4 Process Modeling Jerry Post Copyright © 1997.

Slides:



Advertisements
Similar presentations
Sequence Diagrams Dan Fleck.
Advertisements

Use Cases -Use Case Diagram Chapter 3 1. Where are we? 2 Analysis Chapters Ch 2Investigating System Requirements Ch 3Use Cases Ch 4Domain Modeling Ch.
Karolina Muszyńska Based on:
Unnat-e Infotech 1 Object Oriented Concepts Introduction.
SYSTEMSDESIGNANALYSIS 1 Chapter 9 Data Flow Diagrams Jerry Post Copyright © 1997.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Use cases.
Lecture 5 UML and Modelling Behaviour. UML Unified Modelling Language Successor to a number of Object-Oriented Analysis and Design methods the 3 Amigos:
Chapter 15: System Modeling with UML
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Slide 11C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Copyright W. Howden1 Lecture 4: Sequence Interaction Diagrams.
Requirements Analysis Classes & Associations b510.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
Object Oriented Analysis Process
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to Systems Requirements Lecture 4 Identifying.
Lecturer: Dr. AJ Bieszczad Chapter 66-1 Object-Oriented analysis and design Special nature of OO development Use cases Design with UML OO system design.
Slide 7C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
SwE 313 Introduction to Rational Unified Process (RUP)
Unified Modeling Language
Object-OrientedMethodologies
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
Chapter 8: Actor-System Interaction Modeling
Lecture 7 Object Oriented Design. Outline  What is UML and why we use UML?  How to use UML diagrams to design software system?  What UML Modeling tools.
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 Unified Modeling Language (UML) Case Study.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
CH06: Considering Objects TECH Computer Science  Set, Class, Type  …of…  Objects, Actors, Agents  Data and Actions Object-Oriented Design and Development.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Object Oriented Programming Lecture 9: OO Design.
Component & Deployment Diagram © copyright 2001 SNU OOPSLA Lab.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Use Cases -Use Case Diagram Chapter 3 1. Where are we? 2 Analysis Chapters Ch 2Investigating System Requirements Ch 3Use Cases Ch 4Domain Modeling Ch.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling with UML Virtusa Training Group (2005) Trainer: Ojitha Kumanayaka Duration: 1 hours.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
The Unified Modeling Language (UML)
(14-2) UML Instructor - Andrew O’Fallon CptS 122 (December 2, 2015) Washington State University.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
OOP Review CS 124.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Unit-3 Identifying use cases Object Analysis Classification
UML (Unified Modeling Language)
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
Slide 12F.135 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
UA. Unified Approach ( UA ) It combines best practices, methods process, guidelines & methodology (Rumbaugh, Booch and Jacobson) along with UML notations.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
1 Advanced DataBases Unified Modelling Language An Introduction and Use Case Lecture 2 Susan Curtis.
Use Cases Preparation for Thursday 10/2/14. Process or Workflow Model Concepts Representing task, process, procedure, workflow, actions, decisions Functional.
Introduction to UML.
Use Cases -Use Case Diagram
Unified Modeling Language (UML)
5/11/2018.
Unified Modeling Language—UML A Very Brief Introduction
Creating Use Cases.
Software Design AITI GP John Paul Vergara.
تحلیل و طراحی سیستم‌های شی گرا
ניתוח מערכות מידע א' הרצאה 3
Lecture 4: Sequence Interaction Diagrams
Presentation transcript:

SYSTEMSDESIGNANALYSIS 1 OO: Chapter 4 Process Modeling Jerry Post Copyright © 1997

SYSTEMSDESIGN 2 Use-Case  Ch. 5 Section 7 client operator Support representative Help Desk Make a call Take the call Do research Return a call

SYSTEMSDESIGN 3 Library Example Library Member Borrow Books Get interlibrary loan Return books Do research Read books, news Purchase supplies Circulation clerk Supplier

SYSTEMSDESIGN 4 Library Details: Use Case Borrow Books Get interlibrary loan Return book Do research Read books, news Purchase supplies Check library card Member Circulation clerk Supplier extends uses

SYSTEMSDESIGN 5 Use Case Hints  Getting started  Identify the actors, look for roles, generalization  Look for transactions  Extends association  A process similar to a base, generic process, but handled differently.  Interlibrary loan.  Uses association  If several processes have sub flows in common, create a new process and use it by association.  Check library card.  Guidelines  For each actor, find tasks and functions that they perform with the system.  Name the use cases (use verbs).  Level of detail?  Goal is to show an abstract picture of the system processes.  Use packages (collection of subsystems) if needed.

SYSTEMSDESIGN 6 Unified Modeling Language (UML)  Design Tools  Standardized  New: 1998  Object-Oriented  Programming/Detail  Can be used for business modeling  Use Case  Collaboration  Sequence Charts  Standard  Rose  Booch, Rumbaugh, Jakobson  CASE tools, automated design  Rational Rose  Stirling: IEF, etc.

SYSTEMSDESIGN 7 Sequence Charts CallerExchangeReceiverTalk Off hook Dial tone Dial number Ring tone Off hook On hook Book: time