Chapter 15

1. Chapter 15 Systems Development

2. Learning Objectives • When you finish this chapter, you will: • Understand the systems development life cycle. • List and explain the pros and cons of prototyping. • Understand how software tools facilitate the monitoring and controlling of systems development.

3. Learning Objectives • Recognize the difficulties involved in systems development. • Be able to list the advantages and disadvantages of different system conversion strategies. • Understand the concept of systems integration.

4. Why Develop an IS? • Three phenomena can trigger IS development • An opportunity (proactive) • A problem (reactive) • A directive

5. The Systems Development Life Cycle (SDLC) • SDLC approach • Life of an IS starts with a need • Followed by assessment of functions that system must have to fulfill that need and • Ends when benefits of the system no longer outweigh its maintenance cost • At this point a new system begins

6. The Systems Development Life Cycle (SDLC) Figure 15.1 The systems development life cycle

7. Analysis Phase • Analysis • System analysis phase is a five-step process…

8. 5 Steps in System Analysis • Step 1: Investigation • Is there a real need and is it feasible? • Step 2: The Technical Feasibility Study • Ensures hardware and software exist to build the system • Step 3: The Economic Feasibility Study • Benefits of the system weighed against the cost • Step 4: The Operational Feasibility Study • Determines if system will be used as intended • Step 5: Requirements Definition • Specific requirements/features of system defined

9. The Design Phase Figure 15.4 Phases in systems design

10. Phases in Systems Design • Logical Design • Translation of user requirements into detailed functions of the system • Physical Design • Construction • Systems Testing

11. Figure 15.6 A flowchart describing a sales bonus system Logical Design: Business Processes

12. Logical Design: Business Processes – For Real

13. Logical Design: Business Processes – For Real

14. Logical Design: Business Processes – For Real

15. Logical Design: Business Processes – For Real

16. Logical Design: Business Processes – For Real

17. Logical Design: Data Flow Diagrams

18. Systems Testing • The idea is to try and break the system • Programs to run code • Human users try and ‘outsmart’ the system • Stress Testing • Often it is one of the most tempting phases to reduce or cut from project plan

19. Implementation Phase • Implementation (also called delivery) consists of two steps: • Training • Conversion • Parallel Conversion • Phased Conversion • Cold Turkey Conversion • Pilot Conversion

20. Strategies used to convert from one IS to another

21. System Support Phase

22. Additional Topics Prototyping, Project Management…

23. Prototyping • Systems developed using an iterative process • Purpose is to develop a working model as quickly as possible, which can be tweaked and revised • Significantly shortens systems development backlog • Can increase risk of incompatibility and other unforeseen mishaps

24. Figure 15.12 In prototyping, refinement of the system continues until users are satisfied. Prototyping

25. Figure 15.13 When to prototype and when not to prototype Prototyping

26. Computer-AidedSoftware Engineering • Computer-Aided Software Engineering (CASE tools) • System development programs that ease and speed design and construction of new ISs • Application generators • I-CASE tools • Rapid Application Development (RAD)

27. Project Management • Project Management Tools • Project Evaluation and Review Technique (PERT) • PERT chart shows events, required activities, and relationships • Advantage: Communication of interdependencies among activities • Gantt Chart • Represents activities and start and completion times, but not the relationships among activities • Advantage: Simple and linear

28. Dimensions of Project Management

29. Project Management • Project Management Goals • Complete the project on time • Complete the project within budget • Meet requirements • Meet expectations

30. Project Management • Project Management Functions • Communication Management • Schedule Management • Quality Management • Financial Management • Resource Management

31. Systems DevelopmentLed by End Users (SDLU) • JAD: An example of User-led Systems Development • Joint Application Development (JAD): method to be used in SDLU • Uses six-step process to take the team through planning and design

32. Figure 15.17 The six steps of JAD Systems DevelopmentLed by End Users (SDLU)

33. JAD Critical Success Factors • All participants must be committed to JAD process. • Customers and IS people must agree on project’s scope. • Sponsor must be supportive and involved. • Team members must be empowered decision makers. • Business objectives must be clearly defined. • Business process must be understood. • Team members must be able to meet two or more days per week. • Members must be committed to the team.

34. Systems Integration • Takes a look at the information needs of an entire organization (or a major division) • Analysts integrate existing systems so that: • Data can flow more easily among business units. • Users can access different types of data via a single interface.

35. Account Mgr Customer System Weekly Feed Siebel Configurable Feed • Siebel’s Role • Opportunities created within Siebel • Sends opportunity and associated data to SYSTEM Daily Synchronization SYSTEM Partner UI Partner • SYSTEM Functionality • Manage partner account/contact and customer data • Evaluate existing managed partners • Select new partners to manage • Fiscal year planning with each partner • Measure and evaluate partners • Enhanced opportunity pipeline management capabilities • Partner Functionality • Participate in fiscal planning process • Manage their account and contact profile including extended attributes like competencies and solutions • Manage their opportunities (accept, reject, claim, return, update and close) Manual feedas needed External Sources • Other Data Sources • Sales • Product Data • Customer data Systems Integration

36. Two Real World Examples Revisited Susan’s Training Wheels: MAX Current Hitachi Consulting Methodology

37. Phase II: World Class Implementation! • Planning & Preparation • Not an easy task… Sample Work Plan • Functional Ownership • Integrated Business Process Redesign • Fast Application Implementation through Prototyping • Base Design Prototype • Integration Prototype • Model Workplace

