Standards in software development and modeling
Software & Systems Modeling, vol. 24, pp. 1315–1316
Abstract
There are important standardization bodies that actually create very good and widely used standards in engineering and development.This is prominent in other engineering domains, but less common in computer science.We may speculate about the reasons, but it may be that computer science is relatively young, and therefore, techniques and methods evolve frequently, and standards may hinder this form of innovation.A second reason may be that in computer science, large companies are developing the de facto standards that are not necessarily becoming formal standards.But in computer science, standards also ensure compatibility, interoperability, reliability, security, reusability, and potentially many other good properties across services, applications, systems, and technologies.And we all know some key categories and examples of relevant standards, such as programming language standards (e.g., ISO/IEC 9899-for C, Java Community Process (JCP) specs-for Java, ECMA-262/ISO/IEC 16262-for JavaScript, HTTP/HTTPS (RFC 9110) protocol-for web communication, and RFC 8259-for JSON).The most relevant standards for Software & Systems Engineering are UML (first by the OMG and later by ISO/IEC 19505), IEEE 830 / ISO/IEC/IEEE 29148-for Software Requirements Specification, and the newly emerging standards around the digital twin technologies stack that are in discussion by the Digital Twin Consortium (DTC) and the Industrial Digital Twin Association (IDTA).As a side note, B
Authors 4
-
Affiliation as printed
University of Toronto, Toronto, ON, Canada
-
Affiliation as printed
University of Rennes, Rennes, France
-
Affiliation as printed
University of Alabama, Tuscaloosa, AL, USA
-
Affiliation as printed
RWTH Aachen University, Aachen, Germany
Cited by 0 stored of 0
No patents citing this paper on Lens.org (checked 2026-10-06).