Business Models Modeling.

Slides:



Advertisements
Similar presentations
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Advertisements

A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Analysis and Design with UML
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Use-case Modeling.
UML Class Diagram and Packages Written by Zvika Gutterman Adam Carmi.
Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.
SwE 313 Case Study Registration System.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
© Copyright Eliyahu Brutman Programming Techniques Course.
Requirements Analysis Activity Diagrams b511.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
COMP1007 Intro to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis Lecture.
SE-565 Software System Requirements More UML Diagrams.
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML.
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Page 1 What is the UML? UML stands for Unified Modeling Language The UML combines the best of the best from – Data Modeling concepts (Entity Relationship.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Page 1  Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling captures essential parts of.
Page 1 R Copyright © 1998 by Rational Software Corporation Visual Modeling and the UML.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
UML-1 3. Capturing Requirements and Use Case Model.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
COP43311 Copyright © 1997 by Rational Software Corporation Unified Modeling Language (UML) Based on slides and papers from Rational’s UML website
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.
1 The Unified Modeling Language. 2 The Unified Modeling Language (UML) is a standard language for writing software blueprints. The UML may be used to.
Business Analysis with For PG MDI, Gurgaon Kamna Malik, Ph.D.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML Presentation was downloaded (and is available for free) from Rational.
Systems Analysis and Design in a Changing World, Fourth Edition
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
Essentials of Visual Modeling w/ UML Instructor Notes
UML Activity Diagrams.
Chapter 3: Introducing the UML
UML - Development Process 1 Software Development Process Using UML.
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.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
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.
GOVT. ENGINEERING COLLEGE, AJMER. A SEMINAR PRESENTATION ON UNIFIED MODELING LANGUAGE(UML) SUBMITTED TO:-PRESENTED BY:- Dr. REENA DADHICHPALLAVI VASHISTHA.
Systems Analysis and Design in a Changing World, Fourth Edition
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Recall The Team Skills Analyzing the Problem (with 5 steps)
Object-Oriented Analysis and Design
Unified Modeling Language
UML SEQUENCE AND CLASS DIAGRAMS
UML Activity Diagrams.
The Unified Modeling Language
Use Case Modeling - techniques for detailing use cases
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Unified Modeling Language
UML Class Diagram.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
BPMN - Business Process Modeling Notations
Software Design Lecture : 15.
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Case Analysis – continued
Behavioral Diagrams P. P. Mahale
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Software Development Process Using UML Recap
Presentation transcript:

Business Models Modeling

Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers (users) do before using our system? What business value does the system bring? What is the business system (process) this computer system will be supporting? How do you know you have identified all system use cases?

Business Modeling Why Business Modeling ? Business complexity Need to understand the structure and dynamics of the organization Common understanding of the organization Unified Modeling Language (UML) Graphical language Visualize Specifying construction Documenting artifacts Use the business use case and business object model

Find Business Actors and Use Cases Purpose To outline the processes in the business. To define the boundaries of the business to be modeled. To define who and what will interact with the business. To create diagrams of the business use-case model. To develop a survey of the business use-case model.

Find Business Actors A business actor candidate is any individual, group, organization, company, or machine that interacts with the business, such as: Customers Partners Suppliers Authorities (legal, regulatory, and so forth) Subsidiaries Owners and investors (decide whether the board of directors should be part of the business or modeled as an actor) Information systems outside of the business If the business you're going to model is part of a large company, these categories may also contain business actors: Other parts of the company Individual roles within other departments Name each business actor in such a way that its name denotes its role in the business. Define each business actor by writing a brief description, including its responsibility and why it interacts with the business.

Find Business Use Cases To find the primary business use cases, consider what value each business actor gets from the business. Start with the primary and most important business actors — the customers — and ask yourself: What are the primary services a customer receives from the business? A good tip is to study the customer's lifecycle to determine the answers to such questions as: What was the customer's first contact with the business?  What stages or states does the customer go through in relation to the business? From a perspective of supporting the business, processes can also be represented as business use cases. Look for the following kinds of activities: Develop and maintain the staff Develop and maintain the IT within the business Develop and maintain the office Security Legal activities From the perspective of managing the business, processes can be represented as business use cases, although they are seldom as interesting from an information-system perspective. These types of processes are found by looking for activities that have to do with managing the business as a whole and they normally interact with the owner actors. Consider what the owner actors gets from the business. Look for these kinds of activities: Develop and provide information about the business to owners and investors Set up long-term budget goals Coordinate and prioritize between the other use cases in the business Create new processes in the business Monitor the processes in the business

Prioritize Business Use Cases Once you've identified the business actors and business use cases, you must prioritize those business use cases that are of interest and that you'll describe in some detail. This involves: Determining what business use cases are of interest to the intended system if you perform business engineering to find requirements on information systems. These need to be described in detail Developing a step-by-step description before you make a decision whether to include them or not for business use cases where you cannot clearly see their relevance from an information-system perspective, .

Develop an Outline of the Workflow of Business Use Cases Often, you need a step-by-step outline of the workflow to understand the purpose of the business use case. The person who will later specify the business use case—even if it's the same person—will need this step-by-step description. Example: The first draft of a step-by-step workflow description of the business use case "Individual Check-in" might look as follows. Passenger enters the queue to the check-in counter. Passenger gives ticket to check-in agent. Check-in agent validates ticket. Check-in agent registers baggage. Check-in agent reserves seat for the passenger. Boarding card is printed. Check-in agent gives passenger boarding card. Passenger leaves the check-in counter. Note that this is a first draft, so it may very well lack activities that will be discovered later. You may also include alternative flows in this first draft.

Describe How Business Actors and Use Cases Interact Establish those business actors who interact with the business use case by defining a communicates-association between them. If it's important to show who initiated the communication, you can add navigability to the association.

Final steps Package Business Use Cases and Actors Present the Business Use-Case Model in Use-Case Diagrams Use-case diagrams illustrate the combination of business actors, business use cases, and their relationships. A diagram may contain any of the following: a business actor and all the business use cases with which he or she interacts business use cases that interact with the same business actors business use cases that are usually performed in a sequence business use cases that belong to the same use case package a diagram of the most important business use cases, which can function as a summary of the complete business use-case model and can help in reviewing the model Develop a Survey of the Business Use-Case Model The Survey Description of the business use-case model needs to convey the following information: the purpose of the business being described the typical sequences in which the business use cases are employed the parts of the business that are not included in the business use-case model Evaluate Your Results all necessary business use cases are identified any unnecessary business use cases are identified the behavior of each business use case is described in the right order each business use case's workflow is as complete as it could be at this stage the Survey Description of the business use-case model makes it understandable

UML conventions for use case as a business model Icons Stick man (actor) Oval with slash (process)

Business Modeling with the UML

The UML provides different diagrams Each UML diagram provides a different view of the business: use case diagrams describe the business context. activity diagrams describe behaviors in the business, or business workflows. class diagrams describe the static structure in the business. interactions diagrams (sequence diagrams and collaboration diagrams) describe the dynamic interactions between employees and things that they manipulate. Thus they indicate how the behaviors described in activity diagrams are realized.

Use-Case Diagrams

Activity Diagrams A business activity diagram provides a graphical way to document a business workflow. It provides a simple and intuitive illustration of: what happens in a workflow, what activities can be done in parallel, whether there are alternative paths through a workflow.

What Is an Activity Diagram? An activity diagram in the use-case model can be used to capture the activities and actions performed in a use case. It is essentially a flow chart, showing flow of control from one activity or action to another. Activity 1 Activity 3 Activity 2

What Is an Activity? A specification of behavior expressed as a flow of execution via sequencing of subordinate units. Subordinate units include nested activities and ultimately individual actions. May contain boolean expression constraints when the activity is invoked or exited Activity 2 <<Precondition>> Boolean constraint Activity 4 <<Postcondition>> Boolean constraint Activity 5

Example: Activity Diagram Decision Activity/Action Select Course Concurrent Threads [ delete course ] Delete Course [ add course ] Synchronization Bar (Fork) Guard Condition Check Schedule Check Pre-requisites Synchronization Bar (Join) [ checks completed ] [ checks failed ] Assign to Course Resolve Conflicts Transition Update Schedule

business activity diagram An Activity Diagram documenting how the business performs a Proposal process, with three areas of responsibilities (Customer Sales Interface, Proposal Owner, and Quote Owner).

Show business entities being manipulated in the activities. An activity diagram showing business entities (a Proposal, a Quote, a Plan) and their states (created/complete).

Business class diagrams To show which business workers and business entities are collaborating to implement a business process. To show static structure and relationships among business entities. A class diagram would be used to represent the org chart of a business (using organization units and business workers). A class diagram showing relationships between business workers (Check-in Agent, Baggage Coordinator) and business entities (Baggage, Baggage Tag), showing that the Check-In Agent has the knowledge of a Baggage Tag, but the Baggage Coordinator does not. A class diagram showing relationships among business entities.

A business collaboration diagram A collaboration diagram showing a view of participating business workers (Sales Person, Solution Owner) and business entities (Customer Profile, Sales Plan, etc) in a Proposal process.

Practice draw; (1) Use Case Diagram, (2)Activity Diagram and (3) a Business Class Diagram for the following system Business Process to be implemented UTD wants to computerize its registration system The Registrar sets up the curriculum for a semester One course may have multiple course offerings Students select four (4) primary courses and two (2) alternate courses Once a student registers for a semester, the billing system is notified so the student may be billed for the semester Students may use the system to add/drop courses for a period of time after registration Professors use the system to set their preferred course offerings and receive their course offering rosters after students register Users of the registration system are assigned passwords which are used at logon validation