ooi epe release 2 initial operating capability review system development overview

EPE Release 2 IOC ReviewAugust 7, 2012

Ocean Observatories Initiative

OOI EPE Release 2 Initial Operating Capability Review

System Development Overview

Sage Lichtenwalner (Lead Developer)

R2 IOC ReviewRutgers University, August 7, 2012


Development Team

Name Organization Focus Area FTESage Lichtenwalner Rutgers Ed. Visualization 0.85*Michael Mills Rutgers Ed. Visualization 0.95Alan Raytheon Lab/Lesson Builder ~0.80Avinash Rude Maine Concept Mapping ~1.0Sean Raytheon Concept Mapping ~0.1

2

* Split among management, SE, design and development tasks

FTE is average over Construction Phase (6 months)


System Design

Release Themes

Product Specification

Release Objectives

Requirements

Use Cases

Architecture

System Integration

System Services

System Deployment

Design

User Stories

Wireframes / UI

EPE Architecture Documentation


EPE System Design

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


The EPE Game Plan

Six Tools/Services

1. Educational Visualization (EV)

2. Concept Mapping (CM)

3. Lab/Lesson Builder (LLB)

4. Educational Resource Data Base (ERDB) - Starts in R3

5. Collaboration Portal (CP) - Starts inR3

6. Education Web Services (EWS)

5


EPE System Level Architecture

6


Release 2 Product Specification

ThemeRelease 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)

7

https://confluence.oceanobservatories.org/display/EPEDev/EPE+R2+Product+Specification


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.

8


EPE Architecture & Design (AD)

The Architecture and Design plan includes the following elements:

• System Integration Plan• Subsystem Service Specifications

1. Overview2. Capabilities3. Decomposition4. Service Components5. Dependencies6. Technologies7. Content models8. Prototype Reports

• System Deployment (Implementation) Plan

• User Interfaces and Wireframes

9

https://confluence.oceanobservatories.org/display/EPEDev/EPE+Architecture+and+Design

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.


EPE System Integration Plan

10

System Integration will be a primary goal of Release 3

Key Integration Points• Content Management System (CMS) - Drupal• User Interface (UI)• Resource Model


EPE System Integration – R2

11


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

Cycle Software ReleaseC1 0.2 pre alpha

C2 0.2 alpha

C3/IOC 0.2 beta

After Transition 0.2 RC

12

Software Releases


Release 3 Preview

• CI Hardware• CI Web Services – direct and custom• Data Stream connector• More/Advanced Tools• EEP Integration (Drupal plugins and

common UI)

13


Ocean Observatories Initiative

OOI EPE Release 2 Initial Operating Capability Review

Education Web Services (WS)

Sage Lichtenwalner (Lead Developer)

R2 IOC ReviewRutgers University, August 7, 2012


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

17

ooi epe release 2 initial operating capability review system development overview

Documents

ioc reviewaugust

monthsepe release

epe system design https

design plan

interface design

design basis

design approach

system integration pla