BS ISO IEC IEEE — ISO_IEC_IEEE Joint International Standards Single-File Series Overview (13 Standards)

💻 BS ISO IEC IEEE is BSI’s designation for British Standards that adopt international standards jointly published by the International Organization for Standardization (ISO), the International Electrotechnical Commission (IEC) and the Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE joint standards typically merge same-titled ISO/IEC and IEEE standards (e.g. ISO/IEC 12207 with IEEE 12207), forming the most important international standard family in “systems and software engineering”. BSI committee IST/15 (Software and systems engineering) has led most of the UK participation. This batch collects 13 BS ISO/IEC/IEEE single-file standards, centred on the systems and software engineering (SSE) process standards, complemented by the Ubiquitous Green Community Control Network (UGCCNet) protocol family and the high-voltage shore connection (HVSC) standard, covering life-cycle processes, content of information products (documentation), requirements engineering, architecture description, life-cycle management planning, vocabulary, content management, website engineering, and port shore supply.

1. Series Overview and Document Inventory 📌

All 13 documents in this batch are single-file series. ISO/IEC/IEEE 15288, 15289, 24748, 24765, 26531, 29148 and 42010 belong to the “systems and software engineering life-cycle process” family; 18880–18883 form the UGCCNet (IEEE 1888) protocol family; and 80005-1 is the international standard for high-voltage shore connection in ports. The table below lists the complete inventory.

2. Representative Standard (1): BS ISO/IEC/IEEE 15288 System Life Cycle Processes 🔄

BS ISO/IEC/IEEE 15288:2015 is the framework international standard for system life-cycle processes, extending beyond pure software to the “system” as a whole — including hardware, software, data, personnel, processes, facilities and natural entities. It partitions system life-cycle processes into four categories: Agreement Processes (acquisition and supply), Organizational Project-Enabling Processes, Technical Management Processes (planning, assessment, decision, risk management, configuration management, information management, etc.) and Technical Processes (stakeholder needs definition, requirements analysis, architecture design, implementation, integration, verification, transition, operation, maintenance and disposal). For each process the standard defines purpose, inputs, activities and outputs.

15288 is widely adopted by aerospace, defence, rail, energy and ICT industries, and is usually applied together with ISO/IEC/IEEE 12207 (software life-cycle processes). It is the core methodological basis of Systems Engineering as a discipline and a direct reference of the Systems Engineering Body of Knowledge (SEBoK) and INCOSE practice.

3. Representative Standard (2): BS ISO/IEC/IEEE 29148 Requirements Engineering 📋

BS ISO/IEC/IEEE 29148:2011 specifies requirements engineering processes and product requirements, covering elicitation, analysis, specification and validation of stakeholder and system/software requirements, and provides the content framework of requirements documents (e.g. clause structure of requirements specifications) and the quality attributes of requirement statements (unique, complete, consistent, verifiable, traceable, unambiguous, etc.). It is the detailed implementation of the “stakeholder needs definition” and “requirements analysis” technical processes of 15288.

Requirements engineering is the highest-defect-cost phase of system development: the cost of fixing a requirements defect grows exponentially as the development stage advances. By standardising the expression and validation of requirements, 29148 helps projects capture errors early and is the “first quality gate” of modern mixed systems engineering and agile practice.

4. Representative Standard (3): BS ISO/IEC/IEEE 42010 Architecture Description 🏛️

BS ISO/IEC/IEEE 42010:2011 (formerly IEEE 1471) specifies the framework and terminology of Architecture Description (AD), establishing the conceptual system of “Architecture, Architecture Description, View, Viewpoint, Architecture Concern, Stakeholder, Architecture Model”. The standard requires an architecture description to define its stakeholders and concerns explicitly and to provide a corresponding viewpoint and view for each concern, ensuring traceability and communicability of architecture decisions.

42010 is the common vocabulary basis for software and system architecture practice: whether TOGAF, ArchiMate or government/defence architecture frameworks (e.g. DoDAF, MODAF-derived frameworks), their “view-viewpoint” mechanism traces back to 42010. It directly guides how the architecture design process of ISO/IEC/IEEE 15288 is conducted.

5. Representative Standard (4): Port High-Voltage Shore Connection BS ISO/IEC/IEEE 80005-1 ⚓

BS ISO/IEC/IEEE 80005-1:2012 specifies the general requirements for High Voltage Shore Connection (HVSC) systems, including matching of shore voltage (typically 6.6/11 kV) and frequency (50/60 Hz), connection/disconnection procedures, safety interlocks, protection coordination, monitoring and control, and interchangeability of the ship-shore interface. It was jointly developed by ISO (ships and marine technology), IEC (ship electrical installations) and IEEE (shore power), and is the core document for standardising “cold ironing”/shore power under IMO and port-emission-reduction initiatives.

Shore power lets a berthed ship shut down its auxiliary engines and connect to the port grid, significantly reducing NOx, SOx, PM and CO₂ emissions and noise in the port area. The standard’s unified requirements for ship-shore connectors, cable management and communication interfaces enable interoperability between different ports and ship types. On the BSI side, JPEL/18 (Electrical installations of ships and of mobile and fixed offshore units) is responsible.

6. Representative Standards (5): Ubiquitous Green Community Control Network 18880 Series 🌱

BS ISO/IEC/IEEE 18880:2015 specifies the base protocol architecture of the Ubiquitous Green Community Control Network (UGCCNet, IEEE 1888); its companion documents 18881 (control and management), 18882 (heterogeneous networks convergence and scalability) and 18883 (security) complete the protocol family from the management, interconnection and security perspectives. UGCCNet targets energy-consumption monitoring, lighting control and green-building management at campus/community level, using a registry-centre-based distributed service architecture with an XML data model to support multi-vendor interoperability.

The 18880 series is one of the representative international standards for IoT control in “ubiquitous green communities”. Its loosely coupled “registry-centre — node — application” structure achieves scalability and security, providing a standardised communication basis for energy metering and regulation in smart parks and green buildings; the technology also has a significant ecosystem in China (aligned with GB/T promotion).

7. Remaining Standards at a Glance 📋

• Documentation and information products: 15289 specifies the organisation and content of life-cycle information products (documentation); 26531 specifies content management (CM) requirements for product life-cycle, user and service management documentation; 23026 specifies engineering and management of websites for systems, software and services information, covering website planning, design, deployment and operation.
• Planning and vocabulary: 24748-4 specifies systems engineering planning (including the content of the Systems Engineering Management Plan, SEMP), superseding BS ISO/IEC 26702:2007; 24765 provides a unified vocabulary for systems and software engineering, the shared terminology basis of the SSE standard family.
• Standardisation package: these process standards together form the complete “process — product — documentation — vocabulary” package of the ISO/IEC/IEEE 12207/15288 family, and are common references of CMMI, management systems and engineering procurement contracts.

8. Frequently Asked Questions ❓