Email:
Password: [?] 
  Register with the DACS
Site Search: Advanced Search
Search: Bibliographic Database(SEBD)      Lifecycle Database(SLED)    DoD Acronyms 
DACS Home DACS Services Publications Training About Us DACS Store Suggest A Link
Rate this page's content:
  poor
excellent


  • Defining Software Process Improvement - CrossTalk (February 1996) - by Dr. David J. Szymanski and Capt. Thomas D. Neff. The authors propose a working definition of software process improvement pointing to its importance to several persons including those involved in software engineering process groups (SEPGs). The definition is based on denotations of process and software process advanced by the Institute of Electrical and Electronics Engineers (IEEE) and the Software Engineering Institute (SEI), and a definition of process improvement based on a value-added approach. The definition of software process improvement (SPI) is offered for consideration.- CrossTalk is a publication of the DoD Software Technology Support Center (STSC).

  • Measurement for Process Improvement, Sept 2005 - This technical report, prepared by PSM, provides measurement guidance for Process Improvement using the PSM approach. It represents activities of the PSM community since 1998. It identifies areas of PI that have needs for measures, measuring the value of PI, readiness for PI, and PI progress. It contains many resources related appendices.

  • Process Maturity Profile - Semi-Annual Process Maturity Profile of the Software Community from the SEI.

  • Process Tailoring for Software Project Plans - This report has been developed to address the most obvious issues that arise when tailoring a set of building blocks to the unique aspects of a software project. The report discusses the concept of software processes at the organization and project levels and how these processes are implemented through software development plans. An example is used to show how an organization's standard software process can be tailored and implemented as a project's defined software process. The report presents information on automated tool support for documenting a project's defined software process and providing inputs to a project plan based on the chosen software process.

  • Process Technologies Method and Tool Report - Volume I is a synopsis of the progress of the Software Technology Support Center (STSC) in evaluating process technologies. A software process is a set of activities, methods, practices, and transformations that people use to develop and maintain software and associated products. Process technologies are defined as those technologies that can be applied to support an organization's software process. Volume II contains detailed information on process products, user critiques of products, and IDEF training information. {MS-WORD Zip format}

  • Reengineering Technology Report - The purpose of this report is to increase contact, awareness, and understanding of software reengineering tools. Use of this report should be the first step in transferring effective software reengineering processes, methods, and tools into practical use. The targets of this report are organizations responsible for the development and maintenance of computer software. This report defines the ideas of software reengineering and identifies their value in improving software quality for embeded, MCCR, and MIS applications. It explains how the features of current reengineering tools can improve software development and maintenance. It includes information about specific products in the marketplace. The information is aimed at those who must make the decisions about acquiring advanced technology and prepare their organizations to use it effectivly. Also, this report attempts to identify the future directions of the field to help in planning long-range stategies. Volume II contains detailed information on reengineering products lists, and product sheets. {Zip format of MS-WORD and Word Perfect documents}

Suggest Supporting Web Sites
Related pages:
sidebar
sidebar
sidebar

s

s

s

s


SISOS cover
DACS Latest Technical Report


TEMS Logo
Visit the DTIC TEMS Initiative

   DACS Gold Practice Initiative ROI Dashboard
 
Acquisition Process Improvement
Architecture-First Approach
Assess Reuse Risks and Costs
Binary Quality Gates at the Inch-Pebble Level
Capture artifacts in rigorous, model-based notation
Commercial Specifications and Standards/Open Systems
Defect Tracking Against Quality Targets
Develop and Maintain a Life-cycle Business Case
Ensure Interoperability
Formal Inspections
Formal Risk Management
Goal-Question-Metric Approach
Integrated Product and Process Development
Manage Requirements
Metrics-based Scheduling
Model Based Testing
Plan for Technology Insertion
Requirements Trade-Off/Negotiation
Statistical Process Control
Track Earned Value
  Access benefit data from software technical and management improvements including SEI CMMI, PSP/TSP, Cleanroom, Inspections, and Agile Development.

View the ROI Dashboard
Copyright © 2010, QSI    Privacy Policy
This site is best viewed in Firefox 2.0+ or IE 6.0+
XHTML