Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Decision model for legacy systems

Decision model for legacy systems

For access to this article, please select a purchase option:

Buy article PDF
£12.50
(plus tax if applicable)
Add to cart
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)
Add to cart

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
IEE Proceedings - Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

IEE
Published

Legacy systems pose major problems for industry - existing software seems so difficult and expensive to change quickly to keep up with the needs of business. The authors firstly summarise the general problems with modifying existing software - termed software maintenance - and then address the problems of legacy systems. They show that one of the major difficulties is trying to decide rationally among very different options, ranging from discarding the old software completely, through reverse engineering, to freezing it, or outsourcing. A novel two-phase model is presented to assist organisations in making decisions about legacy systems. The first phase, often neglected, is to model business strategy from a top-down perspective, involving many stakeholders. This is then used as input to a technical phase, where solutions are evaluated according to their ability to meet the objectives identified in phase one.

Inspec keywords: outsourcing; software maintenance; reverse engineering; systems re-engineering; business data processing

Other keywords: legacy systems; outsourcing; business; reverse engineering; two-phase model; decision model; system reengineering; software maintenance

Subjects: Systems analysis and programming; Business and administrative computing; Business applications of IT

References

    1. 1)
      • EDWARDS, H.M., MUNRO, M.: `RECAST: reverse engineering from COBOL to SSADM specification', Proc. 15th Int. Conf. on Software Engineering, 1993, Baltimore, p. 499–508.
    2. 2)
      • E.B. SWANSON , C.M. BEATH . (1989) , Maintaining information systems in organizations.
    3. 3)
      • C. BROOKE . (1997) A modified framework for the evaluation of technological choice, Proceedings of the 2nd IFIP 8.6 International Working Conference Ambleside, UK 25–27th June.
    4. 4)
      • RAMAGE, M., BENNETT, K.H.: `Maintaining maintainability', Proc. IEEE Int. Conf. on Software Maintenance, Washington, USA, 1998.
    5. 5)
      • B. LIENTZ , E.B. SWANSON , G.E. TOMPKINS . Characteristics of applications software maintenance. Commun. ACM , 6 , 466 - 471
    6. 6)
      • E. YOUNGER , H.J. VAN ZUYLEN . (1993) Documentation, The REDO Compendium.
    7. 7)
      • G. VERGUGO . (1988) Portfolio analysis: managing software as an asset, Proc. of the 6th International Conference on Software Maintenance/Management, Washington, D.C., USA.
    8. 8)
      • RENAISSANCE PROJECT: `The renaissance method handbook'. http://www.comp.lancs.ac.uk/computing/research/cseg/projects/renaissance/Renaissance Web/project/Documents3.html, 1998.
    9. 9)
      • M. WARD . Reverse engineering through formal transformation. Comput. J. , 9 , 795 - 813
    10. 10)
      • J.M. Carroll . (1995) , Scenario-based design: envisioning work and technology in system development.
    11. 11)
      • M. WARD , K.H. BENNETT . Formal methods to aid the evolution of software. Int. J. Softw. Eng. Knowl. Eng., Special Issue on `Software Evolution' , 1 , 25 - 47
    12. 12)
      • J.I. CASH , R.G. ECCLES , N. NOHRIA , R.L. NOLAN . (1994) , Building the information-age organization: structure, control and information technologies.
    13. 13)
      • G. CANFORA , A. CIMITILE , M. MUNRO . RE2: reverse engineering and reuse re-engineering. J. Softw. Maint. , 5 , 53 - 72
    14. 14)
      • SABA project: http://www.dur.ac.uk/CSM/SABA/. May 1999.
    15. 15)
      • B. LIENTZ , E.B. SWANSON . (1980) , Software maintenance management: a study of the maintenance of computer application software in 487 data processing organisations.
    16. 16)
      • J.A. MCDERMID . (1991) , The Software Engineer's Reference Book'.
    17. 17)
      • BENNETT, K.H., YOUNGER, E.J., BULL, Y., LUO, Z.: `Reverse engineering concurrent programs using formal modelling and analysis', Proceedings of the IEEE International Conference on Software Maintenance, 1996, Monterey, p. 255–264.
    18. 18)
      • C. CLEGG , P. COLEMAN , P. HORNBY , R. MACLAREN , J. ROBSON , N. CAREY , G. SYMON . Tools to incorporate some psychological and organisational issues during the development of computer-based systems. Ergon. , 3 , 482 - 511
    19. 19)
      • C. BROOKE . Information technology and the quality gap. Employee Relations , 4 , 22 - 34
    20. 20)
      • V. STENNING . Judgement day for IT Systems. Comput. Bull. , 2 , 16 - 17
    21. 21)
      • M.L. BRODIE , M. STONEBRAKER . (1995) , Migrating legacy systems.
    22. 22)
      • SNEED, H.M.: `Encapsulating legacy software for use in client-server systems', Proc. IEEE Int. Conf. on Software Maintenance, 1996, Monterey, CA, p. 104–120.
    23. 23)
      • CIMITILE, A., MULLER, H., KLOSCH, R.R.: `Pulling together'. Proc. of ICSE-19 Workshop on Migration Strategies for Legacy Systems', TUV-1841-97-06, Available as Tech. Report, 1987, from Technical University of Vienna, A-1040 Vienna, Austria.
    24. 24)
      • BENNETT, K.H.: `Do program transformations help reverse engineering?', Proc. IEEE Int. Conf. on Software Maintenance, Washington D.C., 1998, p. 247–254.
    25. 25)
      • E.J. CHIKOFSKY , J.H. CROSS . Reverse engineering and design recovery: a taxonomy. IEEE Softw. , 13 - 17
    26. 26)
      • WARD, M.P., BENNETT, K.H.: `A practical program transformation system for reverse engineering', Proc. IEEE Conf. on Reverse Engineering, May 1993, Baltimore, p. 217–221.
    27. 27)
      • RAMAGE, M.: `The learning way: evaluating co-operative systems', , PhD thesis, University of Lancaster, UK.
    28. 28)
      • SNEED, H.M.: `Migration of procedurally oriented COBOL programs in an object oriented architecture', IEEE Conf. on Software Maintenance, 1992, IEEE Comp. Press, p. 105–116.
    29. 29)
      • BROOKE, C., RAMAGE, M., BENNETT, K.H., GOLD, N.E.: `Change effects and legacy information systems: a framework to aid our understanding', Information Systems: Current Issues and Future Changes, IFIP working groups 8.2 & 8.6 Conference, Helsinki, Finland, 10-13 December 1998.
    30. 30)
      • FOSTER, J.R.: `Cost factors in software maintenance', 1993, Ph.D. Thesis, University of Durham, Computer Science Department.
    31. 31)
      • SEBPC: Systems Engineering for Business Process Change Programme, EPSRC (May 1999). http://www.staff.ecs.soton.ac.uk/∼ph/sebpc.
    32. 32)
      • F. MATZDORF , M. RAMAGE . Out of the box - into the future!. Organ. People
    33. 33)
      • H. SNEED . Planning the re-engineering of legacy systems. IEEE Softw. , 1 , 24 - 34
    34. 34)
      • G. ALKHATIB . The maintenance problem of application software: an empirical analysis. J. Softw. Maint., Res. Pract. , 2 , 83 - 104
    35. 35)
      • K.H. BENNETT . Legacy systems: coping with stress. IEEE Softw. , 1 , 19 - 23
    36. 36)
      • M. WARD . Abstracting a specification from code. J. Softw. Maint., Res. Pract. , 2 , 101 - 122
http://iet.metastore.ingenta.com/content/journals/10.1049/ip-sen_19990617
Loading

Related content

content/journals/10.1049/ip-sen_19990617
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
Print this page
This is a required field
Please enter a valid email address