Title
Re-engineering solutions for Y2K challenge
Abstract
The technologies to solve the Y2K problem are re-engineering technologies. Many tools are provided by tool venders to support various areas of Y2K activities. These activities are categorized into the following phases: the preparation phase, the analysis and design phase, the modification phase, and the testing and verification phase. Among these, the key phase is the analysis and design phase. The key technology is often called impact analysis or ripple effect analysis, which helps customers to identify source code that needs to be modified. Fujitsu has developed RWB/2000 for this problem which uses an OODB-based repository and global ripple effect analysis. However, there are no automatic tools to change/fix all the source code which requires modification. Also, the required effort and times heavily depend on customers' current status of applications and their related standardization and documentation. This is why the Y2K project manager has such difficulties making their Y2K plan. We have a maximum of 2 years 5 months to complete the project. Set up the Y2K project as early as possible and start by examining your application system. Identify your completion date for Y2K compliance and start a pilot project to make more accurate plans, and execute it.
Year
DOI
Venue
1997
10.1109/CMPSAC.1997.624837
COMPSAC
Keywords
Field
DocType
y2k compliance,y2k activity,key phase,y2k problem,y2k plan,source code,following phase,y2k project manager,y2k project,re-engineering solution,y2k challenge,design phase,data integrity,standardization,documentation,project management,system testing,software maintenance,year 2000 problem,packaging
Year 2000 problem,Software engineering,Systems engineering,Source code,Computer science,Data integrity,Project manager,Software maintenance,Documentation,Standardization,Project management
Conference
ISSN
ISBN
Citations 
0730-3157
0-8186-8105-5
0
PageRank 
References 
Authors
0.34
0
1
Name
Order
Citations
PageRank
Takashi Sano111.07