Design guidelines for software processes knowledge repository development

Context

Staff turnover in organizations is an important issue that should be taken into account mainly for two reasons:

1.

Employees carry an organization’s knowledge in their heads and take it with them wherever they go

2.

Knowledge accessibility is limited to the amount of knowledge employees want to share

Objective

The aim of this work is to provide a set of guidelines to develop knowledge-based Process Asset Libraries (PAL) to store software engineering best practices, implemented as a wiki.

Method

Fieldwork was carried out in a 2-year training course in agile development. This was validated in two phases (with and without PAL), which were subdivided into two stages: Training and Project.

Results

The study demonstrates that, on the one hand, the learning process can be facilitated using PAL to transfer software process knowledge, and on the other hand, products were developed by junior software engineers with a greater degree of independence.

Conclusion

PAL, as a knowledge repository, helps software engineers to learn about development processes and improves the use of agile processes.     

一种软件智能部署方法的研究

研究了能够根据不同环境自动调整软件部署过程的软件智能部署问题。介绍并分析现有软件的部署工具,提出了软件智能部署的概念、整体框架和部署工作流程。介绍并分析了软件规范化描述语言和客户端信息的模型描述方法。在此基础之上,提出了一种能够根据环境差异,自动调整软件部署过程的软件智能部署算法。最后,对比并分析了软件智能部署实际应用效果。     

A practitioner’s guide to light weight software process assessment and improvement planning

Software process improvement (SPI) is challenging, particularly for small and medium sized enterprises. Most existing SPI frameworks are either too expensive to deploy, or do not take an organizations’ specific needs into consideration. There is a need for light weight SPI frameworks that enable practitioners to base improvement efforts on the issues that are the most critical for the specific organization.

This paper presents a step-by-step guide to process assessment and improvement planning using improvement framework utilizing light weight assessment and improvement planning (iFLAP), aimed at practitioners undertaking SPI initiatives. In addition to the guide itself the industrial application of iFLAP is shown through two industrial cases. iFLAP is a packaged improvement framework, containing both assessment and improvement planning capabilities, explicitly developed to be light weight in nature. Assessment is performed by eliciting improvements issues based on the organization’s experience and knowledge. The findings are validated through triangulation utilizing multiple data sources. iFLAP actively involves practitioners in prioritizing improvement issues and identifying dependencies between them in order to package improvements, and thus establish a, for the organization, realistic improvement plan. The two cases of iFLAP application in industry are presented together with lessons learned in order to exemplify actual use of the framework as well as challenges encountered.     

Enabling the creation of knowledge about software assets

In most companies two factors play a crucial role: managing the knowledge that is necessary for doing business and managing the hardware and software infrastructure that supports the business processes. Usually, business processes and infrastructure are not optimally aligned.

We investigate how principles from knowledge management can be applied to enable the creation, consolidation, conservation and continuous actualization of knowledge about valuable software systems (“software assets”) that are part of the infrastructure.

Our point of departure is a generic framework for knowledge creation proposed by Von Krogh, Ichijo and Nonaka. We investigate the explicit and tacit knowledge about software assets that may exist in an organization and specialize the framework to obtain a strategy for creating new knowledge about these software assets. By applying this strategy, one can optimize the quality and the flexibility of the software assets while reducing costs.     

Using planning poker for combining expert estimates in software projects

When producing estimates in software projects, expert opinions are frequently combined. However, it is poorly understood whether, when, and how to combine expert estimates. In order to study the effects of a combination technique called planning poker, the technique was introduced in a software project for half of the tasks. The tasks estimated with planning poker provided: (1) group consensus estimates that were less optimistic than the statistical combination (mean) of individual estimates for the same tasks, and (2) group consensus estimates that were more accurate than the statistical combination of individual estimates for the same tasks. For tasks in the same project, individual experts who estimated a set of control tasks achieved estimation accuracy similar to that achieved by estimators who estimated tasks using planning poker. Moreover, for both planning poker and the control group, measures of the median estimation bias indicated that both groups had unbiased estimates, because the typical estimated task was perfectly on target. A code analysis revealed that for tasks estimated with planning poker, more effort was expended due to the complexity of the changes to be made, possibly caused by the information provided in group discussions.     

Design and implementation of an adaptable software environment

In any major software project, a large volume of project-related information must be maintained and manipulated throughout the software life-cycle. Often this information is scattered, in different media ranging from scraps of papers to program listings, poorly cross-referenced, and inaccessible. TRIAD, an adaptable, integrated software development environment, has been designed to integrate and manage all this information in an organized and structured manner.

