Software Quality & Systems Engineering
Documents and Publications
Methodologies
Departmental Information Systems Engineering
The Departmental Information Systems Engineering (DISE), Volume 1 (pdf), Information Systems Engineering Lifecycle, provides an overview of information systems engineering, project initiation and strategic planning activities, resources, and quality management. It includes a discussion on drivers, roles, capital planning, acquisition, and Information Architecture as they relate to information systems projects.
The Departmental Information Systems Engineering (DISE), Volume 2 (pdf), Managing DOE IT Projects, provides guidance on project management practices such as earned value and performance measurement, and project life cycle processes such as project planning and control, tracking and oversight, estimating and uses of project plans and work breakdown structures.
HQ Project Management Guide (pdf)
The purpose of this document is to present an overview of project management processes that can be consistently and repeatably used in the planning, budgeting, management, and execution of IM and IT projects. The document defines activities required for project authorization and justification, and outlines project roles and responsibilities, and other processes involved in conducting a project.
IEEE SWEBOK
The SWEBOK project is a joint effort of the IEEE Computer Society and the Association for Computing Machinery to develop a guide to the Software Engineering Body of Knowledge. The effort seeks to determine the core subset of knowledge characterizing the software engineering discipline. Additional information may be found at the IEEE website.
PMI PMBOK® - Online Guide
The "Project Management Body of Knowledge" (PMBOK®) is an inclusive term that describes the sum of knowledge within the profession of project management. This full body of knowledge includes knowledge of proven, traditional practices, which are widely applied, as well as knowledge of innovative and advanced practices, which may have seen more limited use.
SEI CMMI
Capability Maturity Models (CMMs) assist organizations in maturing their people, process, and technology assets to improve long-term business performance. The SEI has developed CMMs for Systems Engineering and Integrated Product Development. A current priority of the SEI is CMM Integration (CMMI).
Systems Engineering Methodology (SEM) (pdf)
The SEM integrates systems engineering, software engineering, project management, and quality assurance processes into a lifecycle that is controllable, predictable, and repeatable. The lifecycle processes are compatible with Departmental policy on development and maintenance of information technology projects, and compliant with Level 2 and 3 key process areas in the Software Engineering Institute's Capability Maturity Model. The lifecycle processes are divided into stages, activities, and tasks that can be combined or modified as necessary to fit the needs of various types and sizes of projects.
Crosswalk to the SEI CMM-SW Level 2 (pdf) Level 3 (pdf)
Listing of SEI/CMM-SW Key Process Areas (KPAs) and a crosswalk to the SEM chapters, work products, and web site location where these KPAs are addressed.
SEM Record of Changes (pdf)
Provides a record and audit trail of changes to the SEM since its last publication.
SEM Change Request Form (pdf)
The change request form is used to communicate requests for changes to the SEM and is provided to facilitate the submission of such requests.
Process Guides
ABC Guideline
Guideline for Analysis of Benefits and Costs (ABC). The purpose of this document is to present an overview of project management processes that can be consistently and repeatably used in the planning, budgeting, management, and execution of IM and IT projects. The document defines activities required for project authorization and justification, and outlines project roles and responsibilities, and other processes involved in conducting a project.
Basic Performance Measures for Technology Projects (pdf)
A white paper to provide guidance for project teams in the identification of performance measures oriented to information technology (IT) projects, which allow for the collection and reporting of project data to help track and assess project progress, product quality, project success, and customer satisfaction.
Computer System Retirement (pdf)
This procedure establishes the process for the orderly retirement of information systems, regardless of software platform or size, both classified and unclassified. It also addresses the disposition of IS records according to DOE requirements.
Guidelines for Software Measurement, SQAS (pdf)
This document defines a core set of four software measures that can be used within any software organization to characterize a software project and to improve software project processes and products.
In-Stage Assessment (pdf)
Provides guidance on conducting an In-Stage Assessment (ISA). An ISA is an independent review of a project's processes, work products, and deliverables, conducted in all stages of the software development and maintenance lifecycle.
PGMA Model (pdf)
The PGMA (Policy, Guidance, Metrics, Assessment) model provides guidance on developing corresponding elements for the components of the model.
Planning for a Software Process Assessment, SQAS (pdf)
This report presents a guide for how to plan for a software assessment and how to use the assessment results to guide process improvement. It defines the steps associated with conducting a successful assessment and identifies the framework needed to establish a successful process improvement program. The assessment methodology is based upon the Software Engineering Institute's (SEI) software process assessment.
Preparation for a Software Quality Audit, SQAS (pdf)
This document will enable a site to prepare for a software quality audit by providing specific guidance. It will also provide guidance to a site that would enable it to perform a software quality audit.
Requirements Management Awareness (pdf)
Describes the benefits of good requirements specifications and the risks and pitfalls associated with incomplete or unclear requirements.
Requirements Management, SQAS (pdf)
Guideline document intended to help project teams and organizations plan, manage, and improve their requirements definition and management. Provides guidelines for establishing, implementing, and sustaining requirements management processes throughout a project and product lifecycle.
Risk Management, SQAS (pdf)
A practical guide for integrating risk management into a software project.
Software Configuration Management - A Practical Guide, SQAS (pdf)
Provides a practical guide for integrating software configuration management disciplines into the management of software engineering projects. Other publications on software engineering best practices, adopted as DOE guidance, are available from the SQAS web site.
Software Quality: A Guide to Responsibilities and Resources, SQAS (pdf)
This Guide provides guidance to the software managers, software developers, and software quality engineers at DOE sites, to foster the advance of good software management concept.
Software Quality Assurance Control of Existing Systems, SQAS (pdf)
Existing software systems often represent significant investments and play important roles in the every day businesses of organizations. To meet current and future operational needs, organizations need to plan how best to address these support issues. Some of the issues to consider are presented in this document with references to related standards for further detailed examination. Two tutorials, one based on software maintenance and another detailing a baseline recovery strategy are included..
Stage Exit Process (pdf)
Practical guidance on implementing a stage exit process. A stage exit is a vehicle for securing the concurrence (i.e., approval) of designated individuals to continue with a project and move forward into each subsequent stage of development or maintenance.
Structured Walkthrough Training and Guidance (pdf)
Classroom or individual project team training and materials on how to conduct structured walkthroughs (peer review of products/code). This process guide describes how to conduct a structured walkthrough during the lifecycle stages of software engineering development and maintenance projects, regardless of hardware or software platform.
Checklists
Acceptance (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in identifying and planning system acceptance activities. The checklist reflects recognized acceptance management activities.
Configuration Management (pdf)
This checklist is intended to provide system owners, project managers, configuration managers, and other information systems development and maintenance professionals with guidance in identifying and planning configuration management (CM) activities. The checklist reflects recognized CM activities to be performed throughout the information systems (IS) life cycle.
Design (pdf)
This checklist is intended to provide system owners, project managers, configuration managers, and other information systems development and maintenance professionals with guidance in identifying and planning system design activities. The checklist reflects recognized design activities to be performed throughout the information systems (IS) life cycle.
Maintenance (pdf)
This checklist is intended to provide system owners, project managers and other information systems developers and maintainers with guidance in identifying and planning information systems maintenance activities.
Pre-Acceptance (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in preparation for the acceptance activities. Initiation of acceptance activities begins with successful completion of system testing.
Project Planning (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in identifying and documenting project planning activities. The checklist reflects recognized project planning activities to be performed throughout the information system (IS) life cycle.
Project Tracking (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in identifying and planning project tracking activities. The checklist reflects recognized project tracking activities to be performed throughout the information systems (IS) life cycle.
Quality Assurance (pdf)
This checklist is intended to provide system owners, project managers and other information systems development and maintenance professionals with guidance in identifying and planning quality assurance (QA) activities. The checklist reflects recognized QA activities to be performed throughout the information systems (IS) life cycle.
Requirements Management (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in identifying and planning requirements management activities. The checklist reflects recognized requirements management activities to be performed throughout the information systems (IS) life cycle.
Risk Assessment Questionnaire (pdf)
This self assessment questionnaire provides project managers with a tool for identifying and planning for potential project risks. It is applicable to a variety of projects.
Security (pdf)
This checklist is intended to provide system owners, project managers, and other information systems development and maintenance professionals with guidance in preparation for identifying the security issues during the acceptance activities. Initiation of acceptance activities begins with successful completion of system testing.
Testing (pdf)
This checklist is intended to provide system owners, project managers, configuration managers, and other information system development and maintenance professionals with guidance in identifying and planning testing activities. The checklist reflects recognized testing activities to be performed throughout the information systems (IS) life cycle.
Training (pdf)
This checklist is intended to provide system owners, project managers, trainers, and other information system development and maintenance professionals with guidance in identifying and planning training activities. The checklist reflects recognized training activities to be performed in support of the information systems (IS) life cycle.
Templates
Acceptance Test Plan (pdf)
This template is used to document the plan for performing the systems acceptance test, the roles and responsibilities of individuals involved and the tests to be performed.
Acquisition Plan (pdf)
This template is used for documenting the plans for acquiring hardware, software and communications equipment for a systems development project.
Change Control Forms:
Use the Software Change Request form in conjunction with the SCR Log form to record supplementary details about a given software change request.
Configuration Management Plan (pdf)
This template is used for documenting the configuration management methodology, tools, techniques, roles and responsibilities and tasks for a systems development project.
Continuity of Operations Plan (pdf)
The Continuity of Operations Plan template is used for documenting the plan of actions to be taken to provide the capability to continue mission-essential processing and restore normal operations after a disaster
Conversion Plan (pdf)
This template is used to document the conversion plan that clearly defines the system or project's conversion procedures; outlines the installation of new and converted files/databases; coordinates the development of file-conversion programming, and plans the implementation of conversion procedures.
Feasibility Study (pdf)
This template is used for documenting the methodology and outcome of a feasibility study.
Functional Design (pdf)
This template can be used to document a system's functional design.
System Design (pdf)
This template is used to define the system design.
System Retirement
The System Retirement template contains DOE headquarters-specific information that may be adapted for use by any site or organization. It is recommended that this template be used in conjunction with the SEM Computer System Retirement Guidelines (pdf) and information provided in the Records Management page.
This template is used to define the plan, scope, roles and responsibilities for a system being retired.
Training Plan (pdf)
This template is used to define the plan, scope, environment, roles and responsibilities for training needs for system/software development and installation.
Transition Plan (pdf)
This template is used to define the objectives, resources, and plans for systems transition, e.g., scheduling the transition from acceptance testing to full operational status, identifying staffing and training needs for system operation and maintenance, planning for data migration, etc.
Document Samples
CITSS Configuration Management Plan
A software configuration management plan (pdf) and configuration items list (pdf), from an actual project that can be downloaded and used as templates for your particular project.
CITSS Project Plan (pdf)
The Customer Information Technology Support System (CITSS) Project Plan, from an actual DOE Commercial Off-The-Shelf (COTS) software integration project, can be used as a template to facilitate the creation of the project plan for your particular project.
CITSS Training Plan (pdf)
The Customer Information Technology Support System (CITSS) Training Plan, from an actual DOE Commercial Off-The-Shelf (COTS) software integration project, can be used as a template to facilitate the creation of the training plan for your particular project.
CSR Software Quality Assurance Plan (pdf)
The actual Software Quality Assurance Plan (SQAP) for the Center for Space Research (CSR) can be used as a template to facilitate the creation of the SQA plan for your project.
DOCS System Configuration Management Plan (pdf)
The DOCS Systems Configuration Management Plan (SCMP), from an actual DOE systems engineering project, can be used as a template to facilitate the creation of the CMP for your particular project.
EC-Web Project Plan (pdf)
The Electronic Commerce World Wide Web (EC-WEB) Project Plan, from an actual DOE software engineering project, can be used as a template to facilitate the creation of the project plan for your particular project. EC-WEB is a Lotus Notes based DOE business application.
FMIS Configuration Management Plan (pdf)
The FMIS Software Configuration Management Plan (SCMP), from an actual DOE software engineering project, can be used as a template to facilitate the creation of the SCMP for your particular project.
NMMSS Software Quality Assurance Plan (pdf)
The Software Quality Assurance Plan (SQAP) for the Nuclear Materials Management and Safeguard System (NMMSS) software upgrade project (an actual DOE software development project) can be used as a template to facilitate the creation of the SQA plan for your particular project.
Last Updated: 3/18/2008
|
