Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.

Slides:



Advertisements
Similar presentations
Use Case Diagrams.
Advertisements

Chapters 7 & 9 System Scope
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Object-Oriented Analysis and Design
Prof. Dr. Nizamettin AYDIN
Objectives Detailed Object-Oriented Requirements Definitions
Object-Oriented Analysis and Design
 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.
Systems Analysis and Design in a Changing World, Fourth Edition
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Functional Modeling Chapter 6.
Use Case Modeling.
Detailed Object-Oriented Requirements Definitions
DATA FLOW DIAGRAMS IT 155.
Use Case Diagram.
Unified Modeling Language
Chapter 7: The Object-Oriented Approach to Requirements
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Phase 2: Systems Analysis
Chapter 7 Structuring System Process Requirements
Object-Oriented Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Use Cases Week 8 CMIS570. Refresher – Class Diagrams Appointment scheduling example Car Rental example E-Commerce example.
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Kyung Hee University System Functional Model OOSD 담당조교 석사과정 이정환.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
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 Model Use case diagram.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Use Cases and Use Case Diagrams Reporter: 陳雅萍. Outline Use cases, actors Organizing use cases Modeling the behavior of an element Use case diagrams Common.
 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.
ISMT221 Information Systems Analysis and Design Use case diagram Lab 4 Tony Tam.
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.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
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.
Systems Analysis and Design in a Changing World, Fourth Edition
WHAT IS A Context Diagram?
Business Process and Functional Modeling
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
Use case Diagram.
Use Case Model Use case diagram.
Sequence Diagrams Lecture 6.
Chapter 9 Use Cases.
Object Oriented Analysis and Design
Use Cases.
Unified Modeling Language
WHAT IS A Use Case Diagram?
What is a Relationship Map?
INFS 6225 Object Oriented Systems Analysis & Design
Software Design Lecture : 15.
Presentation transcript:

Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.

Introduction A use case is a formal way of representing the way of business system interacts with its environment It ilustrates the activities performed by the users of the system Use cases can document the current system (as-is system) or the new system being developed(to-be system) An activity diagram can be used for any type of process-modeling activity Process models depict how a business system operates They ilustrate the process or activities that are performed and how objects (data) move among them

A process models can be used to document a current system (as-is system) or new system being developed (to-be system), whetever computerized or not. Activity diagram and use case are logical models-models that describe the business domain’s activities without suggesting how they are conducted Logical models are some times referred to as problem domain models

Business Process Identification with Use Cases and Use-Case Diagram

Elements of Use-case Diagram Actors Is a person or system that derives benefit from and is external to the subject Is depictes as either a stick figure (default) or, if nonhuman actor is involved, as a rectangle with > in it (alternative) Is labeled with its role Can be associated with other actors using a specialization/superclass association denoted by an array with a hollow arrohead Is placed outside the subject boundary

Use Case Represebts a major piece of system functionality Can extend another use case Can include another use case Is placed inside the system boundary Is labeled with a descriptive verb-noun phrase An Association Relationship Links an actor with the use case(s) with it interacts An include ralationship An extend relationship

Idenfiying the Major UseCases 1. Review Requirement Definition 2. Identify Subject’s Boundaried 3. Identify Actors & Goals Identify Business Process & Major Use Cases Review Current Set Of Use Cases

Creating a Use-Case Diagram 1. Place & Draw Use Case 2. Place & Draw Actors 3. Draw Subject Bundary 4. Add Associations