Reference Architecture for NASA’s Earth Science Data Systems Richard Ullman ES-DSWG-SPG Chair NASA/GSFC Code 586.

Slides:



Advertisements
Similar presentations
Connected Health Framework
Advertisements

Object-Oriented Application Frameworks Much of the cost and effort stems from the continuous re- discovery and re-invention of core concepts and components.
Life Science Services and Solutions
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
ESDS Reference Architecture In process report ESDSWG, New Orleans, LA October 21, 2010.
Building a SOA roadmap for your enterprise Presented by Sanjeev Batta Architect, Cayzen Technologies.
e-Framework Components and Responsibilities.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Enterprise development reference architecture (EDRA) -Deepti Seelamsetti.
Enterprise SOA and Cloud Planning Presentation to Association of Enterprise Architects, Washington DC Chapter John Chi-Zong Wu
Azad Madni Professor Director, SAE Program Viterbi School of Engineering Platform-based Engineering: Rapid, Risk-mitigated Development.
1 IBM SanFrancisco Product Evaluation Negotiated Option Presentation By Les Beckford May 2001.
Enterprise Architecture The Arkansas Approach. Key Areas What is enterprise architecture? Why is it important? How you can participate Current status.
1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
PRESENTED BY SANGEETA MEHTA EECS810 UNIVERSITY OF KANSAS OCTOBER 2008 Design Patterns.
Domain-Specific Software Engineering Alex Adamec.
Extended Enterprise Architecture Framework (E2AF)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
A Methodology that is PROVEN PRACTICAL EFFECTIVELY INTEGRATED SCALABLE CUSTOMIZABLE.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Architectural Specification Principles & Foundation Piero Corte, Engineering Ing. Inf. NEXOF-RA.
The Challenge of IT-Business Alignment
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Cohesive Design of Personalized Web Applications Presented by Yinghua Hu Schwabe, D. Mattos Guimaraes, R. Rossi, G. Pontificia Univ. Catolica do Rio de.
3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 1.
© Mahindra Satyam 2009 Decision Analysis and Resolution QMS Training.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
Designing software architectures to achieve quality attribute requirements F. Bachmann, L. Bass, M. Klein and C. Shelton IEE Proceedings Software Tzu-Chin.
Landstar Application Case Study: Development Of Content-rich Solutions For The Mobile Employee Bob Leo Director of Professional Services October 15, 2000.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Seeking SC Feedback on Draft Technology Strategy and Roadmap for EarthCube Draft of 3 November 2015 The Technology and Architecture Committee (TAC) Chairs:
1 Chapter 5:Design Patterns. 2 What are design pattern?  Schematic description of design solution to recurring problems in software design and,  Reusable.
Architecture Who Cares?. Architecture The fundamental organization of a system, embodied in 1) its components, 2) their relationships to each other and.
Smart Home Technologies
1 CBSE Process: issues and Challenges From CBSE Landscape document chapter From.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
NATIONAL AERONAUTICS AND SPACE ADMINISTRATION ESDS Reuse Working Group Earth Science Data Systems Reuse Working Group Case Study: SHAirED Services for.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
Process 4 Hours.
eHealth Standards and Profiles in Action for Europe and Beyond
Chapter 16 – Software Reuse
Design Patterns: MORE Examples
CIM Modeling for E&U - (Short Version)
Chapter 5:Design Patterns
Next Generation Distribution System Platform (DSPx)
Introduction to Design Patterns
Chapter 16 – Software Reuse
Chapter 6 System Engineering
Model-Driven Analysis Frameworks for Embedded Systems
The Strategic Information Technology Formulation
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Chapter 16 – Software Reuse
Chapter 8, Design Patterns Introduction
Presentation to SISAI Luxembourg, 12 June 2012
ESS Enterprise Architecture
Presentation transcript:

Reference Architecture for NASA’s Earth Science Data Systems Richard Ullman ES-DSWG-SPG Chair NASA/GSFC Code 586

What is a Reference Architecture? An abstraction of solution architectures that have been designed and successfully deployed to address the same types of business problems. Incorporate knowledge, patterns, and best practices gained from those implementations. Describes the major foundational components. Includes multiple “views.” Business, Information, Services,, Technology, Engineering. Provides common vocabulary. Reference architecture as a PROVEN SOLUTION or PATTERN for design. Reference Architectures are used to identify the common enterprise primitives under a line of business. – Reference Architecture as a TEMPLATE

Reference Architecture Benefits Reduce risk: Provide a common framework such that solutions can be repeatedly designed and deployed in a consistent, high- quality, supportable fashion. Flexible and extensible infrastructure: Because reference architectures naturally lead to modularity and separation of concerns projects can change out components with little impact on other components. Product mapping and reuse: Components can be either built or can be taken of the shelf (reused) depending on the needs of the project. Well defined interfaces mean that best in class components can be selected. Simplified decision making and improved deployment speed: Critical architectural decisions require time, several rounds of requirement discussion, alternative consideration, and the like. A lot of this time can be saved by using a reference architecture as guidance.

Conclusion Goals of ES-DSWG Reference Architecture: Provide articulation of the NASA domain context and implementation of the Earth Science Data System component of NASA environmental remote sensing satellite missions “well enough” to insure successful use of the pattern by decadal survey missions. Enable evolution of the present architecture to reduce cost and improve interoperability and flexibility. Every project will have its own unique set of challenges and risks that need to be considered for the implementation strategy solution. Selecting the right elements to meet both the tactical and strategic objectives is critical for achieving both the immediate project solution and long-term NASA value. The Reference Architecture provides the basis for developing a project solution that is consistent with architecture patterns and best practices within the NASA’s Earth Science Data Systems “enterprise”.

Next Steps – WORK PLAN - Roadmap Who – volunteers to write? volunteers to review? What – particular views, diagrams, glossary of terms? How – wiki? Google Docs? TWG? When – A substantial draft must be available for explanation and discussion and review before the ESDS-WG meeting October , New Orleans.