Automatic Transition of Natural Language Software Requirements Specification into Formal Presentation

  • M. G. Ilieva
  • Olga Ormandjieva
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3513)


Software requirements specification is a critical activity of the software process, as errors at this stage inevitably lead to problems later on in system design and implementation. The requirements are written in natural language, with the potential for ambiguity, contradiction or misunderstanding, or simply an inability of developers to deal with a large amount of information. This paper proposes a methodology for the natural language processing of textual descriptions of the requirements of an unlimited natural language and their automatic mapping to the object-oriented analysis model.


Unify Modeling Language Semantic Network Automatic Transition Software Requirement Specification Natural Language Requirement 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Bryant, B.R.: Object-Oriented Natural Language Requirements Specification. In: 23rd Australian Computer Science Conference, 2000, ACSC 2000 (2000)Google Scholar
  2. 2.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. In: van Leeuwen, J. (ed.) Computer Science Today, Addison-Wesley, Reading 19983Google Scholar
  3. 3.
    John Lewis, J., Loftus, W.: Java Software Solutions – Foundations of Program Design, 4th edn. Addison-Wesley, Reading (2004) ISBN: 0-321-24583-0Google Scholar
  4. 4.
    Subramaniam, K., Liu, D., Far, B.H., Eberlein, A.: UCDA: Use Case Driven Development Assistant Tool for Class Model Generation. In: Proceeding of Sixteenth International Conference on Software Engineering and Knowledge Engineering (SEKE 2004), Banff, Canada (June 2004)Google Scholar
  5. 5.
    Kop, C., Mayr, H.C.: Mapping Functional Requirements: From Natural Language to Conceptual Schemata. In: Proc. 6th IASTED Int. Conference on Software Engineering and Applications (SEA 2002), Cambridge, USA (November 2002)Google Scholar
  6. 6.
    Lee, B.-S., Bryant, B.R.: Automated conversion from requirements documentation to an object-oriented formal specification language. In: SAC 2002, ACM, New York (2002)Google Scholar
  7. 7.
    Mencl, V.: Deriving Behavior Specifications from Textual Use Cases. In: Proceedings of Workshop on Intelligent Technologies for Software Engineering (WITSE 2004), Lenz, Austria, September 21, part of ASE 2004, pp. 331–341 (2004) ISBN 3-85403-180-7 Oesterreichische Computer GesellschaftGoogle Scholar
  8. 8.
    Moreno, A.M.: Object-oriented analysis from textual specifications. In: Proceedings of Ninth International Conference on Software Engineering and Knowledge Engineering, Madrid, Spain (1997)Google Scholar
  9. 9.
    Alagar, V.S., Ormandjieva, O., Liu, S.H., Shen, J.: Performance Assessment in Real-Time Reactive Systems. In: Proceedings of the Seventh IASTED International Conference on Software Engineering and Applications (SEA 2003), USA, November 3-5, pp. 714–722 (2003)Google Scholar
  10. 10.
    Alagar, V.S., Chen, M., Ormandjieva, O., Zheng, M.: Automated Test Generation from Object- Oriented Specifications of Real-Time Reactive Systems. In: Tenth Asia-Pacific Software Engineering Conference, Chiang Mai, Thailand, December 10-12 (2003)Google Scholar
  11. 11. – Discovering Business Processes 1 – The Digital Library – Example
  12. 12. – Domain Analysis – The object modeler looks for nouns, verbs and verb phrase

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • M. G. Ilieva
    • 1
  • Olga Ormandjieva
    • 1
  1. 1.Department of Computer Science and Software EngineeringConcordia UniversityMontrealCanada

Personalised recommendations