Organisational scenarios and legacy systems

Brooke, Carole and Ramage, Magnus (2001) Organisational scenarios and legacy systems. International Journal of Information Management, 21 (5). pp. 365-384. ISSN 0268-4012

Full content URL: http://dx.doi.org/10.1016/S0268-4012(01)00023-8

Documents
uoa36cb03.pdf
Scan
[img] PDF
uoa36cb03.pdf - Whole Document
Restricted to Repository staff only

5MB
Item Type:Article
Item Status:Live Archive

Abstract

A legacy system is made up of technical components and social factors (such as software, people, skills, business processes) which no longer meet the needs of the business environment. The study of legacy systems has tended to be biased towards a software engineering perspective and to concentrate on technical properties. This paper suggests that the evaluation of potential change options for legacy systems can only be carried out as part of an holistic organisational analysis. That is, the evaluation of legacy systems must take place within a framework that combines business and technical considerations. In particular, we believe that the business strategy must lead this process. Accordingly, we have designed an inter-disciplinary approach which brings together an organisational scenarios tool (based on concepts from the field of organisational development) and a technical scenarios tool (based on concepts from the field of software engineering). These tools are applied in an iterative way, so that technical options are tested out against the business needs. It is, thus, a dynamic tool which seeks to mimic the nature of organisational change, as far as is practicable. The research project described here is entitled software as a business asset (SABA) and was funded by the Engineering and Physical Sciences Research Council (EPSRC) under the systems engineering for business process change (SEBPC) programme. This paper describes the research approach and its iterative stages, and illustrates its use within a large engineering firm (Engco). Its application produced useful insights for the organisation, as well as pointers for further modification of our research approach

Additional Information:A legacy system is made up of technical components and social factors (such as software, people, skills, business processes) which no longer meet the needs of the business environment. The study of legacy systems has tended to be biased towards a software engineering perspective and to concentrate on technical properties. This paper suggests that the evaluation of potential change options for legacy systems can only be carried out as part of an holistic organisational analysis. That is, the evaluation of legacy systems must take place within a framework that combines business and technical considerations. In particular, we believe that the business strategy must lead this process. Accordingly, we have designed an inter-disciplinary approach which brings together an organisational scenarios tool (based on concepts from the field of organisational development) and a technical scenarios tool (based on concepts from the field of software engineering). These tools are applied in an iterative way, so that technical options are tested out against the business needs. It is, thus, a dynamic tool which seeks to mimic the nature of organisational change, as far as is practicable. The research project described here is entitled software as a business asset (SABA) and was funded by the Engineering and Physical Sciences Research Council (EPSRC) under the systems engineering for business process change (SEBPC) programme. This paper describes the research approach and its iterative stages, and illustrates its use within a large engineering firm (Engco). Its application produced useful insights for the organisation, as well as pointers for further modification of our research approach
Keywords:Information systems
Subjects:G Mathematical and Computer Sciences > G500 Information Systems
N Business and Administrative studies > N200 Management studies
Divisions:Lincoln International Business School
ID Code:533
Deposited On:22 Jun 2007

Repository Staff Only: item control page