Automated code generation from system requirements in natural language

• Autorzy: Francu J. , Hnětynka P.
• Języki publikacji: EN

Abstrakty

EN

An initial stage of a software development is specification of the system requirements. Typically, these requirements are expressed in UML and consist of use cases and domain model. A use case is a sequence of tasks, which have to be performed to achieve a specific goal. The tasks of the use case are written in a natural language. The domain model describes objects used in the use cases. In this paper, we present an approach that allows automated generation of executable code directly from the use cases written in a natural language. Usage of the generation significantly accelerates the system development, e.g. it makes immediate verification of requirements completeness possible and the generated code can be used as a starting point for the final implementation. A prototype implementation of the approach is also described in the paper.

Słowa kluczowe

EN

code generation; domain model

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2009
• Tom: Vol. 3, nr 1
• Strony: 73--88
• Opis fizyczny: Bibliogr. 17 poz.

Twórcy

autor

Francu J.

autor

Hnětynka P.

• Faculty of Mathematics and Physics, Department of Software Engineering, Charles University in Prague

Bibliografia

• [1] B. Anda and D. I. Sjober. Investigating the role of use cases in the construction of class diagrams. Empirical Software Engineering, Volume 10(3), Jul. 2005.
• [2] AndroMDA. http://galaxy.andromda.org.
• [3] A. Cockburn. Writing Effective Use Cases. Addison-Wesley, Jan. 2000.
• [4] J. Drazan and V. Mencl. Improved processing of textual use cases: Deriving behavior specifications. In Proceedings of SOFSEM 2007, Harrachov, Czech Republic, Jan. 2007.
• [5] G. Engels, R. Huecking, S. Sauer, and A. Wagner. UML collaboration diagrams and their transformation to Java. In Proceedings of UML ’99, Fort Collins, USA, Oct. 1999.
• [6] M. Fiedler, J. Francu, V. Mencl, J. Ondrusek, and A. Plsek. Procasor environment: Interactive environment for requirement specification. http://dsrg.mff.cuni.cz/~mencl/procasor-env.
• [7] JBoss application server. http://jboss.org.
• [8] C. Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process. Prentice Hall PTR, 2nd edition, 2001.
• [9] V. Mencl. Deriving behavior specifications from textual use cases. In Proceedings of WITSE ’04, Linz, Austria, Sep. 2004.
• [10] Objecteering software. Objecteering 6. http://www.objecteering.com.
• [11] OMG. Model driven architecture (MDA). OMG document ormsc/01-07-01, Jul. 2001.
• [12] openArchitectureWare.http://www.openarchitectureware.org.
• [13] F. Plasil and V. Mencl. Getting “whole picture” behavior in a use case model. In Proceedings of IDPT, Austin, Texas, USA, Dec. 2003.
• [14] F. Plasil and S. Visnovsky. Behavior protocols for software components. IEEE Transactions on Software Engineering, Volume 28(11), Nov.2002.
• [15] L. Quan, L. Zhiming, L. Xiaoshan, and H. Jifeng. Consistent code generation from UML models. UNU-IIST Rep. No. 319, The United Nations University, Apr. 2005.
• [16] S. S. Somé. Supporting use cases based requirements engineering. Information and Software Technology, 48(11):43–58, 2006.
• [17] Sun Microsystems. Core J2EE patterns: Best practices and design strategies. http://java.sun.com/blueprints/corej2eepatterns.