Quick Intro to Business Process Re-engineering Basic Introduction Important notice: –This handout is a much simplified version of three handouts: –11.2.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
Maths Counts Insights into Lesson Study
An Integrated Approach to Enterprise Architecture LIACS, Martijn Wiering 23 juni ‘04.
Unified Modeling Language Sequence Diagrams Chapter 2 (JIA)
Chapter 15: System Modeling with UML
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 The.
Documenting Requirements using Use Case Diagrams
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 5, 2001 Introduction.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
UFCEPM-15-M Object-oriented Design and Programming Jin Sa.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
1 An introduction to design patterns Based on material produced by John Vlissides and Douglas C. Schmidt.
Chapter 7: The Object-Oriented Approach to Requirements
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
Slide 12.1 © The McGraw-Hill Companies, CS 4310: Software Engineering Lecture 7 Systems Analysis Object-Oriented Design.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
© 2000 Ian Alexander - Introduction to Scenarios Introduction to Scenarios A range of techniques for engineering better systems Ian Alexander
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
IS0514Slide 1 IS0514 Lecture - Week 1 (Semester 2) Business Systems Development Tools and Techniques.
Business Process Change and Discrete-Event Simulation: Bridging the Gap Vlatka Hlupic Brunel University Centre for Re-engineering Business Processes (REBUS)
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
1 Change and restructuring, Re-engineering Geoff Leese September 2005 revised September 2006, August 2008, August 2009.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
SWT - Diagrammatics Lecture 4/4 - Diagramming in OO Software Development - partB 4-May-2000.
Modeling as a Design Technique Chapter 2 Part 1: Modeling Concepts Object-Oriented Modeling and Design Byung-Hyun Ha
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Chapter 5: Software Re-Engineering Omar Meqdadi SE 3860 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
English Language Services
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Unified OO becomes commonly used in the late 1980s Various analysis and design methods The “three amigos” join forces in Rational Software Also include.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Basic Characteristics of Object-Oriented Systems
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
By Mashael AlDayel Introduction to UML. What is UML? UML (Unified Modeling Language) is a graphical language that is suit-able to express software or.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
1 Systems Analysis and Design Behavioral Modeling Chapter 8 (Last one before the Midterm!)
Chapter 5 – System Modeling
Testing Tools & Standards
Chapter 1: Introduction to Systems Analysis and Design
Chapter 5 System modeling
Roberta Roth, Alan Dennis, and Barbara Haley Wixom
The Movement To Objects
Chapter 5 – System Modeling
Introduction to Unified Modeling Language (UML)
Week 10: Object Modeling (1)Use Case Model
System Modeling Chapter 4
Unified Modeling Language
Systems Analysis and Design With UML 2
Appendix A Object-Oriented Analysis and Design
Software Design Methodologies and Testing
Chapter 1: Introduction to Systems Analysis and Design
UML Design for an Automated Registration System
Information system analysis and design
Presentation transcript:

Quick Intro to Business Process Re-engineering Basic Introduction Important notice: –This handout is a much simplified version of three handouts: –11.2 Object modelling –11.3 Dynamic modelling and Business Process Re-engineering (BPR) –11.4 Theories Underlying Approaches to Systems Modelling You can find the original documents at:

Purpose of modelling

Aims of Modelling Social Engineering  Change agent  Support / facilitation    Gain Understanding  Encourage group working 

Modelling paradigms Object orientated –OMT –UML (Unified Modelling Language)

Objects

Objects & Classes Class = Template –In databases = table definition Object = Instance –In databases = a record

Classes Amount of detail shown may vary

Views A model is always context specific. It is never purely a reflection of reality - whatever that is!

Data / Activities Objects / classes have two aspects: –Data = static aspect –Activities = dynamic aspect

Dynamic aspects= Sequence Diagrams (Event traces in OMT)

Enhancements to the sequence diagram

Sequence diagrams - Issues Guard condition Incremental development Limitations

Exercise: Device a sequence diagram for: 1 Two situations (scenarios) involving yourself at work. 2 Items of service claims forms for GPs, 3 Clinical audit within a Hospital department, 4 Multidisciplinary assessment in the community, 5 Commissioning negotiation. 6 A & E Assessment 7 Care Programme Approach review meeting in Psychiatry

(Business) Process Re-engineering (BPR) Before

After BPR

Looking at single objects (state diagrams)

Limitations of BPR Never lived up to initial expectations. original idea radical restructuring of organisations Now a more gradualist, participative approach Why?: –1. BPR methods are crude i.e job satisfaction, informal methods of communication, etc. not analysed –-> more qualitative (i.e. ethnographic) techniques e.g. video analysis ->problems regarding -> quality -> generalisability. –2. Implementation of change not managed.

Summary Systems modelling -> change agent Object oriented modelling Unified Modelling Language (UML) Objects Classes Views PTO

Summary (cont.) Sequence Diagrams: Additions to Sequence diagrams Incremental development Business Process Re-engineering (BPR) Limitations of BPR State Diagrams Appendix - Additional information: –References –Useful Internet links