6-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 6 Systems Development Steps, Tools, and Techniques

6-2 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Presentation Overview Seven Phases In The Systems Development Life Cycle Seven Phases In The Systems Development Life Cycle Knowledge Workers and Their Roles In The Systems Development Life Cycle Knowledge Workers and Their Roles In The Systems Development Life Cycle Why Systems Fail Why Systems Fail Selfsourcing Selfsourcing Outsourcing Outsourcing Prototyping Prototyping

6-3 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Introduction Systems development life cycle (SDLC) - a structured step-by-step approach for developing information systems. Systems development life cycle (SDLC) - a structured step-by-step approach for developing information systems.

6-4 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved

6-5 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved

6-6 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Planning phase - involves determining a solid plan for developing your information system. Planning phase - involves determining a solid plan for developing your information system. Critical success factor (CSF) - a factor simply critical to your organization’s success. Critical success factor (CSF) - a factor simply critical to your organization’s success.

6-7 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 1: Plan Project scope – high-level system requirements. Project scope – high-level system requirements. Project scope document – written project scope definition. Project scope document – written project scope definition. Project plan – defines the what, when, and who questions. Project plan – defines the what, when, and who questions. Project milestones - key dates for deliverables. Project milestones - key dates for deliverables. Project manager - an expert in project planning. Project manager - an expert in project planning.

6-8 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 2: Analysis Analysis phase - involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system. Analysis phase - involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system. Business requirements - the detailed set of knowledge worker requests that the system must meet in order to be successful. Business requirements - the detailed set of knowledge worker requests that the system must meet in order to be successful.

6-9 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 2: Analysis Joint application development (JAD) - knowledge workers and IT specialists meet, sometimes for several days, to define or review the business requirements for the system. Joint application development (JAD) - knowledge workers and IT specialists meet, sometimes for several days, to define or review the business requirements for the system. Requirements definition document – prioritizes the business requirements and places them in a formal comprehensive document. Requirements definition document – prioritizes the business requirements and places them in a formal comprehensive document. Sign-off - the knowledge workers’ actual signatures indicating they approve all of the business requirements. Sign-off - the knowledge workers’ actual signatures indicating they approve all of the business requirements.

6-10 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design Design phase - build a technical blueprint of how the proposed system will work. Design phase - build a technical blueprint of how the proposed system will work. Technical architecture - defines the hardware, software, and telecommunications equipment required to run the system. Technical architecture - defines the hardware, software, and telecommunications equipment required to run the system.

6-11 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design Modeling - the activity of drawing a graphical representation of a design. Modeling - the activity of drawing a graphical representation of a design. Graphical user interface (GUI) - the interface to an information system. Graphical user interface (GUI) - the interface to an information system. GUI screen design - the ability to model the information system screens for an entire system. GUI screen design - the ability to model the information system screens for an entire system.

6-12 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 3: Design

6-13 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 4: Development Development phase - take all of your detailed design documents from the design phase and transform them into an actual system. Development phase - take all of your detailed design documents from the design phase and transform them into an actual system.

6-14 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 5: Test Testing phase - verifies that the system works and meets all of the business requirements defined in the analysis phase. Testing phase - verifies that the system works and meets all of the business requirements defined in the analysis phase. Test conditions - the detailed steps the system must perform along with the expected results of each step. Test conditions - the detailed steps the system must perform along with the expected results of each step.

6-15 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved For example, to test cut and paste functionality you must ensure the following:  Cut text  Cut text in each available font  Cut text in each available font for each available size  Cut text in each available font, for each available size, bolded  Cut text in each available font, for each available size, italicized  Cut text in each available font, for each available size, bolded, and italicized  Cut text in each available font, for each available size, bolded, italicized, and underlined  Now all of the same for the paste functionality

6-16 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 6: Implement Implementation phase - distribute the system to all of the knowledge workers for use. Implementation phase - distribute the system to all of the knowledge workers for use. User documentation - how to use the system. User documentation - how to use the system. Online training - runs over the Internet or off a CD-ROM. Online training - runs over the Internet or off a CD-ROM. Workshop training - is held in a classroom environment and lead by an instructor. Workshop training - is held in a classroom environment and lead by an instructor.

