Formalizing patterns with the user requirements notation

Design Pattern Formalization Techniques

Volumn , Issue , 2007, Pages 302-323

  Mussbacher, Gunter ^a   Amyot, Daniel ^a   Weiss, Michael ^b  

^a UNIVERSITY OF OTTAWA   (Canada)

^b CARLETON UNIVERSITY   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 77955322175     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-59904-219-0.ch014     Document Type: Chapter

References (33)

1. Alexander, C. (1979). A pattern language. Oxford University Press.
2. Amyot, D. (2003). Introduction to the user requirements notation: Learning by example. Computer Networks, 42(3), 285-301.
3. Amyot, D., Weiss, M., & Logrippo, L. (2005). UCM-based generation of test purposes. Computer Networks, 49(5), 643-660.
4. Andrade, R., & Logrippo, L. (2000, July). Reusability at the early development stages of the mobile wireless communication systems. In Proceedings of the 4th World Multiconference on Systemics, Cybernetics and Informatics (SCI 2000), Orlando, FL (Vol. VII, Part I, pp. 11-16).
5. Araujo, I., & Weiss, M. (2002). Linking non-functional requirements and patterns. In Proceedings of the 9th Conference on Pattern Languages of Programs (PLoP). Retrieved November, 16, 2006, from http://jerry.cs.uiuc.edu/~plop/plop2002/final/PatNFR.pdf
6. Avgeriou, P., & Zdun, U. (2005, July). Architectural patterns revisited: A pattern language. In Proceedings of the 10th European Conference on Pattern Languages of Programs (EuroPlop), Irsee, Germany.
7. Billard, E.A. (2004, August). Patterns of agent interaction scenarios as use case maps. IEEE Transactions on Systems, Man, and Cybernetics. Part B, Cybernetics, 34(4), 1933-1939.
8. Buhr, R.J.A., & Casselman, R.S. (1995). Use case maps for object-oriented systems. Prentice Hall.
9. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M. (1996). Pattern-oriented software architecture. Wiley.
10. Chung, L., Nixon, B., Yu, E., & Mylopoulos, J. (2000). Non-functional requirements in software engineering. Kluwer Academic Publishers.
11. Chung, L., Supakkul, S., & Yu, A. (2002, July 8-11). Good software architecting: Goals, objects, and patterns. In Proceedings of the Information, Computing & Communication Technology Symposium (ICCT- 2002), UKC'02, Seoul, Korea.
12. Coplien, J. (1996). Software patterns. SIGS. Retrieved November 16, 2006, from http://users.rcn.com/jcoplien/Patterns/WhitePaper/SoftwarePatterns.pdf
13. Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design patterns: Elements of reusable object-oriented software. Addison-Wesley.
14. Gross, D., & Yu, E. (2001). From non-functional requirements to design through patterns. Requirements Engineering, 6(1), 18-36.
15. Hannemann, J., & Kiczales, G. (2002, November). Design pattern implementation in Java and AspectJ. In Proceedings of the 17th OOPSLA (pp. 161-173).
16. ITU-T (2003). Recommendation Z.150 (02/03), user requirements notation (URN) - Language requirements and framework. Geneva, Switzerland.
17. Jacobson, I., & Ng, P.-W. (2004). Aspect-oriented software development with use cases. Addison-Wesley.
18. Mouratidis, H., Weiss, M., & Giorgini, P. (2005). Security patterns meet agent oriented software engineering: A complementary solution for developing secure information systems. Conceptual modeling (ER) (LNCS 2716, pp. 225-240). Springer-Verlag.
19. Mussbacher, G., & Amyot, D. (2001, October 3-5). A collection of patterns for use case maps. In Proceedings of the 1st Latin American Conference on Pattern Languages of Programming (SugarLoafPLoP 2001), Rio de Janeiro, Brazil.
20. Mussbacher, G., Amyot, D., & Weiss, M. (2006, September 11). Visualizing aspect-oriented requirements scenarios with use case maps. In Proceedings of the International Workshop on Requirements Engineering Visualization (REV 2006), Minneapolis/St. Paul, Minnesota.
21. Ong, H., Weiss, M., & Araujo, I. (2003, March). Rewriting a pattern language to make it more expressive. Hot topic on the expressiveness of pattern languages, ChiliPLoP. Carefree, USA.
22. Petriu, D., & Woodside, M. (2002). Software performance models from system scenarios in use case maps. Computer performance evaluation / TOOLS 2002 (LNCS 2324, pp. 141-158). Springer-Verlag.
23. Rising, L. (2000). Pattern almanac 2000. Addison-Wesley.
24. Roy, J.-F., Kealey, J., & Amyot, D. (2006, May). Towards integrated tool support for the user requirements notation. In Proceedings of the Fifth Workshop on System Analysis and Modelling (SAM'06), Kaiserslautern, Germany.
25. Shaw, M., & Garlan, D. (1996). Software architecture: Perspectives on an emerging discipline. Prentice Hall.
26. Taibi, T., & Ngo, D.C.L. (2001). Why and how should patterns be formalized. Journal of Object-Oriented Programming (JOOP), 14(4), 8-9.
27. URN Focus Group (2003a, September). Draft Rec. Z.151 - Goal-oriented requirement language (GRL). Geneva, Switzerland.
28. URN Focus Group (2003b, September). Draft Rec. Z.152 - Use case map notation (UCM). Geneva, Switzerland.
29. Wassermann, R., & Cheng, B. (2003). Security patterns (Tech. Rep. No. MSU-CSE-03-23). Michigan State University.
30. Weiss, M., & Amyot, D. (2005, July-September). Business process modeling with URN. International Journal of E-Business Research, 1(3), 63-90.
31. Yacoub, S., & Ammar, H. (2004). Pattern-oriented analysis and design: Composing patterns to design software systems. Addison-Wesley.
32. Yu, E. (1997, January 6-8). Towards modelling and reasoning support for early-phase requirements engineering. In Proceedings of the 3rd IEEE International Symposium on Requirements Engineering (RE'97) (pp. 226-235). Washington, DC.
33. Yu, Y., Leite, J.C.S.P., & Mylopoulos, J. (2004, September). From goals to aspects: Discovering aspects from requirements goal models. In Proceedings of the 12th IEEE International. Conference on Requirements Engineering (RE 2004) (pp. 38-47). Kyoto, Japan.