@conference {12163,
	title = {Tool supported detection and judgment of nonconformance in process execution},
	booktitle = {Empirical Software Engineering and Measurement, 2009. ESEM 2009. 3rd International Symposium on},
	year = {2009},
	month = {2009/10//},
	pages = {312 - 323},
	abstract = {In the past decades the software engineering community has proposed a large collection of software development life cycles, models, and processes. The goal of a major set of these processes is to assure that the product is finished within time and budget, and that a predefined set of functional and nonfunctional requirements (e.g. quality goals) are satisfied at delivery time. Based upon the assumption that there is a real relationship between the process applied and the characteristics of the product developed from that process, we developed a tool supported approach that uses process nonconformance detection to identify potential risks in achieving the required process characteristics. In this paper we present the approach and a feasibility study that demonstrates its use on a large-scale software development project in the aerospace domain. We demonstrate that our approach, in addition to meeting the criteria above, can be applied to a real system of reasonable size; can represent a useful and adequate set of rules of relevance in such an environment; and can detect relevant examples of process nonconformance that provide useful insight to the project manager.},
	keywords = {aerospace, community;tool, cycle;software, detection;software, development, domain;large-scale, engineering, execution;process, life, management;software, nonconformance, project;nonfunctional, requirement;process, software, supported, tools;},
	doi = {10.1109/ESEM.2009.5315983},
	author = {Zazworka, N. and Basili, Victor R. and Shull, F.}
}
@article {12133,
	title = {Experience in implementing a learning software organization},
	journal = {Software, IEEE},
	volume = {19},
	year = {2002},
	month = {2002/06//may},
	pages = {46 - 49},
	abstract = {In an effort to improve software development and acquisition processes and explicitly reuse knowledge from previous software projects, DaimlerChrysler created a software experience center (SEC). The authors report on challenges the company faced in creating the SEC},
	keywords = {ACQUISITION, center;software, centres;project, DaimlerChrysler;explicit, development, experience, improvement;, improvement;automobile, industry;computer, knowledge, management;software, organization;previous, process, processes;software, projects;software, reuse;learning, software},
	isbn = {0740-7459},
	doi = {10.1109/MS.2002.1003453},
	author = {Schneider,K. and von Hunnius,J.-P. and Basili, Victor R.}
}
@conference {12107,
	title = {A light-weight process for capturing and evolving defect reduction experience},
	booktitle = {Engineering of Complex Computer Systems, 2002. Proceedings. Eighth IEEE International Conference on},
	year = {2002},
	month = {2002/12//},
	pages = {129 - 132},
	abstract = {Selecting technologies for developing software is a crucial activity in software projects. Defect reduction is an example of an area in which software developers have to decide what technologies to use. CeBASE is a NSF funded project that has the role of improving software development by providing decision support on the selection of techniques and tools. The decision support is based on empirical data organized in experience bases and refined into high-level models. Empirical data is collected through various activities, for example through eWorkshops in which experts discuss important issues, and formalized using the lightweight knowledge dust to knowledge pearl process.},
	keywords = {bases;experience, CeBASE;NSF, defect, development;software, experience;software, funded, knowledge;software, management;lightweight, management;software, project;decision, projects;software, reduction, reusability;software, reuse;software, support;eWorkshops;experience, tools;, tools;knowledge},
	doi = {10.1109/ICECCS.2002.1181505},
	author = {Basili, Victor R. and Lindvall,M. and Shull, F.}
}
@article {12126,
	title = {COTS-based systems top 10 list},
	journal = {Computer},
	volume = {34},
	year = {2001},
	month = {2001/05//},
	pages = {91 - 95},
	abstract = {Presents a COTS-based system (CBS) software defect-reduction list as hypotheses, rather than results, that also serve as software challenges for enhancing our empirical understanding of CBSs. The hypotheses are: (1) more than 99\% of all executing computer instructions come from COTS products (each instruction passed a market test for value); (2) more than half the features in large COTS software products go unused; (3) the average COTS software product undergoes a new release every 8-9 months, with active vendor support for only its latest three releases; (4) CBS development and post-deployment efforts can scale as high as the square of the number of independently developed COTS products targeted for integration; (5) CBS post-deployment costs exceed CBS development costs; (6) although glue-code development usually accounts for less than half the total CBS software development effort, the effort per line of glue code averages about three times the effort per line of developed applications code; (7) non-development costs, such as licensing fees, are significant, and projects must plan for and optimize them; (8) CBS assessment and tailoring efforts vary significantly by COTS product class (operating system, database management system, user interface, device driver, etc.); (9) personnel capability and experience remain the dominant factors influencing CBS development productivity; and (10) CBS is currently a high-risk activity, with effort and schedule overruns exceeding non-CBS software overruns, yet many systems have used COTS successfully for cost reduction and early delivery},
	keywords = {activity;hypotheses;independently, capability;personnel, challenges;software, code, COTS-based, defect, delivery;glue, developed, development, development;high-risk, effort;products, effort;software, efforts;unused, experience;post-deployment, features;software, instructions;costs;development, integration;schedule, management;software, off-the, overruns;software, packages;software, productivity;early, products;personnel, quality;, reduction;software, releases;system, shelf, support;commercial, systems;active, systems;computer, vendor},
	isbn = {0018-9162},
	doi = {10.1109/2.920618},
	author = {Basili, Victor R. and Boehm,B.}
}
@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}
}
@article {18430,
	title = {Software engineering technology infusion within NASA},
	journal = {Engineering Management, IEEE Transactions on},
	volume = {43},
	year = {1996},
	month = {1996/08//},
	pages = {250 - 261},
	abstract = {Abstract technology transfer is of crucial concern to both government and industry today. In this paper, several software engineering technologies used within NASA are studied, and the mechanisms, schedules, and efforts at transferring these technologies are investigated. The goals of this study are: (1) to understand the difference between technology transfer (the adoption of a new method by large segments of an industry) as an industrywide phenomenon and the adoption of a new technology by an individual organization (called technology infusion); and (2) to see if software engineering technology transfer differs from other engineering disciplines. While there is great interest today in developing technology transfer models for industry, it is the technology infusion process that actually causes changes in the current state of the practice},
	keywords = {and, computing;aerospace, development, development;aerospace, disciplines;government;industry;software, engineering, industry;research, infusion;technology, management;software, management;technology, MODELS, NASA;engineering, technologies;technology, transfer, transfer;},
	isbn = {0018-9391},
	doi = {10.1109/17.511836},
	author = {Zelkowitz, Marvin V}
}
