Init8bes15 - Registration of Models in GME

Date: 

01/14/2010

Requirement # unique id <SemConOps Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Init8bes15

Originator/Customer's Name:

Tony Pan

Originator/Customer's Company:

Emory University

Summary of requirement initial analysis, by Reviewer: (as unambiguously as possible, describe who (List of Actors) is interacting with the system, what the business goal is and how the system might support the actor's ability to acheive their goal)

Actor: Information Technologist (more specifically software engineer)
Business goal: To main interoperability between services utilizing the same data/information model in different implementation-specific representations. To provide developers alternative consistent data/information model representations to best suit their implementation needs.
Motivation:
Information Technologist would like to be able to find implementation-specific formats/representations such as XML schemas for the data/information models. For instance XML schemas can be used by caGrid service authoring tools for defining inputs and outputs of a caGrid service to maintain consistency and interoperability between different caGrid services utilizing the same data model, authoritative XML schema for each data model should be tracked (alternatively, authoritative mapping rules from UML to XSD should be defined and enforced)
Requirement:
A repository (or multiple) should exist to support authoritative representations of the model for that architecture implementation. If multiple repositories involved, then the consistency/correspondence between these model representations should be guaranteed through tooling (e.g. watchdogs) and/or processes (e.g. concurrent registration from single point).

A browser should exist that will allow Information Specialist (developer) searching (discovering) and retrieval of corresponding model representations from single or multiple repositories. |

Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

Observe - Currently GME is part of caGrid. Depending on how knowledge repositories will shape this can either become a requirement for the repositories in semantic infrastructure con-op document or may be a requirement for architecture.