Copyright 03/15/20021 CREATING A FOREST ONE GROVE AT A TIME Regenerative Reengineering©

Slides:



Advertisements
Similar presentations
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Advertisements

Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
System Development Life Cycle Process of creating and altering systems or software by using methodologies or models to develop the systems in a logical.
CLEANROOM SOFTWARE ENGINEERING
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
LARGE SYSTEMS IMPLETATION PROCESS  Overview Review process diagram homework practice.
Software Engineering.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
Fundamentals of Information Systems, Second Edition
Chapter 10 Information Systems Management. Agenda Information Systems Department Plan the Use of IT Manage Computing Infrastructure Manage Enterprise.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
Chapter 1 Assuming the Role of the Systems Analyst
Business Intelligence Dr. Mahdi Esmaeili 1. Technical Infrastructure Evaluation Hardware Network Middleware Database Management Systems Tools and Standards.
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
Information Technology Project Management by Jack T. Marchewka Power Point Slides by Jack T. Marchewka, Northern Illinois University Copyright 2006 John.
Chapter 14 Maintaining Information Systems
C ALL C ENTER O PTIMIZATION P ROJECT J.P. Cap + Vitality, Inc. | J.P. Cap |
Chapter 13 Organizing Information System Resources MIS Department Centralization and Decentralization Outsourcing Computer Facilities and Services.
© Copyright High Performance Concepts, Inc. 12 Criteria for Software Vendor Selection July 14, 2014 prepared by: Brian Savoie Vice President HIGH.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
CLEANROOM SOFTWARE ENGINEERING.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
1 IT Project – Project Lifecycle, methodologies, tools, resources and other issues.
Information Systems Technology Ross Malaga "Part III - Building and Managing Information Systems" III 11 Copyright © 2005 Prentice Hall, Inc MANAGING.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
1 © 2011 Infosys Ltd. Pay Per Test Case Presented At STEP AUTO 2011 – ERP testing Conference – Dec 8, 2011 by Jitendra Atale, Project Manager – Package.
CS1: Classic Software Life Cycle “Waterfall” method: 1.Requirements/Analysis Determine the problem to be solved – client-centered 2.Specification.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
MERCURY BUSINESS PROCESS TESTING. AGENDA  Objective  What is Business Process Testing  Business Components  Defining Requirements  Creation of Business.
Chapter 1. Introduction.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Copyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin CHAPTER NINE SYSTEMS DEVELOPMENT AND PROJECT MANAGEMENT CHAPTER.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
XLIX Engineering Design Firm © 2010 ENGR/ETGR Definition of Project 1 A project is “…a combination of human and non-human resources pulled together.
Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
MITM743 Advanced Project Management Dr. Abdul Rahim Ahmad Assoc. Professor College of IT, UNITEN Kerzner Chapter 4 Project Management Methodologies.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
Chapter 2: The Process. What is Process? Software Engineering Process is the glue that holds the technology layers together and enables rational and timely.
Embedded Systems Software Engineering
Chapter 14 Maintaining Information Systems
Methodologies and Algorithms
Computer Jobs Data Entry Operators Computer Librarians
APQP Five Phase Process
Lecture 3 Prescriptive Process Models
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Building Information Systems
Fundamentals of Information Systems, Sixth Edition
Principles of Information Systems Eighth Edition
Chapter 18 Maintaining Information Systems
Modern Systems Analysis and Design Third Edition
School of EE and Computer Science
Introduction to Software Engineering
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Object Oriented Analysis and Design
Software life cycle models
Cost Xpert Group Copyright © 2001, Marotz, Inc..
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Chapter 8 Software Evolution.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Software Development Life Cycle Models
Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
Information Technology Project Management
OU BATTLECARD: WebLogic Server 12c
Presentation transcript:

Copyright 03/15/20021 CREATING A FOREST ONE GROVE AT A TIME Regenerative Reengineering©

Copyright 03/15/20022 How Important is Good Project Management? The Standish Group International, Inc. in The CHAOS Report: “In over 8,000 projects conducted by 350 companies, only 16 percent of the projects were considered successful … delivered on time and within budget”

Copyright 03/15/20023 Department of Defense Software Study 29 % -paid for, but not delivered 20% - used, but extensively reworked or abandoned 2% - used as delivered 46% - delivered, but not successfully used 3% - used after changes

Copyright 03/15/20024 WHO GETS TO SAY WHAT THE FOREST LOOKS LIKE? Goal setters They only see what they know

Copyright 03/15/20025 WHO GETS TO SAY WHAT THE FOREST LOOKS LIKE? Business processors They are busy running the business and not looking to the future

