loading...
From Software Architecture to Design Patterns: A Case Study of an NFR Approach
Towson University, Towson, Maryland, USA May 23-May 25
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/SNPD-SAWN.2005.38Sixth International Conference on Sof ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Jing Wang, Towson University
Yeong-Tae Song, Towson University
Lawrence Chung, University of Texas at Dallas
There has been extensive research on establishing a non-functional requirement (NFR) framework [3] and applying it systematically in selecting software architectural design alternatives. However there is still a gap between software architecture and concrete detailed design. This paper presents a way to come up with more detailed designs by selecting a set of applicable design patterns. The method in selecting design patterns will be applied step by step systematically in a defined process. After a preliminary selection of a set of potentially applicable design patterns based on existing knowledge, analysis of their applicability is conducted on each of the design patterns. In each analysis process, the potentially applicable design pattern and the chosen architectural design are decomposed; the traceability from software architecture to design patterns is analyzed. This method is applied in the case study on keyword in context system (KWIC) [2] [3]. The notation of NFR approach [4] is further refined.
Index Terms:
Non-functional requirements, software architecture, design pattern
Citation:
Jing Wang, Yeong-Tae Song, Lawrence Chung, "From Software Architecture to Design Patterns: A Case Study of an NFR Approach," snpd-sawn, pp.170-177, Sixth International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing and First ACIS International Workshop on Self-Assembling Wireless Networks (SNPD/SAWN'05), 2005
Usage of this product signifies your acceptance of the Terms of Use.