1. Chapter 6: Systems Development Steps, Tools, and Techniques Management Information Systems for the Information Age

2. Chapter 6: Systems DevelopmentSlide 2 Visual Map of Chapter 6 KW & Roles KW & Roles In SDLC In SDLC 7 Phases 7 Phases Of SDLC Of SDLC Prototyping Sourcing - In - In - Self - Self - Out - Out Why Systems Why Systems Fail ? Fail ? Plan Plan Analyze Analyze Design Design Develop Develop Test Test Implement Implement Maintain Maintain KW = Knowledge Workers KW = Knowledge Workers SDLC = Systems Development Life Cycle SDLC = Systems Development Life Cycle SystemsDevelopment

3. Chapter 6: Systems DevelopmentSlide 3 Systems Development Life Cycle The SDLC provides a structured step-by-step approach for creating information systems Not all real-life development projects follow the SDLC and, as a result, experience high failure rates

4. Chapter 6: Systems DevelopmentSlide 4 SDLC: 1. PlanObjective To determine a solid and practical plan for developing a new information systemActivities Define the system to be developed (CSFs) Set the project scope and boundaries Develop the project plan including tasks, people, resources, and time frames Treat as a living document (continually updated) Project manager sets and tracks milestone dates

5. Chapter 6: Systems DevelopmentSlide 5 SDLC: 2. AnalysisObjective To comprehend the business problem or opportunity and to specify the business requirements for the proposed systemActivities Gather the business requirements—detailed set of requests from knowledge workers and the actual users of the system But no details generated on potential technologies or how the system will meet the requirements Write a Functional Specification document

6. Chapter 6: Systems DevelopmentSlide 6 SDLC: 3. DesignObjective To design a technical blueprint showing how the system will achieve the requirements outlined in the Functional Specifications documentActivities Identify the technical architecture (hardware, software, and telecommunications equipment) required to support the proposed system Design system models (DFDs, ERDs, & GUIs) Write a Technical Specification document

7. Chapter 6: Systems DevelopmentSlide 7 SDLC: 4. DevelopObjective To build the new information system (physical components) based on the functional and technical specifications (logical requirements)Activities Build the technical infrastructure, including sourcing and installing hardware systems and telecommunications equipment Create the database and programs, including coding and programming software systems

8. Chapter 6: Systems DevelopmentSlide 8 SDLC: 5. TestObjective To verify that the system successfully solves the problem, meets the opportunity, and/or achieves the business requirements specifiedActivities Write the test conditions Document the detailed steps and expected results Perform testing on the system Component (Unit), Interface (Integration), System (Whole Unit), User Acceptance (Requirements), Usability (GUI), and Release testing

9. Chapter 6: Systems DevelopmentSlide 9 SDLC: 6. ImplementObjective To distribute the completed information system to all knowledge workers for everyday useActivities Provide training for the system users Instructor-led workshops Just-in-time learning via Internet and CBT Write detailed user documentation Uses results from user and usability testing Often based on functional specifications document

10. Chapter 6: Systems DevelopmentSlide 10 SDLC: 7. MaintainObjective To monitor and support the information system to ensure that it continues to meet the business requirements of its knowledge workersActivities Build a help desk to support the users of the system Provide an environment that supports system changes and adaptation

11. Chapter 6: Systems DevelopmentSlide 11 What Is Your Role in the SDLC? Business Process Expert You know how the business works Customer Liaison You know how to meet the customer’s needs Quality Control Analyst You need to keep the team focused and on track Manager You need to ensure the system improves productivity for your team

12. Chapter 6: Systems DevelopmentSlide 12 How Are IS/IT Projects Unique? People 20:1 productivity difference in programmers 1 brilliant member worth more than 100 others 2-guys-in-a-garage issue Cost to change a line of code is up to 100x the cost to generate it in the first place Productivity Technology changes every 12-18 months Technology Does all this technology pay for itself? More now means even more later

13. Chapter 6: Systems DevelopmentSlide 13 Why Do IS/IT Projects Fail? Only 20% of IS projects are successful Reasons for Failure 1.Incorrect, unclear, or missing requirements 2.Fast-tracking or skipping SDLC phases 3.Failure to manage the scope Scope Creep and Feature Creep 4.Failure to manage the project Project plan is a living document that must be monitored, revised, and updated continuously 5.Changing technology architectures

14. Chapter 6: Systems DevelopmentSlide 14 What Do Errors Really Cost? It’s far cheaper to find an error during the planning or analysis phase than it is to find the same error during the implementation or maintenance phase.

15. Chapter 6: Systems DevelopmentSlide 15 Project Management 101 Microsoft Project lets you define tasks, specify timeframes to completion, and assign resources. It then draws a structured GANTT chart, so you can map and track key milestone dates.

16. Chapter 6: Systems DevelopmentSlide 16 Who Is Going to Build It? In-sourcing Using IT specialists within your company Self-sourcing Using your own skills (or those of other knowledge workers and end-users) Out-sourcing Using external employees, from another company, or specialist contractors

17. Chapter 6: Systems DevelopmentSlide 17 InsourcingAdvantages Typically cheapest approach Personnel is familiar with business processes, activities, and company structure Promotes “buy-in” if people who will use the system had a hand in creating itDisadvantages Company may not have the technical expertise Difficult to fully commit resources to long-term projects; who handles the operational side Can you ensure staff isn’t transient?

18. Chapter 6: Systems DevelopmentSlide 18 SelfsourcingAdvantages You know what you need and want better than anyone else Sense of pride and ownership over the system Iterative model design moves quite quicklyDisadvantages Takes time away from you doing other tasks— the ones you have been hired to perform You may lack the technical expertise Often users do not effectively test, document, or support their own creations

19. Chapter 6: Systems DevelopmentSlide 19 OutsourcingAdvantages You can focus on your core competencies Exploit external intellect, expertise, and IT Better predict timelines and reduce costsDisadvantages Limits your technical know-how for making future enhancements and modifications Reduces your degree of control (dependency) You may need to turn over sensitive data You must create a detailed and binding RFP

20. Chapter 6: Systems DevelopmentSlide 20 Outsourcing Software Development

21. Chapter 6: Systems DevelopmentSlide 21 PrototypingObjective To build a model that demonstrates the features of a proposed product, service, or systemAdvantages Involves users and lets them see, touch, work with, and evaluate an inexpensive model Good for gathering and refining requirements Proves that a plan is technically feasible Proof-of-Concept prototype Helps to sell the concept of a proposed system Selling prototype

22. Chapter 6: Systems DevelopmentSlide 22 SDLC Summary