UC: Define New Type

Description: This use case enables a Metaspace Steward to define, describe and persistently store a new MAP Type.

Actor: Metaspace Steward

Preconditions:

• a Metaspace Steward has navigated to the MAP Home Page

Post-conditions:

The Type will either have been discarded or committed to persistent storage.

Assumptions:

Main Flow

1. This use case starts when a Metaspace Steward selects Define a New Type from the MAP Home Page.
2. The system responds by presenting a Define New Type Dialog that prompts the Steward to provide values for type_name and description, and to select a base type from the list of available Base Types. The dialog offers Continue and Cancel actions.
3. The Steward supplies the requested values and selects an action.
4. If the Steward selected Cancel, any supplied values are ignored, the dialog is dismissed, and this use case ends. If the Steward selected Continue and a base type of Composite, include UC: Edit Composite Property Type. Otherwise, include UC: Edit Scalar Property Type
5. This flow resumes when the Steward has selected Submit from the MAP Type editor. The system persists the initial version of the Type and presents a Confirmation Dialog.
6. The Steward acknowledges the Confirmation Dialog.
7. The dialog is dismissed and this use case ends.

Alternate Flows

None.

Wireframes

New Property Type Dialog

Confirmation Dialog

Issues

Implementation Notes

Holon, Collection, Property, Relationship, Value->ValueType(Boolean, Integer, String) ValueArray->(Boolean, Integer, String)