The TRIAD tool-box environment supports different methodologies to guide the users during development and maintenance of project related information. The environment can be customized by selecting a set of forms which enforce a particular methodology. These forms help develop, integrate, and maintain project information. Forms for a methodology can be tuned to reflect a project-team's experience. When customized by the tuned methodology, TRIAD can provide better project oriented support.

TRIAD uses grammar forms as its organizational model. This paper will discuss the advantages of using grammar forms in the modeling and implementation of an adaptable software information editor, within the TRIAD tool-box environment.     

An empirical analysis of software life spans to determine the planning horizon for new software

This paper presents an empirical analysis of the life span of over 180 systems aimed at developing a model for determining the planning horizon for new software at the business case stage of software acquisition. At this early stage, the firm has limited knowledge about the project, but must make crucial decisions, such as scope (breadth of requirements), approach (both insource vs. outsource and custom vs. package) and technology, including fit with standards (adhere to current vs. adopt new technology). These decisions are associated with different system lifetimes that, in turn, impact both the costs incurred and benefits received from the system. The failure to explicitly and properly address these differences can lead to the implementation of systems better left undone or to unintended consequences, such as the Y2K problem. We find that technology and approach, but not scope decisions are strongly related to system lifetime. In particular, systems that use an operating system that conforms to the firm’s standard or are acquired using a blended team entail longer system life. On the other hand, shorter system life is indicated if the system is technically complex, custom developed or uses an older programming language. Furthermore, modified packaged software is shorter lived than is a vanilla package. In addition, environmental variables also impact the appropriate horizon. For example, as one would expect, strategic systems are used longer. On the other hand, somewhat surprisingly, systems sponsored by executives last less long and despite the quickening pace of technological and business process advancement, a small trend toward longer lived systems is uncovered.     

Quality management metrics for software development

It can be argued that the quality of software management has an effect on the degree of success or failure of a software development program. We have developed a metric for measuring the quality of software management along four dimensions: requirements management, estimation/planning management, people management, and risk management. The quality management metric (QMM) for a software development program manager is a composite score obtained using a questionnaire administered to both the program manager and a sample of his or her peers. The QMM is intended to both characterize the quality of software management and serve as a template for improving software management performance. We administered the questionnaire to measure the performance of managers responsible for large software development programs within the US Department of Defense (DOD). Informal verification and validation of the metric compared the QMM score to an overall program-success score for the entire program; this resulted in a positive correlation.     

A Lagrangian heuristic for sprint planning in agile software development

Agile methods for software development promote iterative design and implementation. Most of them divide a project into functionalities, called user stories; at each iteration, often called a sprint, a subset of user stories are developed. The sprint planning phase is critical to ensure the project success, but it is also a difficult problem because several factors impact on the optimality of a sprint plan, e.g., the estimated complexity, business value, and affinity of the user stories to be included in each sprint. In this paper we present an approach for sprint planning based on an integer linear programming model. Given the estimates made by the project team and a set of development constraints, the optimal solution of the model is a sprint plan that maximizes the business value perceived by users. Solving to optimality the model by a general-purpose MIP solver, such as IBM Ilog Cplex, takes time and for some instances even finding a feasible solution requires too large computing times for an operational use. For this reason we propose an effective Lagrangian heuristic based on a relaxation of the proposed model and some greedy and exchange algorithms. Computational results on both real and synthetic projects show the effectiveness of the proposed approach.     

RATSNO—an experiment in software adaptability

Adaptable programs are one of the benefits of structured programming. The adaptability of a program is the degree to which it can be transformed into another program that performs a similar, but slightly different, function. While it is clear that the aims of structured programming are best satisfied by the use of modern programming languages, a great number of programmers must use languages such as Fortran. To alleviate this situation, a number of preprocessors have been introduced that give Fortran a more structured facade. This paper describes an experiment performed to test the adaptability of programs written in RATFOR, one of these preprocessors. Judging from the results, the use of a good preprocessor can significantly increase the adaptability of Fortran programs.     

A comparative study of software tools for user story management

