|Actors||System Process Developer|
|Is Used By|
|Is Extended By|
|In Acceptance Scenarios||None|
|Primary Service||User Workflow, Interaction, and Visual Design|
This information summarizes the Use Case functionality.
Recommended for deprecation. Presents design recommendations, not user functionality.
An Integrated Observatory System Process Developer needs a new user interface to present a certain functional capability. The developer makes use of a template or other starting point for developing such screens. By following directions that are either embedded in a tool, or described in a training document, the developer is able to piece together the components of the desired screen, and inherits a layout and look-and-feel from the overall Integrated Observatory User Interface design.
System Process Developer has need for a new screen.
- The Application Developer navigates to the Integrated Observatory user interface design library.
- This presumes the existence of such a library.
- The Application Developer selects a template from the design library.
- Template serves as a starting point for the screen design.
- The Application Developer makes adaptations to the template for their own needs.
- Directions may be provided in a tool, or in a training document (or may be intuitive).
- Ideally the look and feel is at a level that can not be impacted (much) by the Application Developer.
- The Application Developer saves the modified template to the interface design library.
- The Application Developer references the new interface (in the interface design library) from his/her code.
- The resulting display should reflect the intended Integrated Observatory look and feel.
Display has been developed and reflects the system look and feel.
These comments provide additional context (usually quite technical) for editors of the use case.