| Customized Applications |
|
The issue Departmental customized applications may be used for academic, administrative, instructional, or research purposes. Customized software applications require a different approach then off-the-shelf software, because there are no standard vendor patches or solutions for departmental-unique software applications which were created by programming work of a student, staff member, consultant, or vendor. However they were created, such applications could have Year 2000 problems, and departments should use a planned process for assessing and fixing such problems. A large number of programmers still believe year 2000 problems occur only n software written in Cobol or that their particular language is somehow year 2000-immune. In fact, Y2K problems can occur with very new languages such as C++, Java, JavaScript, JScript, and Perl. For details, see this October 1998 article. Fixing Y2K problems in departmental customized applications is a different process than fixing problems with off-the-shelf software. Although the two can be interrelated - for example, development software should be Y2K compliant before code remediation starts. (More about Year 2000 problems and fixes for off-the-shelf software and database programs can be found here.)
Seven phases for Y2K compliance
What have departments done to date?
Throughout 1999, UCB has reported on the status of more than one hundred systems. Detailed information on these systems is available from:
Individual departments have been required to report on the status of Y2K work on their customized applications since June 1999, to help ensure that the campus knows where applications still need Y2K work and that satisfactory progress is being made. Information on departmental reporting results can be found at the departmental reporting part of this web site.
Contact for questions and comments about this page: customy2k@mail.chance.berkeley.edu Web Administrator: salas@uclink4.berkeley.edu Last Updated Tuesday, 29-Feb-2000 11:48:42 PST Berkeley Campus Home page Copyright Regents of the University of California, 1999 Disclaimer: The University assumes no liability if the information on this page is used for other than University purposes. |