Emphasizing human capabilities in software development

Acuña, Silvia T.; Juristo, Natália; Moreno, Ana M.

doi:10.1109/ms.2006.47

Cited by 129 publications

(80 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Each of the two teams consisted of one line manager, responsible for a product line and overseeing several projects, two project managers, responsible for a single project and his project team, one to two requirements engineers, six to seven software developers and two to four software testers. These roles are a subset of the fairly extensive stakeholder roles identified by Acuna et al [23] and Yilmaz et al [24]. The size of the teams, 13 and 16, is comparable to other software development teams in industry as reported by [25] and [26].…”

Section: A Team Structure and Subjectsmentioning

confidence: 54%

Stakeholders' Information Needs for Artifacts and Their Dependencies in a Real World Context

Müller

Fritz

2013

2013 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

In the evolution of software, stakeholders continuously seek and consult various information artifacts and their interdependencies to successfully complete their daily activities. While a lot of research has focused on supporting stakeholders in satisfying various information needs, there is little empirical evidence on how these information needs manifest themselves in the context of professional software development teams of real world companies. To investigate the information needs of the different stakeholder roles involved in software evolution activities, we conducted an empirical study with 23 participants from two professional development teams of one company. The analysis of the gathered data shows that information needs exhibit a crosscutting nature with respect to stakeholder role, activity, artifacts and even fragments of artifacts. We also found that the dependencies between information artifacts are important for the successful performance of software evolution activities, but often not captured explicitly. The lack of an explicit representation of these interdependencies often result in difficulties identifying dependent artifacts and additional communication effort. Based on our findings, we suggest ways to better support stakeholders with their information needs. Abstract-In the evolution of software, stakeholders continuously seek and consult various information artifacts and their interdependencies to successfully complete their daily activities. While a lot of research has focused on supporting stakeholders in satisfying various information needs, there is little empirical evidence on how these information needs manifest themselves in the context of professional software development teams of real world companies. To investigate the information needs of the different stakeholder roles involved in software evolution activities, we conducted an empirical study with 23 participants from two professional development teams of one company. The analysis of the gathered data shows that information needs exhibit a crosscutting nature with respect to stakeholder role, activity, artifacts and even fragments of artifacts. We also found that the dependencies between information artifacts are important for the successful performance of software evolution activities, but often not captured explicitly. The lack of an explicit representation of these interdependencies often result in difficulties identifying dependent artifacts and additional communication effort. Based on our findings, we suggest ways to better support stakeholders with their information needs.

show abstract

Section: A Team Structure and Subjectsmentioning

confidence: 54%

Stakeholders' Information Needs for Artifacts and Their Dependencies in a Real World Context

Müller

Fritz

2013

2013 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

show abstract

“…This question stems from the fact that when characteristics of individuals and their technical roles are better blended, the productivity of team will increase (Acuna et al, 2006;Capretz, 2003).…”

Section: Research Questions and Hypothesesmentioning

confidence: 99%

AN APPROACH FOR IMPROVING THE SOCIAL ASPECTS OF THE SOFTWARE DEVELOPMENT PROCESS BY USING A GAME THEORETIC PERSPECTIVE - Towards a Theory of Social Productivity of Software Development Teams

Yılmaz¹,

O’Connor

2011

Proceedings of the 6th International Conference on Software and Database Technologies

View full text Add to dashboard Cite

Abstract:As software development is considered a form of knowledge based social activity, investigating social interactions and behaviors of individuals and teams constitutes a starting point for improving organizational performance and productivity. Therefore, a software development organization is regarded as a form of social network, which may be more efficiently structured based upon participants' skills, roles and capacities to exchange information. This paper aims to propose a research framework for modeling development activities in terms of social interrelationships. It investigates ways for improving the productivity of the software development process to several social issues (e.g. team formations, interpersonal conflicts, social loafing) that affect the group setting during the software development process. An industrial survey will be conducted to validate the proposed framework. This survey will be applied to three medium size software organizations; (i) to measure social aspects of productivity, (ii) to assess the effectiveness of our approach, (iii) and to improve the welfare of the software development organization. Semi-structured interviews with practitioners, and expert reviews with the managers will be used to evaluate the results. Ultimately, based on the principles of our game theoretical approach and collected data, we propose a research framework, which will benefit future research by drawing a road map that establishes a body of knowledge, specifically on software development teams and organizations.

show abstract

“…Any designed SPML is based upon fulfilling an objective of the essential software process modeling objectives (see [42], [43]). For instance, programming language-based SPMLs (such as [5]- [7]) play a vital role in automating the software process itself, and its execution.…”

Section: Introductionmentioning

confidence: 99%