Reflections on issues of power in packaged software selection

The adoption of packaged software is becoming increasingly common in a variety of organizations and much of the packaged software literature presents this as a straightforward, linear process based on rationalistic evaluation. This paper applies the framework of power relations developed by Markus and Bjørn-­‐Anderson (1987) to a longitudinal study concerning the adoption of a customer relationship management package in a small organization. This is used to highlight both overt and covert power issues within the selection and procurement of the product and illustrate the interplay of power between senior management, IT managers, IT vendors and consultants, and end-­‐users. The paper contributes to the growing body of literature on packaged software and also to our understanding of how power is deeply embedded within the surrounding processes.

IT consultants, salesmanship and the challenges of packaged software selection in SMEs

Purpose – This paper seeks to analyse the process of packaged software selection in a small organization, focussing particularly on the role of IT consultants as intermediaries in the process. Design/methodology/approach – This is based upon a longitudinal, qualitative field study concerning the adoption of a customer relationship management package in an SME management consultancy. Findings – The authors illustrate how the process of “salesmanship”, an activity directed by the vendor/consultant and focussed on the interests of senior management, marginalises user needs and ultimately secures the procurement of the software package. Research limitations/implications – Despite the best intentions the authors lose something of the rich detail of the lived experience of technology in presenting the case study as a linear narrative. Specifically, the authors have been unable to do justice to the complexity of the multifarious ways in which individual perceptions of the project were influenced and shaped by the opinions of others. Practical implications – Practitioners, particularly those from within SMEs, should be made aware of the ways in which external parties may have a vested interest in steering projects in a particular direction, which may not necessarily align with their own interests. Originality/value – This study highlights in detail the role of consultants and vendors in software selection processes, an area which has received minimal attention to date. Prior work in this area emphasises the necessary conditions for, and positive outcomes of, appointing external parties in an SME context, with only limited attention being paid to the potential problems such engagements may bring.

The social shaping of packaged software selection

As organisations increasingly engage in the selection, purchase, and adoption of packaged software products, how these activities are carried out in practice becomes increasingly relevant for researchers and practitioners. Our focus in this paper is to propose a framework for understanding the packaged software selection process. The functionalist literature on this area of study suggests a number of generic recommendations, which are based on rational assumptions about the process and view the decision making that takes place as producing the “best technology solution.’” To explore this, we conducted a longitudinal, in-depth study of packaged software selection in a small organisation. For interpretation of the case, we draw upon the Social Construction of Technology, a theoretical framework arguing that technology is socially constituted and regarding the process of development as contradictory and uncertain. We offer a number of contributions. First, we further our understanding of packaged software selection with the critique that we offer of the functionalist literature, drawing insights from the emerging critical/constructivist literature and expanding our domain of interest to encompass the wider environment. Second, we weave this together with our experiences in the field, drawing on social constructivism for theoretical support, to develop a framework of packaged software selection that shows how various actors shape the process.

CRM packaged software : a study of organisational experiences

Customer Relationship Management (CRM) packaged software has become a key contributor to attempts at aligning business and IT strategies in recent years. Throughout the 1990s there was, in many organisations strategies, a shift from the need to manage transactions and toward relationship management. Where Enterprise Resource Planning packages dominated the management of transactions era, CRM packages lead in regard to relationships. At present, balanced views of CRM packages are scantly presented instead relying on vendor rhetoric. This paper uses case study research to analyse some of the issues associated with CRM packages. These issues include the limitations of CRM packages, the need for a relationship orientation and the problems of a dominant management perspective of CRM. It is suggested that these issues could be more readily accommodated by organisational detachment from beliefs in IT as utopia, consideration of prior IS theory and practice and a more informed approach to CRM package selection.

Potential pitfalls in packaged software adoption

The common reasons for those in organizations adopting large config- urable packaged software products are compelling. Problems with the existing software situation, the supposed predictability and perceived business benefits of packaged software, and various social influences, can lead to packages being preferred to custom approaches. Yet, for every reason, there is a potential associated problem that must be understood before an informed adoption decision can be made...

Achieving enterprise integration through software customization : part I-evidence from the field

