A systematic literature review of green software development in collaborative knowledge management environment

Background: Main asset in software industry is knowledge of employees who work in software development. Knowledge is main asset to succeed in green sustainable development. There is no research about to implement techniques of Knowledge Management (KM) in order to help in managing knowledge of Green Software Development (GSD). This is the research gap. Aims: This paper assesses literature on GSD in regards to the evolution of green computing, and discusses about how KM comes in to assist in managing the knowledge of GSD. Method: This study reviews current status of GSD by using tertiary study to review articles. A standard systematic literature review method is carried out to employ a manual search. Focus domains, knowledge areas and measurements of GSD will be identified so that can distill a common understanding of the state of the art GSD. Then, discussion about how KM comes in to assist CoP in managing their knowledge of GSD will be carried out in detailed. Results: 37 articles are chosen as primary studies. Among all focus domains, GSD life cycle gains highest interest. Knowledge area of energy efficiency receives the highest attention. Measurement for power consumption obtains the greatest priority to measure “greenness” of software developed. Conclusion: Focuses covered by GSD are limited. Researchers are encouraged to study about diverse areas of GSD. Our future work is to develop model of GSD which involving KM process to ensure members of CoP in software environment able to manage their knowledge and sustain best practices of GSD for the future

Scope Management of Non-Functional Requirements

In order to meet commitments in software projects, a realistic assessment must be made of project scope. Such an assessment relies on the availability of knowledge on the user-defined project requirements and their effort estimates and priorities, as well as their risk. This knowledge enables analysts, managers and software engineers to identify the most significant requirements from the list of requirements initially defined by the user. In practice, this scope assessment is applied to the Functional Requirements (FRs) provided by users who are unaware of, or ignore, the Non-Functional Requirements (NFRs). This paper presents ongoing research which aims at managing NFRs during the software development process. Establishing the relative priority of each NFR, and obtaining a rough estimate of the effort and risk associated with it, is integral to the software development process and to resource management. Our work extends the taxonomy of the NFR framework by integrating the concept of the "hardgoal". A functional size measure of NFRs is applied to facilitate the effort estimation process. The functional size measurement method we have chosen is COSMICFFP, which is theoretically sound and the de facto standard in the software industry

Looking for Reasons behind Success in Dealing with Requirements Change

During development, requirements of software systems are subject to change. Unfortunately, managing changing requirements can take a lot of time and effort. Yet some companies show a better management of changes in requirements than others. Why? What is it that makes some projects deal with changing requirements better than others? We pursue the long term goal of understanding the mechanisms used to successfully deal with change in requirements. In this paper we gather knowledge about the state-of-the-art and the state-of-practice. We studied eight software development projects in four different companies --large and small, inclined toward structured and toward agile principles of development--, interviewing their project managers and analyzing their answers. Our findings include a list of practical (rather than theoretical) factors affecting the ability to cope with small changes in requirements. Results suggest a central role of size as a factor determining the flexibility showed either by the organization or by the software development team. We report the research method used and validate our results via expert interviews, who could relate to our findings

Managing Knowledge as Business Rules

In today’s business environment, it is a certainty that will manage to survive especially those organizations which are striving to adapt quickly and with low costs to the new demands of market competition. Knowledge represented by internal business rules of an organization can help crystallize their orientation in order to ensure a competitive advantage in the market. In this context and in a relatively short time, a new trend in software development has arisen, ex-tending current methods and putting a strong emphasis on business rules. This article outlines the importance of managing business rules in an organized manner using dedicated software products and furthermore presents a general prototype for a business rules repository.Business Rules, Management, Knowledge, Rule Engine, Repository Prototype

Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program

Software development projects have undergone remarkable changes with the arrival of agile development methods. While intended for small, self-managing teams, these methods are increasingly used also for large development programs. A major challenge in programs is to coordinate the work of many teams, due to high uncertainty in tasks, a high degree of interdependence between tasks and because of the large number of people involved. This revelatory case study focuses on how knowledge work is coordinated in large-scale agile development programs by providing a rich description of the coordination practices used and how these practices change over time in a four year development program with 12 development teams. The main findings highlight the role of coordination modes based on feedback, the use of a number of mechanisms far beyond what is described in practitioner advice, and finally how coordination practices change over time. The findings are important to improve the outcome of large knowledge-based development programs by tailoring coordination practices to needs and ensuring adjustment over time.Comment: To appear in Project Management Journa

A Survey on Usage and Diffusion of Project Risk Management Techniques and Software Tools in the Construction Industry

The area of Project Risk Management (PRM) has been extensively researched, and the utilization of various tools and techniques for managing risk in several industries has been sufficiently reported. Formal and systematic PRM practices have been made available for the construction industry. Based on such body of knowledge, this paper tries to find out the global picture of PRM practices and approaches with the help of a survey to look into the usage of PRM techniques and diffusion of software tools, their level of maturity, and their usefulness in the construction sector. Results show that, despite existing techniques and tools, their usage is limited: software tools are used only by a minority of respondents and their cost is one of the largest hurdles in adoption. Finally, the paper provides some important guidelines for future research regarding quantitative risk analysis techniques and suggestions for PRM software tools development and improvemen

A knowledge analytics portal for agile programming

iii, 76 leaves : ill. (some col.) ; 29 cmIncludes abstract.Includes bibliographical references (leaves 72-76).Agile programming has been widely adopted for software development. One criticism on agile programming is the lack of documentation and knowledge sharing in the software development process. This thesis proposes a novel knowledge management approach for creating, managing, and sharing various types of documents for agile software development. The proposed approach divides software developers into two groups, masters and apprentices. Masters are senior software developers who are primarily responsible for agile software development. Masters avoid document writing as advocated in the agile manifesto for software development. Apprentices are junior software developers who are mainly responsible for creating, managing and sharing various types of documents for the agile software development process. The effectiveness of the proposed approach is investigated and validated through a prototype of a knowledge analytics portal. This thesis concludes that the proposed knowledge analytics portal increases the knowledge sharing for the agile software development process

Team knowledge management within an outsourced business systems software maintenance environment: a case study using grounded theory methods

The effective management of knowledge is increasingly seen as an essential contributor to the success of a knowledge-based organisation. There is a wealth of methodologies and approaches providing guidelines or frameworks for managing knowledge in a wide range of domains such as software development, IS service delivery and project management but few are dedicated to software maintenance. This paper presents the case study research of an outsourced software maintenance operation in the e-commerce business unit of a large UK retailer, using grounded theory to investigate a framework for assessing and improving the knowledge management capability of the software maintenance teams. The framework assesses the operation in five areas: leadership, communication, tools, processes and cultures. The results offer an insight into the strengths and areas for improvement in the knowledge management arrangements