Initiation: Begins when a sponsor identifies a need or an opportunity. Concept Proposal is created.
System Concept Development: Defines the scope or boundary of the concept. Includes Systems Boundary Document, Cost Benefit Analysis, Risk Management Plan and Feasibility Study.
Planning: Develops a Project Management Plan and other planning documents. Provides the basis for acquiring the resources needed to achieve a solution.
Requirements Analysis: Analyzes user needs and develops user requirements. Creates a detailed Functional Requirements Document.
Design: Transforms detailed requirements into complete, detailed System Design Document. Focuses on how to deliver the required functionality.
Development: Converts a design into a complete information system. Includes acquiring and installing systems environment; creating and testing databases/preparing test case procedures; preparing test files; coding, compiling, refining programs; performing test readiness review and procurement activities.
Integration and Test: Demonstrates that the developed system conforms to requirements as specified in the Functional Requirements Document. Conducted by the Quality Assurance staff and users. Produces Test Analysis Reports.
Implementation: Includes implementation preparation, implementation of the system into a production environment, and resolution of problems identified in the Integration and Test Phase.
Operations and Maintenance: Describes tasks to operate and maintain information systems in a production environment. Includes Post-Implementation and In-Process Reviews.
Disposition: Describes end-of-system activities. Emphasis is given to proper preservation of data.
The project advocate articulates a need statement to a sponsor who passes it to an existing development organization or agency IRM office, or the agency head and DOJ CIO for a project to be initiated. Several factors lead to the need statement: public law, other government agencies, the public and public agencies, commercial products, new user need, technical opportunity or sustainability need.
After the project has been initiated in the Initiation Phase, the project office organizational development and need refinement take place. The Project Office creates the feasibility study, cost/benefit analysis and acquisition strategy. The project office also performs advanced planning for subsequent phases, a risk analysis and prepares resource estimates and requests resource approval. After these activities are completed, the Project Office performs a review and gets approval to proceed into the Planning Phase.
If the selection criteria includes: type of development - any; cost- class 4; mission criticality - all; risk - D3 to D4; and complexity - E2 or E3, choose the Reduced Effort (small application) work pattern. If the selection criteria includes: type of development - 1,2,3; cost - class 3 or 4; mission criticality - all; risk - D3 to D4; and complexity - E2 or E3, choose RAD work pattern. If the selection criteria includes: type of development - 1; cost - Class 2 and 3; mission criticality - C2 to C4; risk - D1; and complexity - high, choose pilot development work pattern. If the selection criteria includes: type of development - 1; cost - Class 1 and 2; mission criticality - C1 or C2; risk - D1; and complexity - E1, choose MED work pattern. If the selection criteria includes: type of development - 1; cost - Class 1 and 2; mission criticality - C1 to C2; risk - D1; and complexity - E1 to E2, choose full sequential work pattern. If the selection criteria includes: type of development - 5; cost - Class 5; mission criticality - any; risk - any; an complexity - any, choose O&M small scale enhancement. If the selection criteria includes: type of development - 6; cost- Class 2 to 4; mission criticality - any; risk - any; and complexity - any, choose O&M project. If the selection criteria includes: type of development - 4 ; cost - Class 3 or 4; mission criticality - any; risk - any; and complexity - any, choose COTS acquisition.
In the reduced effort work pattern, some of the phases are combined. The initiation and systems concept development phases are combined. The planning and requirements analysis phases are combined. The design and development phases are combined. And the integration, test and implementation phases are combined.
In the initiation and system concept development phases, the tasks include: define/document business need, develop a recommendation, present findings to executive management, conduct ADP position sensitivity analysis. The deliverables (work products) include: concept proposal, Project Manager Charter, system boundary document, cost-benefit analysis, risk management plan, feasibility study and feasibility study. The formal reviews include: concept proposal, system boundary document, and phase-end.
In the Planning and Requirements Analysis Phase, the tasks include: review security requirements, plan configuration management, analyze and document requirements, develop test criteria and plans, establish quality assurance mechanisms, establish project and system security. The deliverables (work products) include: acquisition plan, CM plan, project management plan, concept of operations, FRD, QA plan, test & evaluation master plan, system security plan, privacy act notice, ICD, systems engineering management plan, V&V plan, records disposition schedule. The formal reviews include: acquisition plan, CM plan, project management plan, concept of operations, functional requirements, QA plan, test & evaluation master plan, system security plan, system interfaces, V&V plan, systems engineering management plan, phase-end.
In the Design and Development Phase, the tasks include: design the application, design business processes, design conversion/migration/transition strategies, continue procurement activities, continue CM and change control, develop security operating procedures, develop the application, develop business processes, institute internal management controls. The deliverables (work products) include: system design document, implementation plan, software development document, system software, test files/data, contingency plan, operations manual, conversion plan, security risk assessment, maintenance manual , training plan, user manual, integration document, test analysis report. The formal reviews include: final system design, implementation plan, security risk assessment, contingency plan, conversion plan, maintenance manual, training plan, user manual, integration document, software peer reviews, test readiness, phase-end.
In the Integration and Test and Implementation Phase, the tasks include: conduct subsystem integration testing, conduct system testing, conduct user acceptance testing, conduct test analysis review, computer user and operator training, install system in production environment, convert data to production environment, confirm that the system is ready for operation, continue configuration status accounting and change control, certify system security and readiness features, complete acquisitions, perform operation reviews, obtain formal acceptance of the installed system from the user. The deliverables (work products) include: test problem reports, test analysis approval determination, IT systems security certification and accreditation, delivered system, change implementation notice, version description document (initial release) post-implementation review report. The formal reviews include: version description document, post-implementation review, phase-end.
In the Operations and Maintenance Phase, the tasks include: all tasks in Chapter 11. Note: system begins O&M project work pattern. The deliverables (work products) include: periodic system review report, user satisfaction review. Note: See O&M project. The formal reviews include: periodic system review, user satisfaction review. Note: See O&M project.
In the Disposition Phase, the tasks include: all tasks in Chapter 12. The deliverables (work products) include: disposition plan, post-termination review report. The formal reviews include: post-disposition.
Phases include: initiation, system concept development, planning phase, iterative definition and design, development phase, integration and test phase, implementation phase, operations and maintenance phase, disposition phase.
In the initiation phase, tasks include: all tasks in Chapter 3. The deliverables (work products) include: Concept Proposal and Project Manager Charter. The formal reviews include the concept proposal.
In the system concept development phase, tasks include: all tasks in Chapter 4. The deliverables (work products) include: cost-benefit analysis, feasibility study, risk management plan, system boundary document. The formal reviews include: cost-benefit analysis, feasibility study, risk management plan, system boundary document, phase-end.
In the Planning Phase, tasks include: all tasks in Chapter 5. The deliverables (work products) include: acquisition plan, CM plan, QA plan, project management plan, V&V, CONOPS, system security plan, systems engineering management plan. The formal reviews include: acquisition plan, CM plan, QA plan, project management plan, V&V plan, CONOPS, system security plan, systems engineering management plan, phase-end.
In the Requirements Analysis and Design Phase, the following combined phase tasks are iterative: assess the current situation, analyze and document requirements, establish the application environment, design the application. The following combined phase tasks are not iterative: develop test criteria, establish project and system security, revise planning phase documents, design business processes, design conversion/migration/transition strategies, develop security operating procedures. The deliverables (work products) include: FRD, system design document (based on design prototype), interface control document, test and evaluation master plan, security risk assessment, implementation plan, privacy act notice, records disposition schedule, contingency plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server), training plan, user manual. Note: FRD and SDD may be published as one deliverable. The formal reviews include: functional requirements design (based on design prototype), system interfaces, test and evaluation master plan, security risk assessment, implementation plan, design phase-end, contingency plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server), training plan, user manual. Note: requirements and design reviews may be combined.
In the Development Phase, tasks include: all tasks in Chapter 8. The deliverables (work products) include: software development document, integration document, system software, test files/data, test analysis report. The formal reviews include: software peer reviews, test readiness, phase-end.
In the Integration and Test Phase, tasks include: all tasks in Chapter 9. The deliverables (work products) include: test problem reports, test analysis approval determination. IT systems security certification and accreditation. Formal reviews include: phase-end.
In the Implementation Phase, tasks include: all tasks in Chapter 10. The deliverables (work products) include: delivered system, post-implementation review report, change implementation notice, version description document (initial release). The formal reviews include: version description document, post-implementation review, phase-end.
In the Operations and Maintenance Phase, tasks include: all tasks in Chapter 11. Note: system begins O&M Project Work pattern. The deliverables (work products) include: periodic system review report, user satisfaction review. The formal reviews include: periodic system review, user satisfaction review.
In the Disposition Phase, tasks include all tasks in Chapter 12. The deliverables (work products) include: disposition plan, post-termination review report. The formal reviews include: post-disposition.
Phases include: initiation through development phases (sequential or RAD); test phase further broken out into subsystem integration test, system test, user acceptance test, pre-pilot, pilot, and evaluation; additional development; additional testing; implementation phase; operations and maintenance phase; disposition phase.
In the initiation phase, tasks include: all tasks in Chapter 3. The deliverables (work products) include: Concept Proposal and Project Manager Charter. The formal reviews include the Concept Proposal.
The system concept development phase, tasks include: all tasks in Chapter 4. The deliverables (work products) include: cost-benefit analysis, feasibility study, risk management plan, system boundary document. The formal reviews include: cost-benefit analysis, feasibility study, risk management plan, system boundary document, phase-end.
In the planning phase, tasks include: all tasks in Chapter 5. The deliverables (work products) include: acquisition plan, CM plan, QA plan, project management plan, CONOPS, system security plan, V&V plan, systems engineering management plan. The formal reviews include: acquisition plan, CM plan, QA plan, project management plan, system security plan, CONOPS, V&V plan, systems engineering management plan, phase-end.
In the requirements analysis phase, tasks include: all tasks in Chapter 6. Note: the pilot development work pattern may also follow the rapid application development work pattern for the requirements analysis and design phases. The deliverables (work products) include: FRD, test and evaluation master plan, ICD, privacy act notice, records disposition schedule. The formal reviews include: functional requirements, test and evaluation master plan, system interfaces, phase-end.
In the design phase, tasks include: all tasks in Chapter 7. Note: the pilot development work pattern may also follow the rapid application development work pattern for the requirements analysis and design phases. The deliverables (work products) include; software development document, security risk assessment, implementation plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server), training plan, user manual, contingency plan. The formal reviews include: design, implementation plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server), training plan, user manual, contingency plan, final system design, phase-end.
In the development phase, tasks include: all tasks in Chapter 8. The deliverables (work products) include: software development document, integration document, system software, test analysis report, test files/data. The formal reviews include: software peer reviews, test readiness, phase-end.
In the integration and test phase, tasks include: all tasks in Chapter 9. The deliverables (work products) include: test problem reports, test analysis approval determination, IT systems security
certification and accreditation. The formal reviews include: field test and evaluation.
In the implementation phase, tasks are deferred until field test and evaluation proves system concept, then all tasks in Chapter 10. The deliverables (work products) are deferred until field test and evaluation proves system concept, then include: delivered system, change implementation notice, post-implementation review report, version description document. The formal reviews include: post-implementation review, phase-end.
In the operations and maintenance phase, the tasks are deferred until field test and evaluation proves system concept, then all in Chapter 11. The deliverables (work products) are deferred until field test and evaluation proves system concept, then include periodic system review report, user satisfaction review. The formal reviews include: user satisfaction review, periodic system review (to evaluate concept).
In the disposition phase, tasks include: all tasks in Chapter 12. The deliverables (work products) include: disposition plan, post-termination review report. The formal reviews include: post-disposition.
Phases include: initiation phase, concept development phase, planning phase, operations and maintenance phase, and disposition phase. There are several builds under the planning phase. These include: requirements analysis, design, development, integration and test, implementation.
In the initiation phase, tasks include: All in Chapter 3. The deliverables (work products) include: Concept Proposal and Project Manager Charter. The formal reviews include the Concept Proposal.
In the system concept development phase, tasks include: all tasks in Chapter 4, determine system boundary. The deliverables (work products) include: cost-benefit analysis, feasibility study, risk management plan, system boundary document. The formal reviews include: cost-benefit analysis, feasibility study, risk management plan, system boundary document, phase-end.
In the planning phase, tasks include: all tasks in Chapter 5 plus: divide system into independent subsystems, plan incremental releases (builds). The deliverables (work products) include: acquisition plan, CM plan, QA plan, project management plan, CONOPS, systems security plan, V&V plan, system engineering management plan. The formal reviews include: acquisition plan, CM plan, QA plan, project management plan, CONOPS, systems security plan, V&V plan, systems engineering management plan, phase-end.
In the requirements analysis phase, tasks include: all tasks in Chapter 6. Note: all tasks, deliverables, and reviews from requirements analysis phase through operations and maintenance phase are done for each build defined during the planning phase. The deliverables (work products) include: FRD, test and evaluation master plan, ICD, records disposition schedule, privacy act notice. The formal reviews include: functional requirements, test and evaluation master plan, system interfaces, phase-end.
In the design phase, tasks include: all tasks in Chapter 7. The deliverables (work products) include: systems design document, implementation plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server) training plan, user manual, contingency plan, security risk assessment. The formal reviews include: design, implementation plan, conversion plan, maintenance manual, operations manual or systems administration manual (client/server), training plan, user manual, continency plan, security risk assessment, final system design, phase-end.
In the development phase, tasks include: all tasks in Chapter 8. The deliverables (work products) include: software development document, integration document, system software, test analysis report, test files/data. The formal reviews include: software peer reviews, test readiness, phase-end.
In the integration and test phase, tasks include: all tasks in Chapter 9. The deliverables (work products) include: test problem reports and test analysis approval determination, IT systems security certification and accreditation. The formal reviews include: phase-end.
In the implementation phase, tasks include: all tasks in Chapter 10. The deliverables (work products) include: version description document (per build, up to complete system), change implementation notice, post-implementation review report, delivered system. The formal reviews include: post-implementation review, version description document, phase-end.
In the operations and maintenance phase, tasks include: all tasks in Chapter 11. Note: system begins O&M project work pattern. The deliverables (work products) include: periodic system review report, user satisfaction review. The formal reviews include: periodic system review, user satisfaction review.
In the disposition phase, tasks include: all tasks in Chapter 12. The deliverables (work products) include: disposition plan, post-termination review report. The formal reviews include: post-disposition.
In the initiation phase, tasks include: identify a need or opportunity. The deliverables (work products) inlcude: Concept Proposal and Project Manager Charter. The formal reviews include: Concept Proposal.
In the concept development and planning phase, the tasks include: evaluate SCR(s), obtain approval to maintain an existing application, confirm total effort is less than 160 labor hours (otherwise, see O&M project), determine appropriate module(s) in which to make changes, identify urgency and priority, develop a work schedule and estimate of resource requirements, identify release and version number in which the change will be included, identify exiting security and privacy requirements for the application needing revision. The deliverables (work products) include: change impact assessment, change directive, project management plan (small-scale enhancement). The reviews include: IRM review of SCR, project management plan, phase-end.
In the requirements analysis and design phases, the tasks include: identify applicable requirements; issue FRD addendum, design the required change, identify needed revisions to baseline documents. The deliverables (work products) include: addendum to CONOPS, addendum to FRD, addendum to ICD, marked-up pages of baseline documents requiring changes. The reviews include: CONOPS requirements, system interfaces, updated design (phase-end).
In the development and integration and test phases, the tasks include: develop changes, make changes to appropriate documentation, revise and unit test application software, conduct system and regression testing for this change. The deliverables (work products) include: updated software development document, updated system software, updated test files/data, test analysis report with attached test problem reports, test analysis approval determination, updated integration document. The reviews include: software peer reviews, test readiness, phase-end.
In the implementation phase, tasks include: complete change implementation notice, deploy revised software and documentation, conduct required training. The deliverables (work products) include: modified software and documentation, change implementation notice. The reviews include: phase-end.
In the initiation phase, tasks include: identify an opportunity to improve. The deliverables (work products) include: Concept Proposal and Project Manager Charter. The formal reviews include: Concept Proposal.
In the concept development and planning phase, the tasks include: evaluate SCR(s), obtain approval to maintain an existing application, determine appropriate module(s) in which to make changes, identify urgency and priority, develop a work schedule and estimate of resource requirements, identify release and version number in which the change will be included, identify existing security and privacy requirements for the application needing revision. The deliverables (work products) include: change impact assessment, change directive, project management plan (based on type of maintenance). The reviews include: change control board review of SCR, project management plan, phase-end.
In the requirements analysis and design phases, the tasks include: identify applicable requirements; issue FRD addendum if SCR(s) add or modify functional or performance requirements, design the required change, identify needed revisions to baseline documents. The deliverables (work products) include: addendum to CONOPS, (enhancement only), addendum to FRD (enhancement only), addendum to ICD, marked-up pages of baseline documents requiring changes. The reviews include: CONOPS (enhancement only), requirements (enhancement only), system interfaces, updated design (phase-end).
In the development and integration and test phases, tasks include: develop changes, make changes to appropriate documentation, revise and unit test application software, conduct system and regression testing for this change. The deliverables (work products) include: updated software development document, updated system software, updated test files/data, test analysis report with attached test problem reports, test analysis approval determination. The reviews include: software peer reviews, test readiness, phase-end.
In the implementation phase, the tasks include: complete change implementation notice, deploy revised software and documentation, conduct required training. The deliverables (work products) include: modified software and documentation, change implementation notice. The reviews include: phase-end.
Conduct adaptive maintenance (ongoing), refer to the tasks, deliverables (work products) and reviews in the O&M enhancement work pattern.
Provide for help desk support (ongoing), respond to user requests for help, maintain log of trouble tickets. There are no deliverables (work products). A periodic peer review is conducted.
In the initiation phase, tasks inlcude: define business need. The deliverables (work products) include: Concept Proposal and Project Manager Charter. The reviews include: Concept Proposal.
In the concept development and planning phases, tasks include: define business need, charter user group. The deliverables (work products) include: feasibility study, cost benefit analysis, risk management plan, user group charter, project management plan, CM plan, QA plan, acquisition plan, CONOPS. The reviews include: CONOPS, system concept development and planning phase end.
In the requirements analysis phase, tasks include: identify functional requirements, identify sensitivity of the system, conduct security risk assessment, develop plan for user acceptance testing, determine privacy act implications, continue acquisition activities. The deliverables (work products) include: FRD, system security plan, security operating procedures (refer to note), contingency plan (refer to note), security risk assessment, user acceptance test plan, privacy act notice. The reviews include: requirements.
In the acquisition phase (replaces design and development), tasks include: perform market survey, evaluate products, initiate selection process, define customization requirements, prepare statement of work, obtain AIS approval, initiate purchase of selected COTS, develop user manual, prepare training plan, develop conversion plan, develop implementation plan. The deliverables (work products) include: statement of work, ICD, user manual, training plan, conversion plan, implementation plan, COTS product. The reviews include: statement of work, system interfaces, implementation plan.
In the integration and test phase, tasks include: conduct stress test, conduct network load test, conduct user acceptance test, conduct security test and evaluation, review test results, initiate problem resolutions, prepare user acceptance certificate. The deliverables (work products) include: test plan, test problem report. Reviews include: test plan.
In the implementation phase, tasks include: conduct training, convert data, implement software, charter change control board. The deliverables (work products) include: change control board charter, IT system security certification and accreditation (refer to note). There are no reviews.
In the operations and maintenance phase, tasks include: monitor system, identify problems, conduct change control board meeting, notify vendor of application problem, initiate formal acquisition request for any system customization requirement. There are no deliverables (work products) or reviews.
In the disposition phase, tasks include: all tasks in Chapter 12. The deliverables (work products) include: disposition plan, post-termination review report. The reviews include: disposition plan, post-termination (phase-end).
Note: May not be required, depending on the nature of the COTS product. This document will be more likely required for systems made up entirely of COTS products that require significant customization and integration. The decision to develop this document should be made during this life cycle phase.
Terms and definitions. Nonrecurring costs: nonrecurring costs are developmental and capital investment costs incurred only once during the analysis, design, development, and implementation of the system. Line items include: system development, prototypes, hardware purchase, module design, development, and integration, system installation and personnel. Recurring costs: Recurring costs are incurred more than once throughout the life of the system and generally include operation and maintenance costs. Line items include: operations and maintenance, telecommunications, supplies, hardware and software upgrades, maintenance, and licenses, personnel, travel and training.
Include nonrecurring costs and recurring costs for each year for alternative 1, alternative 2, and alternative 3.
Tangible benefits: benefits are expressed in dollars or in units. The result of tangible benefits may be: increased revenue, streamlined production, or saved time and money. For purposes of this analysis, tangible benefits are expressed in dollar values so that a valid comparison can be made with costs. The benefits for future years are discounted as per OMB A-94, Guidelines and Discount Rates for Benefit-Cost Analysis of Federal programs. Intangible benefits; benefits are expressed in terms of improved mission performance, improved decision making, or more reliable or usable information. These benefits may be quantifiable, but cannot be expressed in dollar values. Many public goods are difficult to reliably and validly quantify in dollar units; however, intangible benefits are vital to understanding the total outcome of implementing a particular IT system.