1. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition 3 C H A P T E R INFORMATION SYSTEM DEVELOPMENT Part 1

2. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Chapter Three Information System Development Describe the motivation for a system development process in terms of the Capability Maturity Model (CMM) for quality management. Differentiate between the system life cycle and a system development methodology. Define problems, opportunities, and directives—the triggers for systems development projects. Describe the PIECES framework for categorizing problems, opportunities, and directives. Describe the traditional, basic phases of system development. For each phase, describe its purpose, inputs, and outputs.

3. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Chapter Map

4. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Process of System Development A system development process is a set of activities, methods, best practices, deliverables, and automated tools that stakeholders (Chapter 1) use to develop and maintain information systems and software.

5. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition The CMM Process Management Model The Capability Maturity Model (CMM) is a framework to assess the maturity level of an organization’s information system development and management processes and products. It consists of five levels of maturity as measured by a set of guidelines called the key process areas. –Level 1—Initial: System development projects follow no prescribed process. –Level 2—Repeatable: Project management processes and practices are established to track project costs, schedules, and functionality. –Level 3—Defined: A standard system development process (sometimes called a “methodology”) is purchased or developed, and integrated throughout the information systems/services unit of the organization. –Level 4—Managed: Measurable goals for quality and productivity are established. –Level 5—Optimizing: The standardized system development process is continuously monitored and improved based on measures and data analysis established in Level 4.

6. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Capability Maturity Model (CMM) Level 5 OPTIMIZED Level 4 MANAGED Level 3 DEFINED Level 2 REPEATABLE RISK COMPETITIVENESS Level 1 INITIAL

7. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Life Cycle versus Methodology A system life cycle divides the life of an information system into two stages, systems development and systems operation and support. A system development methodology is a very formal and precise system development process that defines (as in CMM Level 3) a set of activities, methods, best practices, deliverables, and automated tools that system developers and project managers are to use to develop and maintain information systems and software.

8. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition A System Life Cycle Conversion Obsolescence Lifetime of a System LIFE CYCLE STAGE System Development using System Development Methodology LIFE CYCLE STAGE System Operation and Support using Information Technology

9. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Principles of System Development Get the owners and users involved. Use a problem-solving approach. Establish phases and activities. Establish standards. Justify systems as capital investments. Don’t be afraid to cancel or revise scope. Divide and conquer. Design systems for growth and change.

10. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Try To Make A Methodology Write down a draft of your own development methodology Try to think of all the steps you might go through to create some software that many people will need to use Pay special attention to the fact that you will have to explain what you are doing to many different people throughout the project

11. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition The Classic Engineering Model Identify the problem Analyze and understand the problem Identify solution requirements or expectations Identify alternative solutions and decide on a course of action Design and implement the “best” solution. Evaluate the results. If the problem is not solved, return to Step 1 or 2 as appropriate

12. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Phases of a Representative Methodology

13. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Overlap of System Development Phases ID 1 2 3 4 5 6 7 8 9 Project management Preliminary investigation Problem analysis Requirements analysis Decision analysis Design Construction Implementation Operations and support MayJunJulAugSepOctNovDecJan 20012002 Task Name

14. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Project Identification and Initiation Problems are undesirable situations that prevent the organization from fully achieving its purpose, goals, and/or objectives. Opportunities are chances to improve the organization even in the absence of specific problems. Directives are new requirements that are imposed by management, government, or some external influence.

15. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition The PIECES Problem-Solving Framework P the need to improve performance I the need to improve information (and data) E the need to improve economics, control costs, or increase profits C the need to improve control or security E the need to improve efficiency of people and processes S the need to improve service to customers, suppliers, partners, employees, etc.

16. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition FAST System Development Phases

17. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition Cross Life Cycle Activities Cross life cycle activities are activities that overlap many or all phases of the methodology. –Fact-finding –Documentation and presentation –Feasibility analysis –Process and project management

18. Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition A repository is a database where system developers store all documentation, knowledge, and products for one or more information systems or projects. Sharing Knowledge via a Repository