¤ Define dialog style and standards:
Review any company wide standards relating to dialogs or screen layouts. Review hardware, software, and user characteristics to ensure appropriate standards. Define an overall dialog style to be followed, plus other screen-related standards. This should be done for the design area, even if company wide standards are not available. Examples of standards are:
* Use of PF keys
* Screen layouts
* Screen navigation
* Method of displaying help text
* Dialog style (e.g., menu system)
* Security methods
¤ Create dialog flow diagram skeleton:
Identify a list of on-line procedures for inclusion in the diagram. The procedure definitions from the process to procedure mapping task identify which procedures are on line.
Include each procedure on the dialog flow diagram, but do not attempt to indicate flows. It is not necessary to put these procedures in any particular order, but the diagram will be easier to use if related procedures (i.e., procedures with flows between them) are grouped.
Include additional procedures for the top-level menu, plus any other levels of menu, where appropriate.
» Creates deliverable D4.9.2 Dialog Flow Diagram.
¤ Define procedures:
This subtask is performed for each on-line procedure in turn.
- Review the procedure definition -
Review the procedure definition generated from the process to procedure mapping. This contains details of how the procedure is to be implemented and an outline of how the user will interact with the procedure. It also lists the process or processes that it implements.
- Review the process action diagram -
Review the process action diagram (and process logic diagram, if available) for each process implemented by the procedure. This gives a more detailed understanding of the processing involved, and it also defines the import and export data views for the process.
- Define the import and export data views -
Define the import and export data views for the procedure. These can be derived mainly from the import and export views for the process. In addition, you must include any extra data to be displayed to the screen as part of the export view.
» Creates deliverable D4.1.4 Procedure Definition.
¤ Define flows between procedures:
This subtask is performed for each on-line procedure in turn.
- Identify flows -
Identify flows into and out of the procedure. Consider the possible paths the user may wish to use to enter this procedure, and the possible destinations. The process dependency diagram will provide input to this analysis, because dependencies usually imply potential dialog flows. Flows may be to or from other design areas.
ð Updates deliverable D4.1.6 Data Flow Diagram.
- Define flow details -
Draw the flows on the diagram and document the flow details as described in dialog flow diagram conventions. When defining data sent to a procedure, check that this corresponds to attributes in the export and import views of the sending and receiving procedure, respectively.
ð Updates deliverable D4.1.6 Data Flow Diagram.
- Define PF keys and commands-
When a flow is to be triggered by the selection of a PF key, the procedure definition should be updated to record the PF key and the associated command that is to be processed by the procedure.
ð Updates deliverable D4.1.6 Data Flow Diagram.
¤ Define procedure steps:
This subtask is performed for each on-line procedure in turn.
- Review the procedure -
Review the procedure to determine if it should be broken down into procedure steps. Separate procedure steps are required when more than one interaction with the user is needed to execute the procedure. Review the import and export views to decide if it is either desirable or possible for the user to input all of the required data or accept all of the output data in one interaction. The processing logic should also be reviewed because this may also indicate that there should be more than one interaction.
- Define new procedure steps -
The import and export views from the procedure are split over the procedure steps. Note that all elements within both the import and export views for the overall procedures must be included in the import/export view of at least one step. Additional elements may need to be included because of the breakdown into steps. Other details are defined for a procedure step as for a procedure.
ð Updates deliverable D4.1.1 Procedure Definition.
- Define flows between procedure steps -
The flows between the procedure steps and the flows to other procedures are defined. Note that flows into the overall procedure are now implicitly flows into the first step in the procedure.
ð Updates deliverable D4.1.1 Procedure Definition.
¤ Define clerical procedures:
Identify the need for manual or clerical steps immediately preceding and following the automated procedures, by considering the following:
* The source and timing of the data flows input to a procedure
* Any associated system control procedures (e.g., to monitor performance of the automated procedures, or to provide an audit trail)
* The destination of data flows output from a procedure
* The collection, filing or dispersal of inputs and outputs, and any retention needs
Identify the user role relevant to performing each step.
Write a paragraph of text describing each step and add a short overview of the clerical procedure.
Consider what references to clerical procedures need to be added to the automated procedures (e.g., to prompt for preparation procedures, or to give guidance on how to follow procedures).
ð Updates deliverable D4.1.1 Procedure Definition.
Previous : This is the first Sub-Activity of Activity A4.5
Activity Overview : A4.5
Stage Overview : Design Stage
Overview : Table of Contents