English 312.04

 

To:  Art Vandelay, President of Computer Systems Inc.

From:  John Sharkey

Subject:  Proposal to research the Y2K problem and how to solve the problem in the best way for our company

Date:  23 September 1998

 

Summary

     Y2K, also known as the millennium bug, could cause serious problems when 12:00.01 A.M. on January 1, 2000 comes. Computer systems could either go back 100 years or they could fail.

     The computers that were built in the 1960s and 1970s were not built to hold a four number change in the year. The old lines of code (LOC), called legacy code, became the foundation for computer science as we know it today. Then, in the 1980s, programmers added code on top of the legacy code. Now, millions of LOC have to be changed. Thus, we have this problem.

     I am proposing that I solve the problem for our company. I have been with the company for ten years now and I feel that I know how to solve the Y2K problem. I will assemble teams of the best programmers and testers in the company and solve the Y2K problem for us. I feel that I am suitable for the job and up to the challenge.

    I have read several articles by computer professionals like Stephen Greif, Irene Dec, Howard Rubin, along with a few others to increase my knowledge on how to solve the problem.  I have began to search for the best tool in solving the problem for us. I have and will stay in touch with late breaking technology through the internet, e-mail,  and the news.

     The cost of this project is approximately $1 for every line of code. However, the longer our company waits, the more expensive the code and tools for solving this problem will become. We must start implementing this code as soon as possible.

 

Introduction

     When computer systems were built in the 1960s and 1970s, computer hardware was expensive. To reduce costs, programmers looked for ways to minimize data storage requirements. It was common for dates to be stored in databases as six digit fields rather that as eight digit fields. The systems built during this period were not very user friendly, but were the ones most critical to the business operations. In the 1980s, personal computers became popular and new graphical front ends were added. However, the underlying databases and computer programs were often retained. Not only did these old systems not disappear, they often grew in size, becoming more complicated and difficult to maintain.

     Because the old systems, the ones from the 60s and 70s, were not designed to run in multiple centuries, most will either produce incorrect information or simply fail at the end of this century. It may not sound like much effort to fix these systems, but it actually involves a great deal of effort and expense.

     Many studies have been done to estimate the cost of addressing the Y2K problem. The Gartner Group, a respected information technology researcher, estimates that it will cost more that 600 billion dollars world-wide. If this problem is not addressed in time, the cost could be close to 1 trillion dollars.

     The biggest problem now is the apparent lack of concern by many businesses and government leaders to take the Year 2000 problem seriously. This problem has been around for a few years now, and it gets closer every minute. It must be addressed directly before its too late.

 

Proposed Program

To attack the Y2K problem for our company, I will:

1.  Study about Y2K and how the problem must be addressed

2.  Take in sessions on COBOL and Y2K code implementation

3.  Shop for the best Y2K tools to help our company overcome the problem

4.  Stay in touch with any late breaking information by going on the web as much as possible.

5.  Start Y2K teams for solving problem

6.  Implement problem solving tools

7.  Testing

8.  Prepare my report for submission

 

Study about Y2K and how the problem must be addressed

 

     I have skimmed through several articles about the problem and have increased my knowledge to some extent. I have read articles written by Stephen Greif, member of the Senior Professional Staff at Johns Hopkins University. His article on software licensing and file expiration dates was extremely helpful. I have read about testing and how much testing is needed after the implementation of the code.  I have read "Year/2000 and Project Management" by Irene Dec. This article discusses careful planning and organizational structures. It also talks about project management and getting the right people together at the time of implementation. I have increased my knowledge by reading the Ascent Logic Corporation’s article, “No Single Vendor Can Solve Your Critical Year 2000 Problem — It Takes A Team”. This article speaks of the Year2000Plus, the most popular tool that is used in solving the Y2K problem.

 

