@article {12572,
	title = {Signal Processing for Biometric Systems [DSP Forum]},
	journal = {Signal Processing Magazine, IEEE},
	volume = {24},
	year = {2007},
	month = {2007/11//},
	pages = {146 - 152},
	abstract = {This IEEE signal processing magazine (SPM) forum discuses signal processing applications, technologies, requirements, and standardization of biometric systems. The forum members bring their expert insights into issues such as biometric security, privacy, and multibiometric and fusion techniques. The invited forum members are Prof. Anil K. Jain of Michigan State University, Prof. Rama Chellappa of the University of Maryland, Dr. Stark C. Draper of theUniversity of Wisconsin in Madison, Prof. Nasir Memon of Polytechnic University, and Dr. P. Jonathon Phillips of the National Institute of Standards and Technology. The moderator of the forum is Dr. Anthony Vetro of Mitsubishi Electric Research Labs, and associate editor of SPM.},
	keywords = {(access, biometric, control);security;signal, forum;signal, magazine, PROCESSING, processing;, security;biometric, standardization;fusion, systems, technique;multibiometric, technique;signal, technology;biometrics},
	isbn = {1053-5888},
	doi = {10.1109/MSP.2007.905886},
	author = {Jain, A.K. and Chellapa, Rama and Draper, S.C. and Memon, N. and Phillips,P.J. and Vetro, A.}
}
@article {12129,
	title = {Eight lessons learned during COTS-based systems maintenance},
	journal = {Software, IEEE},
	volume = {20},
	year = {2003},
	month = {2003/10//sept},
	pages = {94 - 96},
	abstract = {To make better decisions relative to CBSs, we need empirical knowledge. To gain this knowledge, we must more fully understand the lifecycle processes people use when harnessing COTS packages. The initial findings reported here are but the first step in our attempts to capture this empirical knowledge. We plan to continue collecting data and investigating the phenomenology of COTS-based systems.},
	keywords = {COTS, COTS-based, cycle, life, lifecycle, Maintenance, maintenance;, object-oriented, packages;, phase;, processes;, programming;, reusability;, software, systems},
	isbn = {0740-7459},
	doi = {10.1109/MS.2003.1231161},
	author = {Reifer,D.J. and Basili, Victor R. and Boehm,B.W. and Clark,B.}
}
@article {12165,
	title = {User interface evaluation and empirically-based evolution of a prototype experience management tool},
	journal = {Software Engineering, IEEE Transactions on},
	volume = {29},
	year = {2003},
	month = {2003/09//},
	pages = {838 - 850},
	abstract = {Experience management refers to the capture, structuring, analysis, synthesis, and reuse of an organization{\textquoteright}s experience in the form of documents, plans, templates, processes, data, etc. The problem of managing experience effectively is not unique to software development, but the field of software engineering has had a high-level approach to this problem for some time. The Experience Factory is an organizational infrastructure whose goal is to produce, store, and reuse experiences gained in a software development organization. This paper describes The Q-Labs Experience Management System (Q-Labs EMS), which is based on the Experience Factory concept and was developed for use in a multinational software engineering consultancy. A critical aspect of the Q-Labs EMS project is its emphasis on empirical evaluation as a major driver of its development and evolution. The initial prototype requirements were grounded in the organizational needs and vision of Q-Labs, as were the goals and evaluation criteria later used to evaluate the prototype. However, the Q-Labs EMS architecture, data model, and user interface were designed to evolve, based on evolving user needs. This paper describes this approach, including the evaluation that was conducted of the initial prototype and its implications for the further development of systems to support software experience management.},
	keywords = {data, development;, empirical, EMS;, engineering;, evaluation;, experience, experience;, Factory;, interface, interfaces;, knowledge, management, management;, model;, models;, organization, performance, prototype, Q-Labs, re-engineering;, reusability;, reuse;, software, system;, systems, tool;, user},
	isbn = {0098-5589},
	doi = {10.1109/TSE.2003.1232288},
	author = {Seaman,C.B and Mendonca,M.G. and Basili, Victor R. and Kim,Y. M}
}
@conference {18400,
	title = {Maintaining software with a security perspective},
	booktitle = {Software Maintenance, 2002. Proceedings. International Conference on},
	year = {2002},
	month = {2002///},
	pages = {194 - 203},
	abstract = {Testing for software security is a lengthy, complex and costly process. Currently, security testing is done using penetration analysis and formal verification of security kernels. These methods are not complete and are difficult to use. Hence it is essential to focus testing effort in areas that have a greater number of security vulnerabilities to develop secure software as well as meet budget and time constraints. We propose a testing strategy based on a classification of vulnerabilities to develop secure and stable systems. This taxonomy will enable a system testing and maintenance group to understand the distribution of security vulnerabilities and prioritize their testing effort according to the impact the vulnerabilities have on the system. This is based on Landwehr{\textquoteright}s (1994) classification scheme for security flaws and we evaluated it using a database of 1360 operating system vulnerabilities. This analysis indicates vulnerabilities tend to be focused in relatively few areas and associated with a small number of software engineering issues.},
	keywords = {(computers);, budget, classification, classification;, constraints;, data;, engineering;, flaw, maintenance;, of, operating, program, scheme;, Security, software, stable, system, systems, systems;, testing;, TIME, vulnerabilities;, vulnerability},
	doi = {10.1109/ICSM.2002.1167766},
	author = {Jiwnani,K. and Zelkowitz, Marvin V}
}
