Software development with reusable requirements-based cases

Śmiałek, M.

Artykuł - szczegóły

Tytuł artykułu

Software development with reusable requirements-based cases

Autorzy

Śmiałek M.

Identyfikatory

Warianty tytułu

Tworzenie oprogramowania przy pomocy reużywalnych przypadków opartych na wymaganiach

Języki publikacji

Abstrakty

Vast majority of software development projects seem to ignore past knowledge about sohdng specific problems. This might be explained by significant difficulties to reuse knowledge in such a complex domain as software engineering is. There seem to be no eijfective mechanisms to find and reuse past solutions to problems similar to the currently solved one. The main ąuestion that this book aims at solving is the above inability to reuse knowledge about already solved software development problems. In this book there is proposed a process for systematic reuse of so-called Software Cases. Any Software Case contains a precisely expressed problem statement in the form of a Reąuirements Model. Ali elements of this problem statement can be mapped onto appropriate elements of the problem solution. This solution is formed of (again) precisely expressed design models and the finał code. Software Cases can be reused on the basis of their similarity to the currently developed system (current Software Case). This similarity can be determined by comparing the current (perhaps yet incomplete) reąuirements model with reąuirements models of past Software Cases. The past solution can then be easily reused by modifying it in those places that arę precisely marked as needing rework in order to solve the current problem. The book contains a detailed discussion on the issues that lead to constructing a comprehensive reąuirements-based reuse framework. There arę described mechanisms and tools that can support such a framework. A vision of how to organise a reuse process is presented, including details on how a software development organi-sation should follow this process. This includes using a specific precise language for specifying reąuirements and designing systems. The process and the language arę defined both formally and practically. The book introduces concrete syntax for in-dividual elements of Software Cases: reąuirements, architecture and detailed design. This syntax is used to formulate them in a systematic way. Techniąues for transform-ing models to form a coherent path from reąuirements to code arę given. Certain mechanisms for comparing and retrieving Software Cases arę also specified. This includes a ąuery language suitable for formulating ąueries that allow for match-ing reąuirements models thus allowing for reusing solutions to problems specified through reąuirements.

Zdecydowana większość projektów konstrukcji oprogramowania wydaje się ignorować wiedzę na temat rozwiązanych wcześniej problemów. Można to wytłumaczyć trudnościami w ponownym wykorzystaniu wiedzy w tak złożonej dziedzinie jak inżynieria oprogramowania. Brakuje efektywnych mechanizmów znajdowania i ponownego wykorzystania rozwiązań minionych problemów, podobnych do stojących przed nami w danej chwili. Podstawową kwestią, której rozwiązanie jest celem tej książki jest powyższa niemożność "reużycia" wiedzy o rozwiązanych już problemach w konstrukcji oprogramowania. W tej książce zaproponowano proces systematycznego wykorzystywania tzw. przypadków programistycznych (ang. software case). Każdy przypadek programistyczny zawiera precyzyjnie sformułowane stwierdzenie problemu w formie modelu wymagań. Wszystkie elementy tego modelu mogą być przełożone na odpowiednie elementy rozwiązania sformułowanego problemu. To rozwiązanie jest złożone z precyzyjnie wyrażonych modeli projektowych oraz kodu. Przypadki programistyczne mogą być ponownie wykorzystane na podstawie ich podobieństwa do aktualnie tworzonego systemu (aktualnego przypadku programistycznego). To podobieństwo może być określone poprzez porównanie aktualnego (być może jeszcze niekompletnego) modelu wymagań z modelami wcześniej wytworzonych przypadków. Wcześniejsze rozwiązanie może być z łatwością ponownie wykorzystane poprzez jego modyfikację w miejscach oznaczonych jako wymagające przeróbek aby dostosować je do aktualnego problemu. Książka zawiera szczegółową dyskusję kwestii, które umożliwiają skonstruowanie kompleksowego systemu ponownego wykorzystania opartego na wymaganiach. Opisane są mechanizmy i narzędzia wspomagające taki system. Przedstawiono wizję zorganizowania procesu ponownego wykorzystania, łącznie ze wskazówkami dla organizacji wytwarzających oprogramowanie. Oznacza to również wykorzystanie konkretnego, precyzyjnego języka specyfikacji wymagań i projektowania systemów. Proces i język są zdefiniowane zarówno formalnie jak i od strony praktycznej. Książka wprowadza konkretną składnię dla elementów przypadków programistycznych: wymagań, architektury i projektu szczegółowego. Ta składnia jest wykorzystana do formułowania ich w sposób systematyczny. Jednocześnie podano techniki dla transformacji modeli w celu utworzenia spójnej ścieżki od wymagań do kodu. Przedstawiono również określone mechanizmy porównywania i odszukiwania przypadków programistycznych. Dotyczy to również języka zapytań odpowiedniego dla formułowania kwerend pozwalających na dobieranie modeli wymagań, w ten sposób pozwalając na ponowne wykorzystanie rozwiązań wyspecyfikowanych wymaganiami.

Słowa kluczowe

software reuse software requirements software model transformations software development methodologies

ponowne użycie oprogramowania wymagania oprogramowania transformacje modeli oprogramowania metodyki wytwarzania oprogramowania

Wydawca

Oficyna Wydawnicza Politechniki Warszawskiej

Czasopismo

Prace Naukowe Politechniki Warszawskiej. Elektryka

Rocznik

2007

Tom

z. 135

Strony

3--147

Opis fizyczny

Bibliogr. 230 poz., rys., tab., wykr.

Twórcy

autor

Śmiałek M.

Instytut Elektrotechniki Teoretycznej i Systemów Informacyjno-Pomiarowych, Wydział Elekektryczny Politechniki Warszawskiej

