Proceedings ICPW'07: 2nd International Conference on the Pragmatic Web, 22-23 Oct. 2007, Tilburg: NL

Proceedings ICPW'07: 2nd International Conference on the Pragmatic Web, 22-23 Oct. 2007, Tilburg: N

Evaluation based on critical systems heuristics

Introduction: Critical systems heuristics (CSH) draws on the substantive work and philosophy of C. West Churchman, a systems engineer who, along with Russell Ackoff during the 1950s and 1960s, defined operations research in the United States. Churchman later pioneered developments in the 1970s of what is now known as 'soft' and 'critical' systemic thinking and practice in the domain of social or human activity systems. Churchman died in 2004. His legacy lies in signalling the importance of being alert to value-laden boundary judgements when making evaluations. Boundaries are what we socially construct in designing and evaluating any human activity system of interest (e.g., any situation of concern from a kinship group, an organisation, or a larger entity such as a national health system). The primary boundary of any human activity systems is defined by 'purpose'. Churchman's work is characterised by a continual ethical commitment to the overarching purpose of improved human well-being. In order to fulfil such purposeful activity, there is always a need to broaden inquiry from the particular system of focus so as to appreciate what Churchman calls the total relevant system. The effectiveness and efficiency of a system of interest depends on the actual boundary judgements associated with that system of interest. Churchman first identified 9 conditions or categories (including the category 'purpose�) associated with any purposeful system of interest in his book The Design of Inquiring Systems [1, 2]. He later extended these to 12 categories in a book provocatively entitled The Systems Approach and Its Enemies, significantly taking into account 3 extra factors (�enemies�) that lie outside the actual system of interest but which can be affected by, and therein have an effect on, the performance of the system [1, 2]. In the early 1980s a doctorate student of Churchman from Switzerland, Werner Ulrich, translated Churchman's 12 categories into an operational set of 12 questions which he called critical systems heuristics [3]. Ulrich returned to Switzerland and worked with CSH as a public health and social welfare policy analyst and program evaluator [4]. Section 2 introduces the basic toolbox of CSH, along with suggestions on when to use it and the benefits of its use. Section 3 will guide you through a suggested operational use of CSH questions in a process of evaluation. Section 4 provides a summary of an extensive case study in which CSH was used for evaluating the role of public participation in natural resource-use planning. Section 5 provides some advice for the practitioner in developing skills on using CSH for evaluation

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications

Towards a reference framework for open source software adoption

Nowadays, the use of Open Source Software (OSS) components has become a driver for the primary and secondary information technology (IT) sector, among other factors, by the openness and innovation benefits that can give to the organizations, regardless of its business model and activities' nature. Nevertheless, IT companies and organizations still face numerous difficulties and challenges when making the strategic move to OSS. OSS is aligned with new challenges, which mainly derive from the way OSS is produced and the culture and values of OSS communities. In fact, OSS adoption impacts far beyond technology, because it requires a change in the organizational culture and reshaping IT decision-makers mindset. Therefore, this research work proposes a framework to support OSS adopters (i.e., software-related organizations that develop software and/or offer services relate to software) to analyze and evaluate the impact of adopting OSS as part of their software products and/or services offered to their customers/users, mainly in terms of their software related activities.Peer ReviewedPostprint (published version

Critical knowledge map as a decision tool for knowledge transfer actions

Knowledge transfer is no longer reducible to classical solutions such as face-to-face training, technical education or tutoring. Knowledge to be transferred is professional knowledge (Business Knowledge). It involves the whole Knowledge Capital within an organization. Identifying the knowledge components that are worthwhile transferring is not an easy task. This is the problem addressed in this paper.Knowledge transfer, Knowledge Management, Knowledge mapping, Knowledge capitalization