Untitled Document
OHSU Where Healing, Teaching and Discovery Come Together
OHSU Search OHSU OHSU Site Map Contact
About OHSU Health Care Services Academic and Student Information Research Programs outreach Outreach

SDLC Process

OHSU Home --> ITG --> SDLC/PM --> SDLC Process
rule_600

 

SDLC PROCESS OVERVIEW

 

The SDLC process is an eleven phase project life cycle providing a consistent, effective and repeatable practice that serves as the framework for delivering high quality, on time and on budget IT enabled business solutions. OHSU's SDLC builds on industry principles (System & Software Development Life Cycle) for complete IT-enabled solutions.

 

SDLC was designed, developed and is continuously improved based on OHSU business requirements, corporate culture and project management maturity. Within each phase, detail steps and sub steps define work flow and identify cross functional roles and responsibilities for all IT project stakeholders from customers and executive sponsors to business partners and IT subject matter experts.

 

SDLC

 

A partnership between business process owners and the Information Technology Group

 

SDLC PROCESS PHASES

 

  1. New IT Request: customers develop and submit an IT request for a new product or service
  2. New Request Triage: the Project Management Office (PMO) reviews request information for completeness, assigns a Project Manager and notifies the customer and Project Manager
  3. Initial Analysis: the Project Manager conducts a high-level Rough Order of Magnitude (ROM) analysis of the request with the appropriate subject matter experts to prepare a preliminary project plan
  4. Committee Review: the Project Manager presents the preliminary project plan to the appropriate business committee (aligned with key strategic areas) for review and consideration. The committee considers the request, as well as major scope changes, with respect to business project portfolio and strategic information goals
  5. Requirements Document: once a request is approved, the Project Manager forms a cross functional project team to define the detail project scope including the technical solution and alternatives. 
  6. Functional Review: the Project Manager conducts meetings with appropriate project stakeholders to review, modify and/or approve the requirements document
  7. Project Planning: the Project Manager leads the project team to develop a detail and comprehensive project plan based on the preliminary project plan and requirements document
  8. Baseline Review: the Project Manager conducts a meeting with the appropriate project stakeholders to review, modify and/or approve the project plan to establish a Performance Measurement Baseline
  9. Executing: the project team executes the project plan to complete the work associated with the project. This includes managing changes, taking corrective action and providing project plan status to project stakeholders
  10. Go-Live: the project team implements the project into production environment. This includes managing changes, taking corrective action and providing project plan status to project stakeholders and obtaining customer approval
  11. Completion: the Project Manager closes out the project by updating appropriate Project Management Information Systems, notifying project stakeholders and conducting lessons learned meetings.

Copyright 2005 by Oregon Health & Science University

 

Top of Page