Take in session on COBOL and Y2K code implementation

 

     There are several courses that can be taken to teach code implementation. The Ascent Logic Corporation, the originator of Year2000Plus process, offer a set of standard 1 - 3 day Year2000Plus training courses and task-oriented training.

     As you already know, COBOL is basically used in business mainframe systems and with solving the Y2K problem. COBOL classes are offered in many colleges and universities. I look forward to taking a courses to increase my knowledge of the language.

 

 

 

 

Shop for the most popular tools to help our company overcome the problem

 

     There are several tools on the market that are used in solving the Y2K problem.

I will probably choose theYear2000Plus process developed by The Ascent Logic Corporation. It is the most known, the most trusted, and the most user friendly. The Year2000Plus process is supported by engineering and management tools and delivers a flexible client/server environment.

     Another choice that is available and is very successful is the McCabe Visual 2000 process. McCabe Visual 2000 reduces testing efforts and project costs by accurately pinpointing date impact before and after software changes.

 

Stay in touch with any late breaking information by going on the web as much as possible

 

     There are thousand of websites dedicated to the problem. I just subscribed to the Year 2000 journal. This journal e-mails me articles that are written by computer professionals that know about the problem and how to solve it. This will help me stay one step ahead

of the game and solve the problem of Y2K.

 

Start Y2K teams for solving the problem

 

     I believe that this is the most important step in the process. All of the employees that are going to work on this project have to be hard working, fast learning, and very dedicated. This is vital to solving the problem efficiently.

     I am going to start my search by finding which employees would like to work on the problem. These individuals must have been with the company for at least three years and have at least five years computer experience. I need employees that are familiar with the company and have a knowledge of how things work here. I will want valid reasoning why these employees would like to solve the problem for our company. After, I am going to narrow down my selection to the best computer scientists. These scientists are then going to be broken down into teams. The first team is going to implement the code. The second team will test the implementation. The third team will be skilled and knowledgeable in COBOL and COBOL implementation. If I receive the opportunity to assemble this teams, I am certain that I can solve the Y2K problem for Computer Systems Inc..

 

Implement problem solving tools

 

     After the group of programmers is selected, its time to get down to business and solve the problem. Timing is crucial and I will be on top of the project from start to finish. I am up to the challenge. 

      I sincerely believe that the teams will solve the problem of Y2K. We have a staff of employees that have a great amount of knowledge on computer systems.

This kind of knowledge will come in handy during the implementation of the thousands of lines of code (LOC).

Testing

 

     Once the LOC are implemented, then it is time to test. The testers have to locate the Y2K sensitivities in the product. These are the places where the programmers might have to make changes.

     For many applications, particularly newer ones, date sensitivities can be determined from available documentation and source code. Required specifications and design documents are particularly useful sources of information. Additionally, user documentation (maintenance guides and user manuals) can also identify date-related functions. The source code, of course, is the ultimate identifier of date functions within an application.

     After the tester checks the sensitivities, he/she has to check if the system runs as well as it did before the implementation of the Year 2000 LOC. This is called regression testing. Lastly, the tester has to check how well the changed product will operate at the turn of the century. This will validate if the system will run at 12:00.01 on January 1, 2000.   

 

Prepare my report for submission

 

After the problem is solved, I will submit a report. The report will contain:

1.     When the project started and when it ended

2.     Who was on the staff and what was their job

3.     How the implementation was done

4.     How much did the project cost and how much did each individual step cost

 

Credentials and Enthusiasm

     I have been with the company for ten years. I have been working as a programmer for the last four years and I have handled testing and systems analysis in my first three years. I am familiar with the Y2K problem and I have an understanding of how to solve it. I am anxious to start working on the problem. I want to solve the problem for our company. I would like to save the company from all of the problems and hardships that come along with Y2K.

 

Budget

     The employees that I hire for this project are going to continue to work for their regular wages throughout the project. No one should get special treatment throughout this project. I will not choose anyone for this project who wants differently.

     A conversion LOC cost anywhere from $1 to $1.25 for legacy systems. However, as we get closer to the deadline of January 1, 2000, resources will be getting tight, and the cost of a LOC may go as high as $7.