1. Natural Language to Machine Readable Format By: Damian Tamayo Presentation 2 – Nov. 13, 2009 CIS 895 – MSE Project

2. Outline  Flow Diagram  Action Items  Architectural Design  Test Plan  Formal Inspection Checklist  Project Plan  Prototype Demonstration  Questions / Comments

3. NLP Flow Diagram

4. Program Parts  NLP Program  User input into the system  OpenNLP Server  POS tagger  StanfordNLP Server  POS tagger  PPOS Server  Source of user defined POS sentences  PPOS Client  Program to manually define the POS for sentences

5. PPOS Flow Diagram

6. PPOS Parts  PPOS Client  Create manually tagged sentences  Save manually tagged sentences  PPOS Maintenance  View Parse list  Delete parses  Resave Parses

7. Action Items  Formal Specification  USE program

8. Architectural Design/Class Diagram  http://cis.ksu.edu/~dtamayo/Class_Diagra m_Expanded.html http://cis.ksu.edu/~dtamayo/Class_Diagra m_Expanded.html http://cis.ksu.edu/~dtamayo/Class_Diagra m_Expanded.html  http://cis.ksu.edu/~dtamayo/Class_Diagra m_Collapsed.html http://cis.ksu.edu/~dtamayo/Class_Diagra m_Collapsed.html http://cis.ksu.edu/~dtamayo/Class_Diagra m_Collapsed.html

9. Overview

10. Sequence Diagram

11. TagSet   http://bulba.sdsu.edu/jeanette/thesis/Penn Tags.html http://bulba.sdsu.edu/jeanette/thesis/Penn Tags.html

12. Examples Tic-Tac-Toe is a game. Three squares by Three squares composes the game board in which you play Tic-Tac-Toe. There are two players in this game. One Player chooses the X token while the other player gets the O token. Player X draws a grid of 6 empty squares in the formation of 3 rows and 3 columns. The first move is made by Player X. Player X and Player O take turns until the game is over. A turn is placing an X or O on an empty square. The game is over when all nine squares are filled or one player has three of their mark in a horizontal, vertical, or diagonal row. Player X puts his token in the top left corner. Player O puts his token in the middle left. Player X puts his token in the center. Player O puts his token in the bottom left corner. Player X puts his token in the bottom right corner.

22. Formal Specification  USE Version 2.4.0  http://www.db.informatik.uni- bremen.de/projects/USE/#download http://www.db.informatik.uni- bremen.de/projects/USE/#download http://www.db.informatik.uni- bremen.de/projects/USE/#download  Models all classes  Models all necessary methods and calls  Specification can be found at:  Appended to the end of Architectural Design document

23. Test Plan

24. Program will be tested by developer and two fellow graduate students: Michael Marlen Jack Hart

25. Inspection Checklist Action ItemInspection ItemP/F/PartialComments 1Class diagrams use UML standard symbols 2Class diagram is clear 3Sequence Diagram uses UML standard symbols 3Sequence and class diagrams match 4OCL model represents class diagram 5Architecture Design Document meets requirements

26. Milestones  Presentation 1  October 12, 2009  PPOS Client/Server  Internal Rep  Presentation 2  November 13, 2009  Presentation 3  Bug fixes  Logical Support  Dec 7, 2009  Complete by December 10, 2009

27. Gantt Chart

28. Prototype  NLP_Program  Tic Tac Toe Sentences  POViz tab  Shows structure of sentence  PPOS_Client  Manually tag a sentence  Save  Maintenance

29. Phase 3 Deliverables  Action Items  User Manual  Component Design  Source Code  Assessment Evaluations  Project Evaluation  References  Formal Technical Inspection Letters

30. To Do  Work on Deliverables  Revise Documents as needed