Constructing Open Systems via Consistent Components

  • Nguyen Truong Thang
  • Takuya Katayama
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3722)


Open systems capable of handling unanticipated future changes are very desirable. A common approach towards open systems is based on components. There are some essential issues of the component-based software paradigm. First, the most challenging analysis issue is about component consistency – namely a component does not violate some property in another when composed. The paper presents a formal approach to the issue by including consistency semantic to component specification. Based on this semantic information, components can be efficiently cross-checked for the consistency among components. The second issue is on how components are realized from the formal specification. The layered architecture is recommended for component-based system design in which component specifications are separated into layers. Subsequently, each layer can be then respectively implemented by a corresponding module via aspect-oriented programming. The target system simply involves composing those modules together in a well-defined order.


Model Check Interface State Atomic Proposition Layered Architecture Exit State 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Han, J.: An approach to software component specification. In: Proceedings of International Workshop on Component Based Software Engineering (1999)Google Scholar
  2. 2.
    Liu, Y., Cunningham, H.C.: Software component specification using design by contract. In: Proceedings of the SouthEast Software Engineering Conference (April 2002)Google Scholar
  3. 3.
    Tarr, P., Ossher, H., Harrison, W., Sutton, S.M.: N-degrees of separation: Multi-dimensional separation of concerns. In: Proc. ICSE, pp. 109–117 (1999)Google Scholar
  4. 4.
    Warmer, J., Kleppe, A.: The Objects Constraint Language: Precise Modeling with UML. Addison-Wesley, Reading (1999)Google Scholar
  5. 5.
    Clarke, E.M., Grumberg, O., Peled, D.A.: Model Checking. MIT Press, Cambridge (1999)Google Scholar
  6. 6.
    Nguyen, T.T., Katayama, T.: Handling consistency of software evolution in an efficient way. In: Proc. IWPSE, pp. 121–130 (2004)Google Scholar
  7. 7.
    Laster, K., Grumberg, O.: Modular model checking of software. In: Steffen, B. (ed.) TACAS 1998. LNCS, vol. 1384, p. 20. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  8. 8.
    Batory, D., Johnson, C., MacDonald, B., Heeder, D.V.: Achieving extensibility through product-lines and domain-specific languages: A case study. In: Proc. International Conference on Software Reuse (2000)Google Scholar
  9. 9.
    Smaragdakis, Y., Batory, D.: Implementing layered designs with mixin layers. In: Jul, E. (ed.) ECOOP 1998. LNCS, vol. 1445, p. 550. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  10. 10.
    Tarr, P., Ossher, H.: Hyper/J(TM) User and Installation Manual. IBM Research, IBM Corp. (2000)Google Scholar
  11. 11.
    Kiczales, G., Lamping, J., et al.: Aspect-oriented programming. In: Aksit, M., Matsuoka, S. (eds.) ECOOP 1997. LNCS, vol. 1241, pp. 220–242. Springer, Heidelberg (1997)CrossRefGoogle Scholar
  12. 12.
    The AspectJ Team: The AspectJ(TM) Programming Guide. Xerox Corporation (2001)Google Scholar
  13. 13.
    Kupferman, O., Vardi, M.Y.: Modular model checking. In: de Roever, W.-P., Langmaack, H., Pnueli, A. (eds.) COMPOS 1997. LNCS, vol. 1536, p. 381. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  14. 14.
    Pasareanu, C.S., Dwyer, M.B., Huth, M.: Assume-guarantee model checking of software: A comparative case study. In: Dams, D.R., Gerth, R., Leue, S., Massink, M. (eds.) SPIN 1999. LNCS, vol. 1680, p. 168. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  15. 15.
    Grumberg, O., Long, D.E.: Model checking and modular verification. In: Groote, J.F., Baeten, J.C.M. (eds.) CONCUR 1991. LNCS, vol. 527. Springer, Heidelberg (1991)Google Scholar
  16. 16.
    Chakrabarti, A., de Alfaro, L., Henzinger, T.A., Jurdzinski, M., Mang, F.Y.C.: Interface compatibility checking for software modules. In: Brinksma, E., Larsen, K.G. (eds.) CAV 2002. LNCS, vol. 2404, p. 428. Springer, Heidelberg (2002)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Nguyen Truong Thang
    • 1
  • Takuya Katayama
    • 1
  1. 1.School of Information ScienceJapan Advanced Institute of Science and Technology 

Personalised recommendations