Overview

Figure 1: Viasoft’s Enterprise 2000 Solution Framework

FastPath Desktop is a complete solution designed to aid organizations with distributed systems for resolving century date-value issues in support of year 2000 processing. FastPath Desktop has been developed to leverage technology and process consistent with other Viasoft maintenance problem solutions.

The year 2000 solution is achieved through the advanced technology of the OnMark 2000 suite of tools.

Viasoft’s year 2000 solution is divided into six distinct steps. Steps one and two focus on the identification of the enterprise portfolio and an analysis of potentially affected objects. Steps three through six address the actual conversion and implementation of the project.

Step One: Inventory

Step one provides a procedure for developing a comprehensive inventory of the complete enterprise hardware and software portfolio.

Step Two: Planning/Analysis

During step two, specific areas are identified as potentially affected. These areas can be targeted for testing and remediation.

Step Three: Change

Step three addresses change techniques on all platforms supported by the OnMark 2000 toolset.

Step Four: Test

During step four, all conversions are unit-tested for functional equivalency, typically using a test plan, test data, and test scripts.

Step Five: Implement

Step five involves enabling the staff to perform integration testing and production implementation using the existing, established procedures for production promotion.

Step Six: Validate

Step six comprises the full system test of all converted components using a system date that will test year 2000 readiness of all converted components.

FastPath Desktop Framework

Figure 2: FastPath Desktop Framework

The FastPath Desktop Process Framework diagram illustrates the sequence of the major activities within the FastPath Desktop process. In addition, each activity has a sub-framework illustrating the task sequence within the activity. These sub-frameworks are shown on the first page of each activity detail in the process guide.

The framework is a guideline for units of work as they move through the process; an entire enterprise does not necessarily need to move through each activity in unison.

Initiate FastPath Desktop Project

The objective of the first activity is to establish a proper environment for the completion of a successful FastPath Desktop project, including raising user awareness, setting up the infrastructure, training, and determining how the business groups should be represented.

Build Project Inventory

The objective of this activity is to obtain a complete and accurate inventory of all hardware and software in the enterprise. Inventory results may also function as a beginning point to construct an audit trail that can be used to prove that the year 2000 issue has been addressed. A technical discussion is conducted with the subject matter expert (SME) during this activity to obtain information about the applications and components.

Implement Maintenance Plan

The objective of this activity is to produce a plan that reduces or eliminates re-infection of the system with non-year 2000 ready data or applications. This plan makes use of the automation and integration of OnMark Survey and OnMark Assess. A Standards Policy is reviewed; a skill inventory is compiled; and a training plan is developed. An additional and ongoing benefit of this activity is an accurate and up-to-date hardware/software inventory that continues to add value after the conversion project concludes.

Set Up Help Desk

The objective of this activity is to set up Level I support for end users. The potential number of PCs in an enterprise can increase the help support from Viasoft that users may require during remediation and testing. This fact, along with the uniqueness of the customer environment, dictates that Level I support should come from the existing customer help desk or that a year 2000 help desk should be established.

Create Test Benchmarks

The objective of this activity is to plan and create test cases to provide effective and efficient testing of converted components. Execution of the test cases produces testing benchmarks that can be reused in the integration testing task.

Create Audit Trail

The objective of this activity is to document an audit trail to provide proof that the year 2000 issue has been addressed and to track the components as they move through the conversion cycle. The OnMark workbenches can automate portions of this activity.

Prepare OnMark Workbenches

The objective of this activity is to obtain the correct number of OnMark Workbench licenses to support the customer initiative, train the workbench users, and determine the work unit breakdown. The actual number of workbenches required is determined by the results of the Build Project Inventory activity.

Analyze

The objective of this activity is to define the remediation targets and to analyze them using the appropriate OnMark tool. For the development platforms, automated creation of an MS Project plan is possible.

Change

The objective of this activity is to mitigate the date-processing issues associated with the year 2000 rollover. For the application development platforms, much of the change is automated using the OnMark 2000 Workbenches.

Test

The objective of this activity is to attain functional equivalency from the converted components. Depending on the platform or application being tested, methods range from using VIA/AutoTest to manual examination of application date-processing results.

Address Desktop Applications with OnMark Assess

The objective of this activity is to involve the Desktop End User in the remediation of desktop applications. Easy to follow guidelines are provided that step the user through identification of problem files, remediation, and testing.

Address MS Excel Spreadsheets with Workbench for Excel

The objective of this activity is to assist the Desktop Application Specialist with the use of the Workbench for Excel in performing analysis, change, and testing of complex MS Excel workbooks and applications. The additional functionality if the workbench can enhance understanding for those who are assigned the responsibility of remediating complex MS Excel workbooks and applications.

Operate Help Desk

The objective of this activity is to provide support for use of the OnMark 2000 toolset during the analysis, change, testing, and implementation of project components.

Implement

The objective of this activity is to conduct integration tests and to provide guidelines for safe implementation into the production system test environment using the customer's existing implementation techniques.

Validate

The objective of this activity is to conduct a system test using the converted components. Much of this activity is dependent on the site setup, so existing procedures are used as much as possible. Guidelines are provided for a system test with an aged system date and aged data.

Process Considerations

This process has been designed around the current capabilities of the OnMark 2000 tool suite. The following considerations should be incorporated into the process in order to streamline the work steps.

Process Scope

This document covers the entire life cycle of a year 2000 conversion from inventory through validation. It also provides a procedure for maintaining an accurate inventory of hardware and software after the conversion project is concluded.

Training during the Project

Schedule training as far in advance as possible.

There are different training needs for different staff at different stages of the project. The system administrators and project teams need training at the early stages of the project (Initiate FastPath Desktop Project activity). The conversion teams need training both before and after the workbench products are installed (Prepare OnMark Workbenches activity). End users of desktop applications may need ongoing training (Implement Maintenance Plan activity). Please refer to the activities noted for more complete information.

