8,918 research outputs found

    Using grounded theory to understand software process improvement: A study of Irish software product companies

    Get PDF
    Software Process Improvement (SPI) aims to understand the software process as it is used within an organisation and thus drive the implementation of changes to that process to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs. Accordingly, SPI researchers must be equipped with the methodologies and tools to enable them to look within organisations and understand the state of practice with respect to software process and process improvement initiatives, in addition to investigating the relevant literature. Having examined a number of potentially suitable research methodologies, we have chosen Grounded Theory as a suitable approach to determine what was happening in actual practice in relation to software process and SPI, using the indigenous Irish software product industry as a test-bed. The outcome of this study is a theory, grounded in the field data, that explains when and why SPI is undertaken by the software industry. The objective of this paper is to describe both the selection and usage of grounded theory in this study and evaluate its effectiveness as a research methodology for software process researchers. Accordingly, this paper will focus on the selection and usage of grounded theory, rather than results of the SPI study itself

    Embrapa Technological Information: a bridge between research and society

    Get PDF
    This paper presents the efforts undertaken by the Brazilian Agricultural Research Corporation regarding Science and Technology information management, through one of its Decentralized Units, Embrapa Technological Information (Scientific and Technological Information Service', SCT). The major aim of SCT is to promote and improve the processes of scientific communication - information that feeds and that results from research activities - and of science and technology dissemination - information that results from research activities and that is directed to the general publi

    Safer clinical systems : interim report, August 2010

    Get PDF
    Safer Clinical Systems is the Health Foundation’s new five year programme of work to test and demonstrate ways to improve healthcare systems and processes, to develop safer systems that improve patient safety. It builds on learning from the Safer Patients Initiative (SPI) and models of system improvement from both healthcare and other industries. Learning from the SPI highlighted the need to take a clinical systems approach to improving safety. SPI highlighted that many hospitals struggle to implement improvement in clinical areas due to inherent problems with support mechanisms. Clinical processes and systems, rather than individuals, are often the contributors to breakdown in patient safety. The Safer Clinical Systems programme aimed to measure the reliability of clinical processes, identify defects within those processes, and identify the systems that result in those defects. Methods to improve system reliability were then to be tested and re-developed in order to reduce the risk of harm being caused to patients. Such system-level awareness should lead to improvements in other patient care pathways. The relationship between system reliability and actual harm is challenging to identify and measure. Specific, well-defined, small-scale processes have been used in other programmes, and system reliability has been shown to have a direct causal relationship with harm (e.g. care bundle compliance in an intensive care unit can reduce the incidence of ventilator-associated pneumonia). However, it has become evident that harm can be caused by a variety of factors over time; when working in broader, more complex and dynamic systems, change in outcome can be difficult to attribute to specific improvements and difficulties are also associated with relating evidence to resulting harm. The overall aim of Phase 1 of the Safer Clinical Systems programme was to demonstrate proof-of-concept that using a systems-based approach could contribute to improved patient safety. In Phase 1, experienced NHS teams from four locations worked together with expert advisers to co-design the Safer Clinical Systems programme

    Towards developing a software process improvement strategy through the application of ethical concepts

    Get PDF
    Aligning Software Process Improvement with the business and strategic goals of an enterprise is a core factor for process improvement. Achieving success in Software Process Improvement (SPI) has shown to be a problematic challenge for countless organisations. SPI, as a discipline, can be described as a set of use cases, each use case describing the logically related activities that must be undertaken. In addition, each use case is a description of the interactions between itself and the participants, i.e. the Actors. The nature of these interactions more often than not may demand, from the participant, the recognition, and fulfilment, of ethical duties. In this paper we customise a theoretical framework developed by the US Content Subcommittee of the Impact CS Steering Committee that specifies traditional moral and ethical concepts, which can be used to identify the moral issues concerning the Software Process Improvement field. An application of these conventional and generic ethical concepts is made to use cases such as: Determining Business Needs; Conducting Process Improvement Assessment; the Tailoring and Creation of Processes; and Deployment. In doing so a number of ethical issues are highlighted. In the application and utilisation of SPI: business process engineers, software engineering teams, process improvement managers, and so on must be aware of these ethical duties, which have been identified by the application of the moral and ethical concepts, as presented in this paper, in order to become more responsible professionals in general. We propose a set of heuristics for ethical engagement with the SPI discipline proposing that an effective SPI strategy must be underpinned with ethical consideration

    Hospitality in necessitudine : hospices, hostels and hospitals

    Get PDF
    In the continuing series reflecting on hospitality Mario Conti, Kevin O'Gorman and David McAlpine explore an aspect of hospitality often overlooked - the constantly evolving religious practice of providing hospitality to those in most need. They present an overview of the evolution of hospitality for the needy and consider how throughout history, even when religion is under attack, there has always been recognition of the importance of charitable hospitality: hospitality in necessitudine

    Motivators and de-motivators in software process improvement : an empirical study

    Get PDF
    Software quality problems are a concern for the software engineering community. Software Process Improvement (SPI) is the most recent and most popular approach adopted to address this problem. SPI focuses on the processes that develop software in order to deliver improvements to the product. Despite this popularity of SPI there is insufficient evidence of its successful impact on software quality. Quality problems in software continue. This has led to some concern in the industry about the effectiveness of SPI in tackling the problem of software quality. There is evidence to suggest that SPI does improve software quality. However, there is also evidence to suggest that SPI is not sufficiently supported by software practitioners. This lack of support may be one of the reasons why SPI appears to be failing at tackling the problem of software quality. In this research it is argued that this lack of support for SPI is caused by companies' inability to manage software practitioners' motivation for SPI properly. Companies may not be managing software practitioners' motivation for SPI properly because they may not understand them. There is therefore a need to better understand what software practitioners'motivations for supporting SPI are. A review of the literature suggests a set of guidelines that can improve software practitioners' support for SPI. The literature also suggests four themes that underpin software practitioners' motivation for SPI. The four themes are SPI managers' perception of the motivators and demotivators for SPI, software practitioners' motivators, software practitioners' de-motivators and the differences in software practitioners' motivators and de-motivators. The basis of this research is that exploring the four themes that underpin software practitioners' motivation for SPI improves understanding of the factors that influence support for SPI. This knowledge of the factors that influence support for SPI can then be used to validate and provide an empirical basis for the literature-suggested guidelines. Thereby improving confidence in the "-IL iidelines. The four themes underpinning software practitioners' motivation for SPI are examined through empirical studies. Findings from these studies suggest that SPI managers perceive senior managers as not supportive of SPI. They also perceive developers as not enthusiastic about SPI. The findings also suggest that the key motivators of software practitioners for SPI are visible support and commitment from senior management and empowerment of practitioners, whereas the key de-motivators are related to constraints on resources and a failure to secure practitioners' buy-in for SPI. There are also differences in what motivates and de-motivates different practitioner groups for SPI and these differences are related to the jobs that practitioners do. Finally, software practitioners have different perceptions of their role in SPI, which are related to their software development roles. This suggests that the objectives of SPI should be tailored to the software development objectives of practitioners in order to improve their support for SPI. Overall, findinas from these studies confirm most of the guidelines suggested by the t:, literature. The confirmed guidelines are offered as insight to improving support for SPI, which can in turn help to improve the impact of SPI on software quality

    The proposal of adding a society value to the software process improvement manifesto

    Get PDF
    The use of computers has become ubiquitous and spread out to every part of our personal lives and businesses. Computer Ethics focuses on the questions of right and wrong that arise from the development and deployment of computers. Thus, it urges that the social impact of computers must be analysed. In software engineering, the Software Process Improvement (SPI) Manifesto was developed by groups of experts in the field and aimed to improve the software produced, by improving the process, the attitudes of software engineers, and the organisational culture and practices. The manifesto is centred on three basic values: people, business focus and organisational change, underpinning the philosophy of software process improvement; and ten corresponding principles, which serve as foundations for action. In this paper, we argue that SPI professionals, need to, in addition to fulfilling duties to the Organisation, the Business, the Employees who participate in SPI, and the People who will be most affected, broaden their obligations to include wider society. The impact of developed and deployed software systems is often beyond the organisation and affects the daily lives and activities of citizens in society. This paper argues for the inclusion, in the SPI Manifesto, of a fourth value titled Society, along with six corresponding principles. These half-dozen principles are based on traditional moral and ethical concepts, sourced from the field of Computer Ethics. This proposed revision to the SPI manifesto would explicitly espouse the notion of serving the public interest. It will likely help SPI professionals to remember that working in the public interest is also important in Software Process Improvement, thus, making the duty to society clear and obvious or evident

    Extractive Industries

    Get PDF
    "New initiatives recognize that resource wealth can provide a means, when properly used, for poorer nations to decisively break with poverty by diversifying economies and funding development spending. Extractive Industries: The Management of Resources as a Driver of Sustainable Development explores the challenges and opportunities facing developing countries in using oil, gas, and mining to achieve inclusive change. While resource wealth can yield prosperity it can also, when mismanaged, cause acute social inequality, deep poverty, environmental damage, and political instability. There is a new determination to improve the benefits of extractive industries to their host countries, and to strengthen the sector's governance. Extractive Industries provides a comprehensive contribution to what must be done in this sector to deliver development, protect often fragile environments from damage, enhance the rights of affected communities, and support climate change action. It brings together international experts to offer ideas and recommendations in the main policy areas. With a breadth of collective insight and experience, it argues that more attention must be given to the development role of extractive industries, and looks to the future to explain how action on climate change will profoundly shape the sector's prospects.
    corecore