Customer Service:
Mon - Fri: 8:30 am - 6 pm EST

Other

Other software engineering standards are published by ISO/IEC. They cover metamodel for development methodologies, general requirements, concepts and definitions, requirements for benchmarking, high level petri nets, software engineering environment services, and counting practices manual.


ISO/IEC 24744:2014

Software engineering - Metamodel for development methodologies

Development methodologies may be described in the context of an underpinning metamodel, but the precise mechanisms that permit them to be defined in terms of their metamodels are usually difficult to explain and do not cover all needs. For example, it is difficult to devise a practice that allows the definition of properties of the elements that compose the methodology and, at the same time, of the entities (such as work products) created when the methodology is applied. ISO/IEC 24744:2014 introduces the Software Engineering Metamodel for Development Methodologies (SEMDM), a comprehensive metamodel that makes use of a new approach to defining methodologies based on the concept of powertype. The aim of SEMDM is to define methodologies in information-based domains, i.e. areas characterized by their intensive reliance on information management and processing, such as software, business or systems engineering. The SEMDM combines key advantages of other metamodelling approaches with none of their known drawbacks, allowing the seamless integration of process, modelling and people aspects of methodologies. Examples are given where other metamodels are mapped to SEMDM and a brief synopsis of problems is provided. Various methodologies are defined, used, or implied by a growing number of standards, and it is desirable that the concepts used by each methodology be harmonized. A vehicle for harmonization is the SEMDM. Conformance to this metamodel will ensure a consistent approach to defining each methodology with consistent concepts and terminology.


ISO/IEC 24773-1:2019

Software and systems engineering - Certification of software and systems engineering professionals - Part 1: General requirements

This document is part one of the ISO/IEC 24773 series. It contains the requirements which will be common to all other parts of the ISO/IEC 24773 series, for certifications (schemes and bodies) in the domain of software and systems engineering.


ISO/IEC 29155-1:2017

Systems and software engineering - Information technology project performance benchmarking framework - Part 1: Concepts and definitions

ISO/IEC 29155-1:2017 identifies a framework for information technology (IT) project performance benchmarking (e.g. development or maintenance productivity) and related aspects (e.g. data collection and software classification). The framework consists of activities and components that are necessary to successfully identify, define, select, apply, and improve benchmarking for IT project performance. It also provides definitions for IT project performance benchmarking terms, which are also applicable to other parts of the ISO/IEC 29155 series. The target audience of this document are stakeholders of IT project performance benchmarking. NOTE The following are examples of how this document can be used: - by a benchmarking service provider who wants to align their benchmarking process to be consistent with this document; - by a benchmarking user (or third-party agents) for evaluating the performance of an IT project; - by an organization internally to answer specific information needs. ISO/IEC 29155-1:2017 does not cover how to organize benchmarking. It is out of the scope of this document to prescribe the name, format, or explicit content of the documentation to be produced from the benchmarking process.


ISO/IEC 29155-2:2013

Systems and software engineering - Information technology project performance benchmarking framework - Part 2: Requirements for benchmarking

ISO/IEC 29155-2:2013 provides general requirements for processes of the information technology (IT) project performance benchmarking framework by prescribing: the requirements for the processes for individual activities within the benchmarking framework (e.g. conduct benchmarking, maintain repository, submit data), the tasks necessary to successfully execute activities and equip them with components, both of which are defined in ISO/IEC 29155-1. ISO/IEC 29155-2:2013 is intended for use by any stakeholder(s) of IT project performance benchmarking (e.g. benchmarking user, benchmark provider, benchmarking service provider, and IT project team). The following are examples of how ISO/IEC 29155-2:2013 can be used: by a systems and software supplier to implement a benchmarking process to estimate and/or evaluate performance of an IT project, by a systems and software acquirer (or a third-party agent) for evaluating the performance of the supplier's IT project, by a benchmark provider to implement processes to collect and analyse IT project data and provide benchmarks, by a benchmarking service provider to implement various services (e.g. providing instruments for benchmarking, or conducting an instance of benchmarking for a benchmarking user). ISO/IEC 29155-2:2013 does not prescribe how to utilize benchmarking results, nor does it prescribe the name, format, or explicit content of the documentation that results from the benchmarking processes.


ISO/IEC 15909-1:2019

Systems and software engineering - High-level Petri nets - Part 1: Concepts, definitions and graphical notation