ContextUser stories have become widely accepted in agile software development. Consequently, a great number of software tools that provide, inter alia, support for practices based on user stories have emerged in recent years. These tools may have different features and focus in terms of support for agile requirements engineering (RE) concepts and practices.ObjectiveThe present study aims to provide a deep insight into the current capabilities and future trends of software support for agile RE practices based on user stories.MethodA comparative qualitative study of a set of agile software tools has been conducted according to the following criteria: coverage of the key functional requirements, support for basic agile RE concepts and practices, and user satisfaction with the tool. The criteria for tool selection were: diversity of software tools, high rating on the user-stories community Web site (http://www.userstories.com), and availability for review.ResultsThe results show a generally good coverage of key functional requirements related to management of user stories and epics, high-level release planning and low-level iteration planning. On the other hand, user-role modeling and persona support have not been addressed at all, and it has been found that requirements for acceptance testing support were completely covered by only one tool. More importantly, the study has revealed significant differences in the way different tools support agile RE concepts and practices (if at all). Finally, qualitative analysis of user reviews has demonstrated that practitioners prefer tools that are easy to set up, easy to learn, easy to use, and easy to customize, over more sophisticated but simultaneously more demanding tools.ConclusionAlthough the progress that has been made since the inception of these tools is quite clear, there is still room for improvements in terms of support for various agile RE practices within a specific agile process.     

An integrated intelligent process planning system (IIPPS) for machining

A key component of computer integrated manufacturing (CIM) is computer aided process planning (CAPP). Process planning in machining involves the determination of the cutting operations and sequences, the selection of machine tools and cutting tools, the calculation of machining parameters, and the generation of CNC part programs. Industrial structures in Norway are defined as small and medium-sized companies. The important fact is how well these companies use high technologies and resources in order to improve their production efficiency, product quality, and company competition in international markets. The concept of an integrated intelligent system (IIS) is created for this purpose. A prototype system, the integrated intelligent process planning system (IIPPS), is described for machining; it was developed on the basis of an IIS and constructed using three levels of effort: (1) AutoCAD, (2) dBASE III and (3) KnowledgePro. The system may be utilized not only by a process plann ing engineer in a company, but also by students of mechanical or industrial engineering.     

Exploring the relationship between software project duration and risk exposure: A cluster analysis

Software projects often fail. Thus it is important to find ways to ensure a successful outcome. One significant area is a better understanding of the relationship between the software project duration and risk exposure, as this helps project managers with pertinent information to be effective in managing risky projects. We addressed this need by adopting a cluster analysis technique to provide managers with insight into effective planning and control of their projects. The results not only revealed that risk exposures associated with user, requirement, planning & control and team risk dimensions were affected by project duration, but also showed how to manage software risks effectively through observing trends in the risk components. Based on our findings, project managers can adopt appropriate attitudes, skills, and practices to deal with risky areas more effectively rather than just identifying those software risks with which project managers should be concerned.     

Ontology of systems and software engineering

Systems and software engineering have evolved in the last years in a process of consolidation of their specificities as engineering disciplines. This has resulted in research and inquiry on ontological and epistemological issues related to them. Due to the supporting nature of systems and software engineering with regards to other engineering disciplines, these aspects are also relevant to researchers and practitioners in other engineering domains. The contents of this issue provide a selection of research aimed at consolidating ontology of systems and software engineering as a useful and consistent body of knowledge.     

The optimization of success probability for software projects using genetic algorithms

The software development process is usually affected by many risk factors that may cause the loss of control and failure, thus which need to be identified and mitigated by project managers. Software development companies are currently improving their process by adopting internationally accepted practices, with the aim of avoiding risks and demonstrating the quality of their work.This paper aims to develop a method to identify which risk factors are more influential in determining project outcome. This method must also propose a cost effective investment of project resources to improve the probability of project success.To achieve these aims, we use the probability of success relative to cost to calculate the efficiency of the probable project outcome. The definition of efficiency used in this paper was proposed by researchers in the field of education. We then use this efficiency as the fitness function in an optimization technique based on genetic algorithms. This method maximizes the success probability output of a prediction model relative to cost.The optimization method was tested with several software risk prediction models that have been developed based on the literature and using data from a survey which collected information from in-house and outsourced software development projects in the Chilean software industry. These models predict the probability of success of a project based on the activities undertaken by the project manager and development team. The results show that the proposed method is very useful to identify those activities needing greater allocation of resources, and which of these will have a higher impact on the projects success probability.Therefore using the measure of efficiency has allowed a modular approach to identify those activities in software development on which to focus the project's limited resources to improve its probability of success. The genetic algorithm and the measure of efficiency presented in this paper permit model independence, in both prediction of success and cost evaluation.     

Process fusion: An industrial case study on agile software product line engineering

This paper presents a case study of a software product company that has successfully integrated practices from software product line engineering and agile software development. We show how practices from the two fields support the company’s strategic and tactical ambitions, respectively. We also discuss how the company integrates strategic, tactical and operational processes to optimize collaboration and consequently improve its ability to meet market needs, opportunities and challenges. The findings from this study are relevant to software product companies seeking ways to balance agility and product management. The findings also contribute to research on industrializing software engineering.     

Configuration management for Lyee software

This article presents a configuration management concept for software projects using Lyee methodology. To illustrate this concept, an introduction in configuration management is given. Then, the structure of Lyee programs is defined by sets and their dependencies. From this structure, the actual configuration management concept is deduced and discussed by rendering the structure for an existing configuration management testbed and describing the involved key players as well as the necessary procedures.