ISO/IEC/IEEE 42010:2011, Systems and software engineering—Architecture Description Released

Just received news from Rich Hilliard via the IEEE 1471 Users List (to become the “ISO/IEC/IEEE 42010 Users List):

Today I was notified that IEEE P42010 was approved as a revised standard by the IEEE-SA Standards Board on 31 October 2011.

This standard replaces IEEE 1471:2000 and is identical to the ISO standard approved in July with 21 approvals and 0 disapprovals from member bodies.

The new standard, designated ISO/IEC/IEEE 42010:2011, Systems and software engineering—Architecture description, is available from IEEE and ISO.

The IEEE 1471 website will become the ISO/IEC/IEEE 42010 website.

The old website will redirect to the new URL which is:

• https://www.iso-architecture.org/42010/

Looking at the website I noticed

Per IEEE rules: An approved IEEE standard will remain active for   ten years. If the Sponsor does not complete a revision process   within ten years, the standard will be transferred to inactive   status.

Curious to know whether this means a standard has to be revised or whether the requirement is simply to review - it might still be a perfectly good standard even if it hasn’t been revised since the decision might be on review that it’s good enough.

Having to say ISO/IEC/IEEE every time is a bit of a mouthfull and therefore inevitably will be shortened in everyday use. Is there an acceptable shortform(s) e.g. ISO 42010, IEC 42010 and IEEE 42010? It’s unlikely in speech that the full qualification will be used.

Comments

Logged-in site members can receive notifications of comments made on this article.

Comment on this article

Related Articles

Linked directly:

• Conformance Assessment vs ISO/IEC 42010:2011
• New Revision (“The ISO 42010 Mix”) of TRAK Released

Sharing tags:

• What Would a TRAK View Look Like in a Graph Database? Part 1 (40% )
• Risk and Threats - The Common Ground Between Security and Safety? (40% )
• Definitions - What Exactly is a Risk? (20% )
• Definitions - What Exactly is a Risk Part 2? (20% )
• Solution Risk, Vulnerability, Threat and Mitigation - Does Risk Need to be Separate from Event? (20% )

«  Previous  TRAK is a Finalist in the 2011 IET Innovation Awards     TRAK Article Published by The Institution of Engineers (Singapore)  Next »