Graphics User Requirements

General: All subdomains should provide the functionality.
Existence: At least one subdomain should provide the functionality.
Environment: Infrastructure for the functionality should be provided.

Definitions

Real and Graphical Objects: Real objects in the program are mapped to their visual representation, into graphical objects of different kinds, corresponding to different views. The graphical objects correspond to the stored real objects and other real objects created from them. Graphical objects can be described as "model" in MVC system.
Views: Different ways of visualising sets of visual objects. View is generally a window with defined way of displaying graphical objects.
Operations: Any actions made in or from the Graphics. Not all operations are applicable to each object or view.
Operations on Grapical Objects: Operations only changing the visual properties of the graphical objects, the real objects are left intact. Visual operations can be performed on the graphical objects or on the whole views.
Operations on Real Objects: Operations on real objects can change the state of these objects, visual properties of corresponding graphical objects can be also changed.

All higher-level requirements for Atlas software are implicitly inherited and not repeated here. This is mainly true for Control Domain.

Graphics functional requirements fall into three categories:

Furthermore, the validity of any requirement may be restricted to subdomains of a specific kind (Event Display, Statistics, GUI,...).