Feature analysis for architectural evaluation methods

Given the complexity of today's software systems, Software Architecture is a topic that has recently increased in significance. It is consider as a key element in the design and development of systems and has the ability to promote/punish some quality characteristics. Quality is related mainly to the non-functional requirements expected of the system. Using appropriate methods for Architectural Evaluation can help to reduce the risk of low quality Architecture. The objective of this research is to conduct a Features Analysis for three Architectural Evaluation Methods applied to a single case. This resulted in two significant contributions; the aspects which must be present in an architectural evaluation method which is translated in a set of 49 metrics, grouped into features and sub-features to enable the evaluation of a particular method. Different methods can be compared on the basis of these features; however, the choice of method will depend largely on the requirements of the evaluating team. The second contribution pinpoints the strengths of the methods evaluated. The methods studied were: Design and Use of Software Architectures, Architecture Tradeoff Analysis Method, and Architectural Evaluation Method. The evaluation method employed for this research was Features Analysis Case Study.

[1]  Mikael Lindvall,et al.  Evaluating software architectures , 2004, Adv. Comput..

[2]  Amar Ramdane-Cherif,et al.  ISO quality standards for measuring architectures , 2004, J. Syst. Softw..

[3]  Barbara Ann Kitchenham,et al.  Evaluating SW Eng. methods and tools, part 8: analysing a feature analysis evaluation , 1997, SOEN.

[4]  Ian Sommerville,et al.  Software engineering (5th ed.) , 1995 .

[5]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[6]  V. Basili Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .

[7]  Teresita Rojas,et al.  Construction of a Systemic Quality Model for Evaluating a Software Product , 2003, Software Quality Journal.

[8]  Ivar Jacobson,et al.  El proceso unificado de desarrollo de software , 2000 .

[9]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[10]  B. Kitchenham,et al.  DESMET : A method for evaluating Software Engineering methods and tools , 2000 .

[11]  Rick Kazman,et al.  From requirements negotiation to software architecture decisions , 2005, Inf. Softw. Technol..

[12]  Roger S. Pressman,et al.  Ingeniería del software: un enfoque práctico , 1998 .

[13]  Barbara Ann Kitchenham,et al.  Evaluating software engineering methods and tool part 5: the influence of human factors , 1997, SOEN.

[14]  Barbara Kitchenham,et al.  DESMET: a methodology for evaluating software engineering methods and tools , 1997 .

[15]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[16]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[17]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[18]  Francisca Losavio,et al.  Simulation-based architectural evaluation for collaborative systems , 2002, 12th International Conference of the Chilean Computer Science Society, 2002. Proceedings..

[19]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction, Second Edition , 2000 .