<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">475778456</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180406123637.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170329e20001001xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1023/A:1008126200531</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1023/A:1008126200531</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Reengineering an Information System: A Case Study in Risk Reduction</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Steve Clarke, Tony Elliman, Brian Lehaney]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">Business-process reengineering (BPR), like computer information systems development (ISD), deals primarily with process and contains only weak facilities for addressing structure and culture. Manufacturing and ISD have strong roots in the functionalist traditions of natural science, and in a cultural environment their engineering stance deals poorly with obstacles to change. While the structured, or &quot;hard,” engineering approaches have given rise to successful developments, they have not always proved effective. In ISD, the hard engineering methods have a tendency to redefine information systems problems as problems of technical development, and similarly in engineering contexts, BPR risks becoming too focused on technical processes. However, failure to gain commitment and a sense of ownership in new processes is a cause of failure in both BPR and ISD. This article explores a case study where both technical and human issues must be addressed—the extension of student record processing within a university. In this study, the BPR requirement is seen to arise from the users of the information system rather than as an imposed managerial imperative. The use of total systems intervention (TSI) and interactive planning (IP) enabled the immediate technical problems to be separated from underlying BPR requirements and from the need to gain commitment to change. Thus, unnecessary technical effort and the risks of failure from resistance to change were avoided. From the findings of this intervention, it is argued that the wider application of TSI provides a framework within which managerially perceived needs can be translated into a grassroots commitment.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Kluwer Academic Publishers, 2000</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">BPR</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">human factors</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">information systems</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">risk reduction</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">total systems intervention</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Clarke</subfield>
   <subfield code="D">Steve</subfield>
   <subfield code="u">Department of Finance, Systems, and Operations, The University of Luton Business School, LU1 3JU, Luton, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Elliman</subfield>
   <subfield code="D">Tony</subfield>
   <subfield code="u">Department of Information Systems and Computing, Brunel University, Uxbridge, UB8 3PH, Middlesex, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Lehaney</subfield>
   <subfield code="D">Brian</subfield>
   <subfield code="u">Department of Information Systems and Computing, Brunel University, Uxbridge, UB8 3PH, Middlesex, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">International Journal of Flexible Manufacturing Systems</subfield>
   <subfield code="d">Kluwer Academic Publishers</subfield>
   <subfield code="g">12/4(2000-10-01), 305-320</subfield>
   <subfield code="x">0920-6299</subfield>
   <subfield code="q">12:4&lt;305</subfield>
   <subfield code="1">2000</subfield>
   <subfield code="2">12</subfield>
   <subfield code="o">10696</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1023/A:1008126200531</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1023/A:1008126200531</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Clarke</subfield>
   <subfield code="D">Steve</subfield>
   <subfield code="u">Department of Finance, Systems, and Operations, The University of Luton Business School, LU1 3JU, Luton, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Elliman</subfield>
   <subfield code="D">Tony</subfield>
   <subfield code="u">Department of Information Systems and Computing, Brunel University, Uxbridge, UB8 3PH, Middlesex, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Lehaney</subfield>
   <subfield code="D">Brian</subfield>
   <subfield code="u">Department of Information Systems and Computing, Brunel University, Uxbridge, UB8 3PH, Middlesex, UK</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">International Journal of Flexible Manufacturing Systems</subfield>
   <subfield code="d">Kluwer Academic Publishers</subfield>
   <subfield code="g">12/4(2000-10-01), 305-320</subfield>
   <subfield code="x">0920-6299</subfield>
   <subfield code="q">12:4&lt;305</subfield>
   <subfield code="1">2000</subfield>
   <subfield code="2">12</subfield>
   <subfield code="o">10696</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
