SSA DC-IV NEO Fireball Information System · Request : existing neo portal using the Liferay users...

SSA DC-IV NEOFireball Information System

ESRIN, 02/02/2016

Ole Kverneland

Presentation Title | Date

ToC - Agenda

Introduction

Project review

Technical review

Lessons learned & way forward

Questions/AOB

Introduction

Context

SSA : Space Situational Awareness

Predict and assess the risk

due to man-made space debris objects,

potential impacts of Near-Earth Objects (NEOs),

and the effects of space weather phenomena on space- and ground-based infrastructure.

ESA SSA program composed of three segments

SWE : Space Weather

NEO : Near-Earth Objects

SST : Space Surveillance and Tracking

Context

DC-IV WP-NEO: Fireball, Impacts and Atmospheric Explosions Database

Fireball :

A bright meteor with an apparent visual magnitude of -4 mag. or brighter.

Objectives

Develop a fireball database to be included in the NEO Web portal

This database should contain fireballs with a magnitude larger than -10

Observations starting from 01/01/2010

Project review

DC-IV consortium

DC-IV overall consortium

WP-NEO organisation

Capgemini at a glance

Capgemini Mission Critical Systems – Space Unit

250+ dedicated engineers on Space

& ATM programs

30+ experience-years in Space

domain

Prime locations: Toulouse,

Bayonne

Innovative solutions

Science expertise center

Capgemini Mission Critical System- Space Unit

Capgemini Space Organisation

Engineering

Support

System Specification

System Level

Sub-system Development

Simulators

TechnicalQualif.

OperationalQualif.

Operationalprocedures

Exploitation

Operations

Science Expertise CenterSW Architects

& Expert

DC-IV consortium

GMV overall management of the DC-IV activity

Capgemini lead of the WP-NEO

All development phases

Support from GMV in NEO work domain related activities

Mainly requirements engineering and design phases

Tools & methods

Use of ESA Software development environment :

DOORS for requirements

HP Quality Center for test management

Sharepoint for information exchange

Rational Change

Capgemini Continuous Integration Platform

Maven, SVN, checkstyle, PMD, JUNIT, Hudson, Sonar, Findbugs …

ECSS standards for traceability

SCRUM/Agile for flexibility

Schedule

Milestone KO Schedule Final date

(months)

Kick off meeting 12/11/2012 12/11/2012 0

Software requirements review 15/01/2013 23/07/2013 6

Preliminary Design Review 15/03/2013 22/10/2013 7

Cricital Design Review Not planned 25/02/2013 ----

FAT Test readiness review 27/10/2013 01/04/2014 6

Acceptance review 1 31/10/2013 05/09/2014 11

OSAT Test Readiness Review 07/01/2014 01/10/2014 9

Acceptance review 2 13/01/2014 31/10/2014 9

In the end 9 months delay with initial schedule.

Schedule

SWRR : 6 months delay due to contractual issues. All DC-IV activities were put on hold between January 2013 and Mai 2013.

CDR : not part of initial planning and requirements

FAT : delayed in order to FAT testing of the Fireball database in the latest version of the NEO portal (Single Sign-On functionality).

Technical review

Questions

Which are the pieces of data available for a fireball ?

How to collect the data ?

How do we organize the data ?

Where to the data come from ?

=> Not that simple …

Iterative and pragmatic approach, discussion between Capgemini, GMV and ESA

Data model

Difficulty : define the data model, link the different data to the « objects »

Identify optional and mandatory data

Who may access data ? Some should not be available on the web to all visitors

The data model was modified during all project phases

class domain

Identifiable

ConfidentialIdentifiable

+ getConfidentialPublicUsersAttributes() : List<String>

+ getConfidentialRegistredUsersAttributes() : List<String>

+ isConfidentialPublicUsersAttribute(String) : boolean

+ isConfidentialRegistredUsersAttributes(String) : boolean

+ setConfidentialPublicUsersAttributes(List<String>) : void

+ setConfidentialRegistredUsersAttributes(List<String>) : void

+ toString() : String

«enumeration»

Countries

Identifiable

Deriv edData

- comments: String = null

- estimatedMassReachingGround: Integer = null

- estimatedPreAtmosphericSize: Integer = null

- location: Location = null

- orbitalOrigin: String = null

- orbitalParameters: List<OrbitalParameters> = new ArrayList<O...

- origin: List<Origin> = new ArrayList<O...

- releaseEnergy: Integer = null

- serialVersionUID: long = 1L {readOnly}

Identifiable

FireballEv ent

- country: List<Countries> = new ArrayList<C...

- derivedDatas: List<DerivedData> = new ArrayList<D...

- eventDate: Date = null

- isFireballMeteorite: Boolean = null

- meteorites: List<Meteorite> = new ArrayList<M...

- name: String = null

- observations: List<Observation> = new ArrayList<O...

- region: String = null

Location

- beginPoint: LocationPoint = null

- description: String = null

- endPoint: LocationPoint = null

LocationObserv ationPoint

- description: String = null

+ getDescription() : String

+ setDescription(String) : void

LocationPoint

- estimateErrorInPosition: Integer = null

