@article {12144,
	title = {Linking Software Development and Business Strategy Through Measurement},
	journal = {Computer},
	volume = {43},
	year = {2010},
	month = {2010/04//},
	pages = {57 - 65},
	abstract = {The GQM+Strategies approach extends the goal/question/metric paradigm for measuring the success or failure of goals and strategies, adding enterprise-wide support for determining action on the basis of measurement results. An organization can thus integrate its measurement program across all levels.},
	keywords = {approach;business, aspects;software, development;organisational, engineering;, GQM+Strategies, program;software, strategy;enterprise, support;measurement, wide},
	isbn = {0018-9162},
	doi = {10.1109/MC.2010.108},
	author = {Basili, Victor R. and Lindvall,M. and Regardie,M. and Seaman,C. and Heidrich,J. and Munch,J. and Rombach,D. and Trendowicz,A.}
}
@article {12146,
	title = {Maturing Software Engineering Knowledge through Classifications: A Case Study on Unit Testing Techniques},
	journal = {Software Engineering, IEEE Transactions on},
	volume = {35},
	year = {2009},
	month = {2009/08//july},
	pages = {551 - 565},
	abstract = {Classification makes a significant contribution to advancing knowledge in both science and engineering. It is a way of investigating the relationships between the objects to be classified and identifies gaps in knowledge. Classification in engineering also has a practical application; it supports object selection. They can help mature software engineering knowledge, as classifications constitute an organized structure of knowledge items. Till date, there have been few attempts at classifying in software engineering. In this research, we examine how useful classifications in software engineering are for advancing knowledge by trying to classify testing techniques. The paper presents a preliminary classification of a set of unit testing techniques. To obtain this classification, we enacted a generic process for developing useful software engineering classifications. The proposed classification has been proven useful for maturing knowledge about testing techniques, and therefore, SE, as it helps to: 1) provide a systematic description of the techniques, 2) understand testing techniques by studying the relationships among techniques (measured in terms of differences and similarities), 3) identify potentially useful techniques that do not yet exist by analyzing gaps in the classification, and 4) support practitioners in testing technique selection by matching technique characteristics to project characteristics.},
	keywords = {characteristic;project, characteristic;software, classification;matching, engineering, engineering;, knowledge;software, technique, techniques;program, Testing, testing;software, testing;unit},
	isbn = {0098-5589},
	doi = {10.1109/TSE.2009.13},
	author = {Vegas,S. and Juristo,N. and Basili, Victor R.}
}
@article {12158,
	title = {The ASC-Alliance Projects: A Case Study of Large-Scale Parallel Scientific Code Development},
	journal = {Computer},
	volume = {41},
	year = {2008},
	month = {2008/03//},
	pages = {50 - 58},
	abstract = {Computational scientists face many challenges when developing software that runs on large-scale parallel machines. However, software-engineering researchers haven{\textquoteright}t studied their software development processes in much detail. To better understand the nature of software development in this context, the authors examined five large-scale computational science software projects operated at the five ASC-Alliance centers.},
	keywords = {ASC-Alliance, code, development;large-scale, development;parallel, engineering;, machines;software, Parallel, projects;computational, scale, Science, scientific, scientists;large, software, systems;parallel},
	isbn = {0018-9162},
	doi = {10.1109/MC.2008.101},
	author = {Hochstein, L. and Basili, Victor R.}
}
@conference {12106,
	title = {A Framework for Software Engineering Experimental Replications},
	booktitle = {Engineering of Complex Computer Systems, 2008. ICECCS 2008. 13th IEEE International Conference on},
	year = {2008},
	month = {2008/04/31/3},
	pages = {203 - 212},
	abstract = {Experimental replications are very important to the advancement of empirical software engineering. Replications are one of the key mechanisms to confirm previous experimental findings. They are also used to transfer experimental knowledge, to train people, and to expand a base of experimental evidence. Unfortunately, experimental replications are difficult endeavors. It is not easy to transfer experimental know-how and experimental findings. Based on our experience, this paper discusses this problem and proposes a Framework for Improving the Replication of Experiments (FIRE). The FIRE addresses knowledge sharing issues both at the intra-group (internal replications) and inter-group (external replications) levels. It encourages coordination of replications in order to facilitate knowledge transfer for lower cost, higher quality replications and more generalizable results.},
	keywords = {engineering, engineering;, evidence;experimental, experimental, Experiments;experimental, for, Framework, Improving, knowledge, of, replication, replication;software, sharing;software, the, transfer;knowledge},
	doi = {10.1109/ICECCS.2008.38},
	author = {Mendonca,M.G. and Maldonado,J.C. and de Oliveira,M.C.F. and Carver, J. and Fabbri,C.P.F. and Shull, F. and Travassos,G.H. and Hohn,E.N. and Basili, Victor R.}
}
@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}
}
@conference {12279,
	title = {Differentiated traffic engineering for QoS provisioning},
	booktitle = {INFOCOM 2005. 24th Annual Joint Conference of the IEEE Computer and Communications Societies. Proceedings IEEE},
	volume = {4},
	year = {2005},
	month = {2005/03//},
	pages = {2349 - 2359 vol. 4 - 2349 - 2359 vol. 4},
	abstract = {We introduce a new approach for QoS provisioning in packet networks based on the notion of differentiated traffic engineering (DTE). We consider a single AS network capable of source based multi-path routing. We do not require sophisticated queuing or per-class scheduling at individual routers; instead, if a link is used to forward QoS sensitive packets, we maintain its utilization below a threshold. As a consequence, DTE eliminates the need for per-flow (IntServ) or per-class (DiffServ) packet processing tasks such as traffic classification, queueing, shaping, policing and scheduling in the core and hence poses a lower burden on the network management unit. Conversely, DTE utilizes network bandwidth much more efficiently than simple over-provisioning. In this paper, we propose a complete architecture and an algorithmic structure for DTE. We show that our scheme can be formulated as a non-convex optimization problem, and we present an optimal solution framework based on simulated annealing. We present a simulation-based performance evaluation of DTE, and compare our scheme to existing (gradient projection) methods.},
	keywords = {based, Computer, differentiated, DiffServ, DTE;, engineering;, evaluation;, link;, links;, management;, multipath, network, networks;, nonconvex, of, optimisation;, OPTIMIZATION, packet, performance, problem;, provisioning;, QoS, QUALITY, routing;, service;, simulation-based, source, Telecommunication, traffic, traffic;},
	doi = {10.1109/INFCOM.2005.1498521},
	author = {Tabatabaee,V. and Bhattacharjee, Bobby and La,R.J. and Shayman,M.A.}
}
@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.}
}
@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}
}
@article {12121,
	title = {An operational process for goal-driven definition of measures},
	journal = {Software Engineering, IEEE Transactions on},
	volume = {28},
	year = {2002},
	month = {2002/12//},
	pages = {1106 - 1125},
	abstract = {We propose an approach (GOM/MEDEA) for defining measures of product attributes in software engineering. The approach is driven by the experimental goals of measurement, expressed via the GQM paradigm, and a set of empirical hypotheses. To make the empirical hypotheses quantitatively verifiable, GQM/MEDEA supports the definition of theoretically valid measures for the attributes of interest based on their expected mathematical properties. The empirical hypotheses are subject to experimental verification. This approach integrates several research contributions from the literature into a consistent, practical, and rigorous approach.},
	keywords = {attributes;, definition;, development, empirical, engineering;, expected, experimental, goal-driven, GQM, GQM/MEDEA;, hypotheses;, management;, mathematical, measure, measurement;, metrics;, operational, paradigm;, process;, Product, properties;, quality;, software, verification;},
	isbn = {0098-5589},
	doi = {10.1109/TSE.2002.1158285},
	author = {Briand,L.C. and Morasca,S. and Basili, Victor R.}
}
@conference {18453,
	title = {What we have learned about fighting defects},
	booktitle = {Software Metrics, 2002. Proceedings. Eighth IEEE Symposium on},
	year = {2002},
	month = {2002///},
	pages = {249 - 258},
	abstract = {The Center for Empirically Based Software Engineering helps improve software development by providing guidelines for selecting development techniques, recommending areas for further research, and supporting software engineering education. A central activity toward achieving this goal has been the running of "e- Workshops" that capture expert knowledge with a minimum of overhead effort to formulate heuristics on a particular topic. The resulting heuristics are a useful summary of the current state of knowledge in an area based on expert opinion. This paper discusses the results to date of a series of e-Workshops on software defect reduction. The original discussion items are presented along with an encapsulated summary of the expert discussion. The reformulated heuristics can be useful both to researchers (for pointing out gaps in the current state of the knowledge requiring further investigation) and to practitioners (for benchmarking or setting expectations about development practices).},
	keywords = {based, Center, Computer, defect, development;, education;, electronic, Empiric, engineering, engineering;, eWorkshops;, for, heuristics;, reduction;, Science, software, workshops;},
	doi = {10.1109/METRIC.2002.1011343},
	author = {Shull, F. and Basili, Victor R. and Boehm,B. and Brown,A. W and Costa,P. and Lindvall,M. and Port,D. and Rus,I. and Tesoriero,R. and Zelkowitz, Marvin V}
}
@article {18391,
	title = {Experimental models for validating technology},
	journal = {Computer},
	volume = {31},
	year = {1998},
	month = {1998/05//},
	pages = {23 - 31},
	abstract = {Experimentation helps determine the effectiveness of proposed theories and methods. However, computer science has not developed a concise taxonomy of methods for demonstrating the validity of new techniques. Experimentation is a crucial part of attribute evaluation and can help determine whether methods used in accordance with some theory during product development will result in software being as effective as necessary. By looking at multiple examples of technology validation, the authors develop a taxonomy for software engineering experimentation that describes twelve different experimental approaches},
	keywords = {attribute, development;software, engineering, engineering;, evaluation;computer, experimentation;technology, models;product, science;experimental, validation;product},
	isbn = {0018-9162},
	doi = {10.1109/2.675630},
	author = {Zelkowitz, Marvin V and Wallace,D. R}
}
@article {18426,
	title = {SEL{\textquoteright}s software process improvement program},
	journal = {Software, IEEE},
	volume = {12},
	year = {1995},
	month = {1995/11//},
	pages = {83 - 87},
	abstract = {We select candidates for process change on the basis of quantified Software Engineering Laboratory (SEL) experiences and clearly defined goals for the software. After we select the changes, we provide training and formulate experiment plans. We then apply the new process to one or more production projects and take detailed measurements. We assess process success by comparing these measures with the continually evolving baseline. Based upon the results of the analysis, we adopt, discard, or revise the process},
	keywords = {baseline;detailed, engineering, engineering;, evolving, improvement, Laboratory;continually, measurements;experiment, plans;production, process, program;software, projects;training;software, SEL, software},
	isbn = {0740-7459},
	doi = {10.1109/52.469763},
	author = {Basili, Victor R. and Zelkowitz, Marvin V and McGarry,F. and Page,J. and Waligora,S. and Pajerski,R.}
}
@article {18389,
	title = {Experiences building a syntax-directed editor},
	journal = {Software Engineering Journal},
	volume = {4},
	year = {1989},
	month = {1989/11//},
	pages = {294 - 294},
	abstract = {The paper presents a set of techniques for building robust software using the development of a microprocessor SUPPORT programming environment as an example. It discusses some of the attributes built into the system to best handle the concerns of portability, functionality, and effectiveness that had to be dealt with for the system to be reliable on a small machine, and it describes some of the choices made to obtain the best use of available hardware},
	keywords = {applications;, editing;, editor;, engineering;, environment;, environments;, microcomputer, microprocessor;, portability;, Programming, robust, software, software;, Support, syntax-directed, text},
	isbn = {0268-6961},
	author = {Zelkowitz, Marvin V and Kowalchack,B. and Itkin,D. and Herman,L.}
}