Bibliografia

1. Agnar Aamodt and Enric Plaza. Case-based reasoning: Foundational issues, methodological variations, and system approaches. Artificial Intelligence Communications, 7(1):39-59, 1994.
2. Sushil Acharya and R Sadananda. Promoting software reuse using self organizing maps. Neural Processing Letters, 5(3):219-226, 1997.
3. Steve Adolph, Paul Bramble, Alistair Cockburn, and Andy Pols. Patterns for Effective Use Cases. Addison Wesley, 2002.
4. Ian Alexander. A taxonomy of stakeholders, human roles in system development. International Journal of Technology and Human Interaction, 1(1):23-59, 2005.
5. Ian Alexander and Neil Maiden, editors. Scenarios, Stories, Use Cases. John Wiley, 2004.
6. Klaus-Dieter Althoff, Andreas Birk, Susanne Hartkopf, Wolfgang Mller, Markus Nick, Dagmar Surmann, and Carsten Tautz. Systematic population, utilization, and maintenance of a repository for comprehensive reuse. Lecture Notes in Computer Science, 1756:25-50, 2000.
7. Scott W Ambler. A roadmap for Agile MDA. http://www.agilemodeling.com/essays/agileMDA.htm, 2005.
8. Albert Ambroziewicz. Software model library with visual query language. In International Workshop on Model Reuse Strategies -MoRSe, pages 33-36, 2006.
9. Albert Ambroziewicz and Ireneusz Bulwarski.Wyszukiwanie w bibliotece modeli oprogramowania za pomoca języka wizualnych zapytań (Searching in a software model library with a visual query language). Master's thesis, Warsaw University of Technology, 2005. supervised by Michał Śmiałek.
10. AONIX. Using ACD Templates, Tool Documentation, 2004.
11. Frank Armour and Granville Miller. Advanced Use Case Modeling: Software Systems. Addison-Wesley, 2000.
12. S Arnott and G Hinks. HMRC merger tops government IT spending. Accountancy Age, 4 Aug. 2005.
13. Hernán Astudillo, Gonzalo Génova, Michał Śmiałek, Juan Llorens Morillo, Pierre Metz, and Rubén Prieto-Diáz. Use cases in model-driven software engineering. Lecture Notes in Computer Science, 3844:262-271, 2006.
14. C Atkinson, J Bayer, C Bunse, E Kamsties, O Laitenberger, R Laqua, D Muthig, B Paech, J Wüst, and J Zettel. Component-based Product Line Engineering with UML. Addison-Wesley, 2001.
15. F Baader, D Calvanese, D McGuinness, D Nardi, and P Patel-Schneider. The Description Logic Handbook. Cambridge University Press, 2003.
16. Sidney C Bailin. Software reuse as ontology negotiation. Lecture Notes in Computer Science, 3107:242-253, June 2004.
17. Victor Basili and H Dieter Rombach. Support for comprehensive reuse. IEEE Software Engineering Journal, 6(5):303-316, 1991.
18. Kent Beck. Extreme Programming Explained: Embrace Change. Addison-Wesley, 2000.
19. Alex E Bell. Death by UML fever. Queue, 2(1):72-80, March 2004.
20. Alex E Bell. UML fever: Diagnosis and recovery. Queue, 3(2):48-56, March 2005.
21. Birol Berkem. How to increase your business reactivity with UML/MDA. Journal of Object Technology, 2(6):117-138, Nov-Dec 2003.
22. J Bezivin, G Dupe, F Jouault, G Pitette, and J Rougui. First experiments with the ATL model transformation language: Transforming XSLT into XQuery. In OOPSLA Workshop on Generative Techniques in the context of Model Driven Architecture, 2003.
23. Jean Bézivin and Olivier Gerbé. Towards a precise definition of the OMG/MDA framework. In Proc. 16th Annual International Conference on Automated Software Engineering ASE 2001, pages 273-280, November 2001.
24. Robert Biddle, James Noble, and Ewan Tempero. From essential use cases to objects. In L Constantine, editor, for USE 2002 Proceedings. Ampersand Press, 2002.
25. Robert Biddle, James Noble, and Ewan Tempero. Supporting reusable use cases. Lecture Notes in Computer Science, 2319:210-226, 2002.
26. Ted J Biggerstaff. A perspective of generative reuse. Annals of Software Engineering, 5:169-225, 1998.
27. Solveig Bjornestad. Analogical reasoning for reuse of object-oriented specifications. Lecture Notes in Computer Science, 2689:50-64, 2003.
28. Maurits C Blok and Jacob L Cybulski. Reusing UML specifications in a constrained application domain. In Proceedings of 1998 Asia Pacific Software Engineering Conference, pages 196-202, 1998.
29. G Bockle, P Clements, J D McGregor, D Muthig, and K Schmid. Calculating ROI for software product lines. IEEE Software, 21(3):23-31, 2004.
30. Grady Booch. Object-Oriented Design with Applications. Benjamin-Cummings, Menlo Park, 1991.
31. Peter Braun and Frank Marschall. Transforming object oriented models with BOTL. Electronic Notes in Theoretical Computer Science, 72(3):1-15, 2003.
32. J M Carroll, editor. Scenario-based design: Envisioning work and technology in system development. Wiley, New York, 1995.
33. Rick Cattell. The Object Database Standard: ODMG 2.0. Morgan Kaufman, 1997.
34. Christine W Chan. Knowledge and software modeling using UML. Software and Systems Modeling, 3(4):294-302, 2004.
35. Ruzanna Chitchyan, Awais Rashid, Paul Rayson, and Robert Waters. Semantics-based composition for aspect-oriented requirements engineering. In Proc. 6th International Conference on Aspect-Oriented Software Development (AOSD 2007), 2007.
36. Paul Clements and Linda Northrop. Software Product Lines: Practices and Patterns. Addison-Wesley, 2002.
37. Peter Coad and Edward Yourdon. Object-Oriented Analysis. Prentice Hall, Englewood Cliffs, 1990.
38. Peter Coad and Edward Yourdon. Object-Oriented Design. Prentice Hall, Englewood Cliffs, 1991.
39. Alistair Cockburn. Structuring use cases with goals. Journal of Object-Oriented Programming, 5(10):56-62, 1997.
40. Alistair Cockburn. Writing Effective Use Cases. Addison-Wesley, 2000.
41. Alistair Cockburn. Agile Software Development. Addison-Wesley, 2002.
42. Mike Cohn. User Stories Applied. Addison-Wesley, 2004.
43. Jim Conallen. Building Web applications with UML. Addison-Wesley Longman, Boston, MA, USA, 1999.
44. S Condon, C Seaman, V Basili, S Kraft, J Kontio, and Y Kim. Evolving the reuse process at the Flight Dynamics Division (FDD) Goddard Space Flight Center. In Proceedings of the 21st Annual Software Engineering Workshop, NASA/SEL, 1996.
45. Larry L Constantine. What do users want? Engineering usability into software. Windows Tech Journal, 1995. revised in 2000, http://www.foruse.com/articles/whatusers.htm.
46. Larry L Constantine and Lucy A D Lockwood. Structure and style in use cases for user interface design. In M van Harmelen, editor, Object-Modeling and User Interface Design. Addison-Wesley, 2001.
47. James R Cordy. TXL - a language for programming language tools and applications. Electronic Notes in Theoretical Computer Science, 110:3-31, 2004.
48. Jacob L Cybulski, Ralph D (Butch) Neal, Anthony Kram, and Jeffrey C Allen. Reuse of early life-cycle artifacts: workproducts, methods and tools. Annals of Software Engineering, 5(0):227-251, 1998.
49. Luiz Marcio Cysneiros and Julio Cesar Sampaio do Prado Leite. Nonfunctional requirements: from elicitation to conceptual models. IEEE Transactions on Software Engineering, 30(5):328-350, May 2004.
50. Krzysztof Czarnecki, and Ulrich W Eisenecker. Generative Programming: Methods, Tools, and Applications. ACM Press/Addison-Wesley, 2000.
51. Krzysztof Czarnecki and Simon Helsen. Classification of model transformation approaches. In OOPSLA'03 Workshop on Generative Techniques in the Context of Model-Driven Architecture, 2003.
52. Benedicte Dano, Henri Briand, and Franck Barbier. An approach based on the concept of use case to produce dynamic object-oriented specifications. In 3rd IEEE International Symposium on Requirements Engineering (RE'97), pages 54-64. IEEE Computer Society, 1997.
53. E S de Almeida, A Alvaro, D Lucredio, V C Garcia, and S R de Lemos Meira. A survey on software reuse processes. In IEEE International Conference on Information Reuse and Integration, pages 66-71, 2005.
54. P Devanbu, P G Brachman, R J and Selfridge, and B W Ballard. LaSSIE: A knowledge-based software information system. Communications of the ACM, 34(5):34-49, 1991.
55. Dragan Djuric, Dragan Gasevic, and Vladan Devedzic. Ontology modeling and MDA. Journal of Object Technology, 4(1):109-128, 2005.
56. K Duddy, A Gerber, M J Lawley, K Raymond, and Steel J. Model transformation: A declarative, reusable patterns approach. In Proc. 7th IEEE International Enterprise Distributed Object Computing Conference, EDOC 2003, pages 174-195, Brisbane, Australia, September 2003.
57. A Duran, A Ruiz-Cortes, R Corchuelo, and M Toro. Supporting requirements verification using XSLT. In Proc. IEEE Joint International Conference on Requirements Engineering (RE'02), pages 165-172, 2002.
58. Gerald Ebner and Hermann Kaindl. Tracing all around in reengineering. IEEE Software, 19(3):70-77, 2002.
59. Alexander Egyed. A scenario-driven approach to traceability. In ICSE'01: Proc. 23rd International Conference on Software Engineering, pages 123-132, Washington, DC, USA, 2001. IEEE Computer Society.
60. Alexander Egyed. A scenario-driven approach to trace dependency analysis. IEEE Transactions on Software Engineering, 29(2):116-132, 2003.
61. European Space Agency. ESA PSS-05-0 Software Engineering Standards, Issue 2, Revision 1, 1994.
62. Joerg Evermann and Yair Wand. Toward formalizing domain modeling semantics in language syntax. IEEE Transactions on Software Engineering, 31(1):21-37, January 2005.
63. John Favaro. A comparison of approaches to reuse investment analysis. In Proc. 4th International Conference on Software Reuse, pages 136-145, 1996.
64. Christiane Fellbaum, editor. WordNet: An Electronic Lexical Database. MIT Press, 1998.
65. Donald Firesmith and Brian Henderson-Sellers. The OPEN Process Framework. An Introduction. Addison-Wesley, 2001.
66. Gilles Fouqué and Stan Matwin. A case-based approach to software reuse. Journal of Intelligent Information Systems, 2(2):165-197, 1993.
67. Martin Fowler. Analysis Patterns: Reusable Object Models. Addison Wesley, 1996.
68. Martin Fowler. UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition. Addison-Wesley, 2004.
69. William B. Frakes and Kyo Kang. Software reuse research: status and future. IEEE Transactions on Software Engineering, 31(7):529-536, July 2005.
70. Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. Design Patterns. Elements of Reusable Object-Oriented Software. Addison Wesley, Reading, Mass., 1995.
71. David Gelperin. Precise use cases. Technical report, LiveSpecs Software, 2004.
72. Gonzalo Génova, Juan Llorens, Pierre Metz, Rubén Prieto-Diaz, and Hernán Astudillo. Open issues in industrial use case modeling. Lecture Notes in Computer Science, 3297:52-61, 2005.
73. A Gerber, M J Lawley, K Raymond, J Steel, and A Wood. Transformation: The missing link of MDA. Lecture Notes in Computer Science, 2505:90-105, 2002.
74. Martin Glinz. A lightweight approach to consistency of scenarios and class models. In Proc. 4th International Conference on Requirements Engineering (ICRE'00), pages 49-58, 2000.
75. H Gomaa, L Kerschberg, V Sugumaran, C Bosch, I Tavakoli, and L O'Hara. A knowledge-based software engineering environment for reusable software requirements and architectures. Automated Software Engineering, 3(3-4):285-307, 1996.
76. Hassan Gomaa. Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures. Addison Wesley, 2004.
77. Paulo Gomes. Software design retrieval using bayesian networks and WordNet. Lecture Notes in Computer Science, 3155:184-197, 2004.
78. Paulo Gomes, Francisco C Pereira, Paulo Carreiro, Paulo Paiva, Nuno Seco, José Luís Ferreira, and Carlos Bento. Solution verification in software design: A CBR approach. Lecture Notes in Computer Science, 2689:171-185, 2003.
79. Paulo Gomes, Francisco C Pereira, Paulo Carreiro, Paulo Paiva, Nuno Seco, José Luís Ferreira, and Carlos Bento. Case-based adaptation for UML diagram reuse. Lecture Notes in Computer Science, 3215:678-686, 2004.
80. Markus Grabert and Derek G Bridge. Case-based reuse of software examplets. Journal of Universal Computer Science, 9(7):627-641, 2003.
81. Ian MGraham. Migrating to Object Technology. Addison-Wesley,Workingham, 1994.
82. Ian M Graham. Task scripts, use cases and scenarios in object-oriented analysis. Object-Oriented Systems, 3(3):123-142, 1996.
83. Ian M Graham. Object-Oriented Methods Principles & Practice. Pearson Education, 2001.
84. Jack Greenfield and Keith Short. Software Factories. Assembling Applications with Patterns, Models, Frameworks and Tools. Wiley, Indianapolis, Indiana, 2004.
85. Sol Greenspan, John Mylopoulos, and Alex Borgida. On formal requirements modeling languages: RML revisited. In ICSE'94: Proc. 16th International Conference on Software Engineering, pages 135-147, Los Alamitos, CA, USA, 1994. IEEE Computer Society Press.
86. Sol J Greenspan, Alexander Borgida, and John Mylopoulos. A requirements modeling language and its logic. Information Systems, 11(1):9-23, 1986.
87. Paweł Gryczon and Piotr Stańczuk. Obiektowy system konstrukcji scenariuszy przypadków użycia (Object-oriented use case scenario construction system). Master's thesis, Warsaw University of Technology, 2002.
88. Haitham Hamza and Mohamed E Fayad. Applying analysis patterns through analogy: Problems and solutions. Journal of Object Technology, 3(4):197-208, April 2004.
89. M Hause and F Thom. Modeling high level requirements in uml/sysml. In INCOSE 2005 UK Spring Conference, pages 10-15, 2005.
90. Brian Henderson-Sellers and Julian Edwards. Booktwo of Object-Oriented Knowledge. Prentice Hall, Englewood Cliffs, 1994.
91. Brian Henderson-Sellers, Anthony J H Simons, and Houman Younessi. The OPEN Toolbox of Techniques. Addison-Wesley Longman, Wokingham, 1998.
92. Scott Henninger. Case-based knowledge management tools for software development. Automated Software Engineering, 4(1):319-340, 1997.
93. L Hotz, K Wolter, T Krebs, S Deelstra, M Sinnema, J Nijhuis, and J MacGregor. Configuration in Industrial Product Families -The ConIPF Methodology. AKA Verlag, 2005.
94. Russell R Hurlbut. A survey of approaches for describing and formalizing use cases. Technical Report XPT-TR-97-03, Expertech Ltd., 1997.
95. Russell R Hurlbut. Managing Domain Architecture Evolution Through Adaptive Use Case and Business Rule Models. PhD thesis, Illinois Institute of Technology, 1998.
96. International Standards Organization. Information technology - Open Distributed Processing - Unified Modeling Language (UML) Version 1.4.2, 2005. ISO/IEC 19501:2005.
97. I Jacobson, M Christerson, P Jonsson, and G Overgaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, Reading, 1992.
98. Young Jun Kim and Chung Tae Kim. Design of object model reuse system by CBR in system analysis. International Journal of Software Engineering and Knowledge Engineering, 14(3):277-290, 2004.
99. Hermann Kaindl. Using hypertext for semiformal representation in requirements engineering practice. The New Review of Hypermedia and Multimedia, 2:149-173, 1996.
100. Hermann Kaindl. Difficulties in the transition from OO analysis to design. IEEE Software, 16(5):94-102, Sept./Oct. 1999.
101. Hermann Kaindl. A scenario-based approach for requirements engineering: Experience in a telecommunication software development project. Systems Engineering, 8(3):197-209, 2005.
102. Hermann Kaindl and John Mylopoulos. Why is it so difficult to introduce requirements engineering research results into mainstream requirements engineering practice? In Proceedings of the Twelfth Conference on Advanced Information Systems Engineering (CAiSE 2000), pages 7-12, Stockholm, Sweden, June 2000. Springer-Verlag, Heidelberg, Germany. Panelists: S. Brinkkemper, J. A. Bubenko, B. Farbey and I. Jacobson.
103. Hermann Kaindl, Michał Śmiałek, Davor Svetinovic, Albert Ambroziewicz, Jacek Bojarski, Wiktor Nowakowski, Tomasz Straszak, Hannes Schwarz, Daniel Bildhauer, John P Brogan, Kizito Ssamula Mukasa, Katharina Wolter, and Thorsten Krebs. Requirements specification language definition. Project Deliverable D2.4.1, ReDSeeDS Project, 2007. www.redseeds.eu.
104. Audris Kalnins, Janis Barzdins, and Edgars Celms. Basics of model transformation language MOLA. In Workshop on Model Driven Development (WMDD 2004), 2004.
105. Audris Kalnins, Janis Barzdins, and Edgars Celms. Model transformation language MOLA. Lecture Notes in Computer Science, 3599:14-28, 2004.
106. Audris Kalnins, Agris Sostaks, Edgars Celms, Elina Kalnina, Albert Ambroziewicz, Jacek Bojarski, Wiktor Nowakowski, Tomasz Straszak, Volker Riediger, Hannes Schwarz, Daniel Bildhauer, Sevan Kavaldjian, Roman Popp, and Jurgen Falb. Reuse-oriented modelling and transformation language definition. Project Deliverable D3.2, ReDSeeDS Project, 2007. www.redseeds.eu.
107. K C Kang, J Lee, and P Donohoe. Feature-oriented product line engineering. IEEE Software, 19(4):58-65, 2002.
108. Kyo C Kang, Sholom Cohen, Robert Holibaugh, James Perry, and A Spencer Peterson. A reuse-based software development methodology. Technical report, Software Engineering Institute, Carnegie Mellon University, 1992. Special Report CMU/SEI-92-SR-4.
109. Even-André Karlsson. Software Reuse: A Holistic Approach. John Wiley, 1991.
110. Panagiotis Katalagarianos and Yannis Vassiliou. On the reuse of software: A case-based approach employing a repository. Automated Software Engineering, 2(1):55-86, 1995.
111. Anneke G Kleppe, Jos B Warmer, and Bast Wim. MDA Explained, The Model Driven Architecture: Practice and Promise. Addison-Wesley, Boston, 2003.
112. J Koehler, R Hauser, S Kapoor, F Y Wu, and S Kumaran. A model-driven transformation method. In Proc. 7th IEEE International Enterprise Distributed Object Computing Conference EDOC 2003, pages 186-197, September 2003.
113. A Koenigs and A Schuerr. Multi-domain integration with mof and extended triple graph grammars. In J Bezivin and R Heckel, editors, Language Engineering for Model-Driven Software Development, Dagstuhl Seminar Proceedings, IBFI, 2005.
114. P Kruchten. Agility with the RUP. Rational Edge, 3:11 p, 2002.
115. Philippe Kruchten. The Rational Unified Process: An Introduction, 3rd ed. Addison Wesley, 2003.
116. Miguel A Laguna, Oscar López, and Yania Crespo. Reuse, standardization, and transformation of requirements. Lecture Notes in Computer Science, 3107:329-338, 2004.
117. Dean Leffingwell and Don Widrig. Managing Software Requirements: A Use Case Approach, Second Edition. Addison-Wesley, 2003.
118. N G Lester, F G Wilkie, and D W Bustard. Applying UML extensions to facilitate software reuse. Lecture Notes in Computer Science, 1618:393-405, 1999.
119. Tihamer Levendovszky, Gabor Karsai, Miklos Maroti, Akos Ledeczi, and Hassan Charaf. Model reuse with metamodel-based transformations. Lecture Notes in Computer Science, 2319:166-179, Jan 2002.
120. Juan Llorens, José M Fuentes, Rubén Prieto-Diaz, and Hernán Astudillo. Incremental software reuse. Lecture Notes in Computer Science, 4039:386-389, 2006.
121. Chung-Horng Lung, Joseph E Urban, and Gerald T Mackulak. Analogy-based domain analysis approach to software reuse. Requirements Engineering, 11(4):22 p, 2006.
122. Paul Luttikhuizen, editor. Requirements Modelling and Traceability. ESAPS project, ITEA 99005, 2001. Document no. Philips-WP3-0106-01.
123. Robert A Maksimchuk and Eric J Naiburg. UML for Mere Mortals. Addison-Wesley, 2005.
124. Mike Mannion, Hermann Kaindl, and Joe Wheadon. Reusing single system requirements from application family requirements. In Proc. International Conference on Software Engineering 1999 (ICSE'99), 1999.
125. M D McIlroy. Mass produced software components. In P Naur, B Randell, and J N Buxton, editors, Software engineering concepts and techniques, Proceedings of NATO Conference on Software Engineering, pages 88-98, New York, 1969.
126. Nenad Medvidovic, Paul Gruenbacher, Alexander Egyed, and Barry W Boehm. Software model connectors: Bridging models across the software lifecycle. In Proc. 13th Int. Conference on Software Engineering and Knowledge Engineering (SEKE'01), pages 387-396, 2001.
127. Stephen J Mellor and Marc J Balcer. Executable UML: A Foundation for Model-Driven Architecture. Addison-Wesley, 2002.
128. Stephen J Mellor, Kendall Scott, Axel Uhl, and Dirk Weise. MDA Distilled: Principles of Model Driven Architecture. Addison-Wesley, 2004.
129. T Mens and P van Gorp. A taxonomy of model transformation. In Proc. Int'l Workshop on Graph and Model Transformation, GraMoT 2005, 2005.
130. T Menzies and J S Di Stefano. More success and failure factors in software reuse. IEEE Transactions on Software Engineering, 29(5):474-477, 2003.
131. P Metz, J O'Brien, and W Weber. Specifying use case interaction: Types of alternative courses. Journal of Object Technology, 2(2):111-131, March-April 2003.
132. Pierre Metz, John O'Brien, and Wolfgang Weber. Against use case interleaving. Lecture Notes in Computer Science, 2185:472-486, 2001.
133. Bertrand Meyer. Object-Oriented Software Construction. Prentice Hall, Hemel Hempstead, 1988.
134. Amir Michail. Data mining library reuse patterns using generalized association rules. In ICSE'00: Proceedings of the 22nd international conference on Software Engineering, pages 167-176, New York, NY, USA, 2000. ACM Press.
135. A Mili, S F Chmiel, R Gottumukkala, and L Zhang. An integrated cost model for software reuse. In Proceedings of the 2000 International Conference on Software Engineering, pages 157-166, 2000.
136. A Mili, R Mili, and R T Mittermeir. A survey of software reuse libraries. Annals of Software Engineering, 5:349-414, 1998.
137. Granville Miller. The Microsoft Solutions Framework for Agile Software Development: The Definitive Guide to Microsoft's New Agile Methodology. Addison-Wesley, 2007. in press.
138. Joaquin Miller and Jishnu Mukerji, editors. MDA Guide Version 1.0.1, omg/03-06-01. Object Management Group, 2003.
139. Maurizio Morisio, Michel Ezran, and Colin Tully. Success and failure factors in software reuse. IEEE Transactions on Software Engineering, 28(4):340-357, 2002.
140. John G Morris and Christine M Mitchell. A case-based support system to facilitate software reuse. In 1997 IEEE International Conference on Systems, Man, and Cybernetics 'Computational Cybernetics and Simulation', volume 1, pages 232-237, 1997.
141. Ezra K Mugisa. A reuse triplet view of UML. In Proceedings of 2003 IEEE Southeast Conf., pages 126-133, 2003.
142. Jerzy R Nawrocki, Michał Jasiński, Bartosz Walter, and Adam Wojciechowski. Extreme programming modified: Embrace requirements engineering practices. In Proc. 10th IEEE Joint International Conference on Requirements Engineering (RE 2002), pages 303-310, Essen, Germany, 2002. IEEE Computer Society.
143. Jerzy R Nawrocki, Tomasz Nędza, Mirosław Ochodek, and Łukasz Olek. Describing business processes with use cases. In Proc. 9th International Conference on Business Information Systems (BIS 2006), volume 85 of Lecture Notes in Informatics, pages 13-27, Klagenfurt, Austria, 2006. GI.
144. Jerzy R Nawrocki and Łukasz Olek. UC Workbench - a tool for writing use cases and generating mockups. Lecture Notes in Computer Science, 3556:230-234, 2005.
145. J M Nerson. Applying object-oriented analysis and design. Communications of the ACM, 35(9):63-74, 1992.
146. Bashar Nuseibeh and Steve Easterbrook. Requirements engineering: a roadmap. In ICSE - Future of SE Track, pages 35-46, 2000.
147. Object Management Group. MOF 2.0 Query / Views / Transformations RFP, ad/2002-04-10, 2002.
148. Object Management Group. Meta Object Facility (MOF) 2.0 Core Specification, Final Adopted Specification, ptc/03-10-04, 2003.
149. Object Management Group. Reusable Asset Specification: Final Adopted Specification, ptc/04-06-06, 2004.
150. Object Management Group. UML Profile for Patterns Specification, version 1.0, formal/04-02-04, 2004.
151. Object Management Group. Unified Modeling Language: Superstructure, version 2.0, Revised Final Adopted Specification, ptc/04-10-02, 2004.
152. Object Management Group. OCL 2.0, Final Specification, ptc/05-06-06, 2005.
153. Object Management Group. Unified Modeling Language: Infrastructure, version 2.0, formal/05-07-05, 2005.
154. Object Management Group. Unified Modeling Language: Superstructure, version 2.0, formal/05-07-04, 2005.
155. Object Management Group. Meta Object Facility Core Specification, version 2.0, formal/2006-01-01, 2006.
156. Ken Orr and Randy Hester. Beyond MDA 1.0: executable business processes from concept to code. MDA Journal, 11:2-7, 2004.
157. Gunnard Overgaardand Karin Palmkvist. Use Cases: Patterns and Blueprints. Addison Wesley, 2005.
158. Stephen R Palmer and John M Felsing. A Practical Guide to Feature-Driven Development. Prentice Hall PTR, 2002.
159. Ying Pan, Lei Wang, Lu Zhang, Bing Xie, and Fuqing Yang. Relevancy based semantic interoperation of reuse repositories. In SIGSOFT'04/FSE-12: Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering, pages 211-220, New York, NY, USA, 2004. ACM Press.
160. Tom Pender. UML Bible. John Wiley & Sons, New York, NY, USA, 2003.
161. K Periyasamy and J Chidambaram. A method for structural compatibility in software reuse using requirements specification. In 21st Annual International Computer Software and Applications Conference COMPSAC'97, pages 426-433, 1997.
162. James Petro, Michael E Fotta, and David B Weisman. Model-based reuse repositories-concepts and experience. In Proceedings of Seventh International Workshop on Computer-Aided Software Engineering, pages 60-69, 1995.
163. Dan Pilone and Neil Pitman. UML 2.0 in a Nutshell. O'Reilly, 2005.
164. J Poulin. Measuring Software Reuse. Addison-Wesley, 1997.
165. Rubén Prieto-Diaz. Domain analysis: an introduction. SIGSOFT Softw. Eng. Notes, 15(2):47-54, 1990.
166. QVT-Merge Group, OMG. Revised submission for MOF 2.0 Query / View / Transformation RFP, 2005. ad/2005-03-02P.
167. QVT-Partners. Revised submission for MOF 2.0 Query / Views / Transformations RFP, 2003.
168. Chris Raistrick, Paul Francis, and John Wright. Model Driven Architecture with Executable UML. Cambridge University Press, 2004.
169. Volker Riediger, Daniel Bildhauer, Hannes Schwarz, Audris Kalnins, Agris Sostaks, Edgars Celms, Michał Śmiałek, and Albert Ambroziewicz. Software casemeta-model definition. Project Deliverable D3.1, ReDSeeDS Project, 2007. www.redseeds.eu.
170. W N Robinson and H G Woo. Finding reusable UML sequence diagrams automatically. IEEE Software, 21(5):60-67, 2004.
171. C Rolland and C Ben Achour. Guiding the construction of textual use case specifications. Data & Knowledge Engineering, 25(1-2):125-160, March 1998.
172. C Rolland, C Souveyet, and C. Ben Achour. Guiding goal modeling using scenarios. IEEE Transactions on Software Engineering, 24(12):1055-1071, 1998.
173. Pascal Roques. UML in Practice: The Art of Modeling Software Systems Demonstrated through Worked Examples and Solutions. John Wiley & Sons, 2004.
174. Dough Rosenberg and Kendall Scott. Use Case Driven Object Modeling with UML. Addison Wesley, 1999.
175. Dough Rosenberg, Matt Stephens, and Mark Collins-Cope. Agile Development with ICONIX Process: People, Process, and Pragmatism. APress, 2005.
176. Marcus A Rothenberger, Kevin J Dooley, Uday R Kulkarni, and Nader Nada. Strategies for software reuse: a principal component analysis of reuse practices. IEEE Transactions on Software Engineering, 29(9):825-837, September 2003.
177. J Rumbaugh, M Blaha, W Pemerlani, F Eddy, and W Lorensen. Object-Oriented Modeling and Design. Prentice Hall, Englewood Cliffs, 1991.
178. J Rumbaugh, I Jacobson, and G Booch. The Unified Modelling Language Reference Guide. Addison-Wesley, Menlo Park, 1999.
179. Motoshi Saeki. Patterns and aspects for use cases: reuse techniques for use case descriptions. In 4th International Conference on Requirements Engineering, page 62, 2000.
180. M Sasikumar. Case-based reasoning for software reuse. In Knowledge Based Computer Systems - Research and Applications (International Conference on Knowledge-Based Computer Systems), pages 31-42, London, 1996. Narosa Publishing House.
181. Douglas C Schmidt. Why software reuse has failed and how to make it work for you. C++ Report, 11(1), January 1999.
182. Geri Schneider and Jason P Winters. Applying Use Cases: A Practical Guide, Second Edition. Addison-Wesley, 2001.
183. A Schuerr. PROGRES: A VHL-language based on graph grammars. Lecture Notes in Computer Science, 532:641-659, 1991.
184. SEI. Capability Maturity Model: Guidelines for Improving the Software Process. Addison-Wesley, 1995. Software Engineering Institute, Carnegie Mellon University.
185. Richard W Selby. Enabling reuse-based software development of large-scale systems. IEEE Transactions on Software Engineering, 31(6):495-510, June 2005.
186. Anthony J H Simons. Use cases considered harmful. In Proceedings of the 29th Conference on Technology of Object-Oriented Languages and Systems-TOOLS Europe'99, pages 194-203, Nancy, France, June 1999. IEEE Computer Society Press.
187. Michał Śmiałek. Discovery - third generation OOA&D method: Case study with proposition of notation and process. Master's thesis, University of Sheffield, Department of Computer Science, 1996.
188. Michał Śmiałek. Global reuse strategy based on use cases. In OOPSLA 2000 Companion, Conference on Object-Oriented Programming, Systems, Languages and Applications, pages 49-50, Minneapolis, 2000.
189. Michał Śmiałek. Accommodating informality with necessary precision in use case scenarios. Journal of Object Technology, 4(6):59-67, August 2005.
190. Michał Śmiałek. Can use cases drive software factories? In Workshop on Use Cases in Model-Driven Software Engineering (WUsCaM), 2005.
191. Michał Śmiałek. From user stories to code in one day? Lecture Notes in Computer Science, 3556:38-47, 2005.
192. Michał Śmiałek. Profile suite for model transformations on the computation independent level. Lecture Notes in Computer Science, 3297:264-268, 2005.
193. Michał Śmiałek. Zrozumieć UML 2.0. Metody modelowania obiektowego. Helion, 2005.
194. Michał Śmiałek. Mechanisms for requirements based model reuse. In International Workshop on Model Reuse Strategies - MoRSe, pages 17-20, 2006.
195. Michał Śmiałek and Łukasz Balcerek. Knowledge-based content management system application design methodology. Technical report, ICONS Project, 2003. Document D25.
196. Michał Śmiałek, Jacek Bojarski, Wiktor Nowakowski, and Tomasz Straszak. Scenario construction tool based on extended UML metamodel. Lecture Notes in Computer Science, 3713:414-429, 2005.
197. Michał Śmiałek, Jacek Bojarski, Wiktor Nowakowski, and Tomasz Straszak. Writing coherent user stories with tool support. Lecture Notes in Computer Science, 3556:247-250, 2005.
198. Michał Śmiałek and Andrzej Kardas. Model management based on a visual transformation language. In Krzysztof Zielinski and Tomasz Szmuc, editors, Software engineering - evolution and emerging technologies, pages 341-352. IOS Press, 2005.
199. Michał Śmiałek, Markus Nick, Audris Kalnins, Juergen Falb, and Rob Pooley, editors. International Workshop on Model Reuse Strategies - MoRSe. Fraunhofer IRB, 2006.
200. Stepháne S Somé. Beyond scenarios: Generating state models from use cases. In Scenarios and state machines: models, algorithms and tools - ICSE 2002 Workshop, Orlando. Florida, 2002.
201. Andreas Speck, Elke Pulvermller, Ragnhild Van Der Straeten, Ralf H Reussner, and Matthias Clauss. Model-based software reuse. Lecture Notes in Computer Science, 2548:135-146, 2002.
202. Kazimierz Subieta. Teoria i konstrukcja obiektowych języków zapytań (Theory and construction of object query languages). Wydawnictwo PJWSTK, 2004.
203. A G Sutcliffe, N A M Maiden, S Minocha, and D Manuel. Supporting scenario-based requirements engineering. IEEE Transactions on Software Engineering, 24(12):1072-1088, December 1998.
204. Alistair Sutcliffe and Neil Maiden. The domain theory for requirements engineering. IEEE Transactions on Software Engineering, 24(3):174-196, 1998.
205. SysML Partners. Systems Modeling Language (SysML) Specification, version 0.9, 2005.
206. Robert Szmurło and Michał Śmiałek. Teaching software modeling in a simulated project environment. Lecture Notes in Computer Science, 4364:301-310, 2007.
207. G Taentzer. AGG: A graph transformation environment for modeling and validation of software. Lecture Notes in Computer Science, 3062:446-453, 2004.
208. Carsten Tautz and Klaus-Dieter Althoff. Using case-based reasoning for reusing software knowledge. Lecture Notes in Computer Science, 1266:156-165, 1997.
209. Dave Thomas. MDA: Revenge of the modelers or UML utopia? IEEE Software, 21(3):22-24, 2004.
210. Juha-Pekka Tolvanen. Domain-specific modeling: No one size fits all. Lecture Notes in Computer Science, 3713:279, 2005.
211. University of Paderborn. Fujaba: From UML to Java and back again, 2005. http://www.fujaba.de/.
212. Klaas G van den Berg and Anthony J H Simons. Control flow semantics of use cases in UML. Information and Software Technology, 41(10):651-659, 1999.
213. A van Deursen, J Heering, and P Klint, editors. Algebraic Specification. ACM Press, 1996.
214. Han van Loon. Process Assessment and ISO/IEC 15504 Reference Book. Kluwer International Series in Engineering & Computer Science. Springer, 2004.
215. J van Wijngaarden and E Visser. Program transformation mechanics. A classification of mechanisms for program transformation with a survey of existing transformation systems. Technical Report UU-CS-2003-048, Institute of Information and Computing Sciences, Utrecht University, 2003. Technical report.
216. E Visser. Stratego: a language for program transformation based on rewriting strategies. Lecture Notes in Computer Science, 2051:357-361, 2001.
217. E Visser. Dagstuhl workshop on trees vs. graphs. In Transformation Techniques in Software Engineering, 2005. Dagstuhl Seminar No. 05161.
218. W3C Web Services Architecture Working Group. XSL Transformations (XSLT), Version 1.0, 1999. W3C Recommendation.
219. K Watahiki and M Saeki. Scenario patterns based on case grammar approach. In 5th IEEE International Symposium on Requirements Engineering, pages 300-301, 2001.
220. K Weidenhaupt, K Pohl, M Jarke, and P Haumer. Scenarios in system development: current practice. IEEE Software, 15(2):34-45, 1998.
221. D Weiss and C T R Lai. Software Product-Line Engineering. Addison-Wesley, 1999.
222. C A Welty and D A Ferrucci. A formal ontology for reuse of software architecture documents. In 14th IEEE International Conference on Automated Software Engineering, pages 259-262, 1999.
223. Jon Whittle. Specifying precise use cases with use case charts. In MoDELS'05 Workshop on Use Cases in Model Driven Software Engineering, 2005.
224. Keith Williamson and Michael Healy. Deriving engineering software from requirements. Journal of Intelligent Manufacturing, 11(1):3-28, 2000.
225. R J Wirfs-Brock and R E Johnson. A survey on current research in object-oriented design. Communications of the ACM, 33(9):104-124, 1990.
226. R J Wirfs-Brock and B Wilkerson. Object-orientred design: A responsibility driven approach. In OOPSLA'89 Proceedings, pages 71-75, 1989.
227. H G Woo and W N Robinson. Reuse of scenario specifications using an automated relational learner: a lightweight approach. In Proceedings of IEEE Joint International Conference on Requirements Engineering, pages 173-180, 2002.
228. Yunwen Ye and Gerhard Fischer. Supporting reuse by delivering task-relevant and personalized information. In ICSE'02: Proceedings of the 24th International Conference on Software Engineering, pages 513-523, New York, NY, USA, 2002. ACM Press.
229. Chen Yonghao and Betty H C Cheng. Facilitating an automated approach to architecture-based software reuse. In 12th IEEE International Conference on Automated Software Engineering, pages 238-245, 1997.
230. Albert Zündorf. Fujaba as a QVT language for MDA. In Transformation Techniques in Software Engineering, 2005. Dagstuhl Seminar No. 05161.

Typ dokumentu

Bibliografia

Identyfikator YADDA

bwmeta1.element.baztech-article-PWA5-0020-0007