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


Groups, programs, and organizations interested in Software Quality.
  • Composable Software Systems - The Composable Software Systems project at Carnegie Mellon
    University focuses on three research areas: software architecture, formal
    methods, and tractable software analysis. The project develops new models,
    theories, methods, languages, and tools for classifying, specifying,
    analyzing, and designing software systems beyond the component
    level. This support could lead to substantial reduction in
    maintenance costs, improvement in software reuse, and increase
    in quality of software.

  • NASA's Software Assurance Technology Center (SATC) - The Software Assurance Technology Center (SATC) was established in 1992 as part of the Systems Reliability and Safety Office at NASA Goddard Space Flight Center (GSFC). The SATC was founded with the intent to become a center of excellence in software assurance, dedicated to making measurable improvement in both the quality and reliability of software developed for NASA at GSFC. SATC is self-supported with internal funding coming from research and application of current software engineering techniques and tools. Research funding primarily originates at NASA headquarters and is administered by it's Software IV&V Facility in Fairmont, WV. Other support comes directly from development projects for direct collaboration and technical support.


  • National Institute of Standards and Technology Software Quality Group - The Software Quality Group develops tools, methods, and related models for the tracing of software processes to
    variables and related resource utilizations, thus helping industry with improving the quality of software development and maintenance. Semantic correctness, formal methods techniques, performance assessment, and benchmarking are also
    candidate tasks for this group.

  • Society for Software Quality - The Society for Software Quality (SSQ) promotes increased knowledge and interest in the technology associated with the development and maintenance of quality software. Its charter is to advance the arts, sciences, and technologies of quality software and to nurture and
    promote professionalism in those who engage in these pursuits. Information on Software Quality, Testing and Safety can be found at this site.

  • Software Engineering Processes and Measurement Research Group at University of Kaiserslautern, Germany - Our Research Group at University of Kaiserslautern, headed by Prof. Dr. D. Rombach, is doing basic research in key software engineering areas. We do this by following an experimental software engineering paradigm called the Quality Improvement Paradigm (QIP).

  • Software Quality Institute (SQI); the University of Texas at Austin - The Software Quality Institute (SQI) is a multidisciplinary partnership between The University of Texas at Austin and the software and information systems organizations in Texas. Its mission is to inform and educate software producers and software users at the local, state and national levels about issues vital to the production and application of high-quality software. Extensive training offered to software professionals includes 48-week Software Project Management Certificate Program. About 30 seminars a year are offered on a variety of topics, including quality issues, metrics, planning, testing, requirements gathering. Object-oriented topics are also offered, such as Unified Modeling Language, OO Design and Development, Java, etc.

  • University of Maryland -- Experimental Software Engineering Group (ESEG) - The Experimental Software Engineering Group (ESEG) of the University of Maryland views the study of software engineering as a laboratory science. Specific research projects are centered around formalizing various aspects of (a) the Quality Improvement Paradigm (QIP), (b) the Experience Factory (EF), and (c) the Goal/Question/Metric approach (GQM). The QIP is aimed at building descriptive models of software processes, products, and other forms of experience, experimenting with and analyzing these models, in order to build
    improvement-oriented, packaged, prescriptive models. The EF is an organizational approach for packaging reusable software experiences and supplying them to projects and building core competencies in software.

  • University of Tennessee Software Quality Research Laboratory - The University of Tennessee Software Quality Research Laboratory does applied research and development in software engineering. Industrial sponsors support software quality research, demonstration, and technology transfer activities.

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, ITT Corporation    Privacy Policy
webmaster@thedacs.com
775 Daedalian Drive Rome, NY 13441
(800) 214-7921 Fax: 315-838-7130
This site is best viewed in Firefox 1.0+ or IE 6.0+
XHTML