Skip to content

Design Decisions

Joseph Rios edited this page Jul 24, 2018 · 2 revisions

Intro

On this page, we'll try to maintain a list of specific design decisions reached through discussion and work in the utm-apis github project issues. This page will inevitably lag behind the decisions, but will work to keep it as current as we can.

This list should not be construed as the full list of design decisions with respect to the USS concept nor the API. The items here just represent the architecturally significant decisions reached through github issue tracking.

The design decisions and the API in general are products of NASA research into UTM. There should be no inference that the work described here will become operational in the same (or any) form. NASA does not manage the airspace and NASA does not unilaterally set UTM standards. For more information on the scope of our work, see the NASA UTM homepage.

Structure

The following references guide the approach to design decisions.

  1. Documenting Architecture Decisions blog post
  2. arc42 Architecture Decisions
  3. Architecture Decision Record github project
  4. Architecture Decisions: Demystifying Architecture

Each design decision will have the following sections:

  1. Summary
  2. Context
  3. Decision
  4. Consequences
  5. References

The decisions will have an identifier based on at least one GitHub issue recorded within this project.

Design Decisions

The order of these decisions is mostly a function of when a decision was presented and/or reached. The order is not indicative of importance or relevance or any other metric.

  1. Timestamp format
Clone this wiki locally