Separation of concerns in automation of code generation

  • Authors:
  • Paniti Netinant;Sorapak Pukdesree

  • Affiliations:
  • Bangkok University, Bangkok, Thailand;Bangkok University, Bangkok, Thailand

  • Venue:
  • ACST '08 Proceedings of the Fourth IASTED International Conference on Advances in Computer Science and Technology
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

Aspect-oriented programming is a new paradigm that complements the object-oriented technology. The premise of aspect-oriented technology is the separation of concerns. Certain system properties tend to cut across group of functional components such as concurrency, security, and fault tolerance are examples of these crosscutting concerns. Aspect orientation attempts to modularize these crosscutting properties in order to avoid the code-tangling phenomena. Objects are independent entities that cooperate together t0achieve a certain task, how can we mange object interaction without violating basic object orientation principles like abstraction, what triggers an object to perform its functionality, what constraints that an object must consider before performing its task(s) are, how an object behavior impacts other object(s) behavior, how we can model our aspect oriented system with all the above questions in mind using existing CASE tools and guarantee separation of concerns at the implementation (automatic code generation). In this position paper presents a formal methodology that addresses the above questions and supports separation of concerns for system software. The paper demonstrates aspect-oriented framework applying at the design and implementation phase with separation of system properties. Our approach uses CASE tools supporting UML without any extensions to it. Rhapsody CASE tool has been used to model and automatically generate code since it supports UML diagrams which enable us to present different views using different UML diagrams (OMD, SD, Statecharts, and Use Case diagrams).