38. MAX Methodology Phase II: Design and Implementation 100 Project Management and Facilitation 200 Change Management & Communication 800 Process Design and Preparation 900 Base Design Prototype 1000 Detail Design & Integration 1100 Model Workplace Stress Test/ Perfor. Tuning Conversion Design & Development Static---------------------------------->Dynamic Conversion Testing & Validation Install Hardware& Software System Performance Assessment Build Test Scenarios Unit Test System • Regression • Unit Test • Dynamic Data • Integ- • ration • Setup • Config. • Static • Data • Build • Design • Setup • Config. • Test Data Super User Training & Testing MockConver- sion Config- urationPreparation Integration Testing Regression Test Integration Test Prep. Project TeamApplication Training PROCESSSYSTEM Validate Cutover/ Fallback Plan Report, Modification & Interface Gap Analysis & Design Report, Mod. & Interface Validation Report, Modification & Interface Development 1200 Cutover TRAINING Extended Team Kickoff Organizational Transformation ReviewCompleted Analysis Best Practice Review Validate To-Be Detail Design AddressIntegration Issues Validate To-Be Approach & Design Process Implementation Workplan Process Optimization To-Be Process Strategy & Approach Documentation and Process Tool Development Detail Process Design High Level Process Design Pilot Testing of To-Be Processes 600 Performance Measurement & Benefits Tracking

39. Integration Fast Implementation through Prototyping Model Workplace Base Design

40. Process Design and Preparation 800 Process Design and Prep. What • Preparation for the first configuration of the application & high level process definition Goal • To establish the road map for subsequent phase Deliver • Extended Team Kickoff • Install Hardware & Software • Project Team Application Training • Configuration Preparation • Review Completed Analysis • To-Be Process PAVA • High Level Process Design Install Hardware& Software Config- urationPreparation Project TeamApplication Training Extended Team Kickoff ReviewCompleted Analysis Best Practice Review To-Be Process Strategy & Approach High Level Process Design

41. Model Workplace Integration Base Design Base Design Prototype

42. Base Design Prototype 900 Base Design Prototype Conversion Design & Development What • Testing discrete transactions, inquiries, reports within each module Goal • 90% of the business requirements configured, detailed processes defined Deliver • Unit test plan • Conversion, interface plan • Application Gap Analysis • Report development matrix • Process/ long lead matrix • Detailed design Build Test Scenarios Unit Test System • Build • Design • Setup • Config. • Test Data Report, Modification & Interface Gap Analysis & Design Validate To-Be Approach & Design Process Implementation Workplan Detail Process Design

43. Model Workplace Integration Base Design Integration Prototype

44. Detail Design and Integration 1000 Detail Design & Integration What • Building on Base Design Prototype to create an Integrated system Goal • Verify that the processes and system will support the business across interfaces Deliver • Regression Unit Test • Report & Interface Development • Super-User Training & Testing • Conversion Testing & Validation • System Performance Assessment • Integration Testing • Report & Interface Validation Conversion Testing & Validation System Performance Assessment • Regression • Unit Test • Dynamic Data • Integ- • ration • Setup • Config. • Static • Data Super User Training & Testing Integration Testing Integration Test Prep. Report, Mod. & Interface Validation Report, Modification & Interface Development TRAINING Validate To-Be Detail Design AddressIntegration Issues Documentation and Process Tool Development Pilot Testing of To-Be Processes

45. Life Cycle of Implementation Documentation User Documentation Training Manuals Integration Test Plans Detailed Designs UNIT Test Plans Process Inventories To-Be Brown Papers/RACI To-Be PAVA Business Case Requirements

46. Model Workplace Integration Base Design Model Workplace

47. Model Workplace 1100 Model Workplace Stress Test/ Perfor. Tuning What • Full Business Simulation • Stress Testing & Training Goal • To fine-tune cutover procedures and verify potential impacts Deliver • System Performance Assessment • Mock Conversion • End User Training • Stress Test/Performance Tuning • Regression Test • Validate Cutover/Fall Back Plan • Process Optimization • Pilot Testing of To-Be Processes System Performance Assessment MockConver- sion Regression Test Validate Cutover/ Fallback Plan TRAINING Process Optimization Pilot Testing of To-Be Processes

48. Summary • Planning & Preparation • Functional Ownership • Integrated Business Process Redesign • Fast Application Implementation through Prototyping • Base Design Prototype • Integration Prototype • Model Workplace

49. Critical Success Factors • Fast Implementation through Prototyping • Drive to Critical Path / Milestones • High Performance Team — Challenged to Succeed • Committed the BEST PEOPLE • Winning Attitude • Support for Risk Taking • Ownership at ALL LEVELS • Scope Control • Test Thoroughly • No Looking Back

50. Phase II: Analyze Situation Phase I: Mobilize Project Sample Service Offering: Vanilla ERP Implementation (1 of 3) Train Project Team Inventory Manual Procedures Inventory Inputs and Outputs Conduct As-Is Interviews Develop Project Plan / Conduct Kickoff Prepare Simulation / Design Environment Identify Desired Changes Identify Gaps and Constraints Inventory Interface Requirements Develop Business Case Review Functional Requirements Review Technical Infrastructure Requirements Inventory Data Conversion Requirements Plan Business Process Simulation Monitor Budget / Plan / Scope Execute Communications Plan