KDD- Service based Numerical Entity Searcher (KSNES) Presentation 2 on March 31 st, Naga Sowjanya Karumuri. CIS 895 MSE PROJECT

Transcription

1 KDD- Service based Numerical Entity Searcher (KSNES) Presentation 2 on March 31 st, 2009 Naga Sowjanya Karumuri sowji@ksu.edu 1 CIS 895 MSE PROJECT

2 OUTLINE Project Data Flow Diagram Action Items Architectural Design Test Plan Formal Inspection Checklist Project Plan Prototype Demonstration Questions / Comments 2

3 PROJECT DATA FLOW DIAGRAM: NUMERICAL ENTITY SEARCHER 3

4 MODULES IN THE PROJECT Webpage (JSP): For requesting and receiving information from the service. POS Tagger (Java): Stanford POS Tagger Numerical Phrase Extractor (Java): Implemented using Shallow Parsing Technique Number-Unit/Date Pattern Recognizer (C++): Implemented based on the Numerical Quantifier developed by Benjamin Sapp, UIUC. 4

5 ACTION ITEMS Implemented Numerical Phrase Extractor Detailed Description of Test Plan Wrote Formal Specification using USE UML Representation of the System 5

6 ARCHITECTURAL DESIGN Service Oriented Architecture 6

7 PACKAGE VIEW Overall Package View Class Descriptions, Attributes and Operations are contained in Architecture Design Document 7

8 SEQUENCE DIAGRAM 8

9 CLASS DIAGRAM(NPE PACKAGE) 9

10 CLASS DIAGRAM(NDPR PACKAGE) 10

11 IMPLEMENTING NUMERICAL PHRASE EXTRACTOR Input: Tagged Text I/PRP lost/vbd thirty-three/jj dollars/nns in/in 1998/CD Regular Expressions are used to determine the numerical patterns in the input. thirty-three/jj dollars/nns in/in 1998/CD Output: Numerical Phrases thirty-three dollars in

12 TAGSET 12

13 SOME PATTERNS "\\d+-\\d+(/jj /CD) [a-za-z]+/nn" parses \\d+-\\d+(/jj /CD) 3-2/JJ 20-20/JJ [a-za-z]+/nn lead/nn match/nn "(between Between from From In in since Since during During)/IN.../CD (([a-za- Z]+/CC [a-z]+/to).../cd)? parses 'between 1987 and 1997', 'in 2007 and

14 ASSIGNING BOUNDS Words that will be detected so as to set the bounds like >, <, ~, = = is used if no words are mentioned Bound Corresponding words > more than, no less than, no fewer than, at most, over < up to, not over, no more than, at least, less than, not over than ~ about, around, approximately, some, nearly, almost, 14

15 SOME PATTERNS [a-za-z0-9]+/cd( percent/nn)?( out/in)? of/in( the/dt)? ( [a-za-z]+/cd)?( [a-za-z]+/jj)? [a-za- Z]+(/NN /NNS /NNP) one of the five people two of the groups one of the rare cases 89 percent of people parses five of the seven former employees 3 out of 5 people 15

16 PHRASES THAT CAN BE PARSED Numerical Phrases 27 year-old boy A 3-2 lead 9 in 10 people About 100 miles per hour 200 adults and children $3 million About two-thirds of the vote The 17-mile drive Less than 10% support Six-bedroom apartment ml 10:00 a.m. CST From 400 to 500 miles Temporal Phrases Last year Next week Monday Sunday January December Mid-1990s Between 1999 and th centaury 18 April 2008 Dec 21, 2009 October 10 th 1984 John, 67 Since

17 PHRASES THAT ARE NOT CURRENTLY PARSED Numerical Phrases Temporal Phrases six-pack of drinks 31 st of March 1998 $100 more Since mid-november 252 (as POS can t parse this) the January-April period Future Work: These phrases can also be parsed by adding more patterns to the current system but for now the most important and commonly occurring patterns are considered. Current goal is to develop a basic idea of numerical phrase extraction. 17

18 FORMAL SPECIFICATION Created and validated using USE All Classes are specified All important attributes and methods are specified Constructor methods are not specified Contained at the end of the Architectural Design Document 18

19 TEST PLAN Outputs are checked at each module by the developer by matching them to the results manually calculated Check if the POS tagger has given the tagged text. Check if the numerical phrases are extracted Check if the numerical phrase is explained to Value, Unit and Unit-Type. UML diagrams and the required specifications will be checked for consistency by two fellow MSE students User interaction will be tested by the developer and the technical inspectors. 19

20 FORMAL INSPECTION CHECKLIST The following items are to be checked: The symbols used in the class diagram conform to UML standards The symbols used in the sequence diagrams conform to UML standards The classes in the class diagrams have corresponding descriptions provided in the Architecture Document The descriptions of the classes in the Architecture Document are clear and concise The classes in the USE model are consistent with those in the Architecture Document All the requirements in the Software Requirements Specification have been covered in the Architecture Document The multiplicities in the USE model have been depicted in the class diagram 20

21 PROJECT SCHEDULE Key Dates Presentation 1: February 24 th, 2009 Complete Numerical Sub-Chunker Presentation 2: March 31 st, 2009 Complete Numerical Phrase Extractor Presentation 3: April 10 th, 2009 Patch up the modules Develop a GUI Set them up on the server To completely submit the documents by April 13 th, 2009 to the committee Final Portfolio submitted by April 15 th,

22 PROJECT SCHEDULE 22

23 PROTOTYPE DEMONSTRATION POS Tagger working For now it works on the local machine Numerical Pattern Extractor For now it works on the local machine 23

24 PHASE 3 DELIVERABLES Action items Component Design Assessment Evaluation Project Evaluation User s Manual Formal Technical Inspection Checklists Presentation 3 Executable Project Source Code 24

25 TO-DO LIST Revise the Documents Revise Project Schedule Work on the Phase3 deliverables Final Demo 25

26 Questions?? Suggestions!! THANK YOU 26