An Ontology for Microarchitectural Design Knowledge
IEEE Software
Do rules and patterns affect design maintainability?
Journal of Computer Science and Technology
Improving object-oriented micro architectural design through knowledge systematization
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Solving the mapping problem in user interface design by seamless integration in IDEALXML
DSVIS'05 Proceedings of the 12th international conference on Interactive Systems: design, specification, and verification
| Hi-index | 4.10 |
Early in the history of programming, brilliant people realized that every good software system has some desirable properties: It should be extensible; parts of it should be modifiable without major impact on other parts; and so on. Because of the Feigenbaum Bottleneck, it is very hard to describe precise, step-by-step instructions to build systems with such properties. It is easier to articulate the desirable properties in the form of design principles. Over the years, the wealth of knowledge accumulated as design principles has reached a critical mass. Entire books are now dedicated to the subject. Still, despite this body of knowledge, design remains difficult. A major problem is that principles are ambiguous and not very constructive. In more recent times, design patterns have emerged as a valid alternative to the principles-driven approach. If principles represent the “say-what” approach to design, patterns are the “show-how” way