Copyright 03/15/20026 WHO GETS TO SAY WHAT THE FOREST LOOKS LIKE? Technicians They only see technology but not the corporate goals

Copyright 03/15/20027 WHO GETS TO SAY WHAT THE FOREST LOOKS LIKE? Goal setters Business processors Technicians Together the competitive advantage is created

Copyright 03/15/20028 Experience Large Insurance Company Reuse Very Low Very High Modifiable Maintenance Cost 1/3 Less Maintenance Cost New Controlled Methodology Waterfall Development Methodology Legend: Costs On Budget 1/3 Over Budget Reliable Zero Defects Many Defects Time 3 Years to Produce 2 Years to Produce Efficient 1,500 Claims per Hour 15,000 Claims per Hour

Copyright 03/15/20029 Waterfall Software Development Domain Analysis / Waterfall Development Methodology Research Design Code Test Domain Analysis Methods Tuning Domain Engineer Domain AnalysisDomain ModelsOther Inputs Existing Systems Domain Expert Domain Analyst Reuse Manager Usage Data Reusable Resources Asset Manager Librarian System

Copyright 03/15/ Task A Task C Task B Task D Task E Task F Demonstration Pert Chart Task G First H In this example Task A and Task H are the critical time path. So a lot of time will be spent reviewing the progress of this critical time path.

Copyright 03/15/ Task A Task C Task B Task D Task E Task F Demonstration Pert Chart Task G Task H Even though Task A and Task H are the critical time path Task D is the critical technical factor for completing the project on schedule. If Task D extends past the node at the end of A this will force the project to be late.

Copyright 03/15/ Task A (More People Working) Task C Task B Task D Task E Task F Demonstration Pert Chart Task G (More People Working) Task H We need several ways of looking at the critical path. Task A and Task G may be able to be implemented to reduce the risk of a project overrun.

Copyright 03/15/ Regenerative Reengineering Philosophy / Paradigm Business Requirement Technical Need Technical Advantages Selected Upgrade Produce Technology Created Business Advantages Provides New Business/ Technology Insight Negotiation

Copyright 03/15/ Critical Business/ Technology Identify Plausible Alternatives Identify Existing Tools / Functions Select Best Alternatives to Advance Reengineering Phase I Phase II Phase III Phase IV Study of the Forest and the Trees

Copyright 03/15/ Study Alternatives Select Best and Fall-back Alternatives Critical Business/ Technology Identify Plausible Alternatives Identify Existing Tools / Functions Select Best Alternatives to Advance Reengineering Phase I Phase II Phase III Phase IV

Copyright 03/15/ Complete Study of Alternatives Design Specifications Identify New Tools / Functions Critical Business/ Technology Identify Plausible Alternatives Identify Existing Tools / Functions Select Best Alternatives to Advance Study Alternatives Select Best and Fall-back Alternatives Reengineering Phase I Phase II Phase III Phase IV Most methodologies contain these processes

Copyright 03/15/ Write Specifications Code Programs or Design Processes Create New Tools / Functions Debug Items Install Operate Reengineering Phase I Phase II Phase III Phase IV Create Groves to make it easy to create a forest Creating the forest from pre-created groves

Copyright 03/15/ Critical Business/ Technology Identify Plausible Alternatives Identify Existing Tools / Functions Select Best Alternatives to Advance Study Alternatives Select Best and Fall-back Alternatives Complete Study of Alternatives Design Specifications Identify New Tools / Functions Write Specifications Code Programs or Design Processes Create New Tools / Functions Debug Items Install Operate Reengineering Phase I Phase II Phase III Phase IV

Copyright 03/15/ Technical Goals Technical Requirements Customer Driven Corporate Goals Business Goals Business Requirements Combined Business/ Technical Requirements Knowledge Reusable Business Process or Code Create Reusable Business Process or Code

Copyright 03/15/ KNOWLEDGE DATA TIME BUSINESS FUNCTIONS BUSINESS PROCESSES BUSINESS REQUIREMENTS TECHNICAL FUNCTIONS TECHNICAL PROCESSES TECHNICAL REQUIREMENTS

Copyright 03/15/ KNOWLEDGE SUPPORTS BUSINESS Management Controls Knowledge Technicians Propose Changes / Enhancements to: Business Capability - Alternatives Business Process - Alternatives Knowledge Usage and Alternatives Technical Alternatives

Copyright 03/15/ CREATING A FOREST ONE GROVE AT A TIME Regenerative Reengineering© Thank You ! ! !