Versions Compared

Old Version 2

changes.mady.by.user Anastasia Alexov (Unlicensed)

Saved on

compared with

New Version 3

changes.mady.by.user Anastasia Alexov (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning

The Data Center Design information should be viewed on using Firefox or Chrome;  there are known issues on Safari.


Introduction 

The DKIST Data Center is a microservices based enterprise science data management system that was developed to meet the Science requirements of the DKIST. The design aimed to meet the requirements within the context of a long running program, wherein new technologies, both in telescope instrumentation and computing, will create new scientific opportunities, and necessary improvements and extensions of the Data Center. To that end, the DC was design with modifiability, extensibility, reliability, and maintainability as its main architectural features. The following pages describe, in detail, the data center design, including the processes by which the design was realized. 




MetaHow

A process for understanding a problem and the processes supported by technology that will be used to solve it.

MetaHow Document

MetaHow Artifacts

Child pages (Children Display)
depth2
sorttitle


Suggested Review Order

The MetaHow process for the Data Center has been followed all the way from Strategy through Gap Analysis. The results are both artifacts that have been deprecated over time (e.g., Strategy worksheets, Process Definitions, and intermediate design elements) and artifacts that are maintained to represent the current state of the design. The maintained artifacts of Solution Architected Processes provide an operational or process perspective, a problem and its solution. Any given Solution Architected Process will identify what software design components are necessary (if any) to fulfill a step in the process. These software design components are also depicted in a system view to show how they interact independent of the processes.

For the most complete understanding of the design, it is recommended that one first review the operational view of the data center as a whole (00 - Data Center) followed by the high level system design and enabling system management services (00 - High Level System Design, 04 - System Management Services). From the foundation the high level overview provides, one can go through each Solution Architected Process Area (e.g., 01 - Summit Data Receipt and Ingest SA Process), followed by its associated Composite Application (e.g., 01 - Summit Data Management) and finally a deeper dive into the individual Shared Services which comprise a Composite Application (e.g. 07 - Metadata Store).  

MetaHow Artifact Conceptual Model


MetaHow Phase Description



PhaseActivitiesMetaHow Artifacts
Strategy
  • Set Goals
  • Set Scope
  • Define Operational Approach
  • Goals
  • Scope Diagram
  • Process Approaches
  • Key Performance Indicators
  • Key Concepts
  • Sticky Subjects
Process Definition
  • Define Processes in Strategy Context
  • Define Necessary Support Processes
  • Identify Roles & Responsibilities
  • Identify Necessary Rules
  • Identify Necessary Data to Collect
  • Processes
  • Roles & Responsibilities
  • Rules
  • Data Dictionary
Solution Architecture + Gap Analysis
  • Integrate System Design to Process Definition to Create Solution Architected Processes
  • Define Necessary Solution Architected Support Processes
  • Augment Roles & Responsibilities Where Solution Architecture Requires
  • Augment Rules Where Solution Architecture Requires
  • Solution Architected Processes
  • Augmented Roles & Responsibilities
  • Augmented Rules
System Design
  • Define System Architecture to Support Process Definitions
  • Define Logical Data Models to Support System Design and Data Dictionary Needs
  • System Architecture
  • Logical Data Models


MetaHow Artifact Conceptual Model