Achieving business and IT integration is strategic goal for many organisations – it has almost become the ‘Holy Grail’ of organisational success. In this environment Enterprise Resource Planning (ERP) packages have become the defacto option for addressing this issue. Integration has come to mean adopting ERP, through configuration and without customization, but this all or nothing approach has proved difficult for many organisations. In part 1 of a 2 part update we provide evidence from the field that suggests that whilst costly, if managed appropriately, customization can have value in aiding organisational integration efforts. In part 2, we discuss in more detail the benefits and pitfalls involved in enacting a non-standard based integration strategy.

Achieving enterprise integration through software customization : part II-enacting the strategy

In part 1 of this update, we put forward the argument that integration in ERP based environments can be achieved in ways other than adopting a software configuration only approach. We drew on evidence from two large ERP implementations to show how, despite the cost implications, some customization, if carefully managed, could prove helpful. In this, the final part of the update, we discuss the benefits, and potential pitfalls, involved in enacting a non-standard based integration strategy. This requires attention to a) broadening the integration definition; b) bringing legacy practices forward and c) developing a customization based integration strategy.

Vagueness and software engineering

We do not commonly associate software engineering with philosophical debate. Indeed, software engineers ought to be concerned with building software systems and not settling philosophical questions. I attempt to show that software engineers do, in fact, take philosophical sides when designing software applications. In particular, I look at how the problem of vagueness arises in software engineering and argue that when software engineers solve it, they commit to philosophical views that they are seldom aware of. In the second part of the paper, I suggest a way of dealing with vague predicates without having to confront the problem of vagueness itself. The purpose of my paper is to highlight the currently prevalent disconnect between philosophy and software engineering. I claim that a better knowledge of the philosophical debate is important as it can have ramifications for crucial software design decisions. Better awareness of philosophical issues not only produces better software engineers, it also produces better engineered products.

Biceps femoris long-head architecture: A reliability and retrospective injury study

Purpose: To determine i) the reliability of two-dimensional ultrasonography for the assessment of biceps femoris long head (BFlh) architectural characteristics; ii) if limbs with a history of strain injury in the BFlh display different architecture and eccentric strength compared to uninjured limbs. Methods: This case-control study (control [n=20], injured group [n=16], males) assessed the BFlh architecture at rest and during graded isometric contractions using two-dimensional ultrasonography. The control group were assessed three times (>24hrs apart) to determine reliability. Previously injured individuals were evaluated once. Results The assessment of BFlh architecture was highly reliable (intraclass correlations >0.90). Fascicle length (p<0.001; d range: 0.67 to 1.34) and fascicle length relative to muscle thickness (p<0.001; d range: 0.58 to 0.85) of the previously injured BFlh were significantly less than the contralateral uninjured BFlh at all intensities. Pennation angle of the previously injured BFlh was significantly greater (p<0.001; d range: 0.62 to 0.88) than the contralateral uninjured BFlh at all intensities. Eccentric strength in the previously injured limb was significantly lower than the contralateral limb (-15.4%; -52.5N; 95% CI=-28.45 to -76.23; p<0.001, d=0.56). Conclusion These data indicate that two-dimensional ultrasonography is reliable for assessing BFlh architecture at rest and during graded isometric contractions. Fascicle length, fascicle length relative to muscle thickness and pennation angle are significantly different in previously injured BFlh compared to an uninjured contralateral BFlh. Eccentric strength of the previously injured limb is also significantly lower than the uninjured contralateral limb. These findings have implications for rehabilitation and injury prevention practices which should consider altered architectural characteristics.

In pursuit of an architecture realism

The noble idea of studying seminal works to ‘see what we can learn’ has turned in the 1990s into ‘let’s see what we can take’ and in the last decade a more toxic derivative ‘what else can’t we take’. That is my observation as a student of architecture in the 1990s, and as a practitioner in the 2000s. In 2010, the sense that something is ending is clear. The next generation is rising and their gaze has shifted. The idea of classification (as a means of separation) was previously rejected by a generation of Postmodernists; the usefulness of difference declined. It’s there in the presence of plurality in the resulting architecture, a decision to mine history and seize in a willful manner. This is a process of looking back but never forward. It has been a mono-culture of absorption. The mono-culture rejected the pursuit of the realistic. It is a blanket suffocating all practice of architecture in this country from the mercantile to the intellectual. Independent reviews of Australia’s recent contributions to the Venice Architecture Biennales confirm the malaise. The next generation is beginning to reconsider classification as a means of unification. By acknowledging the characteristics of competing forces it is possible to bring them into a state of tension. Seeking a beautiful contrast is a means to a new end. In the political setting, this is described by Noel Pearson as the radical centre[1]. The concept transcends the political and in its most essential form is a cultural phenomenon. It resists the compromised position and suggests that we can look back while looking forward. The radical centre is the only demonstrated opportunity where it is possible to pursue a realistic architecture. A realistic architecture in Australia may be partially resolved by addressing our anxiety of permanence. Farrelly’s built desires[2] and Markham’s ritual demonstrations[3] are two ways into understanding the broader spectrum of permanence. But I think they are downstream of our core problem. Our problem, as architects, is that we are yet to come to terms with this place. Some call it landscape others call it country. Australian cities were laid out on what was mistaken for a blank canvas. On some occasions there was the consideration of the landscape when it presented insurmountable physical obstacles. The architecture since has continued to work on its piece of a constantly blank canvas. Even more ironic is the commercial awards programs that represent a claim within this framework but at best can only establish a dialogue within itself. This is a closed system unable to look forward. It is said that Melbourne is the most European city in the southern hemisphere but what is really being described there is the limitation of a senseless grid. After all, if Dutch landscape informs Dutch architecture why can’t the Australian landscape inform Australian architecture? To do that, we would have to acknowledge our moribund grasp of the meaning of the Australian landscape. Or more precisely what Indigenes call Country[4]. This is a complex notion and there are different ways into it. Country is experienced and understood through the senses and seared into memory. If one begins design at that starting point it is not unreasonable to think we can arrive at an end point that is a counter trajectory to where we have taken ourselves. A recent studio with Masters students confirmed this. Start by finding Country and it would be impossible to end up with a building looking like an Aboriginal man’s face. To date architecture in Australia has overwhelmingly ignored Country on the back of terra nullius. It can’t seem to get past the picturesque. Why is it so hard? The art world came to terms with this challenge, so too did the legal establishment, even the political scene headed into new waters. It would be easy to blame the budgets of commerce or the constraints of program or even the pressure of success. But that is too easy. Those factors are in fact the kind of limitations that opportunities grow out of. The past decade of economic plenty has, for the most part, smothered the idea that our capitals might enable civic settings or an architecture that is able to looks past lot line boundaries in a dignified manner. The denied opportunities of these settings to be prompted by the Country they occupy is criminal. The public realm is arrested in its development because we refuse to accept Country as a spatial condition. What we seem to be able to embrace is literal and symbolic gestures usually taking the form of a trumped up art installations. All talk – no action. To continue to leave the public realm to the stewardship of mercantile interests is like embracing derivative lending after the global financial crisis.Herein rests an argument for why we need a resourced Government Architect’s office operating not as an isolated lobbyist for business but as a steward of the public realm for both the past and the future. New South Wales is the leading model with Queensland close behind. That is not to say both do not have flaws but current calls for their cessation on the grounds of design parity poorly mask commercial self interest. In Queensland, lobbyists are heavily regulated now with an aim to ensure integrity and accountability. In essence, what I am speaking of will not be found in Reconciliation Action Plans that double as business plans, or the mining of Aboriginal culture for the next marketing gimmick, or even discussions around how to make buildings more ‘Aboriginal’. It will come from the next generation who reject the noxious mono-culture of absorption and embrace a counter trajectory to pursue an architecture of realism.

Dataset validation within big data security architecture

In recent years, increasing focus has been made on making good business decisions utilizing the product of data analysis. With the advent of the Big Data phenomenon, this is even more apparent than ever before. But the question is how can organizations trust decisions made on the basis of results obtained from analysis of untrusted data? Assurances and trust that data and datasets that inform these decisions have not been tainted by outside agency. This study will propose enabling the authentication of datasets specifically by the extension of the RESTful architectural scheme to include authentication parameters while operating within a larger holistic security framework architecture or model compliant to legislation.