Packaged Software Implementation Requirements Engineering by Small Software Enterprises

Small to medium sized business enterprises (SMEs) generally thrive because they have successfully done something unique within a niche market. For this reason, SMEs may seek to protect their competitive advantage by avoiding any standardization encouraged by the use of packaged software (PS). Packaged software implementation at SMEs therefore presents challenges relating to how best to respond to mismatches between the functionality offered by the packaged software and each SME's business needs. An important question relates to which processes small software enterprises - or Small to Medium-Sized Software Development Companies (SMSSDCs) - apply in order to identify and then deal with these mismatches. To explore the processes of packaged software (PS) implementation, an ethnographic study was conducted to gain in-depth insights into the roles played by analysts in two SMSSDCs. The purpose of the study was to understand PS implementation in terms of requirements engineering (or 'PSIRE'). Data collected during the ethnographic study were analyzed using an inductive approach. Based on our analysis of the cases we constructed a theoretical model explaining the requirements engineering process for PS implementation, and named it the PSIRE Parallel Star Model. The Parallel Star Model shows that during PSIRE, more than one RE process can be carried out at the same time. The Parallel Star Model has few constraints, because not only can processes be carried out in parallel, but they do not always have to be followed in a particular order. This paper therefore offers a novel investigation and explanation of RE practices for packaged software implementation, approaching the phenomenon from the viewpoint of the analysts, and offers the first extensive study of packaged software implementation RE (PSIRE) in SMSSDCs

ERP customization failure: Institutionalized accounting practices, power relations and market forces

Purpose: This paper examines a detailed case study of Enterprise Resource Planning (ERP) customization failure in an Egyptian state-owned company (AML) by drawing on new institutional sociology and its extensions. It explains how ERP customization failure is shaped by the interplay between institutionalised accounting practices, conflicting institutions, power relations and market forces. Methodology/Approach: The research methodology is based on using an intensive case study informed by new institutional sociology, especially the interplay between conflicting institutions, power relations and market forces. Data were collected from multiple sources, including interviews, observations, discussions and documentary analysis. Findings: The findings revealed that the inability of the ERP system to meet the core accounting requirements of the control authorities (the Central Agency for Accountability) was the explicit reason cited for the ERP failure. The externally imposed requirements of the Uniform Accounting System and planning budgets were used to resist both other institutional pressures (from the Holding Company for Engineering Industries) and market and competitive pressures. Research limitations: There are some limitations associated with the use of the case study method, including the inability to generalize from the findings of a single case study, some selectivity in the individuals interviewed, and the subjective interpretation by the researchers of the empirical data. Practical implications: The paper identifies that the interplay between institutional pressures, institutionalised accounting practices, intra-organizational power relations, and market forces contributed to the failure to embed ERP in a major company. Understanding such relationships can help other organisations to become more aware of the factors affecting successful implementation of new ERP systems and provide a better basis for planning the introduction of new technologies. Originality/value of paper: This paper draws on recent research and thinking in sociology, especially the development and application of new institutional sociology. In addition, the paper is concerned with ERP implementation and use and management accounting in a transitional economy, Egypt, and hence contributes to debate about exporting Western accounting practices and other technologies to countries with different cultures and different stages of economic and political development. Classification: Research paper/ case stud

Growth, Integration and Spillovers in the Central and East European Software Industry

This paper explores growth and competitive advantage in CEE software firms; it looks at the role of strategic partnerships and industry (spillover) effects. The empirical analysis is based on survey data from 224 software firms from six CEE countries (Bulgaria, Czech R, Estonia, Serbia, Slovenia, Romania). The results of the descriptive analysis are interpreted from the perspective of the role of capabilities in industrial development. The analysis shows that the patterns of growth are a mix of sector, region and sub--region specific determinants and show important national differences. This suggests that the CEE software industry cannot be considered as a homogenous phenomenon. There is no general tendency towards an expansion in exports; based on our sample only Romania is developing an export oriented software industry. Research shows that the CEE software industry is populated by young, dedicated, domestic firms, which are independent, and privately owned and which are mainly oriented towards localisation of software. They are strongly dependent for trade and production on alliances and strategic partnerships with foreign partners and a small share of technology based partnerships. There is an extensive process of industry upgrading underway, involving country and sub-region specific changes. The spillover effects are significant, through links with clients and intensive intra-industry knowledge transfer through high employment turnover and potentially high knowledge transfer from foreign to local projects. Differences between central and eastern Europe are strong in terms of degree of diversification of software supply, industrial upgrading and quality of demand. The pattern of software development in CEE differs from that in other emerging markets in the sense that it is domestic market oriented, but with an emerging export market for services. Its further growth and upgrading will be strongly dependent on the acquisition of organisational capabilities by local firms

Economics and Engineering for Preserving Digital Content

