Using Inspection Data for Defect Estimation
IEEE Software
Stakeholder Risk Assessment: An Outcome-Based Approach
IEEE Software
Complex Systems and Agent-Oriented Software Engineering
Engineering Environment-Mediated Multi-Agent Systems
Extraction of the Project Risk Knowledge on the Basis of a Project Plan
KES '08 Proceedings of the 12th international conference on Knowledge-Based Intelligent Information and Engineering Systems, Part II
Choquet integral based aggregation approach to software development risk assessment
Information Sciences: an International Journal
Agile commitments: enhancing business risk management in agile development projects
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Towards formulation of software project risk radars
International Journal of Business Information Systems
Assessment of business value from services re-use on SOA-based e-business platform
Proceedings of the 12th International Conference on Information Integration and Web-based Applications & Services
Multiple risk management process supported by ontology
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
| Hi-index | 0.00 |
In mature engineering disciplines, risk management has been de rigeur for centuries. When Michelangelo set out to raise the dome of St. Peters in 1547, he was well aware of the potential collapse zones under the staging, the possibility of materials failure, and the human capacity for error. For each of these major risks he prepared a mitigation plan: a fallback, a safety factor, or an alternative. Today, we routinely practice risk management in our stewardship of the environment, in planning financial strategy, in construction engineering, and in medicine. But how do we apply it to the ultimate risky business, software development?