The following technical use cases describe the component and system interactions in the DataONE infrastructure. The use cases describe functionality to address the broader scope user scenarios and overall project requirements.
An important early part in the process of system architecture is identifying the functional requirements that the resulting system should be able to address. Use cases are helpful for this as they describe how actors (typically entities external to the system) interact with system components. Interaction diagrams help define the interfaces and messages transmitted between components.
Use Case Layout
Each use case document is structured following a common template which includes the following elements.
A link to the revision history of the document as recorded by subversion.
Brief description of what is intended with the use case.
An overview of the use case which includes the goal and major actors.
- Use case diagram
A diagram representation of the use case, somewhat following the UML.
- Sequence diagram
A sequence diagram that shows the operations involved in addressing the use case.
The participants in the use case - includes people and systems.
The conditions that must exist for the use case. For example, a particular use case may only be valid if the use has been authenticated.
Describes the even that causes the use case to be initiated.
The state of the system after the use case - what conditions are true after the use case is completed.
Miscellaneous notes and discussion items that can’t be placed in the various categories. Comments should be annotated with time and author.