Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling with UML Virtusa Training Group (2005) Trainer: Ojitha Kumanayaka Duration: 1 hours.

Slides:



Advertisements
Similar presentations
UML an overview.
Advertisements

A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
1 The Business Modeling Discipline. 2 Purpose of Business Modeling  To understand the structure and dynamics of the organization in which a system is.
Object-Oriented Analysis and Design
Introduction To System Analysis and Design
231 Business Modeling - Domain Analysis Most materials taken from the RUP textbook Chapter 8 and OOSE, pp
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Chapter 21 Object-Oriented Analysis
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Use Case Analysis – continued
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.
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
USE Case Model.
UML - Development Process 1 Software Development Process Using UML (2)
UML Unified Markup Language Ziya Karakaya Atılım University, Computer Engineering
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Business Modeling : basic concepts Extracted from Rational UML Profile for business modeling.mht.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
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.
231 Business Modeling - Domain Analysis Most materials taken from the RUP textbook Chapter 8 and OOSE, pp
Introduction To System Analysis and Design
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
School of Electrical Engineering and Informatics | ITB | 2010Arry Akhmad Arman Case Study #1 Library System Arry Akhmad Arman School of Electrical Engineering.
Faculty of Computer & Information Software Engineering Third year
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Approaching a Problem Where do we start? How do we proceed?
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Business Process Change and Discrete-Event Simulation: Bridging the Gap Vlatka Hlupic Brunel University Centre for Re-engineering Business Processes (REBUS)
Systems Analysis and Design in a Changing World, 3rd Edition
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Developed by Reneta Barneva, SUNY Fredonia for CSIT 425 Requirements Modeling.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
UML-1 8. Capturing Requirements and Use Case Model.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
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.
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.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
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.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML - Development Process 1 Software Development Process Using UML.
SYSTEMSDESIGNANALYSIS 1 OO: Chapter 4 Process Modeling Jerry Post Copyright © 1997.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Analysis models and design models
Software Design Lecture : 15.
Business Modeling - Domain Analysis
Software Analysis.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Software Development Process Using UML Recap
Presentation transcript:

Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling with UML Virtusa Training Group (2005) Trainer: Ojitha Kumanayaka Duration: 1 hours

2 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Why need Business Model Business model visualize the business from which intended system is going to develop.

3 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL When need Business Model Business Model is optional but in the case of Requirements are not clear As best practices New business Complex domain Form one business many system To reengineer To improve the business process An organization wide automation of business process

4 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling Scenarios Organization Chart Domain Modeling One business, Many systems Generic Business Model New Business Revamp

5 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling from GIP WorkflowsArtifacts

6 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Problem Statement Describe the System Goals Benefits Business Requirements specification 1. Project Vision

7 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Why use UML for Business Modeling ? UML provide common language for both business analyst and developer. UML is visualize business process to developer UML support OO, therefore no need of extra effort to adapt business model (business) to OO development. Business process can be described structurally and dynamically because UML support structural and dynamic views. Because UML is better to derive system requirement easily, tradability is easy from development to business model. In general, no need of learning curve to understand new language tool by both business analysts and developers.

8 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL UML Profile for Business Modeling Standard UML is not sufficient to describe business process. Therefore Extended UML Business Modeling Profile has been introduced for business modeling.

9 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL …UML Profile for Business Modeling According to the UML, the profile has been created using UML extendibility via Stereotypes Tags Constraints

10 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL UML Profile for Business Modeling According to the UML Business Modeling Profile, Business Model consisting basically two sub models, Business Use Case Model Business object (analysis) Model Business Use Case Model is realized by Business Analysis/Object Model

11 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Modeling for GIP Business Use Case Model Business Object Model Business Requirements Specification 5.4 Detailed Business Requirements

12 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL UML Profile for Business Modeling IconStereotype >: Used to structure the business in to parts. Such as units, departments or divisions >:Sequence of actions business perform to complete self-dependent task. >: Define business use case realization in terms of business objects. >: Generally the “things” which persist the business information in the business process. >: The roles people play in the organizations. >: Users of the business.

13 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Use Case Model Business use-case model: Identify the business actors and the business use cases that the actors use.

14 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL …Business Use Case Model The Business use-case model allows the modelers to understand better what value the business provides to its actors. >

15 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL How to develop a Business Model Business object model: This consist of actors, workers, entities and organizational units. The business object model realize the business use case model. >

16 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL The Asset Paradox Typically, a knowledge enterprise sells knowledge, whereas a knowledge industry sells its capability to apply and deploy its knowledge packaged as, for example, software

17 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Knowledge Industry

18 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Automation In a bank called ABC, customers need to have at least one account to apply for loan. After the BPR, bank optimized it loan apply operations. Now customers need to meet only Clerk who will take rest of the work with Loan Specialist to get approval for loan. Account details are secured but customer profiles shared with loan specialist.

19 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Models and actors of the systems (1 st Step) Begin with business workers in the business object model For each business worker identify a candidate system actor. Create candidate business use case for candidate system actor.

20 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Automate Business workers (2 nd Step) Business workers can be removed either by Completely replace business worker by automating his entire process Partially automate business worker process and convert as a system actor who directly communicate with the intended system. The responsibilities of business worker will be moved to System System as well as system actor Responsibilities

21 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Business Model and Entity classes in the Analysis Model (3 rd Step) Attributes of the business entity might corresponds to entities in the analysis model.

22 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Productization aspects Business Model fulfill the productization aspect in the following manner Customize same system for different environments Create family of product for same business. For example, Order handling system and billing system.

23 Copyright ©2004 Virtusa Corporation | CONFIDENTIAL USA UK INDIA SRI LANKA