Traditional engineering design discipline calls for designs to be evaluated long before they are implemented. Early design evaluations predict properties of the artifact that will result from a proper implementation of the design and the value of those properties to the client or end user. The predicted properties can include costs as well as functionality, performance, and quality measures. Software engineering has some such evaluation techniques but the discipline lacks a systematic way to explain, compare, develop, and apply them. This paper discuss the role of early predictive design evaluation in software design, show how a variety of specific predictors serve this role, and propose a unifying framework, Predictive Analysis for Design (PAD) for design evaluation techniques. Focus is given in techniques that predict the value of the finished software system to its client or end user and that make the predictions before the expense of software development or integration is incurred. It is shown that the PAD framework, even in its preliminary state, is sufficiently expressive to be useful in explaining and characterizing design evaluation techniques.
Adobe .pdf files require the Adobe Acrobat Reader.
Download and install the Adobe Acrobat Reader.