From non-functional requirements to design through patterns

Requirements Engineering

Volumn 6, Issue 1, 2001, Pages 18-36

  Gross, Daniel ^a   Yu, Eric ^a  

^a UNIVERSITY OF TORONTO   (Canada)

Author keywords

Architectural properties; Design patterns; Non functional requirements; Process oriented; Quality attributes; Quality requirements; Rationale; Requirements; Satisfying; Softgoal

Indexed keywords

EID: 0003026194     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s007660170013     Document Type: Article

References (33)

1. Boehm BW. Characteristics of software quality. North-Holland, Amsterdam, 1978
2. Bowen TP, Wigle GB, Tsai JT. Specification of software quality attributes (Report RADC-TR-85-37). Rome Air Development Center, Griffiss Air Force Base, NY, 1985
3. Chung L. Representing and using non-functional requirements: a process-oriented approach. Department of Computer Science University of Toronto, Toronto, 1993
4. Chung L, Nixon B, Yu E et al. Non-functional requirements in software engineering. Kluwer Academic, Boston, MA, 2000
5. Mylopoulos J, Chung L, Nixon B. Representing and using nonfunctional requirements: a process-oriented approach. IEEE Trans Software Eng 1992;18(6)
6. Chung L, Nixon B, Yu E. Using quality requirements to systematically develop quality software. In: Proceedings of the 4th international conference on software quality, McLean, VA, 1994
7. Chung L, Nixon B, Yu E. Using non-functional requirements to systematically select among alternatives in architectural design. In: Proceedings of the first international workshop on architecture for software systems, Seattle, WA, 1995
8. Chung L, Gross D, Yu E. Architectural design to meet stakeholder requirements. In: Donohue P (ed). Software architecture. Kluwer Academic, San Antonio, TX, 1999, pp 545-564
9. Chung L, Nixon B, Yu E. Dealing with change: an approach using non-functional requirements. Requirements Eng 1996;1:238-260
10. Gamma E, Helm R, Johnson R, Vlissides J. Design patterns: elements of reusable object-oriented software. Addison-Wesley, Reading, MA, 1995
11. Buschmann F. Pattern-oriented software architecture: a system of patterns. Wiley, Chichester, UK, 1996
12. Coplien OJ. Software patterns. SIGS Books & Multimedia, 1996
13. Beck K, Johnson R. Patterns generate architectures. In: Proceedings of the 8th European conference on object-oriented programming, Bologna, Italy, 1994, pp 139-149.
14. Alexander C. The timeless way of building. Oxford University Press, New York, 1979
15. Eden AH, Gil J, Yehudai A. Precise specification and automatic application of design patterns. In: Twelfth IEEE international automated software engineering conference, 1997
16. Florijn G, Meijers M, Winsen P. Tool support for object-oriented patterns. In: Proceedings of ECOOP'97, Finland, 1997
17. Coplien J, Zhao L. Symmetry and symmetry breaking in software patterns. In: Proceedings of the second international symposium on generative and component-based software engineering, Erfurt, Germany, 2000
18. Alexander C, Ishikawa S, Silverstein M. A pattern language: towns, buildings, construction. Oxford University Press, New York, 1977
19. Coplien OJ. A generative development process pattern language. In: Coplien OJ, Schmidt DC (eds). Pattern languages of program design. Addison-Wesley, Reading, MA, 1995
20. Coplien JO, Schmidt DC. Pattern languages of program design. Addison-Wesley, Reading, MA, 1995
21. http://www.rational.com
22. Molin P, Ohlsson L. The points and deviation pattern language of fire alarm systems. In: Martin RR, Dirk (eds). Pattern languages for program design 3. Corporate & Professional Publishing Group, Reading, MA, 1998, pp 431-445
23. Yu E. Modelling strategic relationships for process reengineering. PhD thesis, Department of Computer Science, University of Toronto, 1995
24. Bosch J, Molin P. Software architecture design: evaluation and transformation. In: IEEE engineering of computer based systems symposium, 1999
25. Lee J. Extending the Potts and Bruns model for recording design rationale. In: Proceedings of the 13th international conference on software engineering, Austin, TX, 1991, pp 114-125
26. Potts C, Bruns G. Recording the reasons for design decisions. In: Proceedings of the 10th international conference on software engineering, 1988, pp 418-427
27. Mylopoulos J, Chung L, Yu E. From object-oriented to goal-oriented requirements analysis. Commun ACM 1999;42(1):31-37
28. Yu E, Mylopoulos J. Why goal-oriented requirements engineering. In: Dubois E, Opdahl AL, Pohl K (eds). Proceedings of the 4th international workshop on requirements engineering: foundations of software quality, Pisa, Italy, 8-9 June 1998, Pisa, Italy. Presses Universitaires de Namur, 1998, pp 15-22
29. Lamsweerde A. Requirements engineering in the year 2000: a research perspective. In: Proceeding of 22nd international conference on software engineering. ACM Press, Limerick, 2000, pp 5-19
30. Jarke M. Requirements Tracing. Communication ACM 1998;41(12)
31. http://www.cs.toronto.edu/km/ome
32. Gentner D. Structure-mapping: a theoretical framework for analogy. Cognitive Sci 1983;7:155-170
33. Jurisica I, Mylopoulos J, Yu E. Using ontologies for knowledge management: an information systems perspective. In: Knowledge: creation, organization and use - Proceedings of the 62nd annual meeting of the American Society for Information Science (ASIS'99), 31 October-4 November 1999, Washington, DC, pp 482-496