1. Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques

2. INTRODUCTION Information systems are the support structure for meeting the company’s strategies and goals Information systems are the support structure for meeting the company’s strategies and goals New systems are created because employees request it New systems are created because employees request it New systems are created to obtain a competitive advantage New systems are created to obtain a competitive advantage Billions of dollars spent yearly on acquisition, design, development, implementation, and maintenance of IT systems Billions of dollars spent yearly on acquisition, design, development, implementation, and maintenance of IT systems Companies depend on information more than ever Companies depend on information more than ever

3. THE SYSTEMS DEVELOPMENT LIFE CYCLE  Systems development life cycle (SDLC)

4. Defining System Success? On time On time On budget On budget Meets requirements Meets requirements

5. Terminology Deliverable Deliverable Milestone Milestone

6. SDLC Phases & Major Activities

7. SDLC as a Waterfall Methodology

8. Phase 1: Planning Planning phase - create a solid plan for developing your information system Planning phase - create a solid plan for developing your information system Three primary planning activities: Three primary planning activities: 1. Define the system to be developed You can’t build every system, so you make choices based on your organization’s priorities, which may be expressed as critical success factors You can’t build every system, so you make choices based on your organization’s priorities, which may be expressed as critical success factors 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

9. Phase 1: Planning 2. Set the project scope Project scope - clearly defines the high- level system requirements Project scope - clearly defines the high- level system requirements Scope creep - occurs when the scope of the project increases Scope creep - occurs when the scope of the project increases Feature creep - occurs when developers add extra features that were not part of the initial requirements Feature creep - occurs when developers add extra features that were not part of the initial requirements Project scope document Project scope document

10. Phase 1: Planning 3. Develop the project plan including tasks, resources, and timeframes Project plan Project plan Project manager Project manager Project milestones Project milestones Other Activities? Other Activities?

11. Phase 1: Planning Sample Project Plan

12. 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

13. Phase 2: Analysis Two primary analysis activities: Two primary analysis activities: 1. Gather the business requirements 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 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

14. Phase 2: Analysis 2. Prioritize the requirements 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 Users sign off on this document which clearly sets the scope for the project Users sign off on this document which clearly sets the scope for the project Other Activities? Other Activities?

15. Phase 2: Analysis Take time during analysis to get the business requirements correct. If you find errors, fix them immediately. The cost to fix an error in the early stages of the SDLC is relatively small. In later stages, the cost is huge.

16. 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 Two primary design activities: Two primary design activities: 1. Design the technical architecture the hardware, software, and telecommunications equipment required to run the system the hardware, software, and telecommunications equipment required to run the system 2. Design system models GUI screens that users will interface with, database designs (see XLM/C), report formats, software steps, etc GUI screens that users will interface with, database designs (see XLM/C), report formats, software steps, etc

17. Phase 3: Design Starting with design, you take on less of an active participation role and act more as a “quality control” function, ensuring that the IT people are designing a system to meet your needs Starting with design, you take on less of an active participation role and act more as a “quality control” function, ensuring that the IT people are designing a system to meet your needs Other Activities? Other Activities?

18. 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 Two primary development activities: Two primary development activities: 1. Build the technical architecture 2. Build the database and programs Both of these activities are mostly performed by IT specialists Both of these activities are mostly performed by IT specialists Other Activities? Other Activities?

19. Phase 5: Testing 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 Two primary testing activities: Two primary testing activities: 1. Write the test conditions 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

20. Phase 5: Testing 2. Perform the testing of the system Unit testing – tests individual units of code Unit testing – tests individual units of code System testing – verifies that the units of code function correctly when integrated System testing – verifies that the units of code function correctly when integrated Integration testing – verifies that separate systems work together Integration testing – verifies that separate systems work together User acceptance testing (UAT) – determines if the system satisfies the business requirements User acceptance testing (UAT) – determines if the system satisfies the business requirements Other Activities? Other Activities?

21. Phase 6: Implementation Implementation phase - distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs Implementation phase - distribute the system to all of the knowledge workers and they begin using the system to perform their everyday jobs Two primary implementation activities Two primary implementation activities 1. Write detailed user documentation User documentation - highlights how to use the system User documentation - highlights how to use the system

