An architectural pattern for non-functional dependability requirements

ABSTRACT

We address the research question of transforming dependability requirements into corresponding software architecture constructs. by proposing first that dependability needs can be classified into three types of requirements and second, an architectural pattern that allows requirements engineers and architects to map dependability requirements into three corresponding types of architectural components. The proposed pattern is general enough to work with existing requirements techniques and existing software architectural styles, including enterprise and product-line architectures.

REFERENCES

• 1: M. R. Barbacci, "SEI Architecture Analysis Techniques and When to Use Them", Technical Note, CMU/SEI-2002-TN-005.
• 2: Manuel Brandozzi and Dewayne E Perry. "From Goal-Oriented Requirements to Architectural Prescriptions: The Preskiptor Process." In From Software Requirements to Architectures Workshop (STRAW), May 2003, pp 107--113.
• 3: Lawrence Chung , Daniel Gross , Eric S. K. Yu, Architectural Design to Meet Stakeholder Requirements, Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1), p.545-564, February 22-24, 1999
• 4: L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, "Nonfunctional Requirements in Software Engineering" Kluwer Academic Publishers 2000.
• 5: L. M. Cysneiros, J. C. S. P. Leite and J. M. S. Neto, "A Framework for Integrating Non-functional Requirements into Conceptual Models", RE'01, 2001.
• 6: Luiz Marcio Cysneiros , Julio Cesar Sampaio do Prado Leite, Nonfunctional Requirements: From Elicitation to Conceptual Models, IEEE Transactions on Software Engineering, v.30 n.5, p.328-350, May 2004 [doi>10.1109/TSE.2004.10]
• 7: D. Gross and E. Yu, "From Non-Functional Requirements to Design Through Patterns", Requirements Engineering Journal, vol. 6, 2001.
• 8: A. van Lamsweerde, "From System Goals to Software Architecture", SFM 2003, 25--43.
• 9: C. V. Lopes and T. C. Ngo, "The Aspect Markup Language and its support of Aspect Plugins", ISR Technical Report UCI-ISR-04-8, University of California, Irvine.
• 10: J. Mylopoulos , L. Chung , B. Nixon, Representing and Using Nonfunctional Requirements: A Process-Oriented Approach, IEEE Transactions on Software Engineering, v.18 n.6, p.483-497, June 1992 [doi>10.1109/32.142871 ]
• 11: Ian Sommerville, Software Engineering (7th Edition), Pearson Addison Wesley, 2004
• 12: Richard N. Taylor , Nenad Medvidovic , Kenneth M. Anderson , E. James Whitehead, Jr. , Jason E. Robbins , Kari A. Nies , Peyman Oreizy , Deborah L. Dubrow, A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering, v.22 n.6, p.390-406, June 1996 [doi>10.1109/32.508313 ]
• 13: Workshop on Early Aspects, "Aspect-Oriented Requirements Engineering and Architecture Design". http://www.early-aspects.net/
• 14: Xu, L., Ziv, H., and Richardson, D., Towards Modeling Non-Functional Requirements in Software Architecture, Early Aspects 2005: Aspect-Oriented Requirements Engineering and Architecture Design, in conjunction with AOSD'2005, Chicago, Illinois, March 2005.
• 15: Yijun Yu , Julio Cesar Sampaio do Prado Leite , John Mylopoulos, From Goals to Aspects: Discovering Aspects from Requirements Goal Models, Proceedings of the Requirements Engineering Conference, 12th IEEE International (RE'04), p.38-47, September 06-10, 2004 [doi>10.1109/RE.2004.23]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures

General Terms:
Design, Reliability

Keywords:
architecture patterns, aspects, nonfunctional requirements, software architecture