Metrics to Assess the Likelihood of Project Success Basedon Architecture Reviews

Authors:
Alberto Avritzer;Elaine J. Weyuker
Affiliations:
AT&T Network Computing Services, Middletown, NJ 07748;AT&T Labs—Research, Florham Park, NJ 07932
Venue:
Empirical Software Engineering
Year:
1999

Citing 5
Cited 4

Collecting and categorizing software error data in an industrial environment

Journal of Systems and Software - Special issue on the fifth Minnowbrook workshop on software performance evaluation
Introduction to the Special Issue on Software Architecture

IEEE Transactions on Software Engineering - Special issue on software architecture
Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Architectural Mismatch: Why Reuse Is So Hard

IEEE Software
Architectural Mismatch: Why Reuse Is So Hard

IEEE Software

Prediction = power

TestCom'03 Proceedings of the 15th IFIP international conference on Testing of communicating systems
Comparing the effectiveness of testing techniques

Formal methods and testing
Sustainability evaluation of software architectures: a systematic review

Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
A systematic review of software architecture evolution research

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Architectureaudits are performed very early in the software development lifecycle,typically before low level design or code implementation hasbegun. An empirical study was performed to assess metrics developedto predict the likelihood of risk of failure of a project. Thestudy used data collected during 50 architecture audits performedover a period of two years for large industrial telecommunicationssystems. The purpose of such a predictor was to identify at avery early stage, projects that were likely to be at high riskof failure. This would enable the project to take correctiveaction before significant resources had been expended using aproblematic architecture. Detailed information about seven ofthe 50 projects is presented, and a discussion of how the proposedmetric rated each of these projects is presented,. A comparisonis made of the metric‘s evaluation and the assessment of theproject made by reviewers during the review process.