6-17 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Seven Phases in the SDLC Phase 7: Maintain Maintenance phase - monitor and support the new system to ensure it continues to meet the business goals. Maintenance phase - monitor and support the new system to ensure it continues to meet the business goals. Help desk - a group of people who responds to knowledge workers’ questions. Help desk - a group of people who responds to knowledge workers’ questions.

6-18 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Knowledge Workers and Their Roles in the SDLC Your participation in the systems development process is vitally important because you are (or will be) a: Your participation in the systems development process is vitally important because you are (or will be) a: 1. Business process expert 2. Liaison to the customer 3. Quality control analyst 4. Manager of other people User acceptance testing (UAT) – determines if the system satisfies the business requirements. User acceptance testing (UAT) – determines if the system satisfies the business requirements.

6-19 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Why Systems Fail 20% of systems are successful, 80% of systems fail. 20% of systems are successful, 80% of systems fail. Five primary reasons why systems fail include: Five primary reasons why systems fail include: 1. Unclear or missing requirements 2. Skipping SDLC phases 3. Failure to manage project scope  Scope creep – project scope increases  Feature creep – developers add extra features 4. Failure to manage project plan 5. Changing technology

6-20 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Insourcing Three choices for building a system include: Three choices for building a system include: 1. IT specialists within your organization - Insourcing 2. Knowledge workers such as yourself – Selfsourcing 3. Another organization – Outsourcing Insourcing - IT specialists within your organization will develop the system. Insourcing - IT specialists within your organization will develop the system.

6-21 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing Selfsourcing (also called knowledge worker development or end user development) - the development and support of IT systems by knowledge workers with little or no help from IT specialists. Selfsourcing (also called knowledge worker development or end user development) - the development and support of IT systems by knowledge workers with little or no help from IT specialists. On Your Own How Have You Selfsourced? (p. 303)

6-22 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing The Selfsourcing Process

6-23 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Selfsourcing Advantages: Advantages:  Improves requirements determination.  Increases knowledge worker participation and ownership.  Increases speed of systems development. Disadvantages: Disadvantages:  Inadequate knowledge worker expertise leads to inadequately developed systems.  Lack of organizational focus creates “privatized” IT systems.  Insufficient analysis of design alternatives leads to subpar IT systems.  Lack of documentation and external support leads to short-lived systems.

6-24 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing Developing Strategic Partnerships Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service. Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service.

6-25 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Outsourcing Process

6-26 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing The Outsourcing Process Request for proposal (RFP) - a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development. Request for proposal (RFP) - a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development.

6-27 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing Advantages: Advantages:  Focus on unique core competencies.  Exploit the intellect of another organization.  Better predict future costs.  Acquire leading-edge technology.  Reduce costs.  Improve performance accountability. Disadvantages: Disadvantages:  Reduces technical know-how for future innovation.  Reduces degree of control.  Increases vulnerability of strategic information.  Increases dependency on other organizations.

6-28 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Outsourcing On Your Own A Request for Proposal and the Systems Development Life Cycle (p. 311)

6-29 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping Prototyping - the process of building a model that demonstrates the features of a proposed product, service, or system. Prototyping - the process of building a model that demonstrates the features of a proposed product, service, or system. Prototype - a model of a proposed product, service, or system. Prototype - a model of a proposed product, service, or system. Proof-of-concept prototype - used to prove the technical feasibility of a proposed system. Proof-of-concept prototype - used to prove the technical feasibility of a proposed system. Selling prototype - used to convince people of the worth of a proposed system. Selling prototype - used to convince people of the worth of a proposed system.

6-30 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Prototyping The Prototyping Process

6-31 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reservedPrototyping Advantages: Advantages:  Encourages participation.  Encourages participation.  Resolves discrepancies  Gives a feel for the final system.  Gives a feel for the final system.  Helps determine technical feasibility.  Helps sell the idea of a proposed system.  Helps sell the idea of a proposed system. Disadvantages: Disadvantages:  Leads to the belief that the final system will follow shortly.  Gives no performance indication.  Leads the team to skip testing and documentation.