SAS J2EE Review
Reviewers

Charge

Agenda

Reviewers' Pre-Queries

Report

  Matt Langston has proposed use of J2EE and related Java technologies as a solution to our data handling and web display applications. To date, the technology has been applied in a 'parasitic' fashion, providing a web interface for display and configuration of the Perl/Oracle-based pipeline.

This is intended as a technical review of the proposal. The GLAST core group will subsequently decide whether it is logistically the best thing to adopt (manpower and schedule mostly).

Date: 23 Nov 2004

Time: 10:30-14:00 PST

Location: Sierra Room@SLAC + vrvs (Astro community)

There will be a dry run of the talks on Fri Nov 19, and all slides will be posted prior to Mon Nov 22.

Charge:

  • evaluate the appropriateness of the technology for the problems at hand
  • evaluate the particular toolset in terms of being the right set of tools for the job
  • evaluate the maintainability of the solution
  • evaluate the manpower needed to support this effort

Reviewers:

Tony Johnson (JAS), Greg White (Tech Div) and Brian Scott (SCS) have been asked to perform the review. Stephen Gowdy (BABAR) has agreed to sit in (if possible - not - new baby takes precedence).

Agenda:

Overview of GLAST's Data Handling Needs [ppt,pdf] Richard 20'
Existing Perl/Oracle Pipeline [ppt,pdf] Dan 20'
Potential Use of JAS [ppt,pdf] Max 20'
J2EE for GLAST Proposal [ppt,pdf,Confluence] Matt 120'

* - preliminary.

News: 2004-11-23 11:40:55 -0800

  • Mark Donszelmann will be giving Max's talk due to the arrival of Max's new baby Sage this weekend.
  • Dan was sick all Friday through the weekend - no sign of his talk yet. 

 

Resources:

Reviewers' Pre-Queries:

  • What are the goals for the project, who are the expected end users, and what is the required timescale.
  • How are these goals being addressed
  • What are the technologies being used to solve the problem. What do they each contribute to achieving the goals
  • What are the major components of the proposed solution, and how do they interact.
  • Which components currently exist and what is the timeline for creating the rest.
  • What are the requirements for future portability
  • How are future portability and maintenance requirements being addressed
  • What is the manpower available to implement the system. How do the skill sets of the available manpower map to those required to implement and maintain the system.
  • How are security concerns being addressed
     

Last Modified: 2004-11-23 11:40:55 -0800