http://www.bibsonomy.org/burst/user/neilernst/could-readBibSonomy BuRST Feed for /user/neilernst/could-read2008-09-05T07:27:54+02:00dblphttp://www.bibsonomy.org/bibtex/22dc15c7416ad9dcde10ea1e949787c90/neilernstneilernst2008-01-07T21:05:28+01:00software empirical could-read complexity <span style="color:#555555;">Victor R. <a href="http://www.bibsonomy.org/author/Basili">Basili</a> und Barry T. <a href="http://www.bibsonomy.org/author/Perricone">Perricone</a> </span><em>Commun. ACM</em><em>27(1):42-52</em>(<em>1984</em>)Mon Jan 07 21:05:28 CET 2008Commun. ACM142-52Software Errors and Complexity: An Empirical Investigation.271984software empirical could-read complexity AO Evolution chapter short paperhttp://www.bibsonomy.org/bibtex/2098640d29eb4ad3256e0401b45936031/neilernstneilernst2007-10-23T22:45:10+02:00could-read evolution oss <span style="color:#555555;">Walt <a href="http://www.bibsonomy.org/author/Scacchi">Scacchi</a> und Joseph <a href="http://www.bibsonomy.org/author/Feller">Feller</a> und Brian <a href="http://www.bibsonomy.org/author/Fitzgerald">Fitzgerald</a> und Scott <a href="http://www.bibsonomy.org/author/Hissam">Hissam</a> und Karim <a href="http://www.bibsonomy.org/author/Lakhani">Lakhani</a> </span><em>Software Process: Improvement and Practice</em><em>11(2):95 --105</em><em>March/April2006. </em>Tue Oct 23 22:45:10 CEST 2007Software Process: Improvement and PracticeMarch/April295 --105Understanding Free/Open Source Software Development Processes112006could-read evolution oss This article introduces a special issue of Software Process – Improvement and Practice focusing on processes found in free or open source software development (F/OSSD) projects. It seeks to provide a background overview of research in this area through a review of selected empirical studies of F/OSSD processes. The results and findings from a survey of empirical studies of F/OSSD give rise to an interesting variety of opportunities and challenges for understanding these processes, which are identified along the way. Overall, what becomes clear is that studies of F/OSSD processes reveal a more diverse set of different types of processes than have typically been examined in conventional software development projects. The articles in this special issue further advance understanding of what processes characterize and shape F/OSSDhttp://www.bibsonomy.org/bibtex/2e7d01c7c1f410e7516660cb68fb915f3/neilernstneilernst2007-06-20T20:33:50+02:00could-read complexity modeling software <span style="color:#555555;">Robert <a href="http://www.bibsonomy.org/author/France">France</a> und Bernhard <a href="http://www.bibsonomy.org/author/Rumpe">Rumpe</a> </span><em>Future of Software Engineering at ICSE, </em><em>Seite37-54. </em><em>Minneapolis, Minnesota, </em><em>May2007. </em>Wed Jun 20 20:33:50 CEST 2007Minneapolis, MinnesotaFuture of Software Engineering at ICSEMay37-54Model-driven Development of Complex Software: A Research Roadmap2007could-read complexity modeling software The term Model-Driven Engineering (MDE) is typically used to describe software development approaches in which abstract models of software systems are created and systematically transformed to concrete implementations. In this paper we give an overview of current research in MDE and discuss some of the major challenges that must be tackled in order to realize the MDE vision of software development. We argue that full realizations of the MDE vision may not be possible in the near to medium-term primarily because of the wicked problems involved. On the other hand, attempting to realize the vision will provide insights that can be used to significantly reduce the gap between evolving software complexity and the technologies used to manage complexity.http://www.bibsonomy.org/bibtex/2533547926f233fe7744bd376d74a7b61/neilernstneilernst2007-01-18T22:28:53+01:00could-read grounded software ethnography <span style="color:#555555;">Adam <a href="http://www.bibsonomy.org/author/Murray">Murray</a> </span><em>University of Ottawa, </em>(<em>2006</em>)Thu Jan 18 22:28:53 CET 2007Discourse Structure of Software Explanation: Snapshot Theory, Cognitive Patterns and Grounded Theory Methods2006could-read grounded software ethnography This thesis introduces a grounded theory of the discourse structure that professional software engineers use while explaining software. The ‘Snapshot Theory’ relates how the snapshot is the critical moment and fundamental building block in the discourse structure. We built Snapshot Theory by applying a rigorous qualitative data analysis research methodology, known as grounded theory, on observational data of professional software developers explaining software architectures. We developed a research methodology, qualitative analysis tools and case data in support of our investigation. We present two versions of our theory, the grounded theory tied to evidence, and our interpretation of the applied theory in pattern form, as cognitive patterns. We intend cognitive patterns to facilitate the development of software tool features based on Snapshot Theory.http://www.bibsonomy.org/bibtex/2e9e63ffaa3ce89cbc58e8b3c54b57abc/neilernstneilernst2006-09-27T23:22:45+02:00could-read visualization software <span style="color:#555555;">Thorsten <a href="http://www.bibsonomy.org/author/Schäfer">Sch&#228;fer</a> und Michael <a href="http://www.bibsonomy.org/author/Eichberg">Eichberg</a> und Michael <a href="http://www.bibsonomy.org/author/Haupt">Haupt</a> und Mira <a href="http://www.bibsonomy.org/author/Mezini">Mezini</a> </span><em>Transactions on Software Engineering</em><em>32(9):753--768</em><em>September2006. </em>Wed Sep 27 23:22:45 CEST 2006Transactions on Software EngineeringSeptember9753--768The SEXTANT Software Exploration Tool322006could-read visualization software In this paper, we discuss a set of functional requirements for software exploration tools and provide initial evidence that various combinations of these features are needed to effectively assist developers in understanding software. We observe that current tools for software exploration only partly support these features. This has motivated the development of Sextant, a software exploration tool tightly integrated into the Eclipse IDE that has been developed to fill this gap. By means of case studies, we demonstrate how the requirements fulfilled by Sextant are conducive to an understanding needed to perform a maintenance task.http://www.bibsonomy.org/bibtex/2dd1595573c25988f6df6a4875df255fc/neilernstneilernst2006-09-25T23:20:40+02:00design open-source empirical could-read complexity <span style="color:#555555;">Alan <a href="http://www.bibsonomy.org/author/MacCormack">MacCormack</a> und John <a href="http://www.bibsonomy.org/author/Rusnak">Rusnak</a> und Carliss Y. <a href="http://www.bibsonomy.org/author/Baldwin">Baldwin</a> </span><em>Working Paper, </em><em>05-016. </em><em>Harvard Business School, </em>(<em>2005</em>)Mon Sep 25 23:20:40 CEST 200605-016Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary CodeWorking Paper2005design open-source empirical could-read complexity This paper reports data from a study that seeks to characterize the differences in design structure between complex software products. In particular, we use Design Structure Matrices (DSMs) to map the dependencies between the elements of a design and define metrics that allow us to compare the structures of different designs. We first use these metrics to compare the architectures of two software products – the Linux operating system and the Mozilla web browser – that were developed via contrasting modes of organization: specifically, open source versus proprietary development. We then track the evolution of Mozilla, paying particular attention to a purposeful “re-design” effort that was undertaken with the intention of making the product more “modular.” We find significant differences in structure between Linux and the first version of Mozilla, suggesting that Linux had a more modular architecture. We also find that the redesign of Mozilla resulted in an architecture that was significantly more modular than that of its predecessor, and indeed, than that of Linux. Our results, while exploratory, are consistent with a view that different modes of organization are associated with designs that possess different structures. However, we also illustrate that purposeful managerial actions can have a large impact on structure. This latter result is important given recent moves to release proprietary software into the public domain. These moves are likely to fail unless the product possesses an architecture that facilitates participation. Our paper provides evidence that a tightly-coupled design can be adapted to meet this objective.