Software quality management improvement through mentoring: an exploratory study from GSD projects

Proceeding of: OTM 2011 Workshops: Confederated InternationalWorkshops and Posters: EI2N+NSF ICE, ICSP+INBAST, ISDE, ORM, OTMA, SWWS+MONET+SeDeS, and VADER 2011, Hersonissos, Crete, Greece, October 17-21, 2011Software Quality Management (SQM) is a set of processes and procedures designed to assure the quality of software artifacts along with their development process. In an environment in which software development is evolving to a globalization, SQM is seen as one of its challenges. Global Software Development is a way to develop software across nations, continents, cultures and time zones. The aim of this paper is to detect if mentoring, one of the lead personnel development tools, can improve SQM of projects developed under GSD. The results obtained in the study reveal that the influence of mentoring on SQM is just temperate

Exchange Reactions between Alkanethiolates and Alkaneselenols on Au{111}

When alkanethiolate self-assembled monolayers on Au{111} are exchanged with alkaneselenols from solution, replacement of thiolates by selenols is rapid and complete, and is well described by perimeter-dependent island growth kinetics. The monolayer structures change as selenolate coverage increases, from being epitaxial and consistent with the initial thiolate structure to being characteristic of selenolate monolayer structures. At room temperature and at positive sample bias in scanning tunneling microscopy, the selenolate-gold attachment is labile, and molecules exchange positions with neighboring thiolates. The scanning tunneling microscope probe can be used to induce these place-exchange reactions

Using developer activity data to enhance awareness during collaborative software development

Software development is a global activity unconstrained by the bounds of time and space. A major effect of this increasing scale and distribution is that the shared understanding that developers previously acquired by formal and informal face-to-face meetings is difficult to obtain. This paper proposes a shared awareness model that uses information gathered automatically from developer IDE interactions to make explicit orderings of tasks, artefacts and developers that are relevant to particular work contexts in collaborative, and potentially distributed, software development projects. The research findings suggest that such a model can be used to: identify entities (developers, tasks, artefacts) most associated with a particular work context in a software development project; identify relevance relationships amongst tasks, developers and artefacts e.g. which developers and artefacts are currently most relevant to a task or which developers have contributed to a task over time; and, can be used to identify potential bottlenecks in a project through a 'social network' view. Furthermore, this awareness information is captured and provided as developers work in different locations and at different times