Systems Development Lifecycle (SDLC)

1. Systems Development Lifecycle (SDLC) Jason C. H. Chen (陳周宏), Ph.D. Visiting Professor National Taipei University of Technology Professor of MIS Graduate School of Business Administration Gonzaga University Spokane, WA 99258 USA Jason8989.chen@gmail.com

2. What Are Systems Development Activities? • Systems definition/investigation • Management’s statement of objective and goals for new system • Requirements analysis • Identify features and functions • Component design (hardware, software, network) • Based on approved user requirements • Implementation • Purchase, build, test, and convert to new system • System maintenance (fix or enhance) • Repair, add new features, maintain Analysis

3. What Are Systems Development Activities? [1] [2] [3a] [3b] (Feasibility Study) What is it and Why it is important? [4] [5] BPM Provides Requirements for Systems Development

4. Assess Feasibility Dimensions of feasibility • _______________ feasibility • Approximated, “back-of-the-envelope” analysis • Purpose: eliminate infeasible ideas early • Consider cost of previous projects, operational and labor costs • __________ feasibility • Ball park estimate • __________ feasibility • Is it technically likely to meet needs? • _____________ feasibility • Fit with customs, culture, charter, legal requirements of organization • ___________________ feasibility • Is the proposed system legally? Cost/Economic Schedule Technical Organizational Legal and Contractual

5. Economic Feasibility Systems Definition/Investigation (Feasibility Study) What are new from the last slide? Operational Feasibility Can we afford it? Will it be accepted? Schedule Feasibility Technical Feasibility Will it be completed by the deadline? Does the IT capability exist? Organizational Feasibility Legal and Contractual Feasibility (Is it a good fit – objective of the organization Is the proposed system legally?

6. Form a Project Team • Typical three personnel on a development team are: • Manager (or mangers for larger projects) • Specialist: • System analysts • Programmers • Software testers • or, other functional specialist such as accounting, finance, and marketing • Users: • Users must be involved in most of SDLC phases • Depending on nature of project, team may also include hardware and communications specialists, database designers and administrators, and other IT specialists.

7. Systems Development • What happen (and Why) to a project in the Department of Interior of Taiwan?

8. Phase Four: Implementation • Focuses on implementing the system and includes the tasks of • building each of the five system components • testing the system and • converting users to the new system. Fig 10-18: SDLC: Implementation Phase

9. System Conversion Approaches • Pilot • Implement entire system in limited portion of business • MRV uses system for selected customers. • Advantage: limits exposure to business if system fails • Phased • System is installed in phases or modules. • Each piece is installed and tested. • Parallel • Complete new and old systems run simultaneously • Very safe, but expensive • Plunge (or direct) • High risk if new system fails, no old system to fall back on • Only used if new system is not vital to company operation

10. Cut-over time Old System New System Old System New System Old System New System Old System New System Installation Conversion Methods: 4 Ps Parallel Pilot Phased Plunge/ Direct

11. Causes of Information Systems Failures • 35+ years of research on causes of information systems failures • Lack of user __________ • Unclear, incomplete, and inconsistent ___________ • Changing requirements and specifications • Many businesses __________ research findings involvement. requirements. ignore

12. Systems Development Lifecycle (SDLC)