Progress towards practical long-term preservation seems to be stalled. Preservationists cannot afford specially developed technology, but must exploit what is created for the marketplace. Economic and technical facts suggest that most preservation ork should be shifted from repository institutions to information producers and consumers. Prior publications describe solutions for all known conceptual challenges of preserving a single digital object, but do not deal with software development or scaling to large collections. Much of the document handling software needed is available. It has, however, not yet been selected, adapted, integrated, or deployed for digital preservation. The daily tools of both information producers and information consumers can be extended to embed preservation packaging without much burdening these users. We describe a practical strategy for detailed design and implementation. Document handling is intrinsically complicated because of human sensitivity to communication nuances. Our engineering section therefore starts by discussing how project managers can master the many pertinent details.

The real SAP® Business one cost : a case study of ERP adoption in an SME

This paper reports on a UK based service management Small and Medium-sized Enterprise (SME) that invested into SAP® Business One. The action research case study highlights the real cost and difficulties faced in moving to the one single SAP system and the process that was followed in order to identify third-party vendors that can integrate or customise SAP® Business One. This paper highlights the additional costs required to ensure a ‘fit-for-purpose’ solution to close the gap between strategic needs and the existing SAP Business One solution. The gap itself is illustrated by highlighting 10 key functionalities expected by the given service management SME. The actual implementation cost of the Enterprise Resource Planning (ERP) was found to be approximately double the initial SAP costs. The real costs involve time for, among other things, process reengineering, strategic decision making, software add-ons, staff-training, project-management and software maintenance

Process capability assessments in small development firms

[Abstract}: Assessment-based Software Process Improvement (SPI) programs such as the Capability Maturity Model (CMM), Bootstrap, and SPICE (ISO/IEC 15504) are based on formal frameworks and promote the use of systematic processes and management practices for software development. These approaches identify best practices for the management of software development and when applied, enable organizations to understand, control and improve development processes. The purpose of a SPI assessment is to compare the current processes used in an organization with a list of recommended or ‘best’ practices. This research investigates the adoption of SPI initiatives by four small software development firms. These four firms participated in a process improvement program which was sponsored by Software Engineering Australia (SEA) (Queensland). The assessment method was based on SPICE (ISO/IEC 15504) and included an initial assessment, recommendations, and a follow-up meeting. For each firm, before and after snapshots are provided of the capability as assessed on eight processes. The discussion which follows summarizes the improvements realized and considers the critical success factors relating to SPI adoption for small firms

SMEs COMPETITIVE ADVANTAGE AND ENTERPRISE RESOURCE PLANNING IMPLEMENTATION: FINDING FROM CENTRAL JAVA

Enterprise Resource Planning (ERP) is an integrated application software for widespread use in the organization. The aim of this study is to determine factors that affect the successful implementation of ERP in Small and Medium Enterprises (SMEs) in Central Java in order to build competitive advantage. To test the hypothesis, this study utilized data from 107 SMEs in Central Java. The results revealed that variable Business Process Reengineering have the greatest influence toward the successful implementation in Small and Medium Enterprises. It is suggested that SMEs should gain knowledge and solidify its business process reengineering before implementing ERP

Supply chain control: Trade-offs and system requirements

The official published version can be accessed from the link below.A paper describes the underlying forces which drive change in manufacturing enterprises and supply chains. It sets out the complexities in modern capitalism and global economics and illustrates the trade-offs that can be made. IT systems which are required to assist improvements to both customer service and enterprise manufacturing performance are explained, alluding to the special case for the semiconductor industry. Arguments are presented showing how the new tools being developed with the ESPRIT project 20544, X-CITTIC, will satisfy the control needs for a virtual enterprise. This paper describes the underlying forces which drive change in manufacturing enterprises and supply chains. It sets out the complexities in modem capitalism and global economics and illustrates the trade-offs that can be made. IT systems which are required to assist improvements to both customer service and enterprise manufacturing performance are explained alluding to the special case for the semiconductor industry. Finally it shows how the new tools being developed with the ESPRIT project 20544, XCITTIC, will satisfy the control needs for a virtual enterprise

Towards a methodology for the development of integrated IT infrastructures

In this paper, the authors propose and validate a methodology for the development of integrated Information Technology (IT) infrastructures. The motivation for putting forward a new methodology is grounded on the limitations of the various software engineering methodologies (traditional) that exist today. Despite that the traditional methodologies result in the development of Information Systems (IS) from scratch, Enterprise Application Integration (EAI) builds integrated IT infrastructures using existing applications. This significant difference is associated with many issues needed to be realised and addressed like: (a) the changes that such an infrastructure brings to organisations, (b) the resistance to change and (c) the extension of IS lifecycle’s. The proposed methodology consist of eight stages and aims at supporting software engineers, organisations and researchers to build integrated IT infrastructures. As a result the methodology seeks to contribute to the body of knowledge