The Requirements Apprentice: Automated Assistance for Requirements Acquisition
IEEE Transactions on Software Engineering
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
The Domain Theory for Requirements Engineering
IEEE Transactions on Software Engineering
A survey of software inspection checklists
ACM SIGSOFT Software Engineering Notes
Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Further Experiences with Scenarios and Checklists
Empirical Software Engineering
Critiquing Software Specifications
IEEE Software
Social Analysis in the Requirements Engineering Process: From Ethnography to Method
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Getting the requirements right-a professional approach
STEP '97 Proceedings of the 8th International Workshop on Software Technology and Engineering Practice (STEP '97) (including CASE '97)
A comedy of errors: the London Ambulance Service case study
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
| Hi-index | 0.00 |
Requirements completeness and correctness are perhaps the most difficult yet vital issues to identify during validation. If they are not properly identified and resolved early on, they become a serious threat to quality and cost, especially for large software development ventures. Conventional techniques for validation are generally inadequate for such issues. This paper reports an inspection technique named Traceability-based Requirements Inspection that helps identify and resolve these issues by addressing the pre-tracebility of requirements in the documented domain knowledge. The technique is supplemented with appropriate metrics, procedures and a tool named Pensieve to facilitate identification, reporting and resolution of completeness and correctness issues. The viability of the technique has been assessed through a case study, the results of which are also reported and discussed.