Skip to end of metadata
Go to start of metadata

Overview of "Generate New Screen — Deprecated" Use Case

Create a custom UI screen leveraging UX framework. (Deprecated) (not functional).


Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option

Metadata

Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors System Process Developer
References  
Uses  
Is Used By  
Extends  
Is Extended By  
In Acceptance Scenarios None
Technical Notes  
Lead Team UX
Primary Service User Workflow, Interaction, and Visual Design
Version 1.2
UC Priority 2
UC Status Deprecated
UX Exposure PGM

Summary

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.

Assumptions

Initial State

System Process Developer has need for a new screen.

Scenario for "Generate New Screen — Deprecated" Use Case

  1. The Application Developer navigates to the Integrated Observatory user interface design library.
    1. This presumes the existence of such a library.
  2. The Application Developer selects a template from the design library.
    1. Template serves as a starting point for the screen design.
  3. The Application Developer makes adaptations to the template for their own needs.
    1. Directions may be provided in a tool, or in a training document (or may be intuitive).
    2. Ideally the look and feel is at a level that can not be impacted (much) by the Application Developer.
  4. The Application Developer saves the modified template to the interface design library.
  5. The Application Developer references the new interface (in the interface design library) from his/her code.
    1. The resulting display should reflect the intended Integrated Observatory look and feel.

Final State

Display has been developed and reflects the system look and feel.

Comments

These comments provide additional context (usually quite technical) for editors of the use case.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B

Labels

usecase usecase Delete
productdescription productdescription Delete
r2-usecase-deprecated r2-usecase-deprecated Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.