@article {18448,
	title = {Understanding the High-Performance-Computing Community: A Software Engineer{\textquoteright}s Perspective},
	journal = {Software, IEEE},
	volume = {25},
	year = {2008},
	month = {2008/08//july},
	pages = {29 - 36},
	abstract = {Computational scientists developing software for HPC systems face unique software engineering issues. Attempts to transfer SE technologies to this domain must take these issues into account.},
	keywords = {community;software, computational, engineering;, engineering;software, Science, software;high-performance-computing},
	isbn = {0740-7459},
	doi = {10.1109/MS.2008.103},
	author = {Basili, Victor R. and Carver, J. C and Cruzes, D. and Hochstein, L. M and Hollingsworth, Jeffrey K and Shull, F. and Zelkowitz, Marvin V}
}
@article {12140,
	title = {Iterative and incremental developments. a brief history},
	journal = {Computer},
	volume = {36},
	year = {2003},
	month = {2003/06//},
	pages = {47 - 56},
	abstract = {Although many view iterative and incremental development as a modern practice, its application dates as far back as the mid-1950s. Prominent software-engineering thought leaders from each succeeding decade supported IID practices, and many large projects used them successfully. These practices may have differed in their details, but all had a common theme-to avoid a single-pass sequential, document-driven, gated-step approach.},
	keywords = {agile, and, developments;iterative, engineering;, engineering;software, enhancement;software, incremental, methods;iterative, system;history;software},
	isbn = {0018-9162},
	doi = {10.1109/MC.2003.1204375},
	author = {Larman,C. and Basili, Victor R.}
}
@conference {12120,
	title = {An experience management system for a software engineering research organization},
	booktitle = {Software Engineering Workshop, 2001. Proceedings. 26th Annual NASA Goddard},
	year = {2001},
	month = {2001///},
	pages = {29 - 35},
	abstract = {Most businesses rely on the fact that their employees possess relevant knowledge and that they can apply it to the task at hand. The problem is that this knowledge is not owned by the organization. It is owned and controlled by its employees. Maintaining an appropriate level of knowledge in the organization is a very important issue. It is, however, not an easy task for most organizations, and it is particularly problematic for software organizations, which are human- and knowledge-intensive. Knowledge management is a relatively new area that has attempted to address these problems. This paper introduces an approach called the "knowledge dust-to-pearls" approach. This approach addresses some of the issues with knowledge management by providing low-barrier mechanisms to "jump start" the experience base. This approach allows the experience base to become more useful more quickly than traditional approaches. This paper describes the approach and gives an example of its use at the Fraunhofer Center for Experimental Software Engineering, Maryland, USA},
	keywords = {and, approach;knowledge, base;experience, Center, control;knowledge, data, development, dust-to-pearls, engineering, Engineering;business, engineering;software, experimental, for, Fraunhofer, houses;, knowledge;employee, knowledge;experience, level, maintenance;knowledge, management, management;knowledge, management;software, mechanisms;software, organization;software, organizational, organizations;administrative, organizations;knowledge, organizations;low-barrier, ownership;knowledge-intensive, processing;personnel;research, research, software, system;human-intensive},
	doi = {10.1109/SEW.2001.992652},
	author = {Basili, Victor R. and Costa,P. and Lindvall,M. and Mendonca,M. and Seaman,C. and Tesoriero,R. and Zelkowitz, Marvin V}
}
