Advertisement

An Approach to Quality Achievement at the Architectural Level: AQUA

  • Heeseok Choi
  • Keunhyuk Yeom
  • Youhee Choi
  • Mikyeong Moon
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4037)

Abstract

Architecture-based software development plays an important role in successfully developing and managing large and complex software systems. Recently, there have been a number of studies for designing, evaluating, or transforming architectures. However, there is not much work being done for closely connecting an architectural evaluation with an architectural transfor-mation in order to achieve quality attributes during the architecture-based software development. For this reason, it is still difficult to achieve consistently quality attributes at the architectural level. This paper presents an approach to quality achievement in architecture-based software development, which is called AQUA. The AQUA involves two distinctive activities, which are architectural evaluation and transformation, but these activities can be seam-lessly combined through producing relevant artifacts based on the design decisions that led to the architecture. Due to the proposed approach, we can expect to achieve quality attributes in architecture-based software development.

Keywords

Quality Attribute Functional Requirement Design Decision Software Architecture Unary Constraint 
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.

References

  1. 1.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2/E. Addison-Wesley, Reading (2003)Google Scholar
  2. 2.
    Kazman, R., et al.: The Architecture Tradeoff Analysis Method. In: Proceedings of the 4th IEEE International Conference on Engineering of Complex Computer Systems, August 1998, pp. 68–78 (1998)Google Scholar
  3. 3.
    Bosch, J.: Design and Use of Software Architecture. Addison-Wesley, Reading (2000)Google Scholar
  4. 4.
    Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures. Addison-Wesley, Reading (2002)Google Scholar
  5. 5.
    Dobrica, L., Niemela, E.: A Survey on Software Architecture Analysis Methods. IEEE Transactions on Software Engineering 28(7), 638–653 (2002)CrossRefMATHGoogle Scholar
  6. 6.
    Carriere, S.J., Woods, S., Kazman, R.: Software Architectural Transformation. In: Proceedings of the 6th Working Conference on Reverse Engineering, October 1999, pp. 13–23 (1999)Google Scholar
  7. 7.
    Krikhaar, R., et al.: A Two-phase Process for Software Architecture Improvement. In: Proceedings of the International Conference on Software Maintenance, August 1999, pp. 371–380 (1999)Google Scholar
  8. 8.
    Eriksson, H.E., Penker, M.: UML Toolkit. John Wiley & Sons, Chichester (1998)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2006

Authors and Affiliations

  • Heeseok Choi
    • 1
  • Keunhyuk Yeom
    • 2
  • Youhee Choi
    • 3
  • Mikyeong Moon
    • 2
  1. 1.Korea Institute of Science and Technology InformationNTIS OrganizationDaejeonSouth Korea
  2. 2.Department of Computer EngineeringPusan National UniversityBusanSouth Korea
  3. 3.Embedded S/W Research DivisionElectronics and Telecommunications Research InstituteDaejeonSouth Korea

Personalised recommendations