1 / 17

OOI EPE Release 2 Initial Operating Capability Review System Development Overview

OOI EPE Release 2 Initial Operating Capability Review System Development Overview. Sage Lichtenwalner (Lead Developer) R2 IOC Review Rutgers University, August 7, 2012. Development Team. FTE is average over Construction Phase (6 months).

lukas
Download Presentation

OOI EPE Release 2 Initial Operating Capability Review System Development Overview

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. OOI EPE Release 2 Initial Operating Capability ReviewSystem Development Overview Sage Lichtenwalner (Lead Developer) R2 IOC Review Rutgers University, August 7, 2012

  2. Development Team FTE is average over Construction Phase (6 months) * Split among management, SE, design and development tasks

  3. EPE Architecture Documentation

  4. EPE System Design https://confluence.oceanobservatories.org/display/EPEDev/EPE+System+Design

  5. The EPE Game Plan • Six Tools/Services • Educational Visualization (EV) • Concept Mapping (CM) • Lab/Lesson Builder (LLB) • Educational Resource Data Base (ERDB) - Starts in R3 • Collaboration Portal (CP) - Starts inR3 • Education Web Services (EWS) 4

  6. EPE System Level Architecture

  7. Release 2 Product Specification https://confluence.oceanobservatories.org/display/EPEDev/EPE+R2+Product+Specification Theme Release 2 provides an Educational Services Framework, a suite of tools demonstrating preliminary end-to-end functionality and interface design of the educational infrastructure. It targets early-adopters in the undergraduate education community, and provides a design basis for soliciting user feedback. Objectives • Prototype four tools for education developers • Utilize needs assessment results to refine their design • Conduct usability tests with prospective users to validate design approach. Target Audience • Early adopters in the undergraduate educator community • diverse range of educational institutions (i.e. community colleges, research universities) • and implementation environments (ranging from introductory courses to senior level lab courses)

  8. Release 2 Product Specification End of Release Features Glider Profile Visualization Customization of Visualization Tools Concept Map Builder Ontology Search (prototype) Online Lesson Builder Glider Data API (interim) Concept Map API Caveats All system services at the end of R2 will consist of beta versions that function largely independently of each other. The focus of R2 will be primarily be on developing prototype user interfaces. Refinement (including additional features) of the services and integration will occur in R3.

  9. EPE Architecture & Design (AD) Unlike the Product Specifications, the AD plan will be written cumulatively, reflecting the current state of the system architecture as it is built over each successive release. https://confluence.oceanobservatories.org/display/EPEDev/EPE+Architecture+and+Design The Architecture and Design plan includes the following elements: • System Integration Plan • Subsystem Service Specifications • Overview • Capabilities • Decomposition • Service Components • Dependencies • Technologies • Content models • Prototype Reports • System Deployment (Implementation) Plan • User Interfaces and Wireframes

  10. EPE System Integration Plan System Integration will be a primary goal of Release 3 Key Integration Points Content Management System (CMS) - Drupal User Interface (UI) Resource Model

  11. EPE System Integration – R2

  12. EPE System Deployment Plan • Application Hosting • Linux, Apache, MySQL, PHP (LAMP) • Software Code Repository and Versioning • GitHub • Bug Tracking • Via email and JIRA • Usability Testing • During transition and beyond Software Releases

  13. Release 3 Preview CI Hardware CI Web Services – direct and custom Data Stream connector More/Advanced Tools EEP Integration (Drupal plugins and common UI)

  14. OOI EPE Release 2 Initial Operating Capability ReviewEducation Web Services (WS) Sage Lichtenwalner (Lead Developer) R2 IOC Review Rutgers University, August 7, 2012

  15. Education Web Services Capabilities / Components • Concept Map API • R2: Utilize existing architecture to support development of new features • R3: Transition the existing API (built in ColdFusion) to new common architecture (MySQL/PHP) • Resource Database API (R3) • Science Data Services • R2: Utilize and implement provisional web services to access data to support visualization tool development. • R3: EPE will take advantages of processing and web service capabilities of the CI to provide needed datasets for educational visualization tools.

  16. Education Web Services – Science Data The following web services were used in the development of Release 2 data visualization tools: • NDBC/IOOS Sensor Observation Service • Provides time series data from a global array of NDBC and IOOS stations • Custom built a “proxy” script to aggregate and cache data requests • EPE (provisional) Glider Web Service • Provides glider profile data from a selected set of deployments (not real-time) • Custom built simple API to support profile visualizations • Ocean Networks Canada • Provides time series data from Neptune Canada and Venus bottom mounted sensors • Received API information in July • OOI ION • Coming soon

More Related