22. Phase 6: Implementation 2. Provide training for the system users 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 Other Activities? Other Activities?

23. Phase 6: Implementation Choose the right implementation method Choose the right implementation method Parallel implementation Parallel implementation Plunge implementation Plunge implementation Pilot implementation Pilot implementation Phased implementation Phased implementation

24. Phase 7: Maintenance 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 Two primary maintenance activities: Two primary maintenance activities: 1. Build a help desk to support the system users Help desk - a group of people who responds to knowledge workers’ questions Help desk - a group of people who responds to knowledge workers’ questions 2. Provide an environment to support system changes  Other Activities?

25. Sourcing the Project Three choices for building a system include: Three choices for building a system include: insourcing insourcing selfsourcing selfsourcing outsourcing outsourcing

26. SELFSOURCING Selfsourcing (also called knowledge worker development or end user development) Selfsourcing (also called knowledge worker development or end user development)

27. The Selfsourcing Process The advantages of selfsourcing The advantages of selfsourcing Improves requirements determination Improves requirements determination Increases knowledge worker participation and sense of ownership Increases knowledge worker participation and sense of ownership Increases speed of systems development Increases speed of systems development

28. The Selfsourcing Process Potential pitfalls and risks of selfsourcing Potential pitfalls and risks of selfsourcing Inadequate knowledge worker expertise leads to inadequately developed systems Inadequate knowledge worker expertise leads to inadequately developed systems Lack of organizational focus creates “privatized” IT systems Lack of organizational focus creates “privatized” IT systems Insufficient analysis of design alternatives leads to subpar IT systems Insufficient analysis of design alternatives leads to subpar IT systems Lack of documentation and external support leads to short-lived systems Lack of documentation and external support leads to short-lived systems

29. OUTSOURCING Developing strategic partnerships Developing strategic partnerships Outsourcing Outsourcing

30. Developing Strategic Partnerships IT outsourcing takes on 1 of 4 forms: IT outsourcing takes on 1 of 4 forms: 1. Purchasing existing software 2. Purchasing existing software and pay the publisher to make certain modifications 3. Purchasing existing software and pay the publisher for the right to make modifications yourself 4. Outsourcing the development of an entirely new and unique system for which no software exists

31. Outsourcing Options There are three different forms of outsourcing: There are three different forms of outsourcing: 1. Onshore outsourcing - the process of engaging another company within the same country for services 2. Nearshore outsourcing - contracting an outsourcing arrangement with a company in a nearby country 3. Offshore outsourcing - contracting with a company that is geographically far away

32. The Advantages of Outsourcing Focus on unique core competencies Focus on unique core competencies Exploit the intellect of another organization Exploit the intellect of another organization Better predict future costs Better predict future costs Acquire leading-edge technology Acquire leading-edge technology Reduce costs Reduce costs Improve performance accountability Improve performance accountability

33. The Disadvantages of Outsourcing Reduces technical know-how for future innovation Reduces technical know-how for future innovation Reduces degree of control Reduces degree of control Increases vulnerability of strategic information Increases vulnerability of strategic information Increases dependency on other organizations Increases dependency on other organizations

34. PROTOTYPING Prototyping Prototyping Prototype Prototype Proof-of-concept prototype Proof-of-concept prototype Selling prototype Selling prototype

35. The Advantages of Prototyping Encourages active knowledge worker participation Encourages active knowledge worker participation Helps resolve discrepancies among knowledge workers Helps resolve discrepancies among knowledge workers Gives users a feel for the final system Gives users a feel for the final system Helps determine technical feasibility Helps determine technical feasibility Helps sell the idea of a proposed system Helps sell the idea of a proposed system

36. The Disadvantages of Prototyping Leads people to believe the final system will follow shortly Leads people to believe the final system will follow shortly Gives no indication of performance under operational conditions Gives no indication of performance under operational conditions Leads the project team to forgo proper testing and documentation Leads the project team to forgo proper testing and documentation