Wei-Keat Kong, J. Hayes, Alex Dekhtyar, Jeff Holden
{"title":"How do we trace requirements: an initial study of analyst behavior in trace validation tasks","authors":"Wei-Keat Kong, J. Hayes, Alex Dekhtyar, Jeff Holden","doi":"10.1145/1984642.1984648","DOIUrl":"https://doi.org/10.1145/1984642.1984648","url":null,"abstract":"Traceability recovery is a tedious, error-prone, person-power intensive task, even if aided by automated traceability tools. Human analysts must vet candidate traceability links retrieved by such tools and must often go looking for links that such tools fail to locate as they build a traceability matrix. This paper examines a research version of the traceability tool REquirements TRacing On target (RETRO) that logs analyst actions. We examine the user logs in order to understand how analysts work on traceability recovery tasks. Such information is a pre-requisite to understanding how to better design traceability tools to best utilize analyst time while developing a high quality final traceability matrix.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"361 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122793474","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Collabode: collaborative coding in the browser","authors":"Max Goldman, Greg Little, Rob Miller","doi":"10.1145/1984642.1984658","DOIUrl":"https://doi.org/10.1145/1984642.1984658","url":null,"abstract":"Collaborating programmers should use a development environment designed specifically for collaboration, not the same one designed for solo programmers with a few collaborative processes and tools tacked on. This paper describes Collabode, a web-based Java integrated development environment built to support close, synchronous collaboration between programmers. We discuss three collaboration models in which participants take on distinct roles: micro-outsourcing to combine small contributions from many assistants; test-driven pair programming for effective pairwise development; and a mobile instructor connected to the work of many students. In particular, we report very promising preliminary results using Collabode to support micro-outsourcing.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133025950","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Requirements maturation analysis based on the distance between the source and developers","authors":"Takako Nakatani, T. Tsumaki","doi":"10.1145/1984642.1984664","DOIUrl":"https://doi.org/10.1145/1984642.1984664","url":null,"abstract":"The success of a project is often affected by imperfect requirements. In order to cope with this risk, a requirements analyst needs to communicate with a client. However, communication between the requirements analyst and the client is not enough to prevent requirements imperfection, since requirements come from various sources, e.g. environment, laws, documents, actual usage, etc. The process of requirements elicitation is affected by the requirements stability, the ability of a requirements analyst, and accessibility of the source of requirements. This paper focuses on the distance between the source of requirements and a requirements analyst, and clarifies how the distance influences the requirements maturation. Requirements maturation represents the degree to which the requirements are elicited completely. We define a measure for observing requirements maturation and analyzing the accessibility of the source of the requirements. Then, we define a hypothesis. A case is analyzed in order to verify the hypothesis. As a result, there is a correlation between the requirements maturation efficiency and the accessibility of the source of the requirements.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131161912","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Impact of collaborative traces on trustworthiness","authors":"E. Trainer, B. Al-Ani, D. Redmiles","doi":"10.1145/1984642.1984649","DOIUrl":"https://doi.org/10.1145/1984642.1984649","url":null,"abstract":"We investigated how trust among software developers would be affected by providing them with visualizations of collaborative traces. We define collaborative traces to be representations of the past and current activity of a group of developers manipulating software development artifacts. In this paper, we report two main findings. First, we report the results of our controlled experiment in which collaborative traces were visualized. Second, we present an overview of tools which aim to represent collaborative software engineering traces. Our experiment provides evidence that collaborative traces can support the development of several factors of trust identified in our field study. However, we also identified some shortcomings of our current visualizations, gaining insights into future improvements. From our review of tools that represent collaborative traces, we observed that such representations can drive the design of tools that aim to support trust. We also present a table of tools; the table can be used to guide discussion and the design of tools that promote trust in software development.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122513805","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Branching and merging: an investigation into current version control practices","authors":"Shaun Phillips, Jonathan Sillito, R. Walker","doi":"10.1145/1984642.1984645","DOIUrl":"https://doi.org/10.1145/1984642.1984645","url":null,"abstract":"The use of version control has become ubiquitous in software development projects. Version control systems facilitate parallel development and maintenance through branching, the creation of isolated codelines. Merging is a consequence of branching and is the process of integrating codelines. However, there are unanswered questions about the use of version control to support parallel development; in particular, how are branching and merging used in practice? What defines a successful branching and merging strategy? As a first step towards answering these questions, we recruited a diverse sample of 140 version control users to participate in an online survey. In this paper, we present the survey results and 4 key observations about branching and merging practices in software development projects.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"409 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133319102","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Of code and context: collaboration between developers and translators","authors":"Malte Reßin, J. Abdelnour-Nocera, Andy Smith","doi":"10.1145/1984642.1984653","DOIUrl":"https://doi.org/10.1145/1984642.1984653","url":null,"abstract":"Software for international markets often requires cultural adaption in order to be successful in different markets. To achieve this, software developers work together with translators to internationalize and localize their product as necessary. In this paper, we reflect on our experiences of collaboration between these two specialist types from different disciplines. We contrast the differences in object of work, education, values and perception of product quality and illustrate what other factors might have an influence in collaboration. Our experiences suggest that the collaboration between developers and localizers might be improved by integrating translators into development teams, and by emphasizing the importance of understanding each other's work better.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123118299","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Cleviton V. F. Monteiro, F. Silva, Isabella R. M. dos Santos, Felipe Farias Maciel, Elisa S. F. Cardozo, A. R. G. A. Leitão, Dacio N. M. Neto, Miguel J. A. Pernambuco Filho
{"title":"A qualitative study of the determinants of self-managing team effectiveness in a scrum team","authors":"Cleviton V. F. Monteiro, F. Silva, Isabella R. M. dos Santos, Felipe Farias Maciel, Elisa S. F. Cardozo, A. R. G. A. Leitão, Dacio N. M. Neto, Miguel J. A. Pernambuco Filho","doi":"10.1145/1984642.1984646","DOIUrl":"https://doi.org/10.1145/1984642.1984646","url":null,"abstract":"There are many evidences in the literature that the use self-managing teams has positive impacts on several dimensions of team effectiveness. Agile methods, supported by the Agile Manifesto, defend the use of self-managing teams in software development in substitution of hierarchically managed, traditional teams. The goal of this research was to study how a self-managing software team works in practice and how the behaviors of the software organization support or hinder the effectiveness of such teams. We performed a single case holistic case study, looking in depth into the actual behavior of a mature Scrum team in industry. Using interviews and participant observation, we collected qualitative data from five team members in several interactions. We extract the behavior of the team and of the software company in terms of the determinants of self-managing team effectiveness defined in a theoretical model from the literature. We found evidence that 17 out of 24 determinants of this model exist in the studied context. We concluded that certain determinants can support or facilitate the adoption of methodologies like Scrum, while the use of Scrum may affect other determinants.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129381828","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Strawberries are nuts","authors":"Tim Frey, Marius Gelhausen","doi":"10.1145/1984642.1984652","DOIUrl":"https://doi.org/10.1145/1984642.1984652","url":null,"abstract":"Separation of concerns is a central element for program comprehension. This note briefly explains why human categorization can be interesting for program comprehension.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"25 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126532717","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Some non-usage data for a distributed editor: the saros outreach","authors":"L. Prechelt","doi":"10.1145/1984642.1984651","DOIUrl":"https://doi.org/10.1145/1984642.1984651","url":null,"abstract":"After contacting more than 40 companies and 11 OSS projects regarding using our distributed editor Saros, we find that almost all of those many who have a use case for it, are reluctant to even try it out. It appears that distance matters even by anticipatory obedience.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-05-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127729349","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","authors":"","doi":"10.1145/1984642","DOIUrl":"https://doi.org/10.1145/1984642","url":null,"abstract":"Software is created by people for people working in varied environments, under various conditions. Thus understanding cooperative and human aspects of software development is crucial to comprehend how methods and tools are used, and thereby improving the creation and maintenance of software. Over the years, both researchers and practitioners have recognized the need to study and understand these aspects. Despite recognizing this, researchers in cooperative and human aspects have no clear place to meet ans are dispersed in different research conference and areas. \u0000 \u0000The goal of this workshop is to provide a forum for discussing high quality research on human and cooperative aspects of software engineering. We aim at providing both a meeting place for the growing community and the possibility for researchers interested in joining the field to present their work in progress and get an overview over the field.","PeriodicalId":136711,"journal":{"name":"Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124715086","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}