Components of Software Development Risk: How to Address Them? A Project Manager Survey
IEEE Transactions on Software Engineering
How Experienced Project Managers Assess Risk
IEEE Software
COTS Software: The Economical Choice?
IEEE Software
Not All CBS Are Created Equally: COTS-Intensive Project Types
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
Risks and challenges of component-based software development
Communications of the ACM - Program compaction
Overlooked Aspects of COTS-Based Development
IEEE Software
A Critical Look at Open Source
Computer
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Barriers to disseminating off-the-shelf based development theories to IT industry
MPEC '05 Proceedings of the second international workshop on Models and processes for the evaluation of off-the-shelf components
Switch or Struggle: Risk Assessment for Late Integration of COTS Components
IWICSS '07 Proceedings of the Second International Workshop on Incorporating COTS Software into Software Systems: Tools and Techniques
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Hi-index | 0.01 |
Software components, both Commercial-Off-The-Shelf and Open Source, are being increasingly used in software development. Previous studies have identified typical risks and related risk management strategies for what we will call OTS-based (Off-the-Shelf) development. However, there are few effective and well-proven guidelines to help project managers to identify and manage these risks. We are performing an international state-of-the-practice survey in three countries – Norway, Italy, and Germany – to investigate the relative frequency of typical risks, and the effect of the corresponding risk management methods. Preliminary results show that risks concerning changing requirements and effort estimation are the most frequent risks. Risks concerning traditional quality attributes such as reliability and security of OTS component seem less frequent. Incremental testing and strict quality evaluation have been used to manage the possible negative impact of poor component quality. Realistic effort estimation on OTS quality evaluation helped to mitigate the possible effort estimation biases in OTS component selection and integration.