The Systems Development Challenge “Challenges lead to opportunities”

Slides:



Advertisements
Similar presentations
Information Resources Management January 23, 2001.
Advertisements

© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Software Life Cycles ECE 417/617: Elements of Software Engineering
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Chapter 7 CASE Tools and Joint and Rapid Application Development.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
Stepan Potiyenko ISS Sr.SW Developer.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
System Analysis and Design (SAD )
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
Lesson-12 Information System Development-2
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Introduction to Software Engineering Dr. Basem Alkazemi
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Chapter 14 Systems Development. Agenda Reasons for Change System Development Life Cycle (SDLC) Prototyping Rapid Application Development (RAD) Object.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
The Database Development Process
Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will  Understand the systems development life cycle.  Be able.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
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.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
2131 Structured System Analysis and Design
CASE Tool Evolution Computer-aided documentation Computer- aided diagramming Analysis and design tools Automated design analysis Automated.
Managing the development and purchase of information systems (Part 1)
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Information Systems Analysis and Design
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 10 Information Systems Analysis and Design
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
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.
IT Requirements Management Balancing Needs and Expectations.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
Note Excerpts from Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 3: Software Project Management Metrics
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
ANKITHA CHOWDARY GARAPATI
COMM89 Knowledge-Based Systems Engineering Lecture 8 Life-cycles and Methodologies
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
UNIT-1 SOFTWARE PRODUCT AND PROCESS: Introduction – S/W Engineering paradigm – Verification – Validation – Life cycle models – System engineering –
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Chap 4. Project Management - Organising, planning and scheduling
K15T2-Team 5- PoD Team Software Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
1 Chapter 3: Project Management Chapter 22 & 23 in Software Engineering Book.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Role of The Software Development Plan (SDP)
Pragmatics 4 Hours.
CASE Tools and Joint and Rapid Application Development
Software Engineering and Best Practices
SISTEM INFORMASI PRODUKSI.
Software Development Process
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
The Methodology for Business Transformation
System architecture, Def.
Presentation transcript:

The Systems Development Challenge “Challenges lead to opportunities”

Software Crisis!

Software’s Chronic Condition is illustrated by years of: u Canceled or seriously delayed projects u Significant cost overruns u Low productivity u Low system quality l number of defects per x lines of code l not meeting the user’s requirements

The Systems Development Challenge (Quality versus Productivity) QUALITYQUALITY Defects = 0 Defects = 0 PRODUCTIVITY (TIME) A B C D Best

The Cost of Systems Development PERCENTOFTOTALCOSTPERCENTOFTOTALCOST Hardware Software Development (includes software, documentation, training, conversion, etc.)

QUADRUPLE CONSTRAINT u Budget u Schedule u People u Capability

IT: MANAGEMENT ISSUES u Right-sizing the information technology organization u Project backlogs of several years u Projects being late and over budget u User dissatisfaction with both the systems development process and the deliverable products u Hardware and software integration issues u The merger and centralization of voice, data, and video technologies u Concerns for effectively implementing notions such as continuous process improvements, total quality management, and applying for the Malcolm Baldridge Quality Award u Inter/Intra/Extranet development; Java; Corba/Com

SYSTEMS DEVELOPMENT RISKS u Inadequate measurement - cost of user u Excessive schedule pressure u Management malpractice u Creeping user requirements u Canceled projects - 50% for => 1M SLOC

Systems Analyst: Do you want to be one? u Artistic/Creative u Highly Cognitive u Black Art u Miracles u Seat-of-the-Pants u Coding = Productivity u Let the maintenance team worry about that u Sleepless Nights u Long Hours u Frustration u Ulcers/Pills u Loss of Hair u Broken Homes, Marriages, Relationships u Over Budget u Late Projects

Software Engineer: Do you want to be one? u Scientific u Standards u Structure u Details u Rigor u Quality u Productivity u On-time Projects u Within Budget

A SYSTEMS DEVELOPMENT ARCHITECTURE SYSTEMS DEVELOPMENT LIFE CYCLE FRAMEWORK Automated Software Engineering Environment (SEE, SDE, IPSE, etc.) Methodology #2 Methodology #n Methodology #1 I-CASE Technology (Management, Techniques, & Tools) REPOSITORY

SYSTEMS DEVELOPMENT LIFE CYCLE FRAMEWORK u Planning u Scheduling u Estimating u Monitoring u Feedback u Work Breakdown Structure u WBS Precedence Structure u Development Heuristics u Standards Management Strategy Component Development Strategy Component

REPOSITORY u Standards u Methodologies u Plans u Budgets u Schedules u Documentation u Reusable Templates u Expert Assistance u Examples u Etc... u Enterprise Modeling u Strategic Planning u Data Modeling u Process Modeling u Object Modeling u Prototyping u Code Generation u Testing (validation & verification) u Clean Room Engineering u Design Recovery/Reengineering u Reuse Engineering u Etc... Systems Development Component Management & Guidance Component