Abstract — Software reuse enables developers to leverage past accomplishments and facilitates significant improvements in software productivity and quality [1]. The contribution of this paper is a recommended process model for the implementation of software reuse effectively. A critical problem in today’s practice of software reuse is the lack of a standard process model which describes the necessary details to support reuse based software development and evolution. Our research thesis is that software development based upon a reuse-based process model improves quality of products and productivity of processes. A quantitative survey of 100 software organizations is used to test the new process model and the hypothesis of the study. The process model presented in this paper identifies process level, organizational and technical aspects which have to be improved to achieve success in the reuse world.

Abstract. We present the application of the process workshop method to define revised work processes in software development companies. Through two empirical action research studies, we study the impact of company premises and goals on the execution and subsequently on the results of the method. We conclude that both premises and goals will influence the workshops, and suggest how the focus of the workshops should be altered to achieve better results depending on the context. We also strengthen previous claims that the process workshops are a good arena that fosters discussion and organizational learning, and that involvement in the workshops leads to higher acceptance and usage of the resulting process.

There is often a misconception that adopting and tailoring agile methods is straightforward resulting in improved products and increasingly satisfied customers. However, the empirical nature of agile methods means that potential practitioners need to carefully assess whether they are exposed to the risks that can make agile method adoption problematic. This is particularly the case with small software companies who are less able to absorb the impact of failed experimentation. This study describes a minimally intrusive assessment approach for small software companies preparing for agile method adoption and tailoring in the light of key risks. The approach has been conducted with six small software companies, three of which are presented to show the evolution of the approach, describe the resource commitment that companies have to make, and highlight the type of information generated from an assessment. The contribution of this study is that small software companies have an alternative to ‘mere experimentation ’ with agile methods and can take reasoned steps towards their adoption and

The Software Requirements phase has notable importance, since it is responsible for the definition of the system itself. Several customers indicate which functionalities they want to be present in the software. However, constraints, such as budget, make it impossible to implement all desired requirements at once. One activity in this context is the release planning. The selection of which requirements should be implemented to the next release is necessary. In literature, metaheuristics have been employed to solve this problem. The objective of this work is to propose the use of exact optimization techniques in the problem, with the advantage that the resolution through these techniques ensures the best solutions. The results in several experiments show the validity of such application, in comparison with the metaheuristics approach.

Software development is type of work that demands effective processes to support organizing the work: “A software process can be defined as the coherent set of policies, organizational structures, technologies, procedures, and artifacts that are needed to conceive,

Abstract. The software development team is a key factor in software projects, however, achieving and maintaining positive team dynamics in software development project especially when the software companies have fewer resources in term of people, money and time is a remarkable challenge. This paper explores the dynamics of software development teams (structure, process, communication, learning and sharing) and its impact on Software Process Improvement (SPI) in very small software organization, in order to understand the impact between these two variables. We undertook a series of interviews and focus groups with very small software companies and our results show that very small companies have a high level of team dynamics although their SPI initiatives are conducted on a small scale and in an informal and indirect manner. The results also indicated that this situation occurs due to the working and social relationship, willingness to share, having a good interpersonal skill and work closely each others.