The development processes of open source soft-ware are different from traditional closed source de-velopment processes. Still, open source software is frequently of high quality. This raises the question of how and why open source software creates high quality and whether it can maintain this quality for ever larger project sizes. In this paper, we look at one particular quality indicator, the density of comments in open source software code. We find that successful open source projects follow a consistent practice of documenting their source code, and we find that the comment density is independent of team and project size.

Run-Time polymorphism (RTP) has been used in the software community for two decades to satisfy dynamic reconfiguration, plug-n-play, extensibility, and system redundancy requirements. RTP is also used to construct software systems of systems. System engineers now have the same requirements applied to large-scale system architecture. A Polymorphic System Architecture (PSA) uses the same technology, by applying it to the system architecture. By defining specific polymorphic relationship within the system architecture the system architect can reduce the system complexity and satisfy functional requirement.

The relationships between project managers individual characteristics and the success of the projects do not receive enough attentions in the software engineering researches. However, as the core member of a software development team, the project managers leadership level influences the development process in a great part. The existing literatures have shown the importance of individuals personality to his or her behaviors, which include the leadership behaviors certainly. Therefore, exploring how the project managers personality influences the success of the software development projects has significant potential utility. In this paper, we present a research to integrate the Five Factor Model (FFM) for the personality with the existing work on the leaderships with the project success. Through the empirical study based on data from 116 real software projects, we found general support for our hypothesized research model. The results not only reveal that the five big personality factors can be treated as indicators for the success of the software development projects, but also provide the evidence on how the project managers personality influences the success of the software development projects through medium effects of the leadership. The support for the relationship between leadership and the success of software development projects is also found

Communication is a key component in the daily software project management. It is the quintessential carrier of semantic information. But speech is transient and with it the information exchanged in meetings.

To organize a successful meeting, some rules have to be followed. One is to summarize important - said - information in a written protocol to externalize the knowledge shared in the meeting. The act of manually writing meeting minutes implicate a lot of problems. The protocol is published too late, inconsistent, or incomplete, due to the limited perceptivity and time of the protocol writer. Hence, we focus on an approach to automatically generate protocols and make them accessible to the right person. Therefore, keyword spotting, based on a predened and meeting-type dependent grammar, is applied to meeting recordings and the discussed information is extracted and accordingly pipelined into the project information workow.

This paper presents a lightweight framework of an information and knowledge management approach to capture communication in meetings.

Conventional tools yield expensive and inflexible software. By requiring that software be structured as plug-compatible modules, tools preclude out-of-order development; by treating interoperation of languages as rare, adoption of innovations is inhibited. I propose that a solution must radically separate the concern of integration in software: firstly by using novel tools specialised towards integration (the "integration domain"), and secondly by prohibiting use of pre-existing interfaces ("interface hiding") outside that domain.

The Toyota Production System promotes "pull" scheduling to reduce the production of parts that do not comply to what the customer needs. The use of "pull" within software represents a radical change in the way activities are planned. This article gives two examples of the possible application of "pull" within software engineering and de-scribes a measurement tool to assess the current costs and amount of rework within a software development project. The described approach aims to help practitioners to under-stand whether to use "pull" or "push" in their organizations.

Since the 60's the demand for more complex softwares in a shorter time-to-market has been increasing. This fact led major advances in the field of Software Engineering, how-ever, still nowadays the development organizations are fac-ing problems with productivity, software quality, processes adoption and communication. Several re-searches try to find these issues reasons and address some solutions, but in many cases the works identify isolated issues, giving iso-lated alternatives. So, what are the real problems with soft-ware development? Is there a main question to be solved? Looking for these and other answers, this paper analyses some research trends like PSEEs, Knowledge Management, Communication, and Interactivity resources and, based on them, proposes a new Software Engineering paradigm fo-cused basically on people, information and an environment with Augmented Reality support. Nevertheless each drop of paradigm reveals challenges as the sustainability of the ap-proach itself. To deal with this, the present work also pro-poses the use of Intervention Theory, to reduce the impact of the changes to a development team.

The current challenges of the aviation industry call for the development of new and revolutionary aircraft concepts. In general, the task of developing new aircraft is risky and an extremely complex task, and aircraft manufacturers seek to control this complexity by adopting an evolutionary approach. Introducing new ways of controlling this complexity has the potential benefit of reducing the risk associated with aircraft development and enabling the development of revolutionary aircraft. One such new way is based on the application of agile principles. This paper discusses the application of agile principles on aircraft development processes to eliminate to a certain degree the involved complexity of conventional aircraft development processes.