Abstract
Benchmarking1 studies based on actual data supplied by many industrial sites require two types of validation: validation of the collection process as well as validation of the data supplied to the researchers. The former validation will be referred to as a priori validation and the later one as a posteriori validation. The a priori validation will review all the steps and procedures of the data collection process within benchmarking data. The a posteriori validation will establish the degree of quality of the data collected and, wherever required, will eliminate from the comparative studies the data deemed not reliable. Both types of validation are required to ensure the quality and the integrity of the data for meaningful benchmarking studies in software engineering due the current immaturity of both software metrics and software engineering processes at industrial sites as assessed the maturity model developed by the Software Engineering Institute (USA).
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1997 Betriebswirtschaftlicher Verlag Dr. Th. Gabler GmbH, Wiesbaden
About this chapter
Cite this chapter
Desharnais, JM., Morris, P. (1997). Validation Process in Software Engineering: An example with Function Point. In: Lehner, F., Dumke, R., Abran, A. (eds) Software Metrics. Information Engineering und IV-Controlling. Deutscher Universitätsverlag, Wiesbaden. https://doi.org/10.1007/978-3-322-99929-0_12
Download citation
DOI: https://doi.org/10.1007/978-3-322-99929-0_12
Publisher Name: Deutscher Universitätsverlag, Wiesbaden
Print ISBN: 978-3-8244-6518-7
Online ISBN: 978-3-322-99929-0
eBook Packages: Springer Book Archive