Presentation Analysis

Objectives

The potential for the reuse of screen and report layouts in the design phase of the development cycle is explored during this presentation analysis task. Screens and reports are unique in that they encompass tangible items that a user sees and uses in the current, as well as the target application.

In some cases, screen and report layout reuse may not apply. However, given that a segment of the business remains relatively stable, it is much easier for a user to identify how to modify an existing view than to specify a completely new view. Re-documentation is, by the way, not an objective of this task since presentation layer analysis performed this function during the architectural assessment.

Specific objectives include the following:

· Perform user view, reverse requirements analysis for current systems

· Identify current screen designs for potential reuse in new application

· Capture and reuse, where applicable, current screens as baseline for target design

· Identify current report layouts for potential reuse in new application

· Develop screen and report designs for the new application

Entrance Criteria

The entrance criteria for the presentation analysis are listed below.

· Completion of environmental analysis task of Inventory/Analysis

· Completion of general system architecture analysis task of architectural assessment - DFD derivation of current system flows

· Completion of the presentation layer analysis task of architectural assessment - required

· Completion of prior Transformation tasks based on the scenario driving this effort including:

- Logical data analysis

- Process hierarchy/dependency analysis

- Process analysis

- Business rule analysis

- Interaction analysis

- Dialog analysis

Roles/Skills

The personnel and skill requirements necessary to meet the presentation analysis task are identified below.

· Redevelopment Expert

- Expertise in capturing, documenting and import current screen and report designs within the context of this task

- Basic repository update skills

· Current Systems Expert

- Knowledge of existing system technical presentation environment

- Knowledge of the functionality of current user interface

· User Requirements Analyst

- Knowledge of target functional presentation requirements

· Target System Functional Expert

- Knowledge of target functional presentation requirements

· Function Modeling Expert

- Ability to design/build graphical user interfaces (GUI) environments

Input Requirements

The system components and related inputs required to initiate and complete the presentation analysis task are listed below.

· Process hierarchy, process dependency and process action diagrams as dictated by scenario

· Process hierarchy, process dependency and process action diagrams as dictated by scenario

· System flow analysis (DFD) created in general system architecture analysis for batch and on-line systems

· Completed Transformation process mapping Form 031

· Blank copy of Screen & report analysis Form 032

· The following results produce during environmental analysis:

- JCL, Proc, Step to Executable Program

- Executable On-line Program to Screen Macro Definition

- Executable Program to File(s)/Database(s)

- Screen to Program(s)

- Program to Screen(s)

- Report and screen samples grouped by system and sub-system

· Legacy transition meta-model (LTM) populated with all system components and relationships based on used in prior TIM tasks

Tool/Technology Support

Technologies supporting the presentation analysis task include open systems repository, presentation extract/design, I-CASE modeling, and spreadsheet tools. These tools are used to represent information as required by this task.

Open systems repository

A repository provides an important, yet optional, capability to link business areas, systems and components using the legacy transition meta-model. In this task, the repository is used to trace relationships between forms and programs as input to analysis process.

Presentation extract/design tool

Several tools support the analysis of user presentation layer views of a system. Tools capable of providing automated screen or report mockups for system reporting or on-line teleprocessing facilities support this task. Deliverables in this category include:

· BMS screen layouts

· MFS screen layouts

· Report layout mockups

· Alternatively, report record structure breakdown

A second feature that is important, though not essential, to the "refine target system report/screen design" step is automated screen map to GUI conversion. Certain tools read screen maps, including BMS and MFS, and produce an initial GUI design of the screen. Not all tools in this tool class for this step support this feature however. Some tools are listed because they support related tool classes such as Middleware Enabling.

I-CASE modeling tool

I-CASE analysis workstations provide a mechanism for specifying current and target process action diagrams. While automated input facility is not available in all formats for this type of model, captured rules may be respecified into bottom up/top down process action diagrams with this technology.

Spreadsheet

This tool is used to record metric results for this task.

Task Steps