Advertisement

Automated Generation of Implementation from Textual System Requirements

  • Jan Franců
  • Petr Hnětynka
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4980)

Abstract

An initial stage of a software development is a specification of the system requirements. Frequently, these requirements are expressed in UML and consist of use cases and a 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 an executable code directly from the use cases written in a natural language. Use 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.

Keywords

Use cases code generation requirement engineering natural language 

References

  1. 1.
  2. 2.
    Cockburn, A.: Writing Effective Use Cases, 1st edn. Addison-Wesley, Reading (2000)Google Scholar
  3. 3.
    Drazan, J., Mencl, V.: Improved Processing of Textual Use Cases: Deriving Behavior Specifications. In: van Leeuwen, J., Italiano, G.F., van der Hoek, W., Meinel, C., Sack, H., Plášil, F. (eds.) SOFSEM 2007. LNCS, vol. 4362, pp. 856–868. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  4. 4.
    Engels, G.: UML collaboration diagrams and their transformation to java. In: France, R.B. (ed.) UML 1999. LNCS, vol. 1723, pp. 473–488. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  5. 5.
    Fiedler, M., Francu, J., Mencl, V., Ondrusek, J., Plsek, A.: Procasor Environment: Interactive Environment for Requirement Specification, http://dsrg.mff.cuni.cz/~mencl/procasor-env
  6. 6.
    Larman, C.: Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, 2nd edn. Prentice Hall PTR, Upper Saddle River (2001)Google Scholar
  7. 7.
    Mencl, V.: Deriving Behavior Specifications from Textual Use Cases. In: Proc. of WITSE 2004, Linz, Austria (September 2004)Google Scholar
  8. 8.
    OMG: Model Driven Architecture (MDA), OMG document ormsc/01-07-01 (July 2001)Google Scholar
  9. 9.
    Plasil, F., Mencl, V.: Getting ”Whole Picture” Behavior in a Use Case Model. In: Proceedings of IDPT, Austin, Texas, U.S.A. (December 2003)Google Scholar
  10. 10.
    Plasil, F., Visnovsky, S.: Behavior Protocols for Software Components. IEEE Transactions on Software Engineering 28(11) (November 2002)Google Scholar
  11. 11.
  12. 12.
    Quan, L., Zhiming, L., Xiaoshan, L., Jifeng, H.: Consistent Code Generation from UML Models, UNU-IIST Rep. No. 319, The United Nations University (April 2005)Google Scholar
  13. 13.
    Somé, S.S.: Supporting Use Cases based Requirements Engineering. Information and Software Technology 48(1), 43–58 (2006)CrossRefGoogle Scholar

Copyright information

© IFIP International Federation for Information Processing 2011

Authors and Affiliations

  • Jan Franců
    • 1
  • Petr Hnětynka
    • 1
  1. 1.Department of Distributed and Dependable Systems Faculty of Mathematics and PhysicsCharles University in PraguePrague 1Czech Republic

Personalised recommendations