Abstract
With the Year 2000 approaching, there is a massive amount of code review and modification going on within industry. One aspect of this millennium problem is computer systems that have used a two digit rendering of the year when interpreting dates. Since the Year 2000 is a fixed deadline that cannot be moved, time is of the essence for businesses in determining if their software has any date logic within them that is incorrect. This means that any utilities that can be implemented to reduce the amount of time software maintainers spend on comprehension and modification of programs would be of benefit. Since reverse engineering techniques can be used to identify components and interrelationships within software, as well as build up high level abstractions from low level code details, it is possible to determine through practical example whether reverse engineering tools and techniques could serve a role in identifying computer software date code problems for the Year 2000.
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.
