Translation of use case scenarios to Java code

• Autorzy: Śmiałek M. , Jarzębowski N. , Nowakowski W.
• Języki publikacji: EN

Abstrakty

EN

Use cases are usually treated as second class citizens in the software development chain based on models. Their textual descriptions (scenarios) are treated as informal input to more formal design models that can then be (semi-)automatically transformed down to code. In this paper we will show that use case scenarios can gain precise metamodel-based notation and semantics enabling automatic processing. What is more, we will show transformation algorithms that can transform use case scenarios directly to dynamic code in Java. The presented transformation can generate the full structure of the system following the MVP architectural pattern, including complete method contents for the application logic (Presenter) and presentation (View) layers. It also provides a code skeleton for the domain logic (Model) layer. The use case notation and the transformation were implemented within a sophisticated tool suite. Based on this, the paper discusses the evaluation efforts based on a case study.

Słowa kluczowe

EN

use cases; runtime semantics; model transformation

• Wydawca: Wydawnictwa AGH
• Czasopismo: Computer Science
• Rocznik: 2012
• Tom: Vol. 13 (4)
• Strony: 35--52
• Opis fizyczny: Bibliogr. 24 poz., rys.

Twórcy

autor

Śmiałek M.

• Warsaw University of Technology, Warsaw, Poland

autor

Jarzębowski N.

• Warsaw University of Technology, Warsaw, Poland

autor

Nowakowski W.

• Warsaw University of Technology, Warsaw, Poland

Bibliografia

• [1] de Castro V., Marcos E., Vara J. M.: Applying CIM-to-PIM model transformations for the service-oriented development of information systems. Information and Software Technology, 53:87–105, 2011.
• [2] di Lucca G., Fasolino A., de Carlini U.: Recovering use case models from objectoriented code: a thread-based approach. In Proc. 7th Working Conf. on Reverse Engineering, pp. 108–117. IEEE, 2000.
• [3] Ding Z., Jiang M., Palsberg J.: From textual use cases to service komponent models. In Proc. 3rd Int. Workshop on Principles of Engineering Service-Oriented Systems, pp. 8–14. ACM, 2011.
• [4] Fellbaum C., editor. WordNet: An Electronic Lexical Database. MIT Press, 1998.
• [5] Francu J., Hnetynka P.: Automated generation of implementation from textual system requirements. In Software Engineering Techniques, volume 4980 of Lecture Notes in Computer Science, pp. 34–47. Springer; Berlin / Heidelberg, 2011. 50 Michał Smiałek, Norbert Jarzebowski, Wiktor Nowakowski
• [6] Grechanik M., McKinley K. S., Perry D. E.: Recovering and using use-casediagram- to-source-code traceability links. In Proc. 6th Joint Meeting European Software Eng. Conf. and ACM SIGSOFT Symp. on Foundations of Software Eng., pp. 95–104, 2007.
• [7] Hirschfeld R., Perscheid M., Haupt M.: Explicit use-case representation in objectoriented programming languages. In Proc. 7th Symp. on Dynamic Languages, pp. 51–60. ACM, 2011.
• [8] Kaindl H., Smiałek M., Wagner P., Svetinovic D., Ambroziewicz A., Bojarski J., Nowakowski W., Straszak T., Schwarz H., Bildhauer D., Brogan J.P., Mukasa K. S., Wolter K., Krebs T.: Requirements specification language definition. Project Deliverable D2.4.2, ReDSeeDS Project, 2009. www.redseeds.eu.
• [9] Kalnins A., Barzdins J., Celms E.: Model transformation language MOLA. Lecture Notes in Computer Science, 3599:14–28, 2004. Proc. of MDAFA’04.
• [10] Kamalrudin M., Hosking J., Grundy J.: Improving requirements quality Rusing essential use case interaction patterns. In Proc. 33rd International Conference on Software Engineering, pp. 531–540. IEEE, 2011.
• [11] Kleppe A.: Software Language Engineering: Creating Domain-Specific Languages Using Metamodels. Addison-Wesley Professional, 2008.
• [12] Kleppe A. G., Warmer J. B., Wim B.: MDA Explained, The Model Driven Architecture: Practice and Promise. Addison-Wesley, Boston, 2003.
• [13] Object Management Group. Meta Object Facility Core Specification, version 2.0, formal/2006-01-01, 2006.
• [14] Phalp K. T., Vincent J., Cox K.: Improving the quality of use case descriptions: empirical assessment of writing guidelines. Software Quality Journal, 15:383–399, 2007.
• [15] Potel M.: Mvp: Model-view-presenter the taligent programming model for C++ and java. Technical Report, Taligent Inc., 1996.
• [16] Qin T., Zhang L., Zhou Z., Hao D., Sun J.: Discovering use cases from source code Rusing the branch-reserving call graph. In Proc. 10th Asia-Pacific Software Eng. Conf., pp. 60–67. IEEE, 2003.
• [17] Sarkar S., Sharma V. S., Agarwal R.: Creating design from requirements and use cases: bridging the gap between requirement and detailed design. In Proc. 5th India Software Engineering Conference, pp. 3–12. ACM, 2012.
• [18] Simons A. J. H.: Use cases considered harmful. In Proc. of the 29th Conference on Technology of Object-Oriented Languages and Systems-TOOLS Europe’99, pp. 194–203, Nancy, France, June 1999. IEEE Computer Society Press.
• [19] Smiałek M.: Software Development with Reusable Requirements-Based Cases. Publishing House of the Warsaw University of Technology, 2007.
• [20] Smiałek M.: Requirements-level programming for rapid software evolution. In J. Barzdins, M. Kirikova, eds., Databases and Information Systems VI, chapter 3, pp. 37–51. IOS Press, 2011. Translation of use case scenarios to Java code 51
• [21] Smiałek M., Bojarski J., Nowakowski W., Ambroziewicz A., Straszak T.: Complementary use case scenario representations based on domain vocabularies. Lecture Notes in Computer Science, 4735:544–558, 2007. Proc. of MODELS’07.
• [22] Smiałek M., Kalnins A., Ambroziewicz A., Straszak T.,Wolter K.: Comprehensive system for systematic case-driven software reuse. Lecture Notes in Komputer Science, 5901:697–708, 2010. Proc. of SOFSEM’10.
• [23] Simko V., Hnetynka P., Bures T.: From textual use-cases to component-based applications. Studies in Computational Intelligence, 295:23–37, 2010.
• [24] Yue T., Briand L. C., Labiche Y.: A systematic review of transformation approaches between user requirements and analysis models. Requirements Engineering, 16(2):75–99, 2011.