" This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. "
Working Group Details
ISO/IEC/IEEE Systems and software engineering -- Architecture description
ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.
IEEE Standard for Developing a Software Project Life Cycle Process
This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010
IEEE Standard for Software Life Cycle Processes - Risk Management
A process for the management of risk in the life cycle of software is defined. It can be added to the existing set of software life cycle processes defined by the IEEE/EIA 12207 series of standards, or it can be used independently.
IEEE Recommended Practice for CASE Tool Interconnection - Characterization of Interconnections
Interconnections that need to be understood and evaluated when buying, building, testing, or using Computer-Aided Software Engineering (CASE) tools are described in this recommended practice. This recommended practice is intended to help people interconnect tools by identifying and characterizing various contexts for tool interconnection. Each context serves to define a group of interconnections pertinent to various functional perspectives. Each group contains interconnections that have a common kind of endpoint in the environment. This recommended practice considers four contexts: an organizational context for a tool, the individual user context for a tool, the platform context for a tool, and a peer context for a tool. Within a context, subsets of interconnections are characterized by a collection of common features applicable to a given functional perspective. The purpose of this recommended practice is to establish sets of interconnection features with which each perspective on a CASE tool's interconnections can be characterized.
IEEE Standard for CASE Tool Interconnections - Reference Model for Specifying Software Behavior
Computer-Aided Software Engineering (CASE) tools are used to describe the behavior of software using a variety of different design notations. These may be graphical or textual in nature, or may be a combination. This standard provides a reference model of fundamental software concepts that form the building blocks for a number of these commonly used notations. This standard also includes a textual language, the Semantic Transfer Language (STL), for representing software application behavior descriptions. A software behavior description consists of a collection of sentences that conform to the formal syntax of the STL and that are to be interpreted in terms of the software concepts defined in this standard. The STL syntax is designed to be computer-parsable, while at the same time remaining easy for users to read and write. This reference model and transfer syntax may be used for directly recording, storing, and analyzing a software behavior description, as well as for transferring elements of a software behavior description between CASE tools.
IEEE Standard for Software Reviews and Audits
Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.
IEEE Standard for a Software Quality Metrics Methodology
This IEEE Standards product is part of the family on Software Engineering. A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product software quality metrics is defined. The methodology spans the entire software life cycle.
IEEE Guide for CASE Tool Interconnections - Classification and Description
Reaffirmed September 2007. This guide describes the scope of application and interrelationships for the members of the IEEE 1175 family of standards.It points the reader to the appropriate member standard that addresses issues involved in effectively integrating computing system tools into a productive engineering environment.
IEEE Standard for Functional Modeling Language - Syntax and Semantics for IDEF0
Reaffirmed 2004. 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 non-automated. 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 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 US 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 Standard Dictionary of Measures of the Software Aspects of Dependability
A Standard Dictionary of Measures of the Software Aspects of Dependability for assessing and predicting the reliability, maintainability, and availability of any software system; in particular, it applies to mission critical software systems.