[1] Finkelstein A, Dowell J. A comedy of errors: the London ambulance service case study[A]. Proceedings of the 8th International Workshop on Software Specification and Design[C]. 1996.2-4. [2] Lindstrom D R. Five ways to destroy a development project[J]. IEEESoftware, 1993, 10(5):55-58. [3] OMG. Model driven architecture(MDA)( ormsc/2001-07-01)[S]. [4] Boehm B W, Brown J R, Lipow M. Quantitative evaluation of software quality[A]. Proceedings of 2nd International Conference on Software Engineering[C]. San Francisco, CA: IEEE Computer Society, 1976.592-605. [5] Boehm B W. Characteristics of software quality[M]. Amsterdam:North-Holland, 1978. [6] Losavio F, Chirinos L, Perez M A. Quality models to design softwarearchitectures[A]. Proceedings of Technology of Object-Oriented Languages andSystems(TOOLS)[C]. IEEE, 2001.123-135. [7] ISO/IEC IS 9126—1991, Information technology-software product evaluation: quality characteristics and guidelines for their use[S]. [8] ISO/IEC FCD 9126-1.2—1998, Information technology-software productquality. part 1: quality model(draft)[S]. [9] Mylopoulos J, Chung L, Nixon B A. Representing and using nonfunctional requirements: a process-oriented approach[J]. IEEE Transactions on SoftwareEngineering, 1992,18(6):483-497. [10] Chung L, Nixon B A, Yu E, et al. Non-functional requirementsin software engineering[M]. Kluwer Academic Publishers,1999. [11] Rosa N S, Justo G R R, Cunha P R F. A framework for building non-functional software architectures[A]. Proceedings of the 2001 ACM symposium on applied computing[C]. ACM Press, 2001. [12] Franch X, Botella P. Putting non-functional requirements into software architecture[A]. Proceedings of Ninth International Workshop Software Specification and Design[C]. IEEE, 1998. 60-67. [13] Frédéric Duclos, Jacky Estublier, Philippe Morat. Describing and using non functional aspects in component based applications[A]. Proceedings ofthe 1st International Conference on Aspect-Oriented Software Development[C].ACM, 2002. [14] Luiz Marcio Cysneiros, Julio Cesar Sampaio do Prado Leite. Non-functional requirements: from elicitation to modelling languages[A]. Proceedingsof the 24th International Conference on Software Engineering[C]. ACM, 2002. [15] Roman G C. A taxonomy of current issues in requirements engineering[J]. IEEE Computer, 1985,18(4):15-23. [16] Mostow J. Towards better models of the design process[J]. AI Magazine, 1985, 6(1):44-57. [17] Keller S E. Specifying software quality requirements with metrics, in tutorial:system and software engineering[M]. IEEE Computer Society Press,1990. 145-163. [18] Franch X. The convenience for a notation to express non-functionalcharacteristics of software components[A]. Foundations of Component-BasedSystems Workshop (FoCBS)[C]. Zurich,Switzeland,1997.101-109. [19] George R, Ribeiro-Justo, Ahmed Saleh. Non-functional integrationand coordination of distributed component services[A]. Proceedings of the Sixth European Conference on Software Maintenance and Reengineering (CSMR.02)[C].IEEE, 2002. [20] Skene J, Emmerich W. A model driven architecture approach to analysis of non-functional properties of software architectures[A]. Proceedings of the 18th IEEE Conference on Automated Software Engineering[C]. Montreal, Canada: IEEE Computer Society Press, 2003. [21] Binns P, Engelhart M, Jackson M, et al. Domain-specific software architectures for guidance, navigation, and control[J]. International Journal ofSoftware Engineering and Knowledge Engineering, 1996,6(2):66-68. [22] Cohen D, Goldman N, Narayanaswamy K. Adding performance informationto ADT interfaces[A]. Proceedings of the Interface Definition Languages Workshop[C]. ACM Sigplan Notices, 1994. [23] Janet E B, David C B. NFR's: Fact or Fiction?[EB/OL]. http://www.cs.wpi.edu/~dcb/Papers/CASCON03.pdf, 2003. [24] Booch G, Rumbaugh J, Jacobson I. The unified modeling language userguide[M]. Addsion Wesley Longman, 1999. [25] Leite J C S P. Enhancing a requirements base line with scenarios[J]. Requirements Engineering Journal, 1997,2(4):184-198. [26] Chung L, Nixon B A. Dealing with non-functional requirements: threeexperimental studies of a process-oriented approach[A]. Proceedings of IEEE17th International Conference on Software Engineering[C]. Seattle, 1995.25-37. [27] Issarny V, Bidan C, Saridakis T. Achieving middleware customizationin a configuration-based development environment: experience with the Aster prototype[A]. Proceedings of 4th International Conference on Configurable Distributed Systems[C]. Maryland:Annapolis,1998.207-214. [28] Zarras A, Issarny V. A framework for systematic synthesis of transactional middleware[A]. Proceedings of Middleware’98[C]. England: The Lake District, 1998.257-272. [29] Saridakis T, Issarny V. Fault tolerant software architectures[Z].Technical Report 3350,I NRIA, 1998. [30] Pooley R, King P. The unified modeling language and performance engineering[A]. IEEE Proceedings of Software[C]. 1999.2-10. [31] OMG. UML profile for schedulability,performance, and time specification[S]. [32] Skene J, Emmerich W. A model driven architecture approach to analysis of non-functional properties of software architectures[EB/OL]. http://www.cs.ucl.ac.uk/staff/w.Emmerich/publications/ASE2003/index.html,2003-09. [33] Rodrigues G N, Roberts G, Emmerich W, et al. Reliability support forthe model driven architecture[A]. Workshop on Software Architectures for Dependable Systems (WADS), in Conjunction with ICSE '03[C]. Portland: ACM Press, 2003. [34] Torsten L, David B, Jürgen D. SecureUML: a UML-based modeling language for model-driven security[A]. Proceedings of the 5th International Conference on the Unified Modeling Language[C]. 2002.426-441. [35] Gregor Kiczales, Jim des Rivi`eres. The art of the metaobject protocol[M]. Massachusetts: MIT Press, 1991. [36] Shaw M, DeLine R, Zelesnik G. Abstractions and implementations forarchitectural connections[A]. Proceedings of the Third International Conference on Configurable Distributed Systems[C]. 1996. [37] Lopes C V, Hursch W L. Separation of concerns[M]. Boston: Collegeof Computer Science, Northeastern University, 1995. [38] AOP Home Page[EB/OL]. http://www.aosd.net/. [39] Kiczales G. Aspect-oriented programming[A]. Proceedings of the European Conference on Object-Oriented Programming (ECOOP)[C]. Springer-Verlag, 1997. [40] Smith B C. Reflection and semantics in a procedural language[Z].Technical Report, MIT Laboratory of Computer Science, 1982. [41] Smith B C. Reflection and semantics in Lisp[A]. Proceedings ofACM Symposium on Principles of Programming Languages[C]. 1984.23-35. [42] OMG. CORBA Components v3.0 (formal/02-06-65)[S]. [43] Sun. Enterprise JavaBeans specification, version 2.1, proposedfinal draft 2(ejb-2_1-pfd2-spec)[EB/OL]. http://java.sun.com/webapps/download/Redirect/60366713/ejb-2_1-pfd2-spec.pdf,2003-06-02. [44] AspectJ home page[EB/OL]. http://aspectj.org/. [45] Aspect C++ home page[EB/OL]. http://www.aspectc.org/. [46] Killijian M O, Fabre J C, Ruiz-Garcia J C, et al. A metaobject protocol for fault-tolerant CORBA applications[A]. Proceedings of IEEE SRDS'98[C]. Indiana: West Lafayette, 1998.127-134. [47] McCall J. The automated measurement of software quality[A]. Proceedings of 5th COMPSAC'81[C]. 1981. [48] 叶言苓, 朱三元. 软件质量评价体系及其实现[J]. 计算机应用与软件, 2001, 18(1):26-33. Ye Yanling, Zhu Sanyuan. Software quality evaluation system and its implementation[J]. Computer Application and Software, 2001,18(1):26-33. [49] 雍信阳, 施伯乐. 非功能需求跟踪[J]. 计算机研究与发展, 1998, 35(7):584-588. Yong Xinyang, Shi Bole. Non-functional requirements traceability[J]. Computer Research and Development, 1998,35(7):584-588. |