A scenario-driven approach to traceability
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Recovering and using use-case-diagram-to-source-code traceability links
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Conceptual data model-based software size estimation for information systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
Software development can achieve interesting benefits through the use of requirements traceability, including improved program comprehension, easier maintenance, component reuse, impact analysis, and measure of project progress and completeness. On the other hand, while the cost of a new IS can be estimated by applying Function Point Analysis, this technique has limited application on maintenance. By determining the impact of changing a given set of features, IS development organizations can build a clear understanding of the effort that these changes will require. In this paper, we propose a technique which uses traceability to build a bridge between function points and source code. We believe that this technique can support negotiations between IS development organizations and their clients regarding changes to Information Systems.