Abstract
The paper argues that 1998 is the year to reject concepts previously chosen as the basis for implementing high-visibility projects and to postpone projects so that resources can be reallocated to address Year 2000 problems. Systems to store and manipulate data will be based on complex, multi-tiered client-server solutions instead of the simpler two-tiered architecture. Some work originally planned for C++ will be performed in Java. Short development cycles will require developers to make extensive use of third-party components. Information systems departments will stress outside training and certification for both employee and contractor software engineers. Year 2000 paranoia will grow as corporate management recognizes the magnitude of the problem.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
