# Presentation: 766009

## Client Design Working GroupEdmund Dombrowski

**Client Design Working Group****Edmund Dombrowski**

- ED-1

**January 28, 1997**

- 733-PP-005-001

## Client Design Working Group

**Client Design Working Group**

**CDWG Meetings (Telecons)**

**Tiger Teams formulated**
**to address key CLS topics for Release B.**

**ECS Tire Kickers **
**(End User Feedback)**

**ECS CLS**
**Personnel**

**ECS SDE**
**Personnel**

**ESDIS**

**Other ECS Sub-System Representatives**

**Recommendations**
**for CLS Design Integration**

## CDWG Goals

** ****CLS Tool Functional Descriptions Based on End-User Inputs.**
** ****CLS Level 3 and 4  Requirements Analysis.**
** ****CLS Tool Integration.**
** ****Client Screen Design and Human Factors Analysis:**
**-  Screen Mock-Ups and Functional Flows.**
** ****Sub-System Interaction Mapping  (CLS, DMS, DSS, CSS, MSS,  etc.).**

**The Primary focus of the CDWG is to appropriately match all CLS requirements to the proposed ECS system builds (Release B) as well as to introduce End-User preferences in terms of Client Screen functionality and overall system interaction.  CDWG deliverables include final recommendation documents with client functional flows and screen specifications as needed.  The CDWG is a joint SDE and CLS team effort.  CDWG team leads and CLS development personnel are working together on the integration of CDWG specifications into the Release B Client Design.**

## CDWG Team Interaction and Process

**Regulators**

**CDWG **
**Board**

**CLS-DMS-DSS**
**Integration Team**

**CLS Design / Implementation Teams**

**Release B I-Team**

**Tiger **
**Team**

**Tiger **
**Team**

**Tiger **
**Team**

**Tiger **
**Team**

## Slide 5

## Slide 6

## Slide 7

## Slide 8

## CDWG Team Summary 

**Before Oct 1996:**
**Subsetting - P**
**Coincident Search - P**

**Subsetting - C**
**Coincident Search - C**
**Advanced Search (PSA) - C**
**User Statistical Reports - C**
**Report Generation - C**
**DAR Review - C**
**DPR Review - C**
**Data Model Tracking - C**
**Find Box for Attribute Value Searches - C**

**Product Order - P**
**Direct Order - P**
**Browse - P**
**Access to Content Based Metadata (Data Mining) - P**
**Aliasing  - P**
**Timeline - P**
**User Profile - P**
**Metadata Exceptions - P**
**CLS Tool Integration - P**
**Help / User Tutorial - P**

**ECS Requirements - O**
**Search and Display (Data Model) - O**
**Naming Conventions - O**
**DeskTop Tool Integration - O**
**Guide Search Results - O**

**Oct 1996 - Jan 1997**

**24 of 41**

**Legend:**
**O  ****	****Open**
**Team is still meeting and**
**discussing design issues.**
**P  ****	****Pending**
**Team has made final**
**recommendations. **
**Regulators finish issue **
**tracking and present report**
**to Board for closure.**
**C****	****Closed**
**Board approves report and **
**recommends actions.  Web**
**population is complete.**

## CDWG Phase 2 and Implementation Support

**CDWG Phase 2 (Post Workshop):**
**•  ****Close All Pending Teams (Early February).**
**•  ****Initiate Advanced Features and Services Tiger Teams.**
**•  ****Continue with Results Integration.**
**SDE Support for CLS Implementation Teams:**
**•  ****Initiate Integrated CLS-SDE teams.**
**•  ****Organize and Deploy CLS Reference Notebooks:**
**	****-  Requirements analysis, User Feedback, CDWG topic results.**

## CDWG Team Results

**Final Recommendations:**
**-  General Specifications**
**-  Specific Data Flows**
**-  Mock-Ups / Scenarios**
**-  Questions / Issues**

**Topic review; Discussion of Key**
**Features; End-User Preferences.**

**Functional Flows; Discussion of**
**Key CLS sub-system interactions.**

**Screen Mock-Ups as needed; Science scenarios or sample steps through the proposed system.**

**Outstanding Issues or Questions **
**needing resolution or specific actions.**

## CDWG Results Integration

**Product Order**

**Product Order Main Functions**

**Product Order Sub-Functions**

**Product Order Implementation Features**

**CDWG Level of Integration to CLS Design**

## CDWG Examples:  “A Few Weeks in The Life”

**Research Tiger Team Topic**

**Gather all L3s and L4s**

**Formulate Tiger Team**

**Hold “Kickoff” Meeting**

**Host Regular Meetings**

**Produce Final Recommendations**

**Commence Issues Tracking**

**Present to Review Board**

**Oversee CLS Integration and**
**Continue Working Issues and Action Items**

**Team Lead**

**Team Regulator**

## Slide 14

## Browse Tiger Team

**1. Functionality vs. Requirements**
**	****Integrated Browse & Visualization Tool- L3 Req.**
**	****Integrated Browse Release B0 & B1 Release - L4 Req.**
**	****Visualization Tool -  Release A & Release B - L4 Req.**
**2. Findings**
**	****Links to Other services**
**	****Multiple Level Function Flows**
**	****Overlay Requirement**
**	****Ease of Use**
**	****The Relevance of a Generic Browse Tool**
**3. Open Issues**
**	****Metadata Updates**
**	****European and Japanese Dataset Browse**
**4. Potential Integrated Browse Solution**
**Appendix I : Structure Analysis of the Browse**

**Draft Final Recommendations**

**a. Links to Other Services**
**In order for the JEST browse tool to be effective, it must also be closely linked with ECS services such as:**
**•  ****searching (i.e., an excellent browse capability will have desirable effect of narrowing the search scope). Integration with the other search features, such as an aid for search refinement, is desirable.**
**•  ****subsetting (i.e., identifying area of interest and/or latitude and longitude range)**

## Browse Results : Tool Functionality

**Functionality vs. Requirements**
**Presently ECS has requirements for two browse tools: an integrated browser with “JEST” and a stand-alone tool  “EOSView”. **
**JEST operates on readily available EOS data (i.e., browse and metadata).  The tool functionality, and therefore, the workload, is  mostly borne by the client-side.**
**EOSView is geared towards supporting  granules pulled from the archives, but it can also view browse images.  It is suppose to be an HDF-EOS File Examiner, and support other advanced data services.**

## Potential Browse Tool Integration

## Browse:  Level 3 Flow

**Browse:  Level 3 Flow**

## Search and Display Team Progress

**Search and Display of Other Data Model AttributesCDWG:**
**•  ****Review Complete Release B Data Model from the End-User Perspective.**
**•  ****Choose logical search and display only attributes (Phase 1).**
**•  ****Group attributes for selection purposes - across modules and provide end-user mock-ups (Phase 2).**
**•  ****Specify logical group associations for the Attribute Selection Tool.**
**•  ****Discuss and specify necessary functionality for special attribute selection tools, i.e. PSA tool.**

## Search and Display Team Approach and CLS Integration

**Release B**
**Data Model**

**Search      Display**

**CLS Design Team**

**Data Modelling Team**

**CDWG**

**DMWG**

**End-User Review**

- All CLS Tools

**Potential Group Association under AST**

**Novice Groupings**

**User Defined**

**User Defined**

**Advanced**
**Services**

**Research Topics**

**Attribute Selection Tool**