ACM Home Page
Please provide us with feedback. Feedback
Concern impact analysis in configurable system software: the AUTOSAR OS case
Full text PdfPdf (387 KB)
Source Aspect-oriented software development archive
Proceedings of the 2008 AOSD workshop on Aspects, components, and patterns for infrastructure software table of contents
Brussels, Belgium
Article No. 6  
Year of Publication: 2008
ISBN:978-1-60558-142-2
Authors
Wanja Hofer  Friedrich-Alexander University Erlangen-Nuremberg
Daniel Lohmann  Friedrich-Alexander University Erlangen-Nuremberg
Wolfgang Schröder-Preikschat  Friedrich-Alexander University Erlangen-Nuremberg
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 40,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1404891.1404897
What is a DOI?

ABSTRACT

System software for cost-sensitive special purpose-systems has to be configurable and tailorable. AOSD should be beneficial for this purpose, as it provides means to untangle the system's concerns in a very fine-grained way. An important prerequisite for a fine-grained software design based on aspects is, however, that all concerns and their interactions present in the system have been comprehensively captured and understood.

We propose a method called Concern Impact Analysis for this purpose. Based on a system's specification, CIA provides a guideline to iteratively grasp the concerns present in a system, and their interactions. A speciality of CIA is that it also takes unspecified "internal" concerns into consideration as early as possible. We have tested CIA with the AUTOSAR OS specification and the design of our CiAO operating system family, where it led to a very fine-grained, aspect-aware kernel design.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
AUTOSAR. Specification of operating system (version 2.0.1). Technical report, Automotive Open System Architecture GbR, June 2006.
 
2
AUTOSAR homepage. http://www.autosar.org/.
 
3
 
4
I. Brito and A. Moreira. Towards a composition process for aspect-oriented requirements. In Aspect-Oriented Req. Engineering and Arch. Design W'shop, 2003.
 
5
Y. Coady, C. Gibbs, M. Haupt, J. Vitek, and H. Yamauchi. Towards a domain-specific aspect language for virtual machines. In 1st W'shop on Domain-Specific Aspect Languages (DSAL), 2006.
 
6
 
7
P. Durr, T. Staijen, L. Bergmans, and M. Aksit. Reasoning about semantic conflicts between aspects. In 2nd European Interactive Workshop on Aspects in Software (EIWAS '05), 2005.
8
9
10
 
11
 
12
L. Rosenhainer. Identifying crosscutting concerns in requirements specifications. In Proceedings of the Aspect-Oriented Requirements Engineering and Architecture Design Workshop, 2004.
13
14
15

Collaborative Colleagues:
Wanja Hofer: colleagues
Daniel Lohmann: colleagues
Wolfgang Schröder-Preikschat: colleagues