{"title":"Outsourcing IT advice: a success prediction model","authors":"G. Gable","doi":"10.1109/ISCNZ.1996.555284","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555284","url":null,"abstract":"The paper presents an economical prediction model of client success when outsourcing IT advice. Through case studies and statistical evaluation of empirical survey data, the paper identifies those criteria that have broad predictive value as well as those criteria whose predictive value is contingent upon the client's rationale for seeking outside assistance. Client and consultant views on the importance of 10 reasons for outsourcing IT expertise (e.g. objectivity, lack of appropriate skills in-house, company politics) and 15 consultant selection criteria (e.g. price, prior experience, profile, proposal, personalities) are also compared and disparities interpreted.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121813732","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Tabular application development","authors":"Talib Damij, J. Grad","doi":"10.1109/ISCNZ.1996.555305","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555305","url":null,"abstract":"Summary form only given. The work represents an effective approach called tabular application development (TAD). TAD is a new approach, because it introduces a new idea for developing the application by creating several tables. It has nine phases. The first phase of TAD defines the problem to be solved by organizing interviews with all users. The second phase deals with the business processes of the organization. The third phase of TAD builds the process model. The fourth phase transforms the user's models into stable data structures. The fifth phase identifies the objects of the system. The sixth phase builds the object model. The seventh phase deals with analyzing and defining the outputs of the application. The eighth phase has two steps. The first step develops a model of the application using the information existing in the activity and entity tables and the second step deals with creating the algorithms of the application. The last phase is the implementation. In this phase we convert the objects into classes and the operations into methods. Furthermore, we generate a code according to the method specifications and to the defined algorithms.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"58 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126608340","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Systems maintenance and development methodologies","authors":"Michael A. Bailey, R. J. Whiddett","doi":"10.1109/ISCNZ.1996.555302","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555302","url":null,"abstract":"Summary form only given, as follows. Systems maintenance consumes a major proportion of the resources of information systems departments in most organisations. It is often argued that these resource requirements can be reduced by the adoption of particular technologies or methodologies, such as structured analysis or more recently object oriented technologies. The paper reviews these claims by examining some of the more basic issues of systems maintenance such as: (1) the basic definition of maintenance and the various types that can be identified; (2) the methods required for the effective management of maintenance; (3) design issues that favour maintainability; and (4) issues of measurement. Consideration of these issues leads to the conclusion that the most significant impact on systems maintenance costs are more likely to be derived from general improvements in the management tools rather than in the technical tools. Some progress towards evaluating these issues is then discussed.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"98 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122623360","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Managing information systems security: a soft approach","authors":"H. James","doi":"10.1109/ISCNZ.1996.554947","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.554947","url":null,"abstract":"The increasing rate of reported computer security problems suggests that the highly structured and technical traditional approaches to the management of IS security do not appear to be successful. This paper presents the Orion Strategy, a participative approach to the planning and management of information security in organisations. The details of this approach are discussed along with an overview of its pilot implementation within an Australian organisation. The findings from the study indicate that a high level of user participation in the planning and management of security results in raised awareness of security issues and an ownership of responsibility for the successful operations of chosen security measures.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126248329","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"What killed BPR?: some evidence from the literature","authors":"E. Deakins, Hugh H. Makgill","doi":"10.1109/ISCNZ.1996.555276","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555276","url":null,"abstract":"Throughout the first half of the 1990's Business Process Reengineering (BPR) was one of the most eagerly embraced management techniques, although often with results that were far from satisfactory. This tended to reinforce peoples' suspicions of Information Technology since IT is a key enabling agent, if not the driver, for BPR. The aim of this study was to provide literary evidence and reasons for the current widespread dissatisfaction with BPR. Using the keyword Business Process Reengineering/Reengineering, a total of 2019 article abstracts was collected that spanned the period from January 1990 to December 1995 inclusive. The literature was analysed for 18 themes, 6 article types and 32 business areas, in addition to geographic origin, author origin, date, etc. The analysis showed that 97.8% of the BPR literature has been written since the beginning of 1993, since which time there has been an explosive growth in the number of publications. However, a recent sharp downturn in the number of articles may be a sign that BPR is maturing, if not reaching the end, of its useful life cycle. The almost complete absence of research articles to underpin BPR is a distinctive feature of the literature. Thus, opportunities for researchers, as well as hitherto untapped opportunities for consulting practitioners, are clearly identified The article concludes that, while BPR may not have suffered a sudden fatality, it is the victim of neglect in some critical areas of life support.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"678 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121998189","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A repository to support requirement specifications reuse","authors":"José Luís Barros Justo","doi":"10.1109/ISCNZ.1996.555269","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555269","url":null,"abstract":"Software reuse benefits from methodologies and tools to: locate, evaluate, and tailor reusable components to new developments; develop more readily reusable components; reduce cost, time, effort and probability of emerging bugs; and increase efficiency and quality of final products. The paper's focus is on the architecture of a centralized repository to support requirement specifications reuse. The repository enables the application of design-by and design-for reuse methodologies, as it is the core element, where the reusable components are stored in a hierarchy of different levels of abstraction. Indexing techniques for identifying representative descriptors of schemas and similarity techniques to compare schemas for their classification into families, are also discussed. The components engineering process, to identify, select and classify candidate schemas and components, is detailed. Methodology and tools for the repository are briefly described.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"133 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115254942","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Workflow support across organisational boundaries","authors":"R. Tagg","doi":"10.1109/ISCNZ.1996.555255","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555255","url":null,"abstract":"Workflow systems have come into recent vogue as an approach to supporting the co-ordination of business processes. The current surge of commercial activity in groupware and workflow software products has been triggered largely by the widespread use of business process re-engineering (BPR). While commercial products have developed to meet market opportunities, academic research has moved towards support for so-called transactional workflows, where workflow paradigms are applied to the mainstream of mission critical applications. This paper addresses the needs of the growing number of applications which cross the boundaries between organisations. Following a brief review of workflow developments, the needs of such cross-boundary applications are discussed. A model for operation of an appropriate workflow system is described, and the facilities of a \"lightweight\" workflow server are proposed.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"206 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127607715","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Escalation in IT projects: can we afford to quit or do we have to continue?","authors":"U. Nuldén","doi":"10.1109/ISCNZ.1996.555281","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555281","url":null,"abstract":"Many information technology (IT) projects fail. These projects are not within budget, not on time or do not deliver what was promised. Failures in IT projects are more common than failures in any other aspect of modern business. Whereas a large number of projects are obvious failures, some are not. A model of escalation-increasing commitment to a failing course of action-is used to analyze and explain one type of project failure, namely, those projects that seem to take on a life of their own, wasting scarce resources and in many cases never reaching the objectives they were set to fulfil. The paper argues that escalation as a cause of IT project failure has received too little attention in both practice and education. A small case is used to illustrate escalation in an IT project.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"135 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131124325","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A model for information support of environmental management systems","authors":"B. Davey, Clive Mathews","doi":"10.1109/ISCNZ.1996.554949","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.554949","url":null,"abstract":"A review of the literature of environmental management systems has shown a steady development of theory supporting the production of well supported environmental management systems integrated to enterprise information systems. Research into the differences between Australian Chief Financial Officers and Information Systems Managers has shown that there is a gap between company policy on environmental management systems and existing information support for them. This paper reports on the research covering Australia's top 150 companies and preliminary results of interviews of responsible officers. A model is presented which draws on the literature and research findings. This model brings a systems focus to the problem of integrating information systems with environmental management systems so as to achieve organisational goals.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131202192","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Measuring strategic alignment in small firms","authors":"A. Hale, Paul B. Cragg","doi":"10.1109/ISCNZ.1996.555279","DOIUrl":"https://doi.org/10.1109/ISCNZ.1996.555279","url":null,"abstract":"Despite general acceptance of the benefit of aligning IS strategy with organisation strategy, few attempts have been made to define and quantify this alignment relationship. Furthermore, past attempts have largely neglected the specific considerations of small firms. Chart's (1992) instruments were adapted for use in small firms and rigorously tested using eight case firms, from four different industries. The resulting instrument is a significant step towards providing a method for the measurement of strategic alignment. It may prove useful in IS planning by managers and consultants, and by researchers studying the impact of information systems on the performance of small firms.","PeriodicalId":352879,"journal":{"name":"Proceedings of 1996 Information Systems Conference of New Zealand","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129406284","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}