ABSTRACT
An implicit assumption in the rst paragraph is that validated and veried requirements have been elicited, are correctly scoped, and are of sucient depth to permit development
CONTENTS 7.1 Making the Case for Design Processes 99 7.2 Overall Goals for this Form of Analysis 100 7.3 Paper Summaries 101 7.4 Structure of the Design Process 101 7.5 Phases and Activities 103 7.6 Articulation and Roles 104 7.7 Note on Documentation 104 7.8 Issues 105 Acknowledgment 105 References 105
to proceed in a controlled and orderly fashion. is is increasingly unlikely because of increased ecological complexity (Jarke et al., 2011). Even if requirements are correctly specied, the advances typied by the evolution of the patterns communities illustrate that so ware developers have to cross a steep learning curve in order to populate the solution space with meaningful alternatives necessary to synthesize a somewhat optimal design. ese considerations prompt questions as to the strategies that novices can fall back on in the absence of such wisdom, and the mechanism by which experienced engineers can evaluate their practices. An abstract design process would be an appropriate starting point: one that provides guidance on the types of decision-making strategies and techniques that might be adopted, and their distribution over the development life cycle.
