UNIT – II BUSINESS PROCESS MANAGEMENT

Slides:



Advertisements
Similar presentations
Requirements gathering
Advertisements

System Development Life Cycle (SDLC)
BUSINESS PLUG-IN B2 Business Process.
Introduction to System Analysis and Design
Lecture 13 Revision IMS Systems Analysis and Design.
Introduction to Software Engineering Dr. Basem Alkazemi
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 5.
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Business Plug-In B2 Business Process.
Enterprise Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 System and Software Engineering.
Team Skill 1 Analyzing the Problem Business Modeling (6) 1.
Introduction to Information System Development.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Lesson 1 Week01.
Principles of User Centred Design Howell Istance.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
ITEC224 Database Programming
Business Analysis and Essential Competencies
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
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.
Lecture 7: Requirements Engineering
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Lecture 1 The University of Lahore Software Engineering Saeed Akhtar
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
TAL7011 – Lecture 4 UML for Architecture Modeling.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin Business Plug-In B2 Business Process (on OLC)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
The Systems Development Environment Systems Analysis and Design II.
Performance & Development Review System This brief overview of the new Performance and Development Review will serve to introduce you to the reasons why.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Project Management. What is Project Management? Project : A group of milestones or phases, activities or tasks that support an effort to accomplish something.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Chapter 1 Assuming the Role of the Systems Analyst.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Information Technology Planning
Introduction to UML.
Business process management (BPM)
BUSINESS PLUG-IN B2 Business Process.
Chapter 1: Introduction to Systems Analysis and Design
Systems Planning and Analysis
TIM 58 More on Chapter 1: Introduction to Systems Analysis and Design
TECHNOLOGY PLUG-IN T12 BUSINESS PROCESS.
BUSINESS PLUG-IN B2 Business Process.
Object-Oriented Analysis and Design
Business process management (BPM)
System Design and Modeling
Principles of Programming and Software Engineering
SYSTEMS ANALYSIS Chapter-2.
Introduction to System Analysis and Design
University of Central Florida COP 3330 Object Oriented Programming
BUSINESS PLUG-IN B2 BUSINESS PROCESS.
Dokumentasi Perubahan Proses: Pengantar BPM
How does a Requirements Package Vary from Project to Project?
UML: Unified modeling language
Object Oriented Analysis and Design
CS385T Software Engineering Dr.Doaa Sami
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Chapter 1: Introduction to Systems Analysis and Design
Department of Computer Science Abdul Wali Khan University Mardan
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 1: Introduction to Systems Analysis and Design
Implementation Business Case
Presentation transcript:

UNIT – II BUSINESS PROCESS MANAGEMENT DEPARTMENT OF MANAGEMENT STUDIES UNIT – II BUSINESS PROCESS MANAGEMENT 10/4/2017 Dr. G. MAHESWARAN/AP

Introduction Business Process Management is a means to study, identify, change, and monitor business processes. Business Process Management is a generic term, that encompasses the techniques, structured methods, and means to streamline operations and increase efficiency. BPM techniques and methods enable you to identify and modify existing processes to align them with a desired (improved) future state. The automation of manual tasks Re-engineering the Enterprise Change Management Six Sigma A management methodology Workflow or BPM technology 10/4/2017 Dr. G. MAHESWARAN/AP

Principles of BPM: Organise around outcomes not tasks Correct and improve processes before (potentially) automating them Establish processes and assign ownership Standardise processes across the enterprise Enable continuous change Improve existing processes, rather than build radically new or ‘perfect’ processes 10/4/2017 Dr. G. MAHESWARAN/AP

Typical Business Drivers      Typical Business Drivers Perceived or Expected Benefits: Reduce staff and office overhead numbers Process business critical activities faster Reduce the number of errors and exceptions Reduce overall IT costs Reduce duplications Increase visibility into operational efficiencies and bottlenecks Reduce business risks Improve customer service and retention 10/4/2017 Dr. G. MAHESWARAN/AP

Methods In analysis work - consistency of methods of collection and delivery are essential There are many different types of methods The use of any method is typically much more effective than none - or a loose hybrid This presentation introduces you to three potential approaches for both business and technology process analysis Business Process Analysis Structured Analysis Object-oriented Analysis 10/4/2017 Dr. G. MAHESWARAN/AP

1. Business Process Analysis Most common starting point is when something is not right in the organisation… A meta problem: there are duplicative processes and information across departments A business problem: exception rate is too high A micro problem: some user interface screens are confusing Business Analyst needs to evaluate the situation from various angles and identify core issues review any documentation, interview workers flowchart/document current process recommend improvements When to use: When you have already clearly identified a specific process or process for improvements 10/4/2017 Dr. G. MAHESWARAN/AP

2. Object-Oriented Analysis Centered around understanding of Objects and Classes Class - A class describes the characteristics of a thing (attributes, behaviors, properties, etc.) Object - An instance of a class modeling techniques linked to UML (Unified modeling Language) and software engineering Analysis focuses on “use cases” Makes use of Sequence Diagrams, Class Models, and Activity Diagrams When to use: When you wish to improve a specific business applications’ performance and usability 10/4/2017 Dr. G. MAHESWARAN/AP

3. Structured Analysis Views a “System” as a collection of processes executed according to certain logic (or illogic!) Focuses on data flows Models Data and Processes separately Makes use of Data Flow Diagrams, Relationship Diagrams, and Flowcharts When to use: When you wish to improve your existing IT investment infrastructure and gain greater process efficiencies in the enterprise 10/4/2017 Dr. G. MAHESWARAN/AP

Flowcharts Defined A graphical representation of the sequence of activities, steps, and decision points that occur in a particular, discrete process. To explain the sequence of a process graphically To improve communication and obtain business-user validation To identify bottlenecks and loops To assist with problem analysis To provide a blueprint for development To identify variations in process activity 10/4/2017 Dr. G. MAHESWARAN/AP