This paper explores the issue of whether the field of IS is in crisis. To do so, the paper first starts by looking back on where the field has come from. Next, it assesses the status of the IS field by exploring where the field is now. That our current status remains a ‘fragmented
adhocracy’ suggests the field may indeed be in crisis or headed for a crisis. This is compounded by the fact that there are two different views on the state of the IS field, each posing its own set of threats. One is the external view of the community (the view of IS from outside the academic field); the other is the internal view (the view from inside the IS community). By analyzing these two views, a better understanding of the problems the field faces emerges. In the next part of the paper, some thoughts are presented on where might the field go from here for overcoming its internal communication deficit. The paper proposes four different types of knowledge for structuring an IS Body of Knowledge (BoK) and
following on from that, the value of creating a common BoK for the field. Lastly, the implications arising from the paper’s analysis are explored. More specifically, the paper
considers various options that are available for overcoming the internal communications deficit the IS field faces. These include changing the way the field thinks about generalizations, changing the institutional publication practices, focusing more on understanding the field’s organizational stakeholders, and developing new knowledge creation and transformation networks. If IS as a field can overcome its internal communications deficits, it might ultimately contribute to the societal challenge of developing a deliberative cyber democracy and thereby help to address the social communication deficit which is a feature of modern mass societies.

Crisis in the IS field? A critical reflection on the state of the discipline

A review of biometric technology along with trends and prospects

Role of multiple stakeholders and the critical success factor theory for the sustainable supplier selection process

The elicitation or communication of user requirements comprises an early and critical but highly error-prone stage in system development. Socially oriented methodologies provide more support for user involvement in design than the rigidity of more traditional methods, facilitating the degree of user---designer communication and the `capture' of requirements. A more emergent and collaborative view of requirements elicitation and communication is required to encompass the user, contextual and organisational factors. From this accompanying literature in communication issues in requirements elicitation, a four-dimensional framework is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship between users and designers. The facilitation of communication between users and designers is subject to discussion of the ways in which communicative activities can be `optimised' for successful requirements gathering, by making recommendations based on the four dimensions to provide fruitful considerations for system designers.

/pdf/effective-communication-in-requirements-elicitation-a-1hh2y1dn4p.pdf

Effective Communication in Requirements Elicitation: A Comparison of Methodologies

Determining the factors that have an influence on software systems development and deployment project outcomes has been the focus of extensive and ongoing research for more than 30 years. We provide here a survey of the research literature that has addressed this topic in the period 1996–2006, with a particular focus on empirical analyses. On the basis of this survey we present a new classification framework that represents an abstracted and synthesized view of the types of factors that have been asserted as influencing project outcomes.

Factors that affect software systems development project outcomes: A survey of research

The main goal of this research is to understand is there any difference between ERP implementation's CSF in developed and developing countries? Understanding this subject can help us to implement ERP systems properly in developing nations. This research showed that in developed and developing countries "Change Management" was most important factor and in developed countries "Country-related functional requirements" factor was less important factor and "Fit between ERP and business/process" was the least cited factor among developing nations. In last it concluded that national culture of developing countries has an impressive effect on ERP implementation in these countries. In other hand developing countries companies more depend on ERP vendors in compare to developed countries companies. In addition it seems developing countries underestimate business process reengineering (BPR) and fit between ERP and business/process factors in comparison with developed countries.

A Comparative Study of Critical Success Factors (CSFs) in Implementation of ERP in Developed and Developing Countries

We discuss our approach to constructing user requirements whereby users build requirements models themselves. The approach, termed user-led requirements construction (ULRC), is a social process that addresses a major problem: the user-developer culture gap. An important feature of the approach is that we have conducted, with users, an interpretivist empirical evaluation study of its constituent event flow diagram (EFD) modelling method and associated training. The ULRC has also been used in a live environment. The results are that users regard the EFD as effective for the requirements process, the EFD may be used for further studies to deepen our knowledge of the requirements process and the results contribute towards a set of public results for general evaluation and improvement.

Constructing user requirements: a social process for a social context

By developing research and academic centers, the number of performed research articles has also increased. On the other hand, publishing the results of these articles in scientific journals shall also grow. In the meantime, researchers are trying to publish the findings of their research in journals which have been approved by one or more international indices so that such findings can be seen. In order to enhance the academic standards of Universities, proper journal choice will be of interest to researchers, especially those that are indexed in websites such as Thomson Reuters. However, certain forgery frauds researchers by launching fake Web sites that have been named by academic journal titles. In this paper, we introduce an approach to identify this type of journals that will be applicable by researchers in various academic disciplines.

How Can We Identify Hijacked Journals

Characteristics of Hijacked Journals and Predatory Publishers: Our Observations in the Academic World

ERP implementation had always been a complicated process, but it seems it is difficult for business and companies to overlook of assets of these information systems. Iran is a developing country and tries to improve its economy and compete with other economies. Studying ERP implementation in such country which has not had noticeable experiences in this area can be interesting for developers, vendors and other similar cases in developing countries. In this research we will investigate ERP implementation in first Iranian pioneer company that implemented and used this system. Our evaluation will be base on CSFs (Critical Success Factor) which cited as index for success of ERP implementation in others researches.

/pdf/evaluation-of-the-erp-implementation-at-esfahan-steel-3uk13ipur5.pdf

Mohammad Davarpanah Jazi

Papers

A Comparative Study of Critical Success Factors (CSFs) in Implementation of ERP in Developed and Developing Countries

Constructing user requirements: a social process for a social context

How Can We Identify Hijacked Journals

Characteristics of Hijacked Journals and Predatory Publishers: Our Observations in the Academic World

Evaluation of the ERP Implementation at Esfahan Steel Company Based on Five Critical Success Factors: A Case Study