A comprehensive review of the enterprise systems research

(WP 12/04 Clave pdf) Enterprise systems (ES) can be considered as a novel phenomenon for the information system research and other academic fields (e.g. operations and supply chain), which has opened an immense potential and opportunities for research. Although the interest of the scholars on ES is recent, the number of publications is continuously growing since 2000. The aim of this paper is to review a sample of important contributions of the ES works published to date. To do this, the selected works have been classified in four key topics: business implications, technical issues, managerial issues, and implementation issues.Enterprise systems, Research

A Case Study on Artefact-based RE Improvement in Practice

Most requirements engineering (RE) process improvement approaches are solution-driven and activity-based. They focus on the assessment of the RE of a company against an external norm of best practices. A consequence is that practitioners often have to rely on an improvement approach that skips a profound problem analysis and that results in an RE approach that might be alien to the organisational needs. In recent years, we have developed an RE improvement approach (called \emph{ArtREPI}) that guides a holistic RE improvement against individual goals of a company putting primary attention to the quality of the artefacts. In this paper, we aim at exploring ArtREPI's benefits and limitations. We contribute an industrial evaluation of ArtREPI by relying on a case study research. Our results suggest that ArtREPI is well-suited for the establishment of an RE that reflects a specific organisational culture but to some extent at the cost of efficiency resulting from intensive discussions on a terminology that suits all involved stakeholders. Our results reveal first benefits and limitations, but we can also conclude the need of longitudinal and independent investigations for which we herewith lay the foundation

Using the ISO/IEC 9126 product quality model to classify defects : a Controlled Experiment

Background: Existing software defect classification schemes support multiple tasks, such as root cause analysis and process improvement guidance. However, existing schemes do not assist in assigning defects to a broad range of high level software goals, such as software quality characteristics like functionality, maintainability, and usability. Aim: We investigate whether a classification based on the ISO/IEC 9126 software product quality model is reliable and useful to link defects to quality aspects impacted. Method: Six different subjects, divided in two groups with respect to their expertise, classified 78 defects from an industrial web application using the ISO/IEC 9126 quality main characteristics and sub-characteristics, and a set of proposed extended guidelines. Results: The ISO/IEC 9126 model is reasonably reliable when used to classify defects, even using incomplete defect reports. Reliability and variability is better for the six high level main characteristics of the model than for the 22 sub- characteristics. Conclusions: The ISO/IEC 9126 software quality model provides a solid foundation for defect classification. We also recommend, based on the follow up qualitative analysis performed, to use more complete defect reports and tailor the quality model to the context of us

The uses of process modeling : a framework for understanding modeling formalisms

There is wide-spread recognition of the urgent need to improve software processes in order to improve the performance of software organizations. Process models are essential in achieving understanding and visibility of processes and are important for other uses including the analysis of processes for improvement. It has been increasingly difficult to compare and evaluate the variety of process modeling formalisms that have appeared in recent years without a clear understanding of precisely for what they will be used. The contribution of this paper is to provide an understanding and a fairly comprehensive catalog of the applications of process modeling for which formalisms may be used. The primary mechanism for doing this is a guided tour of the literature on process modeling supplemented by recent industrial experience. In the paper, basic definitions concerning processes, process descriptions and process modeling are reviewed and then uses of process modeling are surveyed under the following headings: communication among process participants, construction of new processes, control of processes, process· analysis, and process support by automation. Comments are offered on paradigms for process modeling formalisms and directions for future work to permit evolution of a discipline of process engineering are given

An integrated approach to supply chain risk analysis

Despite the increasing attention that supply chain risk management is receiving by both researchers and practitioners, companies still lack a risk culture. Moreover, risk management approaches are either too general or require pieces of information not regularly recorded by organisations. This work develops a risk identification and analysis methodology that integrates widely adopted supply chain and risk management tools. In particular, process analysis is performed by means of the standard framework provided by the Supply Chain Operations Reference Model, the risk identification and analysis tasks are accomplished by applying the Risk Breakdown Structure and the Risk Breakdown Matrix, and the effects of risk occurrence on activities are assessed by indicators that are already measured by companies in order to monitor their performances. In such a way, the framework contributes to increase companies' awareness and communication about risk, which are essential components of the management of modern supply chains. A base case has been developed by applying the proposed approach to a hypothetical manufacturing supply chain. An in-depth validation will be carried out to improve the methodology and further demonstrate its benefits and limitations. Future research will extend the framework to include the understanding of the multiple effects of risky events on different processe

A collective artefact design of decision support systems: design science research perspective

Purpose - The knowledge of artefact design in design science research can have an important application in the improvement of decision support systems (DSS) development research. Recent DSS literature has identified a significant need to develop user-centric DSS method for greater relevance with respect to context of use. To address this, this study develops a collective DSS design artefact as method in a practical industry context. Design/methodology/approach - Under the influence of goal-directed interaction design principles the study outlines the innovative DSS artefact based on design science methodology to deliver a cutting-edge decision support solution, which provides user-centric provisions through the use of design environment and ontology techniques. Findings - The DSS artefact as collective IT applications through the application of design science knowledge can effectively be designed to meet decision makers’ contextual needs in an agricultural industry context. Research limitations/implications - The study has limitations in that it was developed in a case study context and remains to be fully tested in a real business context. It is also assumed that the domain decisions can be parameterised and represented using a constraint programming language. Practical implications - We conclude that the DSS artefact design and this development successfully overcomes some of the limitations of traditional DSS such as low user uptake, system obsolescence, low returns on investment and a requirement for continual re-engineering effort. Originality/value - The design science paradigm provides structural guidance throughout the defined process, helping ensure fidelity both to best industry knowledge and to changing user contexts

An Audience Centred Approach to Business Process Reengineering

This paper describes a method for process modelling which is designed to provide guidance to the business process modeller. The method has evolved from our experience of attempting to apply software process modelling approaches to business processes. A major influence on the method has been our observations that a pragmatic approach to notation selection is required in order to maintain a meaningful dialogue with end-users. Business process modelling methods typically fall into two camps. General methods attempt to describe the managerial activities which surround the modelling itself (Coulson-Thomas, 94; GISIP, 95). Specific methods, on the other hand, tend to concentrate on the details of a particular notational approach. However, as with programming languages or design methods, no single notational approach is best suited to all problems. Ideally, the process modeller should be able to incorporate the appropriate notational approach into some coherent generic modelling method.This paper addresses the needs of the modeller at the detailed level without prescribing a specific notation. This is achieved by describing categories of modelling activities which the modeller should undertake within process modelling, and suggesting how notations may be used within these categories. Our method is generally applicable, and is illustrated here by models of processes within the Construction industry