![]() ![]() Most of the related work to date has focused on defining the architectural structure of application frameworks or on maintaining structural and behavioral consistency. We also need to make certain that as we expand the domain model to accommodate new applications, that these future applications are not unnecessarily constrained or complex. In order for systems to be successfully implemented from such application frameworks, there are two major concerns that must be addressed: how do we maintain non-interfering applications and how do we minimize bias towards any individual application in developing the domain model? In other words, as we add new applications, we need to ensure that they are not destructive to each other. A sample API specification and other useful resources and tools are also included.The areas of domain engineering, vertical application frameworks, and business objects have generated considerable interest in industry and the research community during the last few years. NET Class Libraries video series, instructional presentations by the authors on design guidelines for developing classes and components that extend the. Every guideline includes a discussion of its applicability, and most include a code example to help illuminate the dialogue.įramework Design Guidelines, Second Edition, is the only definitive source of best practices for managed code API development, direct from the architects themselves.Ī companion DVD includes the Designing. These directives help focus attention on practices that should always be used, those that should generally be used, those that should rarely be used, and those that should never be used. ![]() Guidelines in this book are presented in four major forms: Do, Consider, Avoid, and Do not. Guidelines for–and examples of–common framework design patterns.Issues affecting–and guidelines for ensuring–extensibility. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |