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


The SoftWare Engineering Body Of Knowledge (SWEBOK) contains a taxonomy for the discipline of software engineering. The top level categories in this taxonomy, that is, the SWEBOK Knowledge Areas, are here mapped to selected DACS research areas.
  • Quality (6) - SWEBOK categorizes software quality considerations which transcend the software lifecycle processes. SWEBOK decomposes the software quality knowledge area into fundamentals, software quality management processes, and practical considerations.

  • Related Areas (2) - SWEBOK, in circumscribing software engineering, identifies disciplines with which software engineering shares a common boundary.

  • Software Configuration Management (1) - Software Configuration Management (SCM) is the discipline of identifying the configuration of software at distinct points in time for the purpose of systematically controlling changes to the configuration and of maintaining the integrity and traceability of the configuration throughout the system lifecycle. SWEBOK decomposes this knowledge area into management of the SCM process, software configuration identification, software configuration control, software configuration status accounting, software configuration auditing, and software release management and delivery.

  • Software Construction (3) - Software construction refers to the detailed creation of working, meaningful software through a combination of coding, verification, unit testing, integration testing, and debugging. SWEBOK decomposes this knowledge area into fundamentals, managing construction, and practical considerations.

  • Software Design (3) - Design is both the process of defining the architecture, components, interfaces, and other characteristics of a system or component and the result of that process. SWEBOK divides the software design process area into fundamentals, key issues, software structure and architecture, software design quality analysis and evaluation, software design notations, and software design strategies and methods.

  • Software Engineering Management (6) - Software engineering management addresses the management and measurement of software engineering. SWEBOK decomposes this knowledge area into initiation and scope definition, software project planning, software project enactment, review and evaluation, closure, and software engineering measurement.

  • Software Engineering Process (3) - Software engineering process is concerned with the definition, implementation, assessment, measurement, management, change, and improvement of the software engineering process itself. SWEBOK divides this knowledge area into process implementation and change, process definition, process assessment, and process and product measurements.

  • Software Engineering Tools and Methods (5) - SWEBOK decomposes the software engineering tools and methods knowledge area into two subareas: tools and methods. The tools subarea is decomposed as with SWEBOK itself. The methods subarea is decomposed into heuristic methods, formal methods, and prototyping methods.

  • Software Maintenance (1) - Once in operation, anomalies are uncovered, operating environments change, and new user requirements surface. The maintenance phase of the lifecycle commences upon delivery, but maintenance activities occur much earlier. SWEBOK decomposes this knowledge area into fundamentals, key issues, the maintenance process, and techniques.

  • Software Requirements (2) - A requirement is defined as a property that must be exhibited in order to solve some real-world problem. SWEBOK decomposes the software requirements knowledge area into fundamentals, the requirements process, requirements elicitation, requirements analysis, requirements specification, requirements validation, and practical considerations.

  • Software Testing (3) - Software testing consists of dynamic verification of the behavior of a program on a finite set of test cases, suitably selected from the usually infinite executions domain, against the expected behavior. SWEBOK decomposes this knowledge area into fundamentals, test levels, test techniques, test-related measures, and test process.

  • IEEE SWEBOK Site - The SoftWare Engineering Book Of Knowledge, as available from the IEEE.

Suggest Supporting Web Sites
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