Skip to main content

Information Technology Related Business with the Library

Methodological Approaches to IT

The Library applies best practices and proven methodologies to IT initiatives to ensure optimal results. In particular, the Library’s Systems Development Life Cycle (SDLC) provides a framework for building and maintaining high quality systems that meet or exceed customer expectations. Additionally, the Project Management Life Cycle (PMLC) describes the project management process steps and deliverables required to ensure IT projects are completed within planned schedule, scope and resources. All Library initiatives are expected to follow the SDLC and PMLC. A brief overview of each of these methodologies is provided here for the benefit of prospective vendors and other potential Library of Congress collaborators. More detailed information about the SDLC and PMLC, including process roles and steps for each, will be made available upon contract award.

High Level Overview of the Systems Development Life Cycle

Introduction

The purpose of this document is to provide a high level overview of the Library’s System Development Life Cycle (SDLC) process including a brief description of the SDLC phases and deliverables. This information is provided for the benefit of prospective vendors and other potential Library of Congress collaborators. More detailed information about the SDLC, including process roles and steps, will be made available upon contract award.

Systems Development Life Cycle

The SDLC provides a framework for building and maintaining high quality systems that meet or exceed customer expectations. The SDLC also supports the Library’s Information Technology Investment Management (ITIM) process and is intended to increase the use of Federal government and industry best practices across all IT projects, thereby improving project results. The SDLC consists of seven (7) phases as depicted below. Each phase provides a reusable building block applicable to both waterfall projects and iterative development efforts (e.g., agile, rapid prototyping, and release management). For waterfall projects, each phase is executed and completed before proceeding to the next phase. For iterative development projects, certain groups of sequential SDLC phases such as requirements, design, development, test, and even implementation may repeat multiple times as part of a single development effort. Note, the SDLC describes technical engineering processes only. For the Library’s project management specific deliverables and guidance, see the high level overview of the Project Management Life Cycle.

Systems Development Life Cycle Phases chart

Phases

  • Phase 1: Requirements & Analysis – Gather and analyze business and functional requirements and perform detailed project planning.
  • Phase 2: Design – Transform detailed requirements definitions into complete, detailed system design specifications.
  • Phase 3: Development – Convert the design into a complete information technology system.
  • Phase 4: Testing – Validate whether the developed system meets the system requirements and is ready to be deployed.
  • Phase 5: Implementation – Deploy the system to the Production Environment for operational use.
  • Phase 6: Operations & Maintenance (O&M) – Perform operations and maintenance of the system in the Production Environment.
  • Phase 7: Disposition – Perform end-of-system activities and dispose of the system.

Deliverables

The table below describes the deliverables to be completed during each phase of the SDLC. These deliverables include both standard SDLC deliverables and additional deliverables required specifically for the IT Security Assessment and Authorization (A&A) process as indicated and shown in italic font below. For each deliverable, a link to the current corresponding template is provided. These templates are included here to provide further guidance about the information that is to be captured during each SDLC phase. Alternate document formats may be used as long as all applicable content is included for each deliverable. The specific documents to be provided, including possible additional required deliverables and/or alternate document formats, will be determined for each engagement based on the terms of the contract.

SDLC Phase Deliverable(s) Purpose
Phase 1: Requirements &  Analysis Requirements Document
(Word, 486KB)
Documents the output of the Requirements Gathering / Analysis activity and serves as the foundation for system design and development activities
Initial Security Determination (IT Security A&A)
(Word, 296KB)
Provides the system owner with a clear understanding of the protection requirements concerning the system. 
FIPS 199 Security Categorization (IT Security A&A)
(Word, 804KB)
Used as a basis for IT security measures, ensuring that spending on IT security is commensurate with the value of the information or IT system
ADA/508 Checklist
(Word, 447KB)
Provides a checklist of ADA/508 compliance considerations
Phase 2: Design System Design Document
(Word, 135KB)
Describes the detailed system design specifications
Security Test & Evaluation Plan & Report (IT Security A&A)
(Word, 1.92MB)
Provides a plan for verifying whether the system has implemented necessary security measures and safeguards
Contingency Plan
(Word, 155KB)
Establishes procedures to recover the system following a disruption.
Configuration Management Plan
(Word, 611KB)
Describes the configuration management process for the system
System Administration Manual
(Word, 312KB)
Explains how a system admin will control system accounts and privileges
Phase 3: Development Project Test Plan
(Word, 393KB)
Provides a high-level plan for functional, system, integration, and user acceptance testing
Phase 4: Testing Test Results & Analysis Report (IT Security A&A)
(Word, 375KB)
Provides a summary of the results of tests performed.
Implementation Plan
(Word, 409KB)
Describes how the information system will be deployed, installed, and transitioned into an operational system.
Authorization to Operate (IT Security A&A)
(Word, 360KB)
Provides a review of the readiness status of the project and certifies that the project is authorized to proceed in the Operations Phase.
User Acceptance Memo
(Word, 26KB)
Provides documentation that the system adequately meets or exceeds the specified requirements and has been sufficiently tested
Pre-Implementation Authorization
(Word, 47KB)
Attests that the phases and required deliverables have adequately been completed
Phase 5: Implementation Hotline Survival Guide
(Word, 23KB)
Provides contact information for the primary contact and responsible managers along with special instructions.
Memorandum of Understanding
(Word, 157KB)
Establishes a management agreement between multiple organizations regarding the development, management, operations, and security of the system.
Post-Implementation Authorization
(Word, 44KB)
Attests that the phases have adequately been completed and that the functionality, quality, and reliability is ensured.
Application Data Sheet
(Excel, 157KB)
Verifies and gathers information about applications that are currently hosted on services located in the Library’s Data Center.
Phase 6: Operations & Maintenance Change Request
(Word, 62KB)
Used to document changes to the Production System
Phase 7: Disposition Disposition Memo
(Word, 16KB)
Describes the System Owner’s intent to terminate the system
Disposition Stakeholder List
(Word, 361KB)
Captures stakeholder role(s) and name(s)
Systems Architecture Diagram and Disposition Requirements
(Word, 398KB)
Captures System Architecture Design of the system to be disposed of and all disposition requirements
Notification Email
(Word, 15KB)
Email notification sent to stakeholders before and after executing disposition tasks
Post-Termination Review Report
(Word, 344KB)
Details the findings of the Disposition Phase to identify where to find all products and documentation that has been archived.

