Loading AI tools
From Wikipedia, the free encyclopedia
ISO/IEC JTC 1/SC 7 Software and systems engineering is a standardization subcommittee of the Joint Technical Committee ISO/IEC JTC 1 of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), that develops and facilitates standards within the field of engineering of software products and systems. The international secretariat of ISO/IEC JTC 1/SC 7 is the Bureau of Indian Standards (BIS) located in India.[1]
Abbreviation | ISO/IEC JTC1/SC7 |
---|---|
Formation | 1987 |
Merger of | ISO/TC 97 and IEC/TC 83 |
Type | Standards organization |
Purpose | Standardization of processes, supporting tools and supporting technologies for the engineering of software products and systems |
Headquarters | Bureau of Indian Standards, India |
Region served | Worldwide |
Membership | National standards organisations |
Official language | English, French |
Main organ | Plenary meeting |
Parent organization | ISO/IEC Joint Technical Committee 1 |
Website | www |
Formerly called | ISO/IEC JTC1/SC7 Software engineering |
ISO/IEC JTC 1/SC 7 was first established in 1987, though the origins of the subcommittee began with ISO/TC 97, established in 1960 as a standardization technical committee in the field of information processing. With the formation of ISO/IEC JTC 1 in 1987, ISO/TC 97 and IEC/TC 83 were combined to form ISO/IEC JTC 1/SC 7, Software Engineering.[2] In 2000, the subcommittee changed its title from Software Engineering to its current title, Software and Systems Engineering.[3] ISO/IEC JTC 1/SC 7 held its first plenary in Paris, France in 1987.[2]
The scope of ISO/IEC JTC 1/SC 7 is the “Standardization of processes, supporting tools and supporting technologies for the engineering of software products and systems,” including
The mission of ISO/IEC JTC 1/SC 7 is to
As of August 2020, ISO/IEC JTC 1/SC 7 is made up of 14 active working groups (WGs), three ad hoc working groups (AHGs) and five advisory groups (AGs). Each of these groups carries out specific tasks in standards development within the field of systems and software engineering. As a response to standardization needs within the field of software and systems engineering, working groups within ISO/IEC JTC 1/SC 7 were disbanded if their working area was no longer applicable, or established if new working areas arose. The focus of each working group, special working group, advisory group, and task force is described in the group’s terms of reference.
Active working groups of ISO/IEC JTC 1/SC 7 are:[4][5]
Working Group | Working Area |
---|---|
ISO/IEC JTC 1/SC 7/WG 2 | System Software Documentation |
ISO/IEC JTC 1/SC 7/WG 4 | Tools and Environment |
ISO/IEC JTC 1/SC 7/WG 6 | Software Product and System Quality |
ISO/IEC JTC 1/SC 7/WG 7 | Life Cycle Management |
ISO/IEC JTC 1/SC 7/WG 10 | Process Assessment |
ISO/IEC JTC 1/SC 7/WG 19 | Open Distributed Processing (ODP) and Modeling Languages |
ISO/IEC JTC 1/SC 7/WG 20 | Software and Systems Bodies of Knowledge and Professionalization |
ISO/IEC JTC 1/SC 7/WG 21 | Information Technology Asset Management |
ISO/IEC JTC 1/SC 7/WG 22 | Vocabulary validation |
ISO/IEC JTC 1/SC 7/WG 24 | Systems and Software Standards for Very Small Entities |
ISO/IEC JTC 1/SC 7/WG 26 | Software Testing |
ISO/IEC JTC 1/SC 7/JWG 28 | Common Industry Formats for Usability Reports (Joint between ISO/IEC JTC 1/SC 7 and ISO/TC 159/SC 4) |
ISO/IEC JTC 1/SC 7/WG 29 | Agile and DevOps |
ISO/IEC JTC 1/SC 7/WG 42 | Architecture |
Ad Hoc Group | Working Area |
ISO/IEC JTC 1/SC 7/AHG 3 | System resiliency |
ISO/IEC JTC 1/SC 7/AHG 4 | Machine Readable Standards |
ISO/IEC JTC 1/SC 7/AHG 5 | Cyber physical systems |
ISO/IEC JTC 1/SC 7/AHG 6 | Digital Engineering |
Advisory Group | Working Area |
ISO/IEC JTC 1/SC 7/AG 1 | Chair’s Advisory Group |
ISO/IEC JTC 1/SC 7/AG 2 | Business planning group |
ISO/IEC JTC 1/SC 7/AG 3 | Communications and outreach |
ISO/IEC JTC 1/SC 7/AG 4 | Standards management |
ISO/IEC JTC 1/SC 7/AG 5 | Architecture and future watch |
ISO/IEC JTC 1/SC 7 also had one task force, “Spanish Translation Task Force”.
ISO/IEC JTC 1/SC 7 works in close collaboration with a number of other organizations or subcommittees, both internal and external to ISO or IEC, in order to avoid conflicting or duplicative work. Organizations internal to ISO or IEC that collaborate with or are in liaison to ISO/IEC JTC 1/SC 7 include:[6]
Some organizations external to ISO or IEC that collaborate with or are in liaison to ISO/IEC JTC 1/SC 7 include:[6]
Countries pay a fee to ISO to be members of subcommittees.[7]
The 40 "P" (participating) members of ISO/IEC JTC 1/SC 7 are: Argentina, Australia, Belgium, Brazil, Canada, China, Costa Rica, Czech Republic, Denmark, Finland, France, Germany, India, Ireland, Israel, Italy, Jamaica, Japan, Kazakhstan, Republic of Korea, Luxembourg, Malaysia, Mexico, Netherlands, New Zealand, Peru, Poland, Portugal, Romania, Russian Federation, Slovakia, South Africa, Spain, Sweden, Switzerland, Thailand, Ukraine, United Kingdom, United States of America, and Uruguay.
The 20 "O" (observing) members of ISO/IEC JTC 1/SC 7 are: Austria, Bosnia and Herzegovina, Chile, Colombia, Cuba, Cyprus, Estonia, Ghana, Hong Kong, Hungary, Iceland, Indonesia, Islamic Republic of Iran, Kenya, Morocco, Norway, Philippines, Serbia, the Republic of Macedonia, and Turkey.[8]
ISO/IEC JTC 1/SC 7 currently has 153 published standards within the field of software and systems engineering, including:[9]
ISO/IEC Standard | Title | Status | Description | WG[10] |
---|---|---|---|---|
ISO/IEC TR 19759 | Software Engineering – Guide to the Software Engineering Body of Knowledge (SWEBOK) | Published (2005) | Identifies and describes the subset of body of knowledge of software engineering that is generally accepted[11] | 20 |
ISO/IEC 15288 | Systems and software engineering – System life cycle processes | Published (2008) | Establishes a common framework for describing the life cycle of systems created by humans and defines a set of processes and associated terminology[12] | 7 |
ISO/IEC 12207 | Systems and software engineering – Software life cycle processes | Published (2008) | Establishes a common framework for software life cycle processes with well-defined terminology[13] | 7 |
ISO/IEC 20000-1 | Information technology – Service management – Part 1: Service management system requirements | Published (2011) | Specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain, and improve a service management system (SMS)[14] | 25 |
ISO/IEC 15504-1 | Information technology – Process assessment – Part 1: Concepts and vocabulary | Published (2004) | Provides overall information on the concepts of process assessment and its use in the two contexts of process improvement and process capability determination[15] | 10 |
ISO/IEC/IEEE 42010 | Systems and software engineering – Architecture description | Published (2011) | Addresses the creation, analysis, and sustainment of architectures of systems through the use of architecture descriptions[16] | 42 |
ISO/IEC TR 29110-1 | Software engineering – Lifecycle profiles for Very Small Entities (VSEs) – Part 1: Overview | Published (2011) | Introduces the characteristics and requirements of a VSE and clarifies the rationale for VSE-specific profiles, documents, standards, and guides[17] | 24 |
ISO/IEC TR 9126-2 | Software engineering – Product quality – Part 2: External metrics | Published (2003) | Provides external metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1[18] | |
ISO/IEC 10746-1 | Information technology – Open Distributed Processing – Reference model: Overview | Published (1998) | Provides:[19]
|
19 |
ISO/IEC 19770-1 | Information technology – Software asset management – Part 1: Processes and tiered assessment of conformance | Published (2012) | Establishes a baseline for an integrated set of processes for Software Asset Management (SAM), divided into tiers to allow for incremental implementation, assessment, and recognition[20] | 21 |
ISO/IEC 24744 | Software engineering—Metamodel for development methodologies | Published (2014) | Specifies a metamodel for development methodologies and related information.[21] | 19 |
ISO/IEC/IEEE 26511 | Systems and software engineering — Requirements for managers of user documentation | Published (2011) | Specifies procedures for managing user documentation throughout the software life cycle.[22] | 2 |
ISO/IEC/IEEE 26512 | Systems and software engineering—Requirements for acquirers and suppliers of user documentation | Published (2011) | Defines the documentation process from the acquirer's standpoint and the supplier's standpoint.[23] | 2 |
ISO/IEC/IEEE 26513 | Systems and software engineering — Requirements for testers and reviewers of user documentation | Published (2009) | Defines the process in which user documentation products are tested.[24] | 2 |
ISO/IEC/IEEE 26514 | Systems and software engineering — Requirements for designers and developers of user documentation | Published (2008) | Specifies the structure, content, and format for user documentation, and provides informative guidance for user documentation style.[25] | 2 |
ISO/IEC/IEEE 26515 | Systems and software engineering — Developing user documentation in an agile environment | Published (2011) | Specifies the way in which user documentation can be developed in agile development projects.[26] | 2 |
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.