Comprehensive System Development for Effective Outcomes

2. Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel, and it starts with careful planning • Identify the key participants in the systems development process and discuss their roles • Define the term information systems planning and list several reasons for initiating a systems project • Identify important system performance requirements of transaction processing applications that run on the Internet or a corporate intranet or extranet • Discuss three trends that illustrate the impact of enterprise resource planning software packages on systems development Principles of Information Systems, Seventh Edition

3. Systems development often uses tools to select, implement, and monitor projects, including net present value (NPV), prototyping, rapid application development, CASE tools, and object-oriented development • Discuss the key features, advantages, and disadvantages of the traditional, prototyping, rapid application development, and end-user systems development life cycles • Identify several factors that influence the success or failure of a systems development project • Discuss the use of CASE tools and the object-oriented approach to systems development Principles of Information Systems, Seventh Edition

4. Systems development starts with investigation and analysis of existing systems • State the purpose of systems investigation • Discuss the importance of performance and cost objectives • State the purpose of systems analysis and discuss some of the tools and techniques used in this phase of systems development Principles of Information Systems, Seventh Edition

5. An Overview of Systems Development: Participants in Systems Development • Development team • Responsible for determining the objectives of the information system and delivering a system that meets these objectives • Usually consists of stakeholders, users, managers, systems development specialists, and various support personnel Principles of Information Systems, Seventh Edition

6. Figure 12.1: Systems analyst plays an important role in the development team Principles of Information Systems, Seventh Edition

7. Initiating Systems Development • Systems development begins when an individual or group capable of initiating organizational change perceives a need for a new or modified system • Systems development initiatives arise from all levels of an organization • Systems development initiatives are both planned and unplanned • Systems development projects may be initiated for a number of reasons Principles of Information Systems, Seventh Edition

8. Figure 12.2: Typical Reasons to Initiate a Systems Development Project Principles of Information Systems, Seventh Edition

9. Information Systems Planning and Aligning Corporate and IS Goals • Information systems planning: the translation of strategic and organizational goals into systems development initiatives • Aligning organizational goals and information systems goals is critical for any successful systems development effort • Determining whether organizational and information systems goals are aligned can be difficult Principles of Information Systems, Seventh Edition

10. Figure 12.4: The Steps of IS Planning Principles of Information Systems, Seventh Edition

11. Developing a Competitive Advantage • Creative analysis: the investigation of new approaches to existing problems • Critical analysis: the unbiased and careful questioning of whether system elements are related in the most effective or efficient ways • Questioning statements and assumptions • Identifying and resolving objectives and orientations that conflict Principles of Information Systems, Seventh Edition

12. Establishing Objectives for Systems Development: Performance Objectives • Output quality or usefulness • Output accuracy • Output format quality or usefulness • Speed at which output is produced • Scalability of the resulting system Principles of Information Systems, Seventh Edition

13. Cost Objectives • Development costs • Uniqueness costs • Fixed investments • Ongoing operating costs Principles of Information Systems, Seventh Edition

14. Web-Based Systems Development: The Internet, Intranets, Extranets, and E-Commerce • Internet technology enables companies to extend their information systems beyond their boundaries to reach their customers, suppliers, and partners • Dynamic core business application that runs over the Web • Must be reliable and fault tolerant • Must integrate with existing infrastructure • Development and maintenance must be quick and easy Principles of Information Systems, Seventh Edition

15. Systems Development and Enterprise Resource Planning • Popular approaches to acquiring an ERP system: • Comprehensive ERP package • Best of breed • Hybrid Principles of Information Systems, Seventh Edition

16. Systems Development Life Cycles • The systems development process is also called a systems development life cycle (SDLC) • The later in the SDLC an error is detected, the more expensive it is to correct Principles of Information Systems, Seventh Edition

17. Systems Development Life Cycles (continued) • Common systems development life cycles: • Traditional • Prototyping • Rapid application development (RAD) • End-user development Principles of Information Systems, Seventh Edition

18. Figure 12.6: The Traditional Systems Development Life Cycle Principles of Information Systems, Seventh Edition

19. The Traditional Systems Development Life Cycle • Systems investigation: problems and opportunities are identified and considered in light of the goals of the business • Systems analysis: study of existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement • Systems design: defines how the information system will do what it must do to obtain the problem solution Principles of Information Systems, Seventh Edition

20. The Traditional Systems Development Life Cycle (continued) • Systems implementation: the creation or acquiring of various system components detailed in the systems design, assembling them, and placing the new or modified system into operation • Systems maintenance and review: ensures the system operates and modifies the system so that it continues to meet changing business needs Principles of Information Systems, Seventh Edition

21. Prototyping • An iterative approach to the systems development process • Operational prototype: a functioning prototype that accesses real data files, edits input data, makes necessary computations and comparisons, and produces real output • Nonoperational prototype: a mock-up, or model, that includes output and input specifications and formats Principles of Information Systems, Seventh Edition

22. Rapid Application Development, Agile Development, Joint Application Development, and Other Systems Development Approaches • Rapid application development (RAD): a systems development approach that employs tools, techniques, and methodologies designed to speed application development • RAD makes extensive use of the joint application development (JAD)process for data collection and requirements analysis Principles of Information Systems, Seventh Edition

