By Topic

Using Operational Architecture to Model Embedded Software

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)

Almost methods in embedded software modeling take software architecture as one of the crucial parts of the design process. Since a principal role of embedded software is the interaction with its environments, architectures that describe the dynamic aspects are also needed. Although such architectural view is significantly important in embedded software development, the existing approaches do not practically guide the architectural design based on the dynamic aspects. In this paper, we propose an operational architecture to represent the dynamic aspects of an embedded software. Also we explain how to use our operational architecture in the process of embedded software modeling. Our operational architecture effectively reflects interaction-based dynamic behavior of the system, and gives traceability between requirements and design model.

Published in:

2006 13th Asia Pacific Software Engineering Conference (APSEC'06)

Date of Conference:

6-8 Dec. 2006