By Topic

Legacy Information System-Barriers to Business Process Re-engineering (Digest no. 1994/246), IEE Coilloquium on

Date 13 Dec 1994

Filter Results

Displaying Results 1 - 10 of 10
  • The Medicines Control Agency's product licence database

    Page(s): 6/1 - 6/9
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (520 KB)  

    The Medicines Control Agency (MCA) is the government department responsible for the licensing of medicinal products and pharmaceutical manufacturers and wholesalers within the UK. In 1985 it took delivery of a computer system (MEDSOLVE) intended to permit the recording of all of the details contained on the licences for the marketing of medicinal products in the UK. By 1988 it became apparent that a coherent information systems strategy for the Department of Health Medicines Division, as it then was, would require a new product licensing system, largely because greatly enhanced functionality was required. In addition, the old system made no provision for recording the history of a licence, so that if the specification of a product was changed no record of its previous state was preserved. It had also provided almost no on-line validation, but only an error report that could be acted upon or ignored as the user saw fit. The new requirements included both of these features. In 1990 the feasibility of using the logical design of MEDSOLVE as the core for the new system was considered but soon rejected when its inadequacies became fully apparent. Formulation details are at the core of MEDSOLVE and the new product licence system and are discussed in detail. The physical design, logical data structure, and data migration problems of MEDSOLVE are discussed View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • I've found the will. Now, what does it mean? [The problems in the meanings we put to `legacy' and `migration']

    Page(s): 2/1 - 2/7
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (400 KB)  

    Our current information systems must not only survive but also grow to meet the new tasks demanded of them. There are three possible contexts to discuss the problems that arise from the way we have constructed our existing systems and how the use of terms such as `legacy' restricts the development of new systems. Each context for system development responds differently to introduced change. We suggest that there are three dangers in the use of `legacy' which impose constraints upon new growth in each context-organisation: “it's somebody else's and not ours”; technology: “the base paradigm is out of date”; language: “it's semantically out of date” We need a language context, with particular focus upon `meanings', to investigate the problems of `change' and its affect upon our organisations and their information systems. In the past, we have concentrated upon the mechanisms of implementation: the `How?'. We need to include the `Why?', which can be found using semantics. We must recognise that users give meaning to the data we consume, store and produce within technology implementations. It pays to keep the user of the `signs' at the centre of our vision View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Assisting legacy database migration

    Page(s): 5/1 - 5/3
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (236 KB)  

    We introduce a problem in legacy database migration, describe the approach-implemented in a database software tool, the Conceptualised Constraint Visualisation and Enhancement System (CCVES)-that we are developing to help address this problem, and assess briefly the potential usefulness and significance of this approach View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A strategic attempt to management of legacy information systems

    Page(s): 4/1 - 4/6
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (444 KB)  

    The paper sets up in a business firm a scene of computer-based information systems that are developed in different times and on different technologies. To look for an answer to the question of how to effectively use the corporate information resource with the given technologies has been the theme of the research. After having addressed the problems caused by the legacy information systems, the paper presents the main theoretical bases, i.e. a semiotic framework and knowledge based approach, and then discusses some of the design and implementation issues View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • IEE Colloquium `Legacy Information System - Barriers to Business Process Re-Engineering' (Digest No.1994/246)

    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (52 KB)  

    The following topics were dealt with: legacy information system migration; business process re-engineering; strategic management of legacy systems; reference data model; migrating legacy systems from mainframe to open systems; and change management of legacy systems; View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The design of information systems that can respond effectively and rapidly to change at low cost

    Page(s): 8/1 - 8/3
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (256 KB)  

    The paper is based on the experience gained by the author during the past thirty years while seeking to implement information systems in the face of some severe limitations in time and resources. During this period the shortcomings of many of the conventional methodologies were identified. These are examined in the first part of the paper. The second part concentrates on the development of two complementary methods `Simple Architectures and Models' (SAM) and `Mixed Open Methodology' (MOM) that have overcome these limitations and have proved to be durable in the face of technological advances. These methods also expose the shortcomings of not only the specialist but also the more recently advocated hybrid manager; and they illustrate the need for a composer-conductor wielding the baton of a `poor, determined questioning, thinking, simple, selective, mixer' View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The reference data model applied to migrating information systems

    Page(s): 7/1 - 7/4
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (192 KB)  

    The paper illustrates how a product data model can be extended in a universal manner to handle the four levels of information resource dictionary systems and how this assists in developing a reference model to relate policy statements in different models and environments with consistency and integrity. This is the crux of legacy systems View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Legacy or liability-the will to change

    Page(s): 1/1 - 112
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (716 KB)  

    Legacy systems are usually those systems that have stood the test of time and become or remain the core service component of a substantial fraction of a business. Why then should they be a liability? Systems are a mix of hardware and software, sometimes proprietary, often out-dated, and built to earlier styles of design, implementation or operation. Can such systems be changed? View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • How to migrate legacy systems from mainframe to open systems technology

    Page(s): 9/1 - 9/3
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    It is widely acknowledged that it is the legacy systems which are preventing most organisations from moving from mainframe technology to open systems technology. A legacy system tends to be a system which has been run by an organisation for upwards of 10 years and has acquired its name by being handed down. You may not have the original documentation, and it may be difficult to maintain and enhance, but it has probably taken many years to write, is essential to the smooth running of the business. The author discusses how to migrate these legacy systems from mainframe to open system technology. He considers a set of tools from Legacy Software Downsizing Ltd of Manchester, called Powerdrive, to automate the migration of legacy systems to Unix relational database View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Legacy systems-a process not a problem (the “six-pack” model of in-house IT services)

    Page(s): 3/1 - 3/3
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (156 KB)  

    Developments in computer technology are changing the roles of in-house information technology departments. The rise of the PC has led to a massive decentralisation of functions that traditionally were under the control of the IT department. At the same time, the growing importance of IT to all aspects of business and the need for all those decentralised PCs to communicate with each other means that the IT manager has greater responsibility than ever before. In addition, Boards of Directors are starting to demand tangible benefits from their IT operations and many aspects of IT, including software development, are now being outsourced. The focus of many IT Managers appears to be moving away from the problems of developing new systems towards improving the management of existing ones. A sensible response to this change is to install a quality assurance system which can be the basis for a department-wide improvement programme. If properly managed in this way, legacy systems can continue to serve the needs of the organisations that commissioned them View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.