23. The End-User Systems Development Life Cycle • Any systems development project in which the primary effort is undertaken by a combination of business managers and users • End-user-developed systems can be structured as complementary to, rather than in conflict with, existing and emerging information systems Principles of Information Systems, Seventh Edition

24. Table 12.5: When to Use Outsourcing for Systems Development Principles of Information Systems, Seventh Edition

25. Table 12.5: When to Use Outsourcing for Systems Development (continued) Principles of Information Systems, Seventh Edition

26. Factors Affecting Systems Development Success • Degree of change • Continuous improvement versus reengineering • Managing change • Quality and standards • The Capability Maturity Model (CMM) Principles of Information Systems, Seventh Edition

27. Factors Affecting Systems Development Success (continued) • Use of project management tools • Use of Computer-Aided Software Engineering (CASE) tools • Automate many of the tasks required in a systems development effort and enforce adherence to the SDLC • Object-oriented systems development • Approach to systems development that combines the logic of the systems development life cycle with the power of object-oriented modeling and programming Principles of Information Systems, Seventh Edition

28. Figure 12.9: The degree of change can greatly affect the probability of a project’s success Principles of Information Systems, Seventh Edition

29. Figure 12.10: Systems Development Maturity Based on the Capability Maturity Model (CMM) Principles of Information Systems, Seventh Edition

30. Table 12.9: Advantages and Disadvantages of CASE Tools Principles of Information Systems, Seventh Edition

31. Object-Oriented Systems Development • Object-oriented systems development typically involves: • Identifying potential problems and opportunities within the organization that would be appropriate for the OO approach • Defining the kind of system users require • Designing the system Principles of Information Systems, Seventh Edition

32. Object-Oriented Systems Development (continued) • Object-oriented systems development typically involves (continued): • Programming or modifying modules • Evaluation by users • Periodic review and modification Principles of Information Systems, Seventh Edition

33. Systems Investigation • What primary problems might a new or enhanced system solve? • What opportunities might a new or enhanced system provide? • What new hardware, software, databases, telecommunications, personnel, or procedures will improve an existing system or are required in a new system? • What are the potential costs (variable and fixed)? • What are the associated risks? Principles of Information Systems, Seventh Edition

34. Figure 12.12: The Systems Investigation Team Principles of Information Systems, Seventh Edition

35. Figure 12.13: Technical, Economic, Legal, Operational, and Schedule Feasibility Principles of Information Systems, Seventh Edition

36. Object-Oriented Systems Investigation • Key objects can be identified during systems investigation • System objects can be diagrammed in a use case diagram Principles of Information Systems, Seventh Edition

37. The Systems Investigation Report • Summarizes the results of systems investigation and the process of feasibility analysis • Recommends a course of action: continue on into systems analysis, modify the project in some manner, or drop it Principles of Information Systems, Seventh Edition

38. Systems Analysis • Steps of a formalized analysis procedure: • Assembling the participants for systems analysis • Collecting appropriate data and requirements • Analyzing the data and requirements • Preparing a report on the existing system, new system requirements, and project priorities Principles of Information Systems, Seventh Edition

39. Data Collection • Identifying sources of data (internal and external sources) • Collecting data Principles of Information Systems, Seventh Edition

40. Figure 12.17: The Steps in Data Collection Principles of Information Systems, Seventh Edition

41. Data Analysis • Data modeling • Activity modeling • Application flowcharts • Grid charts • CASE tools Principles of Information Systems, Seventh Edition

42. Figure 12.20: A Grid Chart Principles of Information Systems, Seventh Edition

43. Requirements Analysis • Asking directly • Critical success factors (CSFs) • The IS plan • Screen and report layout • Requirements analysis tools Principles of Information Systems, Seventh Edition

44. Object-Oriented Systems Analysis • Problems or potential opportunities are identified • Identifying key participants and collecting data is performed • Instead of analyzing the existing system using data-flow diagrams and flowcharts, an object-oriented approach is used Principles of Information Systems, Seventh Edition

45. The Systems Analysis Report • The systems analysis report should cover: • The strengths and weaknesses of the existing system from a stakeholder’s perspective • The user/stakeholder requirements for the new system (also called the functional requirements) • The organizational requirements for the new system • A description of what the new information system should do to solve the problem Principles of Information Systems, Seventh Edition

46. Summary • Systems development begins when an individual or group capable of initiating organizational change perceives a need for a new or modified system • Information systems planning is the translation of strategic and organizational goals into systems development initiatives • Aligning organizational goals and IS goals is critical for any successful systems development effort • Common systems development life cycles are traditional, prototyping, rapid application development (RAD), and end-user development Principles of Information Systems, Seventh Edition

47. Summary (continued) • Phases of the traditional systems development life cycle: systems investigation, systems analysis, systems design, systems implementation, and systems maintenance and review • During systems investigation, problems and opportunities are identified and considered in light of the goals of the business • Systems analysis involves the study of existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement Principles of Information Systems, Seventh Edition

48. Summary (continued) • Computer-Aided Software Engineering (CASE) tools automate many of the tasks required in a systems development effort and enforce adherence to the SDLC • Object-oriented systems development is an approach to systems development that combines the logic of the systems development life cycle with the power of object-oriented modeling and programming Principles of Information Systems, Seventh Edition