Validating the TAME resource data model
ICSE '88 Proceedings of the 10th international conference on Software engineering
Software complexity and maintenance costs
Communications of the ACM
Technology-driven business evolution
Journal of Systems and Software
Metrics for data warehouse conceptual models understandability
Information and Software Technology
Architecting-problems rooted in requirements
Information and Software Technology
Defining and validating metrics for assessing the understandability of entity-relationship diagrams
Data & Knowledge Engineering
Teaching disciplined software development
Journal of Systems and Software
Guidelines on the aesthetic quality of UML class diagrams
Information and Software Technology
A study on managing the performance requirements of a distributed service delivery software system
Information and Software Technology
Investigating the impact of a measurement program on software quality
Information and Software Technology
Information Sciences: an International Journal
BDTEX: A GQM-based Bayesian approach for the detection of antipatterns
Journal of Systems and Software
Dynamic cohesion measures for object-oriented software
Journal of Systems Architecture: the EUROMICRO Journal
Expert Systems with Applications: An International Journal
Information and Software Technology
On generating mutants for AspectJ programs
Information and Software Technology
Software project control centers: concepts and approaches
Journal of Systems and Software
Combining lexical and structural information for static bug localisation
International Journal of Computer Applications in Technology
Reusability metrics for program source code written in c language and their evaluation
PROFES'12 Proceedings of the 13th international conference on Product-Focused Software Process Improvement
Validating software metrics: A spectrum of philosophies
ACM Transactions on Software Engineering and Methodology (TOSEM)
SWET-QUM: a quality in use extension model for semantic web exploration tools
Proceedings of the 13th International Conference on Interacción Persona-Ordenador
Issue ownership activity in two large software projects
ACM SIGSOFT Software Engineering Notes
A framework for measuring and evaluating program source code quality
PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
Review: Recent developments in the organization goals conformance using ontology
Expert Systems with Applications: An International Journal
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
International Journal of Web Engineering and Technology
AiOLoS: A model for assessing organizational learning in software development organizations
Information and Software Technology
Software evolution visualization: A systematic mapping study
Information and Software Technology
A decision support framework for metrics selection in goal-based measurement programs: GQM-DSFMS
Journal of Systems and Software
Hi-index | 0.02 |
An effective data collection method for evaluating software development methodologies and for studying the software development process is described. The method uses goal-directed data collection to evaluate methodologies with respect to the claims made for them. Such claims are used as a basis for defining the goals of the data collection, establishing a list of questions of interest to be answered by data analysis, defining a set of data categorization schemes, and designing a data collection form. The data to be collected are based on the changes made to the software during development, and are obtained when the changes are made. To ensure accuracy of the data, validation is performed concurrently with software development and data collection. Validation is based on interviews with those people supplying the data. Results from using the methodology show that data validation is a necessary part of change data collection. Without it, as much as 50 percent of the data may be erroneous. Feasibility of the data collection methodology was demonstrated by applying it to five different projects in two different environments. The application showed that the methodology was both feasible and useful.