High Level Overview of the Project Management Life Cycle

Introduction

The purpose of this document is to provide a high level overview of the Library’s Project Management Life Cycle (PMLC) process including a brief description of the PMLC phases and deliverables. This information is provided for the benefit of prospective vendors and other potential Library of Congress collaborators. More detailed information about the PMLC, including process roles and steps, will be available upon contract award.

Project Management Life Cycle

Project Management is the application of knowledge, skills, tools and techniques to ensure projects are executed within planned budget, scope and resources. The Library accomplishes this through the Project Management Life Cycle (PMLC) which is based on the Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK) and Federal government guidance. The PMLC supports the Library’s Information Technology Investment Management (ITIM) process and is intended to increase the use of Federal government and industry best practices across all IT projects, thereby improving project results. The PMLC consists of four (4) sequential phases as depicted below. Note, the PMLC describes the Library’s project management specific process and deliverables only. For an overview of the Library’s systems development process and deliverables, see the high level overview of the Systems Development Life Cycle.

Project Management Life Cycle Phases chart

Phases

  • Phase 1: Initiation – Formally initiate the project, including solidify the scope and obtain necessary resources and approvals to proceed.
  • Phase 2: Planning – Assemble the project team, refine project objectives, and plan the PM approach.
  • Phase 3: Execution and Control – Coordinate people and resources to carry out plan and ensure project objectives are met by monitoring and measuring progress, identifying variances, and taking corrective action as necessary.
  • Phase 4: Closeout – Formalize acceptance of project deliverables, finalize documentation, assess project processes and results, release resources, and formerly close the project.

Deliverables

The table below describes the deliverables to be completed during each PMLC phase. For each deliverable, a link to the current corresponding template is provided. These templates are included here to provide further guidance about the information that is to be captured during each PMLC phase. Alternate document formats may be used as long as all applicable content is included for each deliverable. The specific documents to be provided, including possible additional required deliverables and/or alternate document formats, will be determined for each engagement based on the terms of the contract.

PMLC Phase Deliverable(s) Purpose
Initiation Project Charter
(Word, 365KB)
Obtain and document approval to initiate project – formally authorizes the existence of a project and provides the PM with the authority to apply organizational resources to project activities.
Planning Project Management Plan
(Word, 386KB)
Defines how the project is to be executed, monitored, and controlled including assumptions, constraints, dependencies, stakeholders, milestones, and development methodology (e.g., agile or waterfall) if applicable
Project Schedule
(MPP, 307KB)
Serves as the primary planning calendar and schedule baseline for the project. It includes both PM and technical tasks and subtasks needed to complete the project. 
Communications Management Plan
(Word, 396KB)
Identifies communications needs, formats for information dissemination, and target audience for each type of communication
Risk Management Plan
(Word, 394KB)
Describes how project risk assessment will be conducted
Change Management Plan
(Word, 369KB)
Describes project change management process
Execution and Control Status Reports
(Excel, 122KB)
Provides a monthly project update format to be submitted to the Library’s IT Project Management Office.
Issue Log
(Excel, 327KB)
Provides a record of issues and resolutions throughout the project life cycle.
Risk Register
(Excel, 49KB)
Provides a record of risks, with assessment of impact and probability, mitigation strategy, contingency plan, and resolution for each risk.
Change Requests
(Word, 48KB)
Used to formally document and track project change requests
Closeout Lessons Learned
(PowerPoint, 261KB)
Captures the results of the project team’s lessons learned discussion to be submitted to the Library’s PMO for reference by other project teams.
Closeout Report
(Word, 358KB)
Serves as a final report to management on the status and results of the project and formally releases project resources.
 Back to top