Systems Development (SD) Presentation

1. Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health mswebb@utah.gov UDOH Informatics Brownbag August 25, 2010

2. Systems DevelopmentDefined • Systems development is the activity of creating new or modifying existing business systems. • IT System development involves two interrelated life cycles: • System Development Life Cycle • Project Management Life Cycle

4. Project Management Defined • The application of knowledge, skills, tools, and techniques to project activities in order to meet customer needs and expectations (usually related to budgets, schedules and quality ‘deliverables’)

5. Project Management Discipline • Many sources of training – one certification source: i.e. Project Management Institute (PMI) • The amount of project management rigor applied is a function of level-of-effort/complexity. • No current state standard PM discipline – Agency culture ‘rules’. • The “Project Planning and Management for IT” course presented by BYU is recommended.

6. Project Management Life Cycle (PMLC) • The classic PMLC is comprised of the following process groups: • Project Initiation (PI). • Project Planning (PP). • Project Execution (PE). • Project Controlling (PC). • Project Shutdown (PS).

7. PMLC – Project Initiation • PI processes include project approval, project organization, and project ‘kickoff’. • The primary PI process deliverable is the ‘Project Charter’: • Issued by senior management. • Contains project scope and objective statement. • High level schedule/target dates. • Empowers the designated project manager to apply organizational resources.

8. PMLC – Project Planning • Project Planning processes include: • Activity definition (all work streams) , sequencing, and estimating. • Detailed schedule development. • Resource planning. • Cost estimating and budgeting. • Risk evaluation. • Communications planning. • Quality planning.

9. Project Planning (cont) • PP process deliverables include: • Updated Project Charter • Project plan/schedule. • Risk Management Plan. • Communications Plan. • Quality Plan.

10. PMLC – Project Execution • PE processes include performing the planned activities, managing project team, solving problems, and distributing progress information to stakeholders. • PE process deliverables include: • Updated project plan. • Scheduled ‘Deliverables’. • Team meeting minutes. • Progress reports.

11. PMLC- Project Controlling • PC processes involve managing the project scope, schedule, cost, quality, and risk. • PC process deliverables include: • Change Management Plan. • Issue log.

12. PMLC – Project Shutdown • PS processes include final system acceptance, overall project evaluation, and transition to operational support. • PS deliverables include: • System ‘sign off’ document. • Lessons learned document. • System Support Plan.

13. System Development Life Cycle (SDLC) • The classic SDLC is comprised of the following process groups: • Systems Investigation (SI). • Systems Analysis (SA). • Systems Design (SD). • Systems Development (SDev). • Systems Deployment (SDploy). • Systems Operation & Maintenance (SO&M).

14. SDLC (cont) • The planning for System Development needs to include all life cycle process groups. • Following the System Analysis processes, the system sponsors will decide whether to use internal resources (make) or external resources (buy) to develop the system.

15. SDLC – Systems Investigation • SI processes involve understanding the need and benefits of the new/enhanced system. • SI process deliverables include: • Concept Definition > Specifies the business processes to be addressed, interfaces with other systems, etc. • Feasibility Study > Preliminary evaluation of required resources, timing, ROI, organizational impact, etc.

16. SDLC – Systems Analysis • SA processes involve understanding the functional requirements of the proposed system. • SA process deliverables include: • Business process model. • Initial Data model. • Object model. • Proposed system Architecture. • Requirements document.

17. SA(cont) NOTE: If a “BUY’ decision has been made, system sponsors will initiate the vendor procurement process at this point.

18. SDLC – Systems Design • SD processes involve translating functional requirements into specific system features and functions, i.e. what the system will do and how the system will be implemented. • SD process deliverables include: • Final data model. • Final system architecture. • Design documents. • ‘Proof of Concept’ prototypes.

19. SDLC – Systems Development • SDev processes involve implementing the designs by creating, integrating, and ‘debugging’ the system components. • SDev process deliverables include: • Software code. • System test plans. • System documentation (e.g. user guide, installation/operation guides).

20. SDLC – Systems Deployment • SDploy processes include user acceptance, user training, system installation, and operational testing. • SDploy process deliverables include: • Acceptance test plan. • User training document. • Installation plan. • ‘Beta’ test plan.

21. SDLC – System Operations & Maintenance • SO&M processes include those oriented to user support: • Insure system operations according to required ‘up-time’ requirements. • Backup system data. • Address system problems. • Process system enhancement requests.

22. SO&M (cont) • SO&M process deliverables include: • Support Coverage Plan. • Change Management Plan. • Regression Test Plan.

23. SDLC Models • There are several types of SDLC models: • ‘Waterfall’ • ‘Prototyping” • ‘Rapid Application Development’ • While each SDLC model address all of the process groups – the sequence of processes differ between models. • System sponsors, project managers, and technical architects collaborate to determine which model is consistent with the proposed system.