Tactics based approach for integrating non-functional requirements in object-oriented analysis and design

Journal of Systems and Software

Volumn 82, Issue 10, 2009, Pages 1642-1656

  Marew, Tegegne ^a   Lee, Joon Sang ^b   Bae, Doo Hwan ^a  

^a Korea Advanced Institute of Science and Technology (KAIST)   (South Korea)

^b LG Electronics Inc   (South Korea)

Author keywords

Aspect oriented software design; NFR framework; NFRs analysis and design; Software design

Indexed keywords

ASPECT ORIENTED SOFTWARE DESIGN; FUNCTIONAL REQUIREMENT; NFR FRAMEWORK; NFRS ANALYSIS AND DESIGN; NON-FUNCTIONAL REQUIREMENTS; OBJECT ORIENTED ANALYSIS AND DESIGN; SOFTWARE DEVELOPMENT;

COMPUTER SOFTWARE; DESIGN; INTEGRATION; LARGE SCALE SYSTEMS; OBJECT ORIENTED PROGRAMMING;

SOFTWARE DESIGN;

EID: 69549121771     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2009.03.032     Document Type: Article

References (33)

1. Advanced Encryption Standard, Federal Information Processing Standards Publication, 197, 2001.
2. AspectJ: .
3. Bachmann, F., Bass, L., Klein, M., Shelton, C., 2004. Experience in using an expert system in designing for modifiability. In: Proceedings of the WICSA, IEEE Press.
4. Bachmann F., Bass L., Klein M., and Shelton C. Designing software architectures to achieve quality attribute requirements. IEE Proceedings - Software 152 4 (2005) 153-165
5. Booch G., Rumbaugh J., and Jacobson I. The Unified Modeling Language User Guide (1999), Addison-Wesley
6. Chidamber S.R., and Kemerer C.F. A metrics suite for object-oriented design. IEEE Transactions on Software Engineering 20 6 (1994) 476-493
7. Chung, L., Nixon, B., 1995. Dealing with Nonfunctional Requirements: Three Experimental Studies of a Process-Oriented Approach. In: Proceedings of the 17th International Conference on Software Engineering, pp. 24-28.
8. Chung L., Nixon B., Yu E., and Mylopoulos J. Non-Functional Requirements in Software Engineering (2000), Kluwer Academic
9. Clements P., Kazman R., and Klein M. Evaluating Software Architectures: Methods and Case Studies (2002), Addison-Wesley
10. Cysneiros L., and Leite J. Nonfunctional Requirements: From Elicitation to Conceptual Models. IEEE Transactions on Software Engineering 30 5 (2004) 328-350
11. Dobrica L., and Niemela E. A survey on software architecture analysis methods. IEEE Transactions on Software Engineering 28 7 (2002)
12. Ghezi C., Jazayeri M., and Mandrioli D. Fundamentals of Software Engineering (1991), Prentice-Hall International Edition
13. HSue Black, 2001. Computing ripple effect for software maintenance. Journal of Software Maintenance and Evolution, Research and Practice.
14. ISO/IEC 9126-1 (2001). Software engineering. Product quality. Part 1: Quality model. International Organization for Standardization.
15. Jacobson I., Booch G., and Rumbaugh J. The Unified Software Development Process (1999), Addison-Wesley
16. Kaiya, H., Horai, H., Saeki, M., 2002. AGORA: attributed goal-oriented requirements analysis method. In: IEEE Joint International Conference on Requirement Engineering, RE02.
17. Karlson J., and Ryan K. A cost-value approach for prioritizing requirements. IEEE Software 14 15 (1997) 67-74
18. Marew, T., Bae, D., 2006. Using classpects for integrating non-functional and functional requirements. In: ASTED Conference on Software Engineering, pp. 141-147.
19. Mead, N. .
20. Mylopoulos J., Chung L., and Nixon B. Representing and Using NonFunctional Requirements: A Process-Oriented Approach. IEEE Transactions on Software Engineering 14 6 (1992)
21. Nilsson N. Problem Solving Methods in Artificial Intelligence (1971), McGraw-Hill, New York
22. Rajan, H., Sulllivan, K., 2005. Classpects: unifying aspect- and object-oriented language design. In: Proceedings of the 27th International Conference Software Engineering, pp. 59-68.
23. Saaty T., and Vargas L. Prediction, Projection, and Forecasting (1991), Kluwer Academic Publisher
24. Sadana, V., Liu, X., 2007. Analysis of conflicts among non-functional requirements using integrated analysis of functional and non-functional requirements. Computer Software and Applications Conference, COMPSAC.
25. Smith C.U., and Williams L.G. Performance solutions: a practical guide to creating responsive, scalable software (2002), Addison-Wesley
26. Spencer I., and Bittner K. Managing Iterative Software Development Projects (2006), Addison-Wesley Object Technology
27. Subramanian, N., Chung, L., 2003. Process-oriented metrics for software architecture evoluability, IWPSE.
28. Triantaphyllou, E., Mann, S.H., 1994. Some critical issues in making decisions with pair-wise comparisons. In: Proceedings of the Third International Symposium on the AHP, pp. 225-236.
29. Xu L., Ziv H., Alspaugh T., and Richardson D. An architectural pattern for non-functional dependability requirements. Journal of Systems and Software (2006) 1370-1378
30. Yau S., and Collofello J. Design stability measures for software maintenance. IEEE Transactions on Software Engineering 11 9 (1985)
31. Yau, S., Collofello, J., McGregor, T., 1978. Ripple effect analysis of software maintenance. In: Proceedings Computer Software and Applications Conference (COMPSAC).
32. Zayaraz, G., Thambidurai, P., 2007. Quantitative model for the evaluation of software architectures, Software Quality Professional.
33. Zhu L., Aurum A., Gortorn I., and Jeffery R. Tradeoff and sensitivity analysis in software architecture evaluation using analytic hierarchy process. Software Quality Journal 13 (2005) 357-375