- height: Integer = null

- latitude: Integer = null

- longitude: Integer = null

Identifiable

LogFile

- dateTime: Date = null

- level: String = null

- logger: String = null

- message: String = null

- userId: String = null

Identifiable

Meteorite

- composition: String = null

- craterSize: Double = null

- decayingManMadeObject: Integer = null

- impact: String = null

- location: List<Location> = new ArrayList<L...

- weight: Double = null

NameIdentifiable

Notifications

- createType: boolean = false

- emailAddress: String = null

- searchRootCriteria: SearchRootCriteria = null

- updateType: boolean = false

+ getEmailAddress() : String

+ getSearchRootCriteria() : SearchRootCriteria

+ isCreateType() : boolean

+ isUpdateType() : boolean

+ setCreateType(boolean) : void

+ setEmailAddress(String) : void

+ setSearchRootCriteria(SearchRootCriteria) : void

+ setUpdateType(boolean) : void

Identifiable

Observ ation

- city: String = null

- country: Countries = null

- date: Date = null

- derivedData: List<DerivedData> = new ArrayList<D...

- location: LocationObservationPoint = null

- meteorite: Meteorite = null

- observationOrigin: Origin = null

- observationPhotos: List<String> = new ArrayList<S...

- observationVideos: List<String> = new ArrayList<S...

- observers: List<Observer> = new ArrayList<O...

- region: String = null

- status: ObservationStatus = ObservationStat...

«enumeration»

Observ ationTypeOrigin

VALUES_ARRAY ([]) = new Observation... {readOnly}

VALUES = Collections.unm... {readOnly}

value {readOnly}

name {readOnly}

l iteral {readOnly}

«enum»

NEWSPAPER

WEBSITE

CAMERA

SCIENTIFICPUBLICATION

Observ er

- company: String = null

- companyAdress: String = null

- email: String = null

- firstName: String = null

- lastName: String = null

- phoneNumber: String = null

- websiteName: String = null

- websiteURL: String = null

Identifiable

OrbitalParameters

- argumentPeriapsis: Integer = null

- ascendingNode: Integer = null

- eccentricity: Integer = null

- inclinaison: Integer = null

- orbitTime: Date = null

- perihelionDistance: Integer = null

- semiMajorAxis: Integer = null

Identifiable

Origin

- articleTitle: String = null

- author: String = null

- cameraDateActivation: Date = null

- cameraType: String = null

- contact: String = null

- derivedDateComments: String = null

- lastRetrieveDate: Date = null

- observatoryName: String = null

- originName: String = null

- publicationDate: Date = null

- typeOfObservationOrigin: ObservationTypeOrigin = null

- url: String = null

NameIdentifiable

Statistics

- meanType: boolean = false

- searchRootCriteria: SearchRootCriteria = null

UserPreferences

- notifications: List<Notifications> = new ArrayList<N...

- searchs: List<SearchRootCriteria> = new ArrayList<S...

- statistics: List<Statistics> = new ArrayList<S...

- userId: String = null

- viewFilter: List<ViewFilter> = new ArrayList<V...

observationOrigin

-meteorite

-location

-country

-endPoint-beginPoint

-location

VALUES_ARRAY

typeOfObservationOrigin

VALUES_ARRAY

Who and how ?

Operator : managing the

database (NEO front desk

operator)

Registered user : may save search,

statistics, acces restriced information

Public users : you and me

on the surfing on the web

Database structure

Fireball event : describing what is considered as a fireball event;

Observation; a reported observation of a fireball event.

And derived data: data that are linked to the fireball that have been computed or derived.

Meteorite: object found on ground linked to the fireball

OBSERVATION

FIREBALL EVENT DERIVED DATA

(0,N)(1,N)

METEORITE

(0,N) (1,N)

Dynamical view

The ‘entry’ data come from the ‘Observations’ which are the main group of data The other groups of data (fireball event and derived data) are created depending on the observation(s)

A fireball event can be created if there is 1 created observation ;

OBSERVATION

CREATIONObservation 1

1 reliable

observation

(e.g.from

European

Fireball

Network)

Observation

2 to NOBSERVATION

CREATION

LINK VERIFICATION

BETWEEN

OBS1 & OBSx

Otherwise

EndDERIVED

CREATION

FIREBALL

CREATIONFireball event

Derived data

OBS1 & OBS2

linked

Otherwise

Techincal view

Portlets integrated in Liferay portal

Business services deployed in a glassfish application server

Database on a mysql data server

Search engine Lucene-Solr

Physical View

All machines are virtual

Load balancing is optional

Authentication

Use of SSA Single Sign-On

Restful interface

Let’s take a look

Menu for public users

Acessing data

Fireball example

Navigation through breadcrumb

Search function

Free search :

Search

Advanced search

Operator view

Menu for operator

Edit tool for the welcome page

Operator

Select observation tab

Add new

Operator my editand removeobservations

Operator

Mandatory fields marked with (*)

Select different tabs and enter data

Managing data

Add derived data

Managing data

Add derived data

Log view

Lessons learned & way forward

General requirements

Many general requirements applicable to all the WP

Relevant to M&C system, less relevant to a web interface

