PhDOOS Logo

Supported by AITO.

These pages are currently maintained by Alex Potanin

 

Automatically Generating Object Models from Natural Language Analysis

Hector G. Perez-Gonzalez
( Mexican )

University Of Colorado at Colorado Springs
5020 El Camino Dr. B-13 Colorado Springs 80918, Colorado, USA
tel: (719) 5484958
fax:
hectorgerardo@acm.org

Keywords:

analysis/design software engineering Object Oriented education

Abstract:

The goal is to enable rapid production of static and dynamic object models from natural language description of problems. Rapid modeling is achieved through automation of analysis tasks. This automation captures the cognitive schemes analysts use to build their models of the world through the use of a precise methodology. The methodology is based on the use of proposed technique called role posets. and a semi-natural language (called 4W). Original problem statements are automatically translated to 4W language. The produced sentences then, are analyzed with role posets to produce static model views. Finally the 4W sentences are used to generate dynamic views of the problem. This set of methods maximizes analysis process agility, promotes reusability and constitutes a valuable tool in the learning process of object thinking.

The purpose of this methodology is to promote rapid software development, reusability, and support memorable experiences in "object oriented thinking" and it is mainly supported by the use of automated tools. The general steps are as follows:

Step 1. Analysts obtain a set of describing requirement documents coming from stakeholders of different kinds. (several documents from final users, several from different clients, etc.)

Step 2. The name of the problem, problem domain's (PD) name and possible sub-domains are declared. Here is an example of one such simple requirements document: Problem Domain: "Operating systems" Sub-domain: "Concurrent programming" Problem name: "Dinning philosophers simulation" Problem Description: There are 5 philosophers and 5 forks around a circular table. Each philosopher can take 2 forks on either side of him. Each fork may be either on the table or used by one philosopher. A philosopher must take 2 forks to eat.

Step 3. Each one of the documents is processed using an automatic tool considering associations between documents with the same kind of authors (users, clients, managers, etc). The tool produces design view diagrams (class, objects, sequence and activity diagrams) that are validated by the user.

Step 4. Any participant, stakeholder or mainly any student of object oriented (OO) design may modify, delete or add new sentences to any requirement text to identify the consequences in real time and produce a memorable learning experience.

Step 5. Produced information is stored associated with the declared problem domain in order to promote reusability. The proposed techniques produce OO static and dynamic model views of the problem in Unified Modeling language (UML).

The PhD work started: July, 2002

NO HTML3
JAVA

 

Last modified on Mon Aug 15 14:59:24 2005