Additional Documentation

OnMark 2000 Survey Installation Guide

OnMark 2000 Survey User’s Guide

OnMark 2000 Assess User’s Guide

VIA/Autotest AutoTester Facility Reference Guide

Naming Conventions for Ongoing Application Maintenance

The year 2000 conversion process must review all existing date-related problems within the enterprise portfolio. The time it takes to obtain the information for an entire enterprise can be lengthy. The process requires input from SMEs and various representatives of the business community.

Internal demands require enhancements and maintenance to the existing applications in conjunction with the conversion effort to ensure that the new data item names and formats of date fields adhere to conventions which are year 2000 ready.

New standards must be implemented as soon as possible within the existing maintenance environment to control the naming and formatting of new date-related fields. (This issue is addressed in the Implement Maintenance Plan activity.)

Choosing an Initial Conversion Project

A pilot project is an excellent way to familiarize the conversion participants with the process. This effort should be used to expose the team to the process and gain an understanding of the tools. During the project, project managers gain an understanding of the effort involved for each task and ensure that the team structure is appropriate within their environment. Starting small and simple is highly recommended.

Coordinating Multiple Initiatives during a FastPath Desktop Project

We recommend that no additional initiatives be combined with a FastPath Desktop project. Activities such as version upgrades (e.g., Visual Basic 4.0 to Visual Basic 5.0) or new software system implementations should be performed separately from year 2000 conversion. If the efforts are combined and problems are encountered during the testing phase, determining the cause of the problem becomes difficult. Additionally, combining the efforts is very difficult from a project management point of view. The timeline for the project plan may also be affected.

Project Team Structure and Responsibilities

Business Community Representative

This team member has knowledge of the business side of the enterprise and contributes to discussions where that knowledge is beneficial. For example, business community representatives usually have knowledge of applications within the business community; their input is instrumental in developing test cases. They can also be valuable assets on the year 2000 help desk.

Desktop Application Specialist

This team member is an expert in analysis, remediation, and testing of desktop applications. If an end user has difficulty analyzing or remediating a spreadsheet or database, desktop application specialists troubleshoot problems and help complete the process. They also support the help desk with technical and in-depth remediation questions regarding desktop applications.

Desktop Application User

This individual is the actual application user.

Project Leader

The project leaders direct the conversion teams. They determine the work distribution and ensure that the project’s component life cycle is current.

Project Manager

The project manager oversees the conversion and maintains the master project plan.

Systems Administrators

This team member is responsible for the installation, set up, and maintenance of the OnMark Survey product. To maximize the effectiveness of OnMark Survey, extensive knowledge of the networking structures is required; systems administrators possess the necessary skillset.

Technical User

This team member belongs to the Management Information Systems (MIS) department. They must have a good working knowledge of networking, and PC hardware and software. They also assists with the year 2000 help desk.

Developer

This team member belongs to the Information Technology (IT) department. They must be skilled in application development.

Subject Matter Expert (SME)

This is a team member who has expertise in a particular application or business function.

Audit Trail Administrator

This team member is responsible for compiling, organizing, and maintaining the audit trail.

External Resources

Education Consultant

OnMark Sales Representative

Using the FastPath Desktop Process Guide

Text Styles

The following style conventions are practiced throughout the process guide:

Italicized text inside angle brackets indicates a variable.

The command, "Type C:\PROGRAM FILES\<filename>" indicates that the user must type the name of their particular file.

Underlined text represents a reference to another printed document or a different activity within the process guide.

See the OnMark 2000 Survey Installation Guide for more information.

This issue is addressed in the Implement Maintenance Plan activity.

Bolded text indicates a word or phrase that actually appears on the screen during an action.

From the Field list, select Extension.

Text placed inside quotation marks indicates that the text inside the marks must be typed in EXACTLY as it appears.

Type "SETUP" at the command prompt.

File and directory names, e-mail addresses, and URLs appear in all capital letters. This practice is observed only for the sake of singularity and does not indicate case sensitivity.

An example of a compliance policy is available on the World Wide Web at the following URL: YEAR2000.COM.

This creates a response file (SETUP.ISS) and places it in the C:\WINDOWS directory on Windows 95 and Windows 3.1 machines.

Overview

This section contains a summary of the conversion process framework including concepts that must be understood in order to complete the process successfully.

FastPath Desktop Procedures

This section lists the activities, tasks, deliverables, inputs, roles, and guidelines necessary to complete a conversion. Each of these components is described in more detail in the FastPath Desktop Process Guide description.

Appendices

This section provides additional guidelines about specific tools and techniques used within the conversion process.

Glossary

This section lists relevant terms and their descriptions and definitions.

FastPath Desktop Process Guide Description

The FastPath Desktop conversion procedures are organized as follows:

Activity

An activity is the highest level of order within the process. The activity and its objectives are described in each section. All activities combine to form the conversion process framework described in the Overview section.

Task

Tasks designate the next level of order within the process. Each task lists its objective and any associated deliverables, inputs, roles, and guidelines.

Ä Objective

The objective describes the purpose of a particular task.

& Deliverables

Deliverables are the results produced from implementing a task. A deliverable can be represented by a physical deliverable for the project or an internal work product that is used as an input for a subsequent task.

F Inputs

Inputs are the components needed to complete a task. An input may be generated externally, produced by a previous task, or used as a tool/technique in the Guidelines section.

Roles

The roles section lists individuals who possess the skillset, responsibility, and authority to perform the task.

þ Guidelines

The Guidelines section contains the steps recommended to complete a task. In some cases, guidelines may direct users to a particular reference source (e.g., Viasoft manuals or online help) for specific instructions.