@conference {Hissam,
	title = {On Open and Collaborative Software Development in the DoD},
	booktitle = {Seventh Annual Acquisition Research Symposium, {NPS} Proceedings -},
	volume = {1},
	number = {1},
	year = {2010},
	month = {04/2010},
	pages = {219{\textendash}235},
	publisher = {Naval Postgraduate School},
	organization = {Naval Postgraduate School},
	address = {Monterey, California},
	abstract = {The US Department of Defense (specifically, but not limited to, the DoD CIO{\textquoteright}s Clarifying Guidance Regarding Open Source Software, DISA{\textquoteright}s launch of Forge.mil and OSD{\textquoteright}s Open Technology Development Roadmap Plan) has called for increased use of open source software and the adoption of best practices from the free/open source software (F/OSS) community to foster greater reuse and innovation between programs in the DoD. In our paper, we examine some key aspects of open and collaborative software development inspired by the success of the F/OSS movement as it might manifest itself within the US DoD. This examination is made from two perspectives: the reuse potential among DoD programs sharing software and the incentives, strategies and policies that will be required to foster a culture of collaboration needed to achieve the benefits indicative of F/OSS. Our conclusion is that to achieve predictable and expected reuse, not only are technical infrastructures needed, but also a shift to the business practices in the software development and delivery pattern seen in the traditional acquisition lifecycle is needed. Thus, there is potential to overcome the challenges discussed within this paper to engender a culture of openness and community collaboration to support the DoD mission.},
	keywords = {collaborative development, open source software, reuse, software engineering},
	url = {http://www.acquisitionresearch.net/cms/_files/FY2010/NPS-AM-10-037.pdf},
	author = {Hissam, S. A. and Weinstock, C. and Bass, L.}
}
@conference {706,
	title = {Retrieving Open Source Software Licenses},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {35 - 46},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software maintenance and reuse require identifying and comprehending the applied software licenses. This paper first characterizes software maintenance, and open source software (OSS) reuse which are particularly relevant in this context. The information needs of maintainers and reusers can be supported by reverse engineering tools at different information retrieval levels. The paper presents an automated license retrieval approach called ASLA. User needs, system architecture, tool features, and tool evaluation are presented. The implemented tool features support identifying source file dependencies and licenses in source files, and adding new license templates for identifying licenses. The tool is evaluated against another tool for license information extraction. ASLA requires the source code as available input but is otherwise not limited to OSS. It supports the same programming languages as GCC. License identification coverage is good and the tool is extendable.
},
	keywords = {gaim, license, license analysis, maintenance, mozilla, reuse},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Retrieving\%20Open\%20Source\%20Software\%20Licenses.pdf},
	author = {Tuunanen, Timo and Koskinen, Jussi and K{\"a}rkk{\"a}inen, Tommi}
}
@conference {1054,
	title = {LASER: a lexical approach to analogy in software reuse},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {112 - 116},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Software reuse is the process of creating a software system from existing software components, rather than creating it from scratch. With the increase in size and complexity of existing software repositories, the need to provide intelligent support to the programmer becomes more pressing. An analogy is a comparison of certain similarities between things which are otherwise unlike. This concept has shown to be valuable in developing UML-level reuse techniques. In the LASER project we apply lexically-driven Analogy at the code level, rather than at the UML-level, in order to retrieve matching components from a repository of existing components. Using the lexical ontology Word-Net, we have conducted a case study to assess if class and method names in open source applications are used in a semantically meaningful way. Our results demonstrate that both hierarchical reuse and parallel reuse can be enhanced through the use of lexically-driven Analogy.},
	keywords = {class, developers, functions, jrefactory, method, naming, natural language, reuse, source code, wordnet},
	doi = {10.1049/ic:20040487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/112LASER.pdf},
	author = {Amin, R. and Mel O Cinneide and Veale, Tony}
}
