Consortium Surveys

Hello LOGIC Community! We are soliciting inputs for existing standards that you are using in your lunar applications. We are also soliciting input for user stories, scenarios and pain points as this data will be our starting point in identifying critical interfaces for which we will develop standards recommendations. If you have input to submit for consideration on any of these topics, please expand and fill out the form below.

Point of Contact

Please provide a valid email.
Please provide a valid email.

Please retype your email.

Organization/Company Details

Available Surveys

We are soliciting inputs for existing standards that you are using in your lunar applications. If you have a standard to submit for consideration, please fill out the form below.

Include standard number if applicable – e.g. MIL-STD-XXXX

Revision / Release Date

E.g. Rev A, B, C, etc.

and / or

E.g. July 2022

Describe standard applicability, if only a subset of the standard is applicable and which sections, etc.

Select a topic area(s) applicable to standard:

Select a applicable standard type(s):

Provide Standards File

Link to Standards

Include link to where the standard can be purchased or downloaded

OR

To upload your selected document, you must click the black "Submit" button above.

To submit your completed surveys, you must click the blue "SUBMIT SURVEY" button at the bottom of this page.

We are soliciting inputs for user stories and pain points. Pain points along with scenarios and user stories will be our starting point in identifying critical interfaces for which we will develop standards recommendations.

Pain Points

Pain points are usually known, existing problems. You can also think of them as things that keep you up at night. Examples include:

  • The ISS has power supplies and connectors from multiple nations.
    • Plugging a system into the wrong power source can destroy the system or damage the ISS
  • The Mars Climate Orbiter crashed into the Martian surface because of a failure in conversion of measurement units.
    • As a result of this failure, the Guide for the Use of the International System of Units (SI) NIST Special Publication 811 standard was updated.

We are soliciting inputs for scenarios. Scenarios along with user stories and pain points will be our starting point in identifying critical interfaces for which we will develop standards recommendations.

Scenarios

Scenarios and use cases tend to have a system perspective, i.e. how a system or systems perform under certain circumstances, possibly in conjunction with other systems and users.

They usually describe the circumstances or triggering factors, in addition to the events / interactions between systems and users.

These are often represented as sequential narratives or UML sequence diagrams.

A narrative scenario might look like this:

  • A scenario is decomposed into individual atomic actions between pairs of actors (systems or people).
    • Each action is labeled with actors that are the source and sink.
  • Actions without sinks are reflexive.
    • The behavior is an action that should trigger an action / response from the sink.

From: Katherine L. Morse and David L. Drake, “Multi-Viewpoint Conceptual Modeling,” Proceedings of the NATO CA2X2 Forum 2020, virtual, September 23 – 24, 2020.

A sequence diagram scenario might look like this:

  • Sequence diagrams show scenario interactions between actors (systems or people) with time running down the page.
  • The interactions are labeled with their content, e.g. data or power.

From: Katherine L. Morse, et al, “Realizing the Cyber Operational Architecture Training System (COATS) Through Standards,” Proceedings of the 2014 Fall Simulation Interoperability Workshop, Orlando, FL, September 8 – 12, 2014.

Provide Scenario File

To upload your selected document, you must click the black "Submit" button above.

To submit your completed surveys, you must click the blue "SUBMIT SURVEY" button at the bottom of this page.

We are soliciting inputs for user stories. User stories along with scenarios and pain points will be our starting point in identifying critical interfaces for which we will develop standards recommendations.

User Stories

User stories have the user perspective. They usually follow the format, “As [a user persona], I want [to perform this action] so that [I can accomplish this goal].”

These are helpful in soliciting inputs from stakeholders who aren’t technical SMEs on systems. These users don’t necessarily know how systems can meet their needs, but they know what they need to be able to do.

Examples include:

  • As a construction engineer, I need Lunar Rover X to return to base autonomously and reliably, so that I can immediately load it the next day.
    • From this, we can infer that Lunar Rover X needs to receive PNT data for its current position and its home base.
      • Where will this data come from/who is/are the service provider(s)?
      • What common hardware / software elements does Lunar Rover X need to be equipped with to process this data?
  • As a construction engineer, I need Lunar Rover X to fully charge at the end of each day, so that I can use it all of the next day.
    • From this, we can infer that Lunar Rover X needs to dock to a common power source/power service provider to recharge its onboard battery.
      • Who's providing power?
      • What interface/design does Rover X need to have in order to recharge?