Validating the Information Systems Design Theory for Dual Information Systems

Conceptual designs of most information systems (IS) reflect a design/use dualism of technology making it difficult for users to be responsible for computerized aspects of work. The IS design theory (ISDT) for Dual Information Systems (DIS) helps bridge the design/use dualism. Its validity has not been studied empirically. This paper presents and applies a model that helps examine the validity of the ISDT. A domain-specific ISDT for Dual Change Management IS (DCMIS) is designed and applied to evaluate a change management IS (CMIS) in an organization responsible for managing a globally deployed enterprise resource planning system. The ISDT for DIS is found applicable for designing the ISDT for DCMIS, showing that IS theory development can be based on paradigms endogenous to the field. The ISDT for DCMIS can be utilized to solve problems in the use of the CMIS. It makes the ISDT for DIS increasingly tractable for practical applications

Validation of Crisis Response Simulation within the Design Science Framework

In design science research in information systems (DSRIS), validation is often neglected in exchange for an emphasis on evaluation. However, rigorous scientific contributions most often explicitly address validation. In order to address the complexity of validation within design science, an explicit recognition of the assumptions and methods used within the DSRIS framework is needed. In this paper we discuss an approach to validation in a research in progress aimed at theory development in coordination of crisis response, through the use of agent-based simulation. This enables validation to be discussed from the point of view of simulation, the agent-based approach and the domain of crisis response, underpinned by a hermeneutical epistemology. Other research endeavors within DSRIS can follow a similar strategy to deal with the issue of validation

Using SPI Manifesto to Recover from CRM Deployment Project Failures and to Proactively Eliminate Similar Failures in Future: An Action Research Study in a Russian organization

The deployment of software products such as Customer Relationship Management systems may seem straightforward when reading the success stories of software providers. Yet, deployment projects are risky and often fail. Ineffective deployment processes of software providers and systems integrators are a major cause of failures. SPI Manifesto is a recent attempt to help the providers improve their processes, so most failures in software development may be eliminated proactively. Yet, the effectiveness and validity of SPI Manifesto relative to deployment projects are unclear. This paper presents an action research study in a customer organization to assess the extent to which SPI Manifesto could be used to help the providers to recover from situations in which CRM deployment projects are about to fail and to eliminate similar problems proactively in future. Based on the assessment, this paper contributes to improving the generic CRM deployment project process and SPI Manifesto

Design and Development of a Patient-Centered E-Health System to Improve Patient Understanding at Discharge

E-health systems are often designed without considering user-centered design principles. Past research on the topic of patient-centered e-health (PCEH) has lacked focus on the design and development of a PCEH artifact and the process for its development. In this study, information systems design theory (ISDT) is applied to design, develop, and evaluate an e-health system based on PCEH principles. The goal of the artifact in this study is to improve patient understanding of diagnoses, procedures, medications, and post-discharge instructions and empower patients with the information needed pre- and post-discharge to make informed healthcare decisions. The artifact justification, meta-requirements, meta-design, development, and evaluation are presented in multiple iterations—beginning with a simple picture book, and ending with a Web-based, mobile, multimedia system. Findings indicate that a PCEH approach can be useful for achieving multiple design goals. The artifact illustrates achievement of an important organizational quality improvement goal for the case study organization involved, a key physician goal to improve patient-physician engagement, and an important patient goal—to improve understanding about patient-specific diagnoses and health conditions prior to discharge from a hospital visit and initiation of home health care

Requirement engineering best practices for Malaysian public sector

Although a variety of ICT standards have been developed as a guide for IT Managers, the Malaysian Public Sector is in tandem by developing new policies for them. The need of Requirement Engineering Best Practices for IT Manager is to produce an appropriate Software Requirement Specification. The proposed Requirement Engineering Best Practices aims to be a standard for the Malaysian Public Sector. The need of the standard is to resolve identified complexity during software project development. The complexity of present Requirement Engineering models and standard is either too specific or too general. These models do not meet the Public Sector’s requirement and the IT Manager depends on other proposed solution or does not use any Requirement Engineering models and standard. The complexity of present software process drives the Malaysian Public Sector to create several committees for monitoring the implementation of software project. It also includes several rules and policy. The rules and policy were prepared by different or multiple agencies and is complex to understand. The proposed software projects have to go through several levels of software project approval. This process is repeated and really took times to be approved. These complexities can be overcome with a proposal of Requirement Engineering Best Practices Guideline. The development of Requirement Engineering Best Practices Guideline is implemented based on the Requirement Engineering Best Practices Guideline Research Framework. This framework used with mixed method. Qualitative techniques were used for interview, refinement and validation. Meanwhile, quantitative techniques were used for the survey. Target respondents for this research are IT Managers in the Malaysian Public Sector. The guideline also consists of identified requirement processes: Software Project Approval Process, Software Requirement Specification Approval Process, Software Requirement Specification Activity Diagram and Software Requirement Specification Development Procedure. The proposed best practices is developed using the mutation and the mapping process between defined Requirement Engineering Process, Software Project Success Factor and Requirement Engineering Critical Issues which were explained in Requirement Engineering Best Practices Framework. This guideline also aligns with the ICT standard. The Requirement Engineering Best Practices had been tested with a pilot test by selected IT Managers and the actual survey had been randomly distributed to IT Manager in Malaysian Public Sector. Furthermore, the guideline had been refined by ICT experts using Delphi techniques. The proposed guideline fulfilled the criteria: completeness, sufficiency, reliability and acceptance. This compliance was validated by selected ICT experts who have different backgrounds and experiences. The proposed guideline will guide IT Managers in implementing the requirement gathering process and will also improve the Software Requirement Specification Process