Konza PrairieKonza Prairie Long-Term Ecological Research (LTER)LTER Henry Mikhail

 Project Overview  Related work  Project Requirements  Project Plan  Cost Estimation  Software Quality assurance plan  Prototype Demonstration  Questions and/or comments

 Goal A.Create an ontology for Konza Prairie data Standards Extensible Complete B.Create a web-based application to navigate thru the ontology. C.Provide functionalities to search data files for ontology entities.  Motivation A.Need to share data with research groups and other personnel. B.Provide easy way to view a high level view of the Konza data ( web access) C.Navigate thru ontology concepts and relations to search data files for desired information.

CUAHSI-HIS (Hydrologic Information System) A.An effort to share hydrologic data(Only). B.It is internet-based C.Require client application installed locally. NeOn Project project that was focused on ontologies on the web and how they are related, and ways to exploit them. or relating different ontologies spread over different locations in a distributed network (networked ontologies) DataONE project Focused on creating a distributed framework that provides open, robust, and secure access to well described and easily discovered data.

 Create an ontology for the Konza Prairie data collected by researchers. Standards Customization Konza dataset AGW02 - Depth and Nutrient Content of Groundwater from Wells near Kings Creek. NO3( Nitrate Nitrogen ) NH4 ( Ammonium-nitrogen ) P04 ( Orthophosphate ) TN ( Total Nitrogen ) TP ( Total Phosphorus ) DOC ( Dissolved Organic Carbon )

Datasets share concepts, ontology helps define how data is related. AWE01: Meteorological data APT01 : Prairie Precipitation RECORD TYPE 1 (Hourly values) RECORD TYPE 1 ( By location) Temperature(Air) Precipitation Amount Relative Humidity Wind Velocity (Absolute) AST01: monitoring of soil temperature wind direction Soil temperature Solar radiation downward Max wind speed Precipitation amount Soil depth Burned(Y/N) Soil temperature

 Create a web application that visually shows the structure and concepts of the Konza ontology. Provide an easy way to find data (for non technical people). Available on the web Easy to use Interactive Easy to search for data

Effort and time estimates for this project Effort = 3.2*EAF (Size)^1.05 Time (in months) = 2.5(Effort)^0.38 Size The estimated number of thousands of lines of code EAF This parameter is based on the evaluation of 15 parameters The values for the above criteria to calculate the EAF are the following: Product attributes Required software reliability: 1.15 Size of application database: 1.08 Complexity of the product: 0.85

Hardware attributes Run-time performance constraints: 1.15 Memory constraints: 1 Volatility of the virtual machine environment: 0.87 Required turnabout time: 0.87 Personnel attributes Analyst capability: 1 Applications experience: 0.91 Software engineer capability: 1 Virtual machine experience: 1.10 Programming language experience: 0.95

Project attributes Application of software engineering methods: 1.10 Use of software tools: 0.91 Required development schedule: 1

ARCHITECTURE ELABORATION PLAN  Revise the Vision Document Revised based on more requirements specifications that are provided by the major professor or feedback provided by the committee members, or observations regarding the prototype.  Revise the Project Plan Will include all the requirement specified in the prior project plan in addition to the new requirements that were suggested and issues noticed by the committee in the first presentation. This revision is going to be the new project plan.  Architectural Design Complete and document the architecture design with the various diagrams and artifacts. The architecture will then be approved by the major professor.

 Revise Prototype New prototype reflecting new requirements and issues indicated by the committee. More functionality will be added to the prototype to expose more of the system capabilities.  Test Plan Several tests will be executed to insure that the system functionality work as expected. The test plan will then be approved by the major professor.

 Management  Documentation  Standards and Practices Reviews  Testing Requirements  Deliverables  Risk Management