Software risk management
The missing link in requirements engineering
ACM SIGSOFT Software Engineering Notes
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
A scenario-driven approach to traceability
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
An Object-Oriented Tool for Tracing Requirements
IEEE Software
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track1 - Volume 1
Global software development at siemens: experience from nine projects
Proceedings of the 27th international conference on Software engineering
A case study on value-based requirements tracing
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Value-Based Software Engineering
Value-Based Software Engineering
Determining the cost-quality trade-off for automated software traceability
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
The institutional aspect of the responsibility distribution in the IT enterprise
EuroIMSA '08 Proceedings of the IASTED International Conference on Internet and Multimedia Systems and Applications
VRRM: a value-based requirements' risk management process
SE '08 Proceedings of the IASTED International Conference on Software Engineering
Hi-index | 0.00 |
A recent survey with project managers of highly distributed projects at Siemens Program and Systems Engineering (PSE) brought up as main challenges: more severe communication hurdles compared to collocated teams and higher effort to communicate requirements in the team. In this paper, we address requirements tracing options to facilitate risk management with requirements clarification, collaboration, and knowledge management. We propose concepts for enhanced requirements tracing that include the rationale for requirements, related decisions, their history; and stakeholder value propositions. We sketch a cost-benefit model that helps the project manager to understand what tracing approach is worthwhile to address requirements risk in a project. The outcome lays the basis for planning empirical studies at PSE.