Logs, …

FIS SRS written by Capgemini engineering team experienced on a system level

=>Adjust the priority given to general requirements with low added-value to users

Integration & CFI

The NEO web portal was not provided as a CFI

Requirement to have look & feel compliant with the existing portal

Discussion and iterations on the HMI on

Colors

Screen width

Button size and forms…

Technical solution for authentication not clear

Request : existing neo portal using the Liferay users management

Other request : Single Sign-On using the SSA OpenAM server.

=> Having the NEO portal at the beginning of the project would have saved time.

Waterfall vs Agile

Contractual baseline : waterfall with reviews

Development method : Scrum Agile

True Agile not compliant with the availability of ESA interfaces (TO and NEO domain experts)

However: flexibility on both sides to adjust and change requirements during entire project (staying at iso-complexity)

=> Agile inside waterfall contract works well if both parties are constructive, mutual thrust needed

Capgemini experience also from other clients

Future

Ergonomic improvements based on user feedback …

Import function may be improved (create events, but operator appreciation needed somewhere in the process)

Import data from other sources than the American Meteor Society

System integration :

Import automatically observations from other websites

Create observations from reports from observers ?

Interface for (Public, Registered) users to submit online new observations ?

Questions / AOB

Contact information

KVERNELANDProject Manager

ole.kverneland@capgemini.com

Capgemini Toulouse

Insert

contact

picture

Insert

contact

picture

Richard

BARRESales engineer

Richard.barre@capgemini.com

Capgemini

Toulouse

The information contained in this presentation is proprietary.

www.capgemini.com

SSA DC-IV NEO Fireball Information System · Request : existing neo portal using the Liferay users...

Documents

Transcript of SSA DC-IV NEO Fireball Information System · Request : existing neo portal using the Liferay users...

OpenAM OpenIDMで シングルサインオンをするた …OAuth 2.0 Provider OAuth 2.0 プロバイダ機能 OpenAM 10.1 Xpressではプロバイダ機能が追加 20 OpenAM OpenAM

OpenAM Dev Guide

ceas2017.orgceas2017.org/.../uploads/2017/10/Detailed-program.docx · Web viewImproved NEO data processing capabilities for the ESA SSA-NEO software system Claudiu Teodorescu (Deimos

Administration Guide - OpenAM 10 - ForgeRock BackStage€¦ · Administration Guide OpenAM 10.1 Mark Craig ForgeRock AS 201 Mission St., Suite 2900 San Francisco, CA 94105, USA +1

ForgeRock OpenAM as flexible integration component

J).pdf · f± 1.6 ssa-18 —x ssa-18s200 ssa-18cioo ssa-18 — ssa-20 y v — 229 206 model ssa-18sioo 180m m 103 289 ssa-18c200 370mm 150 600 203 185 ssa-20s300

OPENAM 12.0. THE BEST, NEWEST AND MOST SHINY VERSION. EVER.

The ESA-‐SSA programme: the NEO and SST segments

Hacking OpenAM Infrastructure - ZeroNights …2012.zeronights.org/includes/docs/Noseevich, Petukhov - No locked...Hacking OpenAM Infrastructure George ... Devs didn't worry too much

SSA. Agenda SSA Introduction Converting to SSA Converting out of SSA SSA Example.

Developer's Guide - OpenAM 12 - ForgeRock BackStage€¦ · Developer's Guide /OpenAM 12 Latest update: 12.0.4 Mark Craig David Goldsmith Gene Hirayama Mike Jang Chris Lee Peter Major

OpenAM as Flexible Integration Component

Case Study - Largest Brazilian Credit and Debtor Operator, A ForgeRock OpenAM Deployment

Street corner meetings held at Madhya Pradesh Pradesh...Street corner meetings held at Madhya Pradesh Bhopal SSA Dhar SSA Satna SSA Hosangabad SSA Rajgarh Beta SSA Panna SSA Dewas

OpenAM Survival Tips

esoc - ESA Space Weatherswe.ssa.esa.int/DOCS/SSA-DC/SSA-DC-SW-ICD-0001.pdf · OpenAM is the open source software that will provide the Identity Management System including the authentication

ACCESS CONTROL SYSTEM · 2011. 6. 20. · ACCESS CONTROL SYSTEM SSA-S30x0/S30x1 SSA-S2100/S2101 SSA-S2000(V) SSA-S1000(V) SSA-C100 /C110/C120 SSA-C200 SSA-X500 SSA-M1000/M1100 SSA-M2000/M2100

Getting Started With OpenAM - OpenAM 13...to the Bitstream Vera Font Software, including without limitation the rights to use, copy, merge, publish, distribute, and/or sell copies

SSA Space Situational Awareness Programme Activity/conf... · in ‘Phase2’, 2013 – 16, a bit under 50 Mio Euro (for all three segments) ISS Station from 400 km, ... SSA-NEO web

Saml v2-OpenAM

OpenAM OpenIDMでシングルサインオンをするた …OAuth 2.0 Provider OAuth 2.0 プロバイダ機能 OpenAM 10.1 Xpressではプロバイダ機能が追加 20 OpenAM OpenAM