This document defines a Petri net modeling language or technique, called high-level Petri nets, including its syntax and semantics. It provides a reference definition that can be used both within and between organizations, to ensure a common understanding of the technique and of the specifications written using the technique. This document also facilitates the development and interoperability of Petri net computer support tools. This document is applicable to a wide variety of concurrent discrete event systems and in particular distributed systems. Generic fields of application include: requirements analysis; development of specifications, designs and test suites; descriptions of existing systems prior to re-engineering; modeling business and software processes; providing the semantics for concurrent languages; simulation of systems to increase confidence; formal analysis of the behavior of systems; and development of Petri net support tools. This document can be applied to the design of a broad range of systems and processes, including aerospace, air traffic control, avionics, banking, biological and chemical processes, business processes, communication protocols, computer hardware architectures, control systems, databases, defense command and control systems, distributed computing, electronic commerce, fault-tolerant systems, games, hospital procedures, information systems, Internet protocols and applications, legal processes, logistics, manufacturing systems, metabolic processes, music, nuclear power systems, operating systems, transport systems (including railway control), security systems, telecommunications and workflows.


ISO/IEC 15909-2:2011

Systems and software engineering - High-level Petri nets - Part 2: Transfer format

ISO/IEC 15909-2:2011 defines an XML-based transfer format for Petri nets, which are defined conceptually and mathematically in ISO/IEC 15909-1. This transfer format enables the exchange of Petri nets among different Petri net tools and among different parties. Moreover, ISO/IEC 15909-2:2011 defines some concepts and XML-based syntax for defining the detailed graphical appearance of Petri nets. The focus of ISO/IEC 15909-2:2011 is on the transfer format for Place/Transition Nets, High-level Petri Nets and Symmetric Nets. The presentation, however, is structured in such a way that it is open for future extensions, so that other versions of Petri nets can be added later. The exact definition of this extension mechanism, called Petri net type definition, is not defined in ISO/IEC 15909-2:2011; it will be defined in ISO/IEC 15909-3. The transfer format will be used to transfer specifications of systems developed in High-level Petri Nets between tools to facilitate the development of systems in teams. ISO/IEC 15909-2:2011 is written as a reference for developers of Petri net tools. It will also be useful for researchers who define new versions and variants of Petri nets.


ISO/IEC 15940:2013

Systems and software engineering - Software Engineering Environment Services

ISO/IEC 15940:2013 aims to update ISO/IEC 15940:2006 to take into account the changes of ISO/IEC 12207:2008 and to add/complete the set of Software Engineering Environment services for software and system processes. Software engineering environments services, or SEE services, refers to a collection of services, partially or fully automated by software tools, that are used to support the execution of human activities in systems and software engineering. ISO/IEC 12207:2008 describes a comprehensive set of processes, activities and tasks to be performed when acquiring or developing a system/software. It does not address their implementation or their automation. These activities are usually carried out within a software or system development/maintenance project, and cover such areas as the specification, development, re-engineering or maintenance of systems. ISO/IEC 15940:2013 describes SEE services and relates them to ISO/IEC 12207:2008 in a manner applicable to a range of organizations. In defining a life cycle process for an organization, the user needs to find the appropriate level of automation provided by a software engineering environment. This may result in establishing a new SEE service or improving an existing one. The suite of SEE services described supports the process definitions in ISO/IEC 12207:2008. The purpose is to define a set of SEE services that are compatible with ISO/IEC 12207:2008, and that can be used either as a general reference, or to define an automated software and system process.


ISO/IEC 20968:2002

Software engineering - Mk II Function Point Analysis - Counting Practices Manual

ISO/IEC 20968:2002 specifies the set of definitions, conventions and activities of the MkII FPA Functional Size Measurement Method. The method can be used to measure the functional size of any software application that can be described in terms of logical transactions, each comprising an input, process and output component. The sizing rules were designed to apply to application software from the domain of business information systems, where the processing component of each transaction tends to be dominated by considerations of the storage or retrieval of data. The method may be applicable to software from other domains, but the user should note that the sizing rules do not take into account contributions to size such as from complex algorithms as typically found in scientific and engineering software, nor do the rules specifically take into account real-time requirements MK II FPA is independent of the project management method to be used and of the development method employed. It is a measure of the logical, business requirements, independent of how they are implemented.


ANSI Logo

As the voice of the U.S. standards and conformity assessment system, the American National Standards Institute (ANSI) empowers its members and constituents to strengthen the U.S. marketplace position in the global economy while helping to assure the safety and health of consumers and the protection of the environment.

CUSTOMER SERVICE
NEW YORK OFFICE
ANSI HEADQUARTERS