![]() |
![]() |
![]() |
|
![]() |
|||
| SSD02 - Supporting Specification of User Interfaces |
LSE02 - Spezifikation von Nutzerschnittstellen unterstützen
1 Allocation to V-Model and Methods Allocation
SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit
SD4.2 - Design of Internal and External SW Interfaces
Method
2 Brief Characteristics
3 Requirements
3.1 Requirements for Interfaces
| SSD02.I.1 | Granularity | The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface. |
| SSD02.I.2 | Input interface to SSD20 - Transforming Code Backwards | It is possible to integrate the interface specifications-generated with SSD20 from the physical schema specifications-from the object management without further transformation. |
| SSD02.I.3 | Output interface to SSD10 - Supporting Component and Module Specification | It is possible to transmit the interface specifications to SSD10 via the object management without further transformation in order to be integrated into the specification of components and modules. |
| SSD02.I.4 | Output interface to SSD14 - Generating User Interface Formats | It is possible to transmit the interface specifications to SSD14 without further transformation in order to generate physical schema specifications for interfaces. |
| SSD02.I.5 | Output interface to SSD19 - Simulating Timing Behavior | It is possible to transmit the interface specifications to SSD19 via the object management without further transformation in order to simulate the expected time behavior. |
| SSD02.I.6 | Output interface to SQA14 - Generation of Test Cases | It is possible to transmit the interface specifications to SQA14 via the object management without further transformation in order to generate test cases. |
3.2 Requirements for the Methods Support
| SSD02.M.1 | DIAL - Dialog Design Modeling | |
| SSD02.M.1.1 | Symbols | |
| SSD02.M.1.1.1 | Mask types | Symbols are available for the representation of all mask types required for a dialogue. |
| SSD02.M.1.1.2 | State symbols |
Symbols are available for the representation of states connected with the individual mask types. It is possible to mark these symbols by text. Examples are horizontal lines marked by text with screen types put in front. |
| SSD02.M.1.1.3 | Transition symbols | Symbols are available for the representation of the transition from one state to another. |
| SSD02.M.1.2 | State transitions | |
| SSD02.M.1.2.1 | Alternative state transitions | It is possible to represent alternative state transitions in dialog diagrams. |
| SSD02.M.1.2.2 | Conditional state transitions | It is possible to represent conditional state transitions in dialog diagrams. |
3.3 Requirements for Functions
| SSD02.F.1 | Handling conventional user interfaces | |
| SSD02.F.1.1 | Entering the target system | |
| SSD02.F.1.1.1 | Masks | It is possible to enter the target system for masks. |
| SSD02.F.1.1.2 | Lists | It is possible to enter the target system for lists. |
| SSD02.F.1.2 | Entering the size | |
| SSD02.F.1.2.1 | Masks | It is possible to specify the size of a mask via lines and columns. |
| SSD02.F.1.2.2 | Lists | It is possible to specify the size of a list via lines and columns. |
| SSD02.F.1.3 | Graphical elements | |
| SSD02.F.1.3.1 | Representation | It is at least possible to represent graphical elements as horizontal and vertical lines. |
| SSD02.F.1.3.2 | Field attributes | It is possible to add field attributes to graphical elements. |
| SSD02.F.1.4 | Literals | |
| SSD02.F.1.4.1 | Position | It is possible to represent literals at any position. |
| SSD02.F.1.4.2 | Field attributes | It is possible to add field attributes to literals. |
| SSD02.F.1.5 | Variables | |
| SSD02.F.1.5.1 | Position | It is possible to represent a variable at any position. Variables are input or output fields. |
| SSD02.F.1.5.2 | Field attributes |
It is possible to add field attributes to variables. Field attributes are the attributes "protected", "underlined", etc. |
| SSD02.F.1.6 | Allocation of attributes | |
| SSD02.F.1.6.1 | Direct selection | When allocating field attributes it is possible to get a selection range well-suited to the target system. |
| SSD02.F.1.6.2 | Default settings | It is possible to preset the values for the field attributes. |
| SSD02.F.1.6.3 | Changing the Default Settings | It is possible to change a valid presetting without nullifying its global default settings. |
| SSD02.F.1.7 | Interaction control | |
| SSD02.F.1.7.1 | Cursor | It is possible to determine the first input field. |
| SSD02.F.1.7.2 | Function keys | It is possible to assign values to the function keys. |
| SSD02.F.1.8 | Data definition | |
| SSD02.F.1.8.1 | Global | When setting a variable it is possible to access globally valid data structures. |
| SSD02.F.1.8.2 | Local | When setting a variable it is possible to limit the domain to the object (mask or list). |
| SSD02.F.1.9 | Preview | |
| SSD02.F.1.9.1 | Masks | It is possible to represent a mask in the environment of the target TP monitor. |
| SSD02.F.1.9.2 | Lists | It is possible to select a representation corresponding to the environment of the target system. |
| SSD02.F.1.10 | Copying | |
| SSD02.F.1.10.1 | Masks | It is possible to copy a mask together with all connected information. |
| SSD02.F.1.10.2 | Lists | It is possible to copy a list together with all connected information. |
| SSD02.F.1.11 | Module Allocation | It is possible to allocate processing modules to objects. Objects are masks, lists, variables, etc. |
| SSD02.F.1.12 | List layout | |
| SSD02.F.1.12.1 | Header | It is possible to define header information for each list in a special area. |
| SSD02.F.1.12.2 | Footer | It is possible to define footer information for each list in a special area. |
| SSD02.F.1.13 | Group control change | |
| SSD02.F.1.13.1 | Simple group control change | It is possible to define a single-stage group control change for a list. |
| SSD02.F.1.13.2 | Nested group control change | It is possible to define a nested group control change for a list. |
| SSD02.F.1.13.3 | Trigger | It is possible to combine several variable field contents used as trigger for a group control change. |
| SSD02.F.2 | Handling window-oriented user interfaces | |
| SSD02.F.2.1 | Windows | |
| SSD02.F.2.1.1 | Window types | |
| SSD02.F.2.1.2 | Single window interface | It is possible to allocate the type "Single Window Interface" to a window. A window of type "Single Window Interface" is placed alone and controls no other dependent windows within its window frame. |
| SSD02.F.2.1.3 | Multiple window interface |
It is possible to allocate the type "Multiple Window Interface" to a window. As a primary window, a window of type "Multiple Window Interface" controls other dependent windows within its window frame. |
| SSD02.F.2.1.4 | Modal windows |
It is possible to define a window as modal. A modal window definitely expects a reaction of the user prior to continuing with the dialog. Parallel processing by the user at another window is therefore excluded. |
| SSD02.F.2.2 | Window representation | |
| SSD02.F.2.2.1 | Window frame alterable in scale | It is possible to put a frame alterable in scale on a window. |
| SSD02.F.2.2.2 | Window frame rigid in scale |
It is possible to put a frame rigid in scale on a window. Pop-up windows usually have a rigid frame. |
| SSD02.F.2.2.3 | Window title | It is possible to allocate a title to a window. |
| SSD02.F.2.2.4 | Vertical scroll bar | It is possible to put a vertical scroll bar on a window. |
| SSD02.F.2.2.5 | Horizontal scroll bar | It is possible to put a horizontal scroll bar on a window. |
| SSD02.F.2.2.6 | Closing box |
It is possible to put a closing box on a window. When activating the closing box, the window will be shut and removed from the screen. |
| SSD02.F.2.2.7 | Minimization box |
It is possible to put a minimization box on a window. When activating the minimization box the window is displayed as an icon. |
| SSD02.F.2.2.8 | Window icon |
It is possible to allocate an icon to the window used in case of minimization. The allocated icon represents the window after the minimization box has been activated. |
| SSD02.F.2.2.9 | Maximization box |
It is possible to put a maximization box on a window. After activating the maximization box the window fills the entire screen. |
| SSD02.F.2.2.10 | Command panel | It is possible to put a command panel on a window. |
| SSD02.F.2.2.11 | Predefined events for windows |
It is possible to allocate predefined events to a window. Predefined events are moving the mouse, pressing mouse buttons, changing the size of windows, activation and deactivation of windows. |
| SSD02.F.2.3 | Command panels | |
| SSD02.F.2.3.1 | Predefined pull-down menus |
It is possible to integrate predefined pull-down menus into command panels. Predefined pull-down menus contain basic window-oriented commands like refresh, move, change size, close active window, etc., or they contain commands for help functions like help about help, help index, help for function keys. |
| SSD02.F.2.3.2 | Command definition | It is possible to define commands. |
| SSD02.F.2.3.3 | Code section for commands | It is possible to deposit commands together with a code section. |
| SSD02.F.2.3.4 | Hierarchical grouping of commands | It is possible to group commands hierarchically whereby each level of refinement of a hierarchy branch corresponds to a pull-down menu in the command panel. |
| SSD02.F.2.3.5 | Changing commands | It is possible to change commands. |
| SSD02.F.2.3.6 | Moving commands | It is possible to move commands. |
| SSD02.F.2.3.7 | Deleting commands | It is possible to delete commands. |
| SSD02.F.2.3.8 | Deactivating the command mode |
It is possible to allocate the mode "deactivated" to commands. In this case the corresponding commands cannot be executed. The deactivation is marked on the screen by means of optical information. Usually the command text is not displayed in the usual color but in shadowy gray. |
| SSD02.F.2.3.9 | Function keys/key combinations |
It is possible to deposit function keys or a key combination to commands. The corresponding command will then be activated by pressing either the function key or the key combination. |
| SSD02.F.2.3.10 | Mnemonic command abbreviations |
It is possible to deposit a mnemonic command abbreviation to commands. The corresponding command will then be activated by entering the mnemonic command abbreviation. Usually this is a specially marked character (e. g. by underlining it) in the command itself. |
| SSD02.F.2.3.11 | Copying of commands to a library | It is possible to copy commands into a library. |
| SSD02.F.2.3.12 | Copying of commands from a library | It is possible to copy commands from a library into a command panel. |
| SSD02.F.2.4 | Control element | |
| SSD02.F.2.4.1 | Static control element | |
| SSD02.F.2.4.1.1 | Text | It is possible to insert static text as control elements into a window area. |
| SSD02.F.2.4.1.2 | Group frame | It is possible to insert group frames as control elements into a window area. |
| SSD02.F.2.4.1.3 | Icons | It is possible to insert icons as control elements into a window area. |
| SSD02.F.2.4.1.4 | Bit maps | It is possible to insert bit maps as control elements into a window area. |
| SSD02.F.2.4.2 | Switches | |
| SSD02.F.2.4.2.1 | Push-buttons | It is possible to insert push-buttons as control elements into a window area. |
| SSD02.F.2.4.2.2 | Radio-buttons | it is possible to insert radio-buttons as control elements into a window area. |
| SSD02.F.2.4.2.3 | Check boxes | It is possible to insert check boxes as control elements into a window area. |
| SSD02.F.2.4.2.4 | Vertical scroll bars | It is possible to insert vertical scroll bars as control elements into a window area. |
| SSD02.F.2.4.2.5 | Horizontal scroll bars | It is possible to insert horizontal scroll bars as control elements into a window area. |
| SSD02.F.2.4.2.6 | Hot spots | It is possible to insert hot spots as control elements into a window area. |
| SSD02.F.2.4.3 | Fields | |
| SSD02.F.2.4.3.1 | Input fields | It is possible to insert input fields as control elements into a window area. |
| SSD02.F.2.4.3.2 | Input field lists |
It is possible to insert input field lists as control elements into a window area. Input field lists are used to collect multi-line inputs. The input field list can be navigated by means of scroll bars. |
| SSD02.F.2.4.3.3 | List boxes |
It is possible to insert list boxes as control elements into a window area. List boxes are used to display multi-line outputs. The display can be navigated by means of scroll bars. |
| SSD02.F.2.4.3.4 | Combo boxes |
It is possible to insert combo boxes as control elements into a window area. A combo box combines the functions of an input field with a list box displaying the corresponding selection options either permanently or only explicitly after pressing a drop-down button. |
| SSD02.F.2.4.3.5 | Data types | It is possible to allocate data types to fields. |
| SSD02.F.2.4.3.6 | Selection of control elements | It is possible to select control elements. |
| SSD02.F.2.4.3.7 | Moving control elements | It is possible to move selected control elements. |
| SSD02.F.2.4.3.8 | Deleting control elements | It is possible to delete selected control elements. |
| SSD02.F.2.4.3.9 | Copying control elements | It is possible to copy selected control elements. |
| SSD02.F.2.4.3.10 | Definition of presentation parameters |
It is possible to specify presentation parameters for selected control elements. Presentation parameters are type font/type size, foreground color, background color. |
| SSD02.F.2.4.3.11 | Combination of control elements | It is possible to combine selected control elements into groups. |
| SSD02.F.2.4.3.12 | Alignment of control elements | It is possible to align selected control elements left or right in a raster. |
| SSD02.F.2.4.3.13 | Horizontal alignment of control elements | It is possible to align selected control elements horizontally to each other with the same distance. |
| SSD02.F.2.4.3.14 | Vertical alignment of control elements | It is possible to align selected control elements vertically to each other with the same distance. |
| SSD02.F.2.4.3.15 | Specifying the distance between control elements | It is possible to specify the required vertical and horizontal distance between control elements. |
| SSD02.F.2.4.3.16 | Adjusting the size of control elements | It is possible to automatically adjust the size of selected control elements. |
| SSD02.F.2.4.3.17 | Adjusting presentation parameters of control elements | It is possible to adjust automatically the presentation parameters of selected control elements. |
| SSD02.F.2.4.3.18 | Copying control elements into a library | It is possible to copy control elements selected in a window area into a library. |
| SSD02.F.2.4.3.19 | Copying control elements from a library | It is possible to copy control elements from a library into a window area. |
| SSD02.F.2.4.4 | Events | |
| SSD02.F.2.4.4.1 | Predefined events for control elements |
It is possible to allocate predefined events to control elements. Predefined events are moving the mouse, pressing mouse buttons, selecting list entries, ending field inputs, activation and deactivation of switches. |
| SSD02.F.2.4.4.2 | Code section for an event | It is possible to deposit a code section to each event. |
3.4 Other Requirements
| SSD02.O.1 | Upward compatibility | It must be possible to process objects generated with an older release of the tool with the later release of that tool, without loss of information and functionality. |
| SSD02.O.2 | Procedural command language | The tool has a procedural command language that can be applied by the user to generate and run macros or procedures. |
| SSD02.O.3 | Complexity | There is no limitation of the complexity caused by the tool itself. |
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |