Abstract
The dominant issue for software management at the end of this century is to make information systems year 2000 compliant. The respective changes of programs and data stores need very high human and system resources. Not all programs and data stores can be converted at once; therefore, work units that consist of those programs and data stores that will be changed simultaneously have to be determined.
In this paper, a hierarchical planning procedure to construct appropriate work units is developed. It combines a cluster identification algorithm, a branch-and-bound technique and a greedy heuristic. The solution obtained also shows whether the planner can expect the project to be finished in time with the resources available. The procedure has been implemented in the prototype FUSE2000 (Fusion & Sequence); the application of this prototype is illustrated by an example.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Arnold, R.S., Bohner, S.A.: Impact analysis — Towards a framework of FUSE2000 is explained by an example. for comparison. In: D. Card (Ed.), Proc. Conference on Software Maintenance 1993, IEEE Computer Society Press, 1993, pp. 292–301.
Ashley, J.: Year 2000 Solutions. Cambridge Market Intelligence, 1996.
Brathwaite, K.S.: Information Engineering, Vol I, Concepts. CRC 1992.
Brown, D.: Project Management and Project Timelines, EMU & YEAR2000 Seminar, Gartner Group, Zurich 1997.
Butler, J.: The Year 2000 Crisis. Computer Technology Research 1996.
Cohen, B.: New York Transit Official Poses Y2K Alternatives. In: ITAA’s Year 2000 Outlook 1 (1996) 6 (Internet Newsletter) http://www.itaa.org/scripts/dbml.exe?action=queryandTemplate=2000lett.dbmandIssueID=31 Registration: http://www.itaa.org/scripts/dbml.exe?Template=get2klet.dbm (as of 1997–05–10)
Cook, W.J.: A Risk Managed Approach to Year 2000 Data Architecture http://pwl.netcom.com/~wjcookly2krisk.html (as of 1997–04–23)
Dun and Bradstreet Satyam Software (Ed.): Year 2000, Code Enabling Strategies and Problem Sizing. http://www.dbss.comly2kpaper.htm (as of 1997–04-23)
de Jager, P.: Systemic Triage. In: American Programmer 9 (1996) 2, pp. 12–15.
Eldridge, A., Louton, B.: A Comparison of Procedural and Data Change Options for Century Compliance. http://www.year2000.com/archive/options.html (as of 1997–05-08)
Essick, K.: Year 2000 problem may be worse than feared. In: InfoWorld Electric, 1997–03-06. http://www.infoworld.com/cgi-bin/displayStory.pl?97036.e2000.htm (as of 1997–05-08)
Farber, A., LaChance, R.: Impact of the year 2000: Next millennium no chance for celebration. In: Enterprise Systems Journal 10 (1995) 12, p. 36.
Hein, K.P.: Information System Model and Architecture Generator. In: IBM Systems Journal 24 (1985) 3–4, pp. 213–235.
IBM (Ed.), The Year 2000 and 2-Digit Dates: Guide Document Number GC28–1251-06, 6th ed., 1997–04-11. http://www.ppdbooks.pok.ibm.com:80/cgibin/bookmgr/bookmgr.cmd/BOOKS1y2kpaper/CCONTENTS(as of 1997–05-08)
ISO 8601: Data elements and interchange formats - Information interchange - Representation of dates and times. Reference number ISO 8601: 1988 (E), (Geneve) 1988.
Jung, J.: Opening statement to CIOs Year 2000 Online Conference, 1996–09-17. http://www.cio.com/forums/year2k.html (as of 1997–07-01)
Kappelman, L.: Year 2000 upgrades: A small price to pay. In: Computerworld 30 (1996) 48, p. 33.
Katz, R.L.: Busines/Enterprise Modeling. In: IBM Systems Journal 29 (1990) 4, pp. 509–525.
Keogh, J.: Solving the Year 2000 Problem. Academic Press 1997.
Knolmayer, G.: The Application of Mixed Integer Programming to the „Business Systems Planning“-Problem. In: H. Dyckhoff et al. (Eds.), Operations Research Proceedings 1993. Springer 1994, pp. 457–463.
Knolmayer, G., Gerber, J.-P.: Experiences with applying a genetic algorithm to determine an information systems architecture. In: OR Spektrum 19 (1997) 1, pp. 47–53.
Knolmayer, G., Spahni, D.: Darstellung and Vergleich ausgewählter Methoden zur Bestimmung von IS-Architekturen. In: H. Reichel (Ed.), Informatik, Wirtschaft, Gesellschaft. Springer 1993, pp. 99–104.
Kusiak, A., Chow, W.S.: An Efficient Cluster Identification Algorithm. In: IEEE Transactions on Systems, Man, and Cybernetics 17 (1987) 4, pp. 696–699.
Martin, J.: Strategic Data-Planning Methodologies. Prentice-Hall 1982.
Millennium Solutions: Legacy System Survival in the Year 2000 http://www.2k-solutions.com/ (as of 1997–05-08)
MS Millennium (Ed.): The Millennium Challenge & MS Millennium Capabilities, 1997.
NN: Lessons from the trenches: Building — and burning — bridges. In: Computerworld 31 (1997) 18, p. 72.
NN: Reply #364 to VIAS VIASOFT and THE Y2K PROBLEM http://www.exchange2000.com/~wsapilinvestor/s-11784/reply-364 (as of 1997–0630)
NN: Database-Program inter-dependency. http://www.bridgeims.com/depend.htm (as of 1997–06-30)
Queille, J.-P., Voidrot, J.-F., Wilde, N., Munro, M.: The impact analysis task in software maintenance: A model and a case study. In: H.A. Muller, M. Georges (Eds.), Proceedings International Conference on Software Maintenance 1994. IEEE Computer Society Press 1994, pp. 234–242.
RICOMM Systems (Ed.): Bridging the Gap, 1997.
Rubin, H.A.: Millennium Metrics: Truth & Consequences. In: Proc. 10th International Conference on Software Maintenance & Software Management, Year 2000 Solutions, 1996.
Schlageter, G., Stucky, W.: Datenbanksysteme: Konzepte und Modelle, 2. Auflage. Teubner 1983.
Spahni, D.: Gestaltung von Informationssystemen, Bestimmung und Sequenzierung geeigneter Teilsysteme. Physica 1997.
Spewak, S.H., Hill, S.C.: Enterprise Architecture Planning, QED 1993.
Turn of the Century (Ed.): Y2K Task Grid. http://www.tocs.com/y2k/a8.htm (as of 1997–04-23)
Ulrich, W.M., Hayes, I.S., The Year 2000 Software Crisis. Yourdon Press 1997.
Valdes, J.: Planning: Y2K Conversion. Mail to (moderated) list year2000@hookup.net (1996–09–25; sent 1996–10–05)
Vetter, M.: Strategie der Anwendungssoftware-Entwicklung. Methoden, Techniken, Tools einer ganzheitlichen, objektorientierten Vorgehensweise. Teubner 1993.
Viasoft: Dynamic Bridging: A Year 2000 Conversion Strategy, BRO1BRDG0996, 1996.
Viasoft: Viasoft’s Bridge 2000, BR10BR0497, 1997. http://www.viasoft.com/PRDCTS/BRIDGE2K/ (as of 1997–05-08)
Visionet Systems: Millennium/400 Segmentation Tools. http://www.visionets.com/ (as of 1997–06-30)
Walter, M.: Vorgehensweise und Erfahrungen bei der Datumsumstellung im SAP System R/2. In: Wirtschaftsinformatik 39 (1997) 1, pp. 19–24.
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1997 B. G. Teubner Verlagsgesellschaft Leipzig
About this chapter
Cite this chapter
Knolmayer, G.F., Spahni, D.M. (1997). Determining Work Units in Year 2000 Maintenance Projects. In: Oberweis, A., Sneed, H.M. (eds) Software-Management ’97. Teubner-Reihe Wirtschaftsinformatik. Vieweg+Teubner Verlag. https://doi.org/10.1007/978-3-322-85166-6_1
Download citation
DOI: https://doi.org/10.1007/978-3-322-85166-6_1
Publisher Name: Vieweg+Teubner Verlag
Print ISBN: 978-3-8154-2603-6
Online ISBN: 978-3-322-85166-6
eBook Packages: Springer Book Archive