TY - GEN
T1 - Architectural point mapping for design traceability
AU - Ubayashi, Naoyasu
AU - Kamei, Yasutaka
PY - 2012
Y1 - 2012
N2 - AOP can be applied to not only modularization of crosscutting concerns but also other kinds of software development processes. As one of the applications, this paper proposes a design traceability mechanism originating in join points and pointcuts. It is not easy to design software architecture reflecting the intention of developers and implement the result of design as a program while preserving the architectural correctness. To deal with this problem, we propose two novel ideas: Archpoint (Architectural point) and Archmapping (Archpoint Mapping). Archpoints are points for representing the essence of architectural design in terms of behavioral and structural aspects. By defining a set of arch-points, we can describe the inter-component structure and the message interaction among components. Archmapping is a mechanism for checking the bidirectional traceability between design and code. The traceability can be verified by checking whether archpoints in design are consistently mapped to program points in code. For this checking, we use an SMT (Satisfiability Modulo Theories) solver, a tool for deciding the satisfiability of logical formulas. The idea of archpoints, program points, and their selection originates in AOP.
AB - AOP can be applied to not only modularization of crosscutting concerns but also other kinds of software development processes. As one of the applications, this paper proposes a design traceability mechanism originating in join points and pointcuts. It is not easy to design software architecture reflecting the intention of developers and implement the result of design as a program while preserving the architectural correctness. To deal with this problem, we propose two novel ideas: Archpoint (Architectural point) and Archmapping (Archpoint Mapping). Archpoints are points for representing the essence of architectural design in terms of behavioral and structural aspects. By defining a set of arch-points, we can describe the inter-component structure and the message interaction among components. Archmapping is a mechanism for checking the bidirectional traceability between design and code. The traceability can be verified by checking whether archpoints in design are consistently mapped to program points in code. For this checking, we use an SMT (Satisfiability Modulo Theories) solver, a tool for deciding the satisfiability of logical formulas. The idea of archpoints, program points, and their selection originates in AOP.
UR - http://www.scopus.com/inward/record.url?scp=84860489217&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84860489217&partnerID=8YFLogxK
U2 - 10.1145/2162010.2162022
DO - 10.1145/2162010.2162022
M3 - Conference contribution
AN - SCOPUS:84860489217
SN - 9781450310994
T3 - FOAL'12 - Proceedings of the 11th Workshop on Foundations of Aspect-Oriented Languages
SP - 39
EP - 43
BT - FOAL'12 - Proceedings of the 11th Workshop on Foundations of Aspect-Oriented Languages
T2 - 11th Workshop on Foundations of Aspect-Oriented Languages, FOAL'12, Held at the 11th International Conference on Aspect-Oriented Software Development, AOSD 2012
Y2 - 26 March 2012 through 26 March 2012
ER -