1. PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 6 Systems Analysis

2. Copyright © 2004 South-Western. All rights reserved.6–2 Learning Objectives To name the systems development process and its major phases and steps To describe how Information Systems are planned, developed, and acquired or modified, so that those systems can be directed at achieving an organization’s objectives To explain the importance of managing the systems development process to ensure attainment of development objectives

3. Copyright © 2004 South-Western. All rights reserved.6–3 Learning Objectives (cont’d) To describe the nature and importance of your future involvement in systems development To name the goals, plans, tasks, tools, and results of the first two steps in systems development, the systems survey and systems analysis To explain the costs of developing, maintaining, and operating an Information System To list typical Information Systems benefits

4. Copyright © 2004 South-Western. All rights reserved.6–4 Causes of Change in Information Systems Legal requirements, such as government reporting. Level and kinds of competition. Technologies, such as data entry devices, bar codes, and radio frequency identification (RFID) tags used to record and process information. Lines of business or kinds of business activities. Management desire for better access to information and improved management reporting.

5. Copyright © 2004 South-Western. All rights reserved.6–5 Systems Development Life Cycle (SDLC) A formal set of activities, or a process, used to develop and implement a new or modified Information System. The documentation that specifies the systems development process referred to as the systems development standards manual. The progression of Information Systems through the systems development process, from birth through implementation to ongoing use.

6. Copyright © 2004 South-Western. All rights reserved.6–6 Systems Development Objectives To develop information systems that satisfy an organization’s informational, operational, and management requirements.  Note that this objective relates to the system being developed. To develop information systems in an efficient and effective manner.

7. Copyright © 2004 South-Western. All rights reserved.6–7 Systems Development Methodology A formalized, standardized and documented set of activities used to manage a system development project. Steps in a process that should be used when information systems are developed, acquired, or maintained.

8. Copyright © 2004 South-Western. All rights reserved.6–8 System Development Methodology Elements Divide project into processes:  Starting and ending points for activities.  One or more deliverables.  Several management control points. Describe reports and other documentation for deliverables. Require that users, managers, and auditors participate in project. Get approvals (signoffs).

9. Copyright © 2004 South-Western. All rights reserved.6–9 Systems Development Life Cycle FIGURE 6.1

10. Copyright © 2004 South-Western. All rights reserved.6–10 Development Choices at Boston Scientific FIGURE 6.2 Source: Reprinted with permission from Dave Ellard, Vice president Global Systems, Boston Scientific Corporation.

11. Copyright © 2004 South-Western. All rights reserved.6–11 Information System Development: Analysis Phase Purpose Define project goals and scope Develop specifications for new or revised system Tasks Study the problem and user requirements Propose alternative solutions TABLE 6.1a

12. Copyright © 2004 South-Western. All rights reserved.6–12 Information System Development: Design Phase Purpose Develop an appropriate system manifestation Tasks Describe desire features Choose software and hardware Write program specs. Devise implementation plans, systems tests, and training TABLE 6.1b

13. Copyright © 2004 South-Western. All rights reserved.6–13 Information System Development: Implementation Phase Purpose Prepare to begin using the new system Tasks Write, test, and debug the computer programs TABLE 6.1c

14. Copyright © 2004 South-Western. All rights reserved.6–14 Information System Development: Operation Phase Purpose Use the new system Tasks Convert to new or revised system Conduct post- implementation review Perform systems maintenance TABLE 6.1d

15. Copyright © 2004 South-Western. All rights reserved.6–15 Alternative Approaches to the SDLC Rapid applications development (RAD)  A management approach (Joint Application Development) that employs small teams of highly skilled developers using higher-order development tools to develop the system iteratively. Data-structured development  Data modeling is used to develop a conceptual model of an organization’s data that serves as the basis for the development of all subsequent systems.

16. Copyright © 2004 South-Western. All rights reserved.6–16 Alternative Approaches to SDLC (cont’d) Object-oriented (OO) development  Regards the world as a set of objects related to one another and that communicate with one another. Unified modeling language (UML)  Is used to specify, visualize, and document models of software systems, including non-object oriented applications. Extreme programming (XP)  Is a deliberate and disciplined approach to software development that emphasizes customer involvement and promotes teamwork.

17. Copyright © 2004 South-Western. All rights reserved.6–17 Reasons Why Organizations Fail to Achieve Systems Development Objectives Lack of senior management support for and involvement in Information Systems development. Shifting user needs. Development of strategic planning systems. New technologies. Lack of standard project management and systems development methodologies. Resistance to change. EXHIBIT 6.2

18. Copyright © 2004 South-Western. All rights reserved.6–18 Reasons for Project Failure Underestimation of the time to complete the project Lack of monitoring by senior management Underestimation of necessary resources Underestimation of size and scope of the project Inadequate project control mechanism Changing systems specifications Inadequate planning.

19. Copyright © 2004 South-Western. All rights reserved.6–19 Quality Assurance (QA) ISO 9000-3  A set of standards developed by The International Organization for Standards (ISO), that describe what an organization must do to manage their software development processes. Capability Maturity Model: the Capability Maturity Model ® for Software (SW-CMM)  A model that helps organizations evaluate the effectiveness of their software development processes and identifies the key practices that are required to increase the maturity of those processes.

20. Copyright © 2004 South-Western. All rights reserved.6–20 Involvement in System Development Systems specialist Consultant System user Assurance provider Business process reengineering (BPR)  Is “the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical contemporary measures of performance, such as cost, quality, service, and speed.”

21. Copyright © 2004 South-Western. All rights reserved.6–21 Systems Survey Often called a feasibility study or a preliminary feasibility study. Comprised of a set of procedures conducted to determine the feasibility of a potential systems development project. Is the preliminary assessment step to preparing a systems development plan for projects considered feasible.

22. Copyright © 2004 South-Western. All rights reserved.6–22 System Survey Goals Determine nature/extent of systems development. Determine scope of problem. Propose course of action that might solve problem. Determine feasibility of any proposed development. Devise detailed plan for conducting analysis. Devise summary plan for entire project.

23. Copyright © 2004 South-Western. All rights reserved.6–23 Types of Feasibility Technical feasibility  Asking if the problem can be solved using available hardware and software technology. Operational feasibility  Determining if problem can be solved given the organization’s available personnel and procedures. Economic feasibility  Assessing if solution costs are affordable and whether benefits gained exceed the costs of solution.  Does the project compare favorably with competing projects?

24. Copyright © 2004 South-Western. All rights reserved.6–24 Reasons for Project Plan Development To provide a means to schedule the use of required resources. To indicate major project milestones to monitor the project’s progress. To forecast the project budget, which is used to authorize project continuation. To furnish guidelines for making a go or no-go decision. To offer a framework by which management can determine the reasonableness and completeness of the project’s steps.

25. Copyright © 2004 South-Western. All rights reserved.6–25 Systems Analysis Goals Define problem precisely. Devise alternative designs (solutions). Choose and justify one of the alternatives. Develop logical specifications for the selected design. Develop physical requirements for selected design. Develop a budget for next two phases: systems design and systems implementation.

26. Copyright © 2004 South-Western. All rights reserved.6–26 Occurrence of Errors during the SDLC FIGURE 6.3

27. Copyright © 2004 South-Western. All rights reserved.6–27 Cost to Fix an Error or Make a Change during the SDLC FIGURE 6.4

28. Copyright © 2004 South-Western. All rights reserved.6–28 Cost/Effectiveness Study Cost/benefit study (or cost/benefit analysis)  “Which alternative accomplishes the users’ goals for the least cost (or greatest benefit)?” Effectiveness study (or effectiveness analysis).  “Which alternative best accomplishes the users’ goals for the system being developed?”

29. Copyright © 2004 South-Western. All rights reserved.6–29 Physical Requirements Used in Systems Selection Data requirements  Database size, growth, activity, access requirements, and update frequency  Event volume and expected growth, and sources (internal, external) Operations requirements  Peripherals, such as printers, scanners, or PCs  Communications (LANs, Internet, security requirements)  Backup and security  Output distribution, uses, media, and formats Management requirements  Processing approaches (distributed, centralized)  Reliability (e.g., mean time between failure)  Response time requirements TABLE 6.3

30. Copyright © 2004 South-Western. All rights reserved.6–30 Other Deliverables The budget and schedule document.  The budget, estimated during the cost/benefit analysis, specifies the expected costs to complete the systems development.  Schedules control systems development efforts by setting limits on the time to be spent on development activities and by coordinating those activities.