CDC UP Phase 3 Project Life Cycle PLC

  • Slides: 8
Download presentation
CDC UP Phase 3 Project Life Cycle (PLC) Integration

CDC UP Phase 3 Project Life Cycle (PLC) Integration

Background Why Address Project Lifecycle Integration? q Advance Understanding of the CDC Unified Process

Background Why Address Project Lifecycle Integration? q Advance Understanding of the CDC Unified Process – Foster understanding of how the CDC UP and various PLCs are connected – Illustrate links between phases and processes of CDC UP and various PLCs – Clarify phase differences between CDC UP and various PLCs – Clarify terminology differences between CDC UP and various PLCs – Publish specific PLC standards q Satisfy Regulatory Requirements – Comply with FISMA audit – Align with NIST requirements

Background Understanding PLC Integration q Regardless of project type, project management activities remain the

Background Understanding PLC Integration q Regardless of project type, project management activities remain the same. However, life cycle activities vary q CDC UP Framework encompasses project management activities that have to do with planning, administration, and leadership of a project q Various PLCs, encompass specific activities that have to do with producing project deliverables and concentrate more on the technical and/or product requirements of a project q Neither the CDC UP Framework nor an SDLC are solely sufficient to successfully manage a project; both are required

Lifecycles Integration Standards Institute of Electrical and Electronics Engineers (IEEE) q IEEE standard does

Lifecycles Integration Standards Institute of Electrical and Electronics Engineers (IEEE) q IEEE standard does not proscribe a specific software development life cycle (SDLC) model, development methodology, nor the creation of specific documents q IEEE provides a list of activities specified in the standard to be incorporated into an organization’s PLC q IEEE standards should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists Capability Maturity Model (CMM) q CMM provides only guidance for improving processes q CMM contains a framework that provides the ability to generate multiple process models q Actual processes used in an organization depend on internal organizational factors

Lifecycles Integration Standards National Institute of Standards and Technology (NIST) q NIST assumes many

Lifecycles Integration Standards National Institute of Standards and Technology (NIST) q NIST assumes many different SDLCs models exist – In general an SDLC includes the following phases: initiation, acquisition/development, implementation/assessment, operations/maintenance, and sunset (disposition) q NIST is a framework, a roadmap for information security process improvement q Each of these five phases includes a minimum set of tasks Information Technology Investment Management (ITIM) q ITIM is a generic framework, a roadmap for investment process improvement q There is no right way to implement ITIM. The framework describes characteristics of success, not specific techniques q ITIM framework can be applied to multiple disciplines as a tool to improve processes q ITIM is technology independent. No specific tools, methods, or technologies are mandated. Appropriate tools, methods, and technologies should be made available to support the processes that an organization develops within ITIM

Lifecycles Integration Standards Centers for Medicare & Medicaid Services (CMS) q CMS assumes many

Lifecycles Integration Standards Centers for Medicare & Medicaid Services (CMS) q CMS assumes many different SDLCs models exist – In general SDLC phases fall within one of three CMS phases: IT Investment Selection, IT Investment Implementation, and IT Investment Evaluation q CMS acknowledges that “regardless of the system development methodology that is employed for a given IT project, the primary activities performed throughout the system life cycle generally remain the same”. . . “While the phases of the life cycle are graphically depicted in sequential order, some of the phases may overlap on some projects or may occur iteratively for other projects, depending on the SDLC selected for the project”. Food & Drug Administration (FDA) q One methodology does not fit all sizes & types of system development & delivery efforts q The FDA SDLC establishes a logical order of events and a common language for conducting system development and delivery for both full sequential and for iterative work patterns

Phase 3 SDLC Integration Summary q Many different life cycles exist but specific activities

Phase 3 SDLC Integration Summary q Many different life cycles exist but specific activities within each lifecycle vary q Project management activities remain the same regardless of lifecycle q A framework is a roadmap that identifies key practices for success. However, it describes what to do, not how to do it q CDC UP Framework encompasses project management activities such as planning, administration, and leadership, not specific activities associated with product development q Neither the CDC UP Framework nor an SDLC are solely sufficient to successfully manage a project; both are required

Phase 3 SDLC Integration Recommendation CDC UP Recommendation for SDLC Integration q Map the

Phase 3 SDLC Integration Recommendation CDC UP Recommendation for SDLC Integration q Map the CDC UP Framework to a generic SDLC q Without standardizing the CDC on one SDLC, a generic SDLC mapping: 1. 2. 3. 4. 5. 6. Clarifies phase differences between the CDC UP and SDLCs Clarifies terminology differences between CDC UP and SDLCs Illustrate links between phases and processes of CDC UP and SDLCs Publishes specific lifecycle standards without favoring one SDLC over other SDLCs Foster understanding of how the CDC UP & SDLCs are connected Furthers the acceptance of the Unified Process