Software Engineering Tools and Methods Knowledge Area

The Software Engineering Tools and Methods knowledge area includes both software development environments and development methods.

Software development environments are the computer-based tools that are intended to assist the software development process. Development methods impose structure on the software development activity with the goal of making the activity systematic and ultimately more likely to be successful.

The partitioning of the Software Tools section uses the same structure as the overall Guide to the Software Engineering Body of Knowledge. The first nine subsections correspond to the nine other Knowledge Areas. Two additional subsections are provided: one for infrastructure support tools that do not fit in any of the earlier sections, and a Miscellaneous subsection for topics, such as tool integration techniques, that are potentially applicable to all classes of tools.

The software development methods section is divided into four subsections: heuristic methods dealing with informal approaches, formal methods dealing with mathematically based approaches, prototyping methods dealing with software development approaches based on various forms of prototyping, and miscellaneous method issues.

The above summary was adapted from the Introduction to the IEEE Computer Society's SWEBOK Guide. For more information on the Software Requirements Knowledge Area, read Chapter 10 of the SWEBOK Guide.





IEEE Std 1028™-1997


IEEE Standard for Software Reviews

This standard defines five types of software reviews, together with procedures required for the execution of each review type. This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.

IEEE Std 1175.1™-2002

IEEE Guide for CASE Tool Interconnections—Classification and Description

IEEE Std 1175.1-2002 is a guide to the IEEE 1175 family of standards. It describes how these standards are intended to be used to accomplish the effective integration of computing system tools into a productive engineering environment and sets forth the fundamental concepts on which these standards are based. These concepts establish the integrating framework for the other members of this family of standards. IEEE Std 1175.1-2002 describes the scope of application of each member standard, the various issues addressed in that standard, and the interrelationships between the family members.

IEEE Std 1320.1™-1998


IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0

IDEF0 function modeling is designed to represent the decisions, actions, and activities of an existing or prospective organization or system. IDEF0 graphics and accompanying texts are presented in an organized and systematic way to gain understanding, support analysis, provide logic for potential changes, specify requirements, and support system-level design and integration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and structured by the relationships among them, both automated and nonautomated. For new systems, IDEF0 may be used first to define requirements and to specify functions to be carried out by the future system. As the basis of this architecture, IDEF0 may then be used to design an implementation that meets these requirements and performs these functions. For existing systems, IDEF0 can be used to analyze the functions that the system performs and to record the means by which these are done.

IEEE Std 1320.2™-1998


IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (IDEFobject)

IDEF1X97 consists of two conceptual modeling languages. The key-style language supports data/information modeling and is downward compatible with the U.S. government’s 1993 standard, FIPS PUB 184. The identity-style language is based on the object model with declarative rules and constraints. IDEF1X97 identity style includes constructs for the distinct but related components of object abstraction: interface, requests, and realization; utilizes graphics to state the interface; and defines a declarative, directly executable Rule and Constraint Language for requests and realizations. IDEF1X97  conceptual modeling supports implementation by relational databases, extended relational databases, object databases, and object programming languages. IDEF1X97 is formally defined in terms of first order logic. A procedure is given whereby any valid IDEF1X97 model can be transformed into an equivalent theory in first order logic. That procedure is then applied to a meta model of IDEF1X97 to define the valid set of IDEF1X97 models.

IEEE Std 1420.1™-1995

IEEE Standard for Information Technology—Software Reuse—Data Model for Reuse Library Interoperability: Basic Interoperability Data Model (BIDM)

The minimal set of information about assets that reuse libraries should be able to exchange to support interoperability is provided.

IEEE Std 1420.1a™-1996


Supplement to IEEE Standard for Information Technology—Software Reuse—Data Model for Reuse Library Interoperability: Asset Certification Framework

A consistent structure for describing a reuse library’s asset certification policy in terms of an Asset Certification Framework is defined, along with a standard interoperability data model for interchange of asset certification information.

IEEE Std 1420.1b™-1999


IEEE Trial-Use Supplement to IEEE Standard for Information Technology—Software Reuse—Data Model for Reuse Library Interoperability: Intellectual property Rights Framework

This extension to the Basic Interoperability Data Model (IEEE Std 1420.1-1995) incorporates intellectual property rights issues into software asset descriptions for reuse library interoperability.

IEEE Std 1462™-1998


IEEE Standard—Adoption of International Standard ISO/IEC 14102: 1995—Information Technology—Guideline for the evaluation and selection of CASE tools

ISO/IEC 14102:1995 deals with the evaluation and selection of CASE tools, covering a partial or full portion of the software engineering life cycle. The adoption of the International Standard by IEEE includes an implementation note, which explains terminology differences, identifies related IEEE standards, and provides interpretation of the International Standard.

IEEE Std 1471™-2000

IEEE Recommended Practice for Architectural Description of Software Intensive Systems

This recommended practice addresses the activities of the creation, analysis, and sustainment of architectural descriptions. A conceptual framework for architectural description is established. The content of an architectural description is defined. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage.

About IEEE standard numbers.