1 / 27

Presentation 3

Konza Prairie Long-Term Ecological Research ( LTER ) Henry Mikhail. Presentation 3. Outline. Action Items Component Design Formal Specification Testing Evaluation Project Evaluation Future Work Demo Questions and/or comments. Action items. Ontology Visualization

heaton
Télécharger la présentation

Presentation 3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Konza Prairie Long-Term Ecological Research (LTER) Henry Mikhail Presentation 3

  2. Outline • Action Items • Component Design • Formal Specification • Testing Evaluation • Project Evaluation • Future Work • Demo • Questions and/or comments

  3. Action items • Ontology Visualization • Change the ontology layout; when a user clicks on a concept view related criteria in an new interactive window instead of a dropdown list. • Add functionality to create dynamically JSON file for the new interactive layout of the criteria.

  4. Component design Changed component names. Added one more operation to the ontology Component (an operation That created dynamically a JSON file).

  5. Formal specification -- $ProjectHeader: use 0.393 Wed, 16 May 2007 14:10:28 +0200 opti $ model Konza -- classes class Get Data operations getTableName(concept: String , criteria: String) : String get Data( table Name: String) : Set(String) createCSVFile( data: Set(String)) : Boolean get Criteria(concept: String) : Set(String) end

  6. Formal Specs - continue constraints context GetData::getTableName(concept : String , criteria : String) : String pre validParams: concept > ' ' post validTable: criteria > ' ' context GetData::getData(tableName : String) : Set(String) pre : tableName > ' ' post : result-> size > 0 context GetData::createCSVFile(data: Set(String)) : Boolean pre : data->size > 0 post : result = true context getCriteria (concept: String) : Set(String) pre : concept > ' ' post : result->size > 0

  7. Formal Specs - continue context GetData::createJSONFile(concept: String, criteria : Set(String)) pre : concept > ' ' pre : criteria->size > 0 pre : criteria->forAll(c:String | c > ' ')

  8. Testing evaluation • Use cases • Interactivity and navigability • Data retrieval performance • User Interface performance

  9. Testing evaluation - continue Use Cases Tests were performed to verify that use cases were working as expected. I tried to test some of the concepts and their related Criteria. Unit testing was performed using assertion to verify the correctness of the java methods. Interactivity and navigability Actions that occur upon mouse clicks on a concept or criteria. Considering some of the limitations of this visual library. Possible action in every state of the navigation.

  10. Testing evaluation - continue • Data Retrieval Performance • Several data retrieval performance tests have been done to • evaluate the response time of the application. • It’s is clear that the amount of data, in terms of number of • columns and rows retrieved. I will list the tests that have been • done and analyze the results.

  11. Testing evaluation - continue Test cases  Number of rows: ~ 256 K Time: 5 seconds Number of rows: ~ 512 K Time: 8 seconds Number of rows: ~ 767 K Time: 10 seconds Number of rows: ~ 1Million Time: 13 seconds Number of rows: ~ 1.28 Million Time: 15 seconds Number of rows: ~ 1.5 Million Time: 20 seconds Number of rows: ~ 2 Million Time: 23 seconds

  12. Interface performance I performed several tests regarding this concept and I found out the maximum number of elements has to do with the location the distribution of the elements in the ontology branches. My final conclusion is that the maximum number should not be greater than 75 elements.

  13. Interface performance – cont (65)

  14. Interface performance – cont (75)

  15. Interface performance – cont (75 L1)

  16. Interface performance – cont (85)

  17. Interface performance – cont Time required for the layout to stabilize Tests 40 elements  4 seconds 55 elements  4 seconds 65 elements  5 seconds 75 elements  7 seconds 85 elements  8 seconds

  18. Test plan • Use cases • View ontology: Navigate to the url of the web page that shows the Konza ontology. • Search Data: Click on an ontology concept to test the search web page. Perform several test cases. • Download data: Attempt to download data files and save them locally.

  19. Project evaluation • Estimates • Project Duration

  20. Project evaluation - cont • Time spent in each phase

  21. Project evaluation - cont • Phase 1

  22. Project evaluation - cont • Phase 2

  23. Project evaluation - cont • Phase 3

  24. Project evaluation - cont • Lessons Learned • Ontology creation requires lots of understanding of the domain. • Data visualization and JavaScript. • Dynamic creation of JSON files for data visualization. • Data import and format ( data cleaning).

  25. Future work There are lots of aspects that can be expanded in the project; the data retrieval process can be improved by having access to real-time data instead of downloading data files and loading them into a different database.

  26. demo

  27. Questions/comments

More Related