1. Workplan for Updating the As-built Architecture of the 2007 GEOSS Architecture Implementation Pilot
Session 7B, 6 June 2007
GEOSS Architecture Implementation Pilot Kickoff Meeting - Frascati, Italy chaired by Ivan DeLoatch, FGDC Executive Director and Co-chair of GEO Architecture and Data Committee

2. Workplan for Pilot As-built Architecture
One of the outcomes of the Kickoff Meeting is to develop the next, more detailed level of design, beyond the architecture contained in Annex B of the CFP.
6 June 2007
Workplan for Pilot As-built Architecture

3. Pilot Architecture in Annex B of the CFP
1 OVERVIEW
2 ENTERPRISE VIEWPOINT – VALUE OF EARTH OBSERVATIONS
3 INFORMATION VIEWPOINT – EARTH OBSERVATIONS
4 COMPUTATIONAL VIEWPOINT – SERVICE ORIENTED INTEROPERABILITY
5 ENGINEERING VIEWPOINT – COMPONENTS TYPES
6 TECHNOLOGY VIEWPOINT – COMPONENT INSTANCES
7 PILOT-SPECIFIC BACKGROUND INFORMATION
6 June 2007
Workplan for Pilot As-built Architecture

4. Pilot Architecture in Annex B of the CFP
1 OVERVIEW
1.1 COMMON ARCHITECTURE AND STANDARDS
1.2 RM-ODP VIEWPOINTS Table 1 – RM-ODP Viewpoints
1.3 GEO ARCHITECTURE DATA AND COMMITTEE (ADC) REFERENCES
6 June 2007
Workplan for Pilot As-built Architecture

5. Pilot Architecture in Annex B of the CFP
2 ENTERPRISE VIEWPOINT – VALUE OF EARTH OBSERVATIONS
2.1 GEO COMMUNITY OBJECTIVE
2.2 SOCIETAL BENEFITS
2.3 DATA SHARING PRINCIPLES
2.4 GEOSS INTEROPERABILITY ARRANGEMENTS
2.5 GEOSS COMPONENTS Figure 1 – GEOSS data exchange and dissemination services
Figure 2 –The Internet Bus model
2.6 PILOT SCENARIOS Table 2 - Disaster Scenario: Wildland Fires
Table 3 - Disaster Scenario: Tanker oil spill
Table 4 – Climate Scenario: Local effects
Table 5 – Ecosystems and Biodiversity: Africa Scenario
Table 6 – Ecosystems and Biodiversity: Polar Scenario
6 June 2007
Workplan for Pilot As-built Architecture

6. Pilot Architecture in Annex B of the CFP
3 INFORMATION VIEWPOINT – EARTH OBSERVATIONS
3.1 EARTH OBSERVATION INFORMATION MODEL
3.2 FEATURES, COVERAGES, OBSERVATIONS AND MAPS
3.3 SPATIAL REFERENCING
3.4 GEOGRAPHIC INFORMATION TYPES
3.5 REGISTRY INFORMATION MODELS Figure 3 – GEOSS Registers Use Case Model
Figure 4 – GEOSS Registers Design Model 3.5
3.6 DATASET METADATA – SEARCHING
3.7 DATASET METADATA – RESPONSE RECORDS
6 June 2007
Workplan for Pilot As-built Architecture

7. Pilot Architecture in Annex B of the CFP
4 COMPUTATIONAL VIEWPOINT – SERVICE ORIENTED INTEROPERABILITY
4.1 SERVICE ORIENTED ARCHITECTURE
4.2 SERVICE TIERS Figure 5 – Service Tiers: User, Business and Data
4.3 CATALOG SERVICE STANDARDS Figure 6 — Catalogue service web
4.4 WEB MAP SERVICE
4.5 DATA ACCESS SERVICES
4.6 OTHER SERVICE TYPES
6 June 2007
Workplan for Pilot As-built Architecture

8. Pilot Architecture in Annex B of the CFP
5 ENGINEERING VIEWPOINT – COMPONENTS TYPES
5.1 ENGINEERING VIEWPOINT SUMMARY Figure 7 – Engineering Viewpoint Components
5.2 INTEROPERABILITY ARRANGEMENTS
Table 7 – Potential Interoperability Arrangements Summary
5.3 ENGINEERING USE CASES Figure 8 - Publish-Find-Bind Sequence
Table 8 - Publish-Find-Bind Steps
Figure 9 – Distributed Search Sequence
Table 9 - Distributed Search Steps
Figure 10 – Visualization of EO Sequence
Table 10 - Visualization of EO Steps
Figure 11 – Processing of Service Response Sequence Table 11 - Processing of Service Response Steps
Figure 12 – Workflow Execution Sequence
Table 12 - Workflow Execution Steps
6 June 2007
Workplan for Pilot As-built Architecture

9. Pilot Architecture in Annex B of the CFP
5 ENGINEERING VIEWPOINT – COMPONENTS TYPES (continued)
5.4 USER INTERFACE COMPONENTS
Table 13 – GEO Web Portal Requirements
5.5 BUSINESS PROCESS COMPONENTS
Figure 13 – GEOSS Clearinghouse Architecture Engineering Viewpoint Table 14 – GEOSS Clearinghouse Requirements
5.6 DATA ACCESS COMPONENTS
5.7 EO DATA ENCODING FORMATS
6 June 2007
Workplan for Pilot As-built Architecture

10. Pilot Architecture in Annex B of the CFP
6 TECHNOLOGY VIEWPOINT – COMPONENT INSTANCES
6 June 2007
Workplan for Pilot As-built Architecture

11. Pilot Architecture in Annex B of the CFP
7 PILOT-SPECIFIC BACKGROUND INFORMATION
7.1 GEO ADC DEFINITIONS
7.2 GEOSS CLEARINGHOUSE RFI RESULTS
Table 15 – Clearinghouse RFI Responses
7.3 FEDEO ARCHITECTURE
Figure 14 - Portals distributed network
Figure 15 - ISO Service Metadata
Figure 16 - GML Application Schemas for EO
6 June 2007
Workplan for Pilot As-built Architecture

12. INCOSE Proposal to Improve GEOSS Documentation and UML Modeling IAW ISO/IEC 19793

13. Workplan for Pilot As-built Architecture
Background
ISO/IEC 19793:2006 International Standard defines use of the Unified Modelling Language (UML 2.0 Superstructure Specification, OMG document formal/ ) for expressing system specifications in terms of the
viewpoint specifications defined by the Reference Model of Open Distributed Processing (RM-ODP, ITU-T Rec.9 X.901 to X.904 | ISO/IEC Parts 1 to 4) and the Enterprise Language (ITU-T Rec. X.911 | ISO/IEC 1541
6 June 2007
Workplan for Pilot As-built Architecture

14. Workplan for Pilot As-built Architecture
Background
The rapid growth of distributed processing has led to the adoption of the Reference Model of Open Distributed Processing (RM-ODP), which provides a co-ordinating framework for the standardization of open distributed processing(ODP).
RM-ODP creates an architecture within which support of distribution, interworking, and portability can be integrated.
This architecture provides a framework for the specification of ODP systems.
6 June 2007
Workplan for Pilot As-built Architecture

15. Workplan for Pilot As-built Architecture
Background
Conformance Profile Structuring of Specifications
The framework defined to govern the assessment of conformance addresses these issues. RM-ODP Part 2 defines four classes of reference points:
programmatic reference point, perceptual reference point, inter-working reference point, and interchange reference point
6 June 2007
Workplan for Pilot As-built Architecture

16. Documentation to be Produced
Enterprise Specification - Specifies the roles played by an IT system in its
organizational environment
Information Specification - Specifies system behavior to meet its objectives abstracted from implementation
Computational Specification - Specifies computational structure in terms of units of functionality and distribution and their interactions
Engineering Specification - Specifies the mechanisms and services to provide the distribution transparencies and meet QoS constraints required by the system
Technology Specification - Specifies the hardware and software pieces from which the system is built.
6 June 2007
Workplan for Pilot As-built Architecture

17. Documentation to Be Provided
Correspondences Specification – Shall Provide
for each enterprise object in the enterprise specification, the set of those engineering nodes (if any) with their nuclei, capsules, and clusters, all of which support some or all of its behaviour;
– for each interaction between roles in the enterprise specification, a list of engineering channel types
and stubs, binders, protocol objects and interceptors (if any) that are constrained by the enterprise interaction
6 June 2007
Workplan for Pilot As-built Architecture

18. UML Profiles to be used for ODP
Enterprise viewpoint -concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part
Information Viewpoint -concerned with the kinds of information handled by the system and constraints on the use and interpretation of that information;
Computational Viewpoint -concerned with the functional decomposition of the system into a set of objects that interact at interfaces – enabling system distribution;
Engineering Viewpoint - concerned with the infrastructure required to support system distribution;
Technology Viewpoint - concerned with the choice of technology to support system distribution.
6 June 2007
Workplan for Pilot As-built Architecture

19. Workplan for Pilot As-built Architecture
Approach
Conform to the ISO/IEC Viewpoint correspondences for the information language and profiles provided for each specification type.
Develop a Use Case For each scenario in the Enterprise Specification and associate at a minimum an Activity Diagram and Sequence Diagram to each use case. Use this a basis for other specifications
Develop in a UML Capable tool in one repository
Capture inputs from each contributor in the repository and integrate into the model
Produce each specification in HTML Format.
6 June 2007
Workplan for Pilot As-built Architecture