Structured walkthroughs: 4th edition
Structured walkthroughs: 4th edition
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Learning from Our Mistakes with Defect Causal Analysis
IEEE Software
Assertions in End-User Software Engineering: A Think-Aloud Study
HCC '02 Proceedings of the IEEE 2002 Symposia on Human Centric Computing Languages and Environments (HCC'02)
Feature specification and automated conflict detection
ACM Transactions on Software Engineering and Methodology (TOSEM)
Applying sampling to improve software inspections
Journal of Systems and Software - Special issue: Applications of statistics in software engineering
Integrating agile software development into stage-gate managed product development
Empirical Software Engineering
Testing and inspecting reusable product line components: first empirical results
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Journal of Systems and Software
Guide to Advanced Empirical Software Engineering
Guide to Advanced Empirical Software Engineering
Evaluating Domain Design Approaches Using Systematic Review
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
Monitoring Software Quality Evolution for Defects
IEEE Software
The importance of documentation, design and reuse in risk management for SPL
Proceedings of the 28th ACM International Conference on Design of Communication
A Regression Testing Approach for Software Product Lines Architectures: Selecting an efficient and effective set of test cases
A Regression Testing Approach for Software Product Lines Architectures
SBCARS '10 Proceedings of the 2010 Fourth Brazilian Symposium on Software Components, Architectures and Reuse
Towards metamodel support for variability and traceability in software product lines
Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems
Extending the RiPLE-DE process with quality attribute variability realization
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
Journal of Systems and Software
Hi-index | 0.00 |
In software product lines (SPL), scoping is a phase responsible for capturing, specifying and modeling features, and also their constraints, interactions and variations. The feature specification task, performed in this phase, is usually based on natural language, which may lead to lack of clarity, non-conformities and defects. Consequently, scoping analysts may introduce ambiguity, inconsistency, omissions and non-conformities. In this sense, this paper aims at gathering evidence about the effects of applying an inspection approach to feature specification for SPL. Data from a SPL reengineering project were analyzed in this work and the analysis indicated that the correction activity demanded more effort. Also, Pareto's principle showed that incompleteness and ambiguity reported higher non-conformity occurrences. Finally, the Poisson regression analysis showed that sub-domain risk information can be a good indicator for prioritization of sub-domains in the inspection activity.