Overview of the Revised Standard on Architecture Description – ISO/IEC 42010

2021 ◽  
Vol 31 (1) ◽  
pp. 1363-1376
Author(s):  
James N Martin
1992 ◽  
Author(s):  
Ray Beaver ◽  
Randy Brasch ◽  
Chuck Burdick ◽  
Brett Butler ◽  
Stephen Downes-Martin

2019 ◽  
Vol 43 (4) ◽  
pp. 52-52
Author(s):  
Umaima Haider ◽  
John D. McGregor ◽  
Rabih Bashroush

2016 ◽  
Vol 5 (3) ◽  
pp. 1-20 ◽  
Author(s):  
Hans Blom ◽  
De-Jiu Chen ◽  
Henrik Kaijser ◽  
Henrik Lönn ◽  
Yiannis Papadopoulos ◽  
...  

EAST-ADL is an Architecture Description Language (ADL) initially defined in several European-funded research projects and aligned with AUTOSAR and ISO26262. It provides a comprehensive approach for defining automotive electronic systems through an information model that captures engineering information in a standardized form. Aspects covered include vehicle features, requirements, analysis functions, software and hardware components and communication. The representation of the system's implementation is not defined in EAST-ADL itself but by AUTOSAR. However, traceability is supported from EAST-ADL's lower abstraction levels to the implementation level elements in AUTOSAR. In this article the authors describe EAST-ADL in detail, show how it relates to AUTOSAR as well as other significant automotive standards and present recent research work on using and advancing EAST-ADL, the functional safety standard ISO 26262, heterogeneous multi / many core architectures, security and for multi-objective optimization.


Author(s):  
YUJIAN FU ◽  
ZHIJIANG DONG ◽  
XUDONG HE

A software architecture design has many benefits including aiding comprehension, supporting early analysis, and providing guidance for subsequent development activities. An additional major benefit is if a partial prototype implementation can be automatically generated from a given software architecture design. However, in the past decade less progress was made on automatically realizing software architecture designs. In this paper, we present a translator for automatically generating an implementation from a software architectural description. The implementation not only captures the functionality of the given architecture description, but also contains additional monitoring code for ensuring desirable behavior properties through runtime verification. Our method takes a software description written in SAM, a software architecture model integrating dual formal methods Petri nets and temporal logic, and generates ArchJava/Java/AspectJ code. More specifically, the structure of a SAM architecture description produces ArchJava code, the behavior models of components/connectors represented in Petri nets lead to plain Java code, and the property specifications defined in temporal logic generate AspectJ code; the above code segments are then integrated into Java code. An experimental result is provided.


Sign in / Sign up

Export Citation Format

Share Document