Practical Software Architecture Design Methods for Non-Conventional Quality Requirements


KIPS Transactions on Software and Data Engineering, Vol. 6, No. 8, pp. 391-400, Aug. 2017
10.3745/KTSDE.2017.6.8.391,   PDF Download:
Keywords: Software Architecture, Non-Functional Requirement, Architectural Tactic, Design Process, Traceability-Based Evaluation
Abstract

Software architecture plays a key role in satisfying non-functional requirement (NFR), i.e. quality requirements and constraints. Architecture design methods and tactics for conventional NFR are largely available in literatures. However, the methods for the target system-specific non-conventional NFRs are not readily available; rather architects should invent the design methods from their experiences and intuitions. Hence, the hardship to design architectures for non-conventional NFRs is quite high. In this paper, we provide a systematic architecture design methodology for non-conventional NFRs. We provide a five-step process, and detailed instructions for the steps. In the process, we treat the traceability among artifacts and seamlessness as essential values for supporting effective architecture design. We apply the methodology on designing architectures for a platform software system. We believe that the proposed methodology can be effectively utilized in designing high quality architectures for non-conventional NFRs.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
H. J. La and S. D. Kim, "Practical Software Architecture Design Methods for Non-Conventional Quality Requirements," KIPS Transactions on Software and Data Engineering, vol. 6, no. 8, pp. 391-400, 2017. DOI: 10.3745/KTSDE.2017.6.8.391.

[ACM Style]
Hyun Jung La and Soo Dong Kim. 2017. Practical Software Architecture Design Methods for Non-Conventional Quality Requirements. KIPS Transactions on Software and Data Engineering, 6, 8, (2017), 391-400. DOI: 10.3745/KTSDE.2017.6.8.391.