Ideally, business rules and logic should reside in a separate project, which should not depend on other projects in the application. The behavior responsible for choosing which items to format should be kept separate from the behavior responsible for formatting the items, since these behaviors are separate concerns that are only coincidentally related to one another.Īrchitecturally, applications can be logically built to follow this principle by separating core business behavior from infrastructure and user-interface logic. For instance, consider an application that includes logic for identifying noteworthy items to display to the user, and which formats such items in a particular way to make them more noticeable. This principle asserts that software should be separated based on the kinds of work it performs. Common design principles Separation of concernsĪ guiding principle when developing is Separation of Concerns. Generally, these principles will guide you toward building applications out of discrete components that are not tightly coupled to other parts of your application, but rather communicate through explicit interfaces or messaging systems. The principles outlined in this section can help guide you toward architectural decisions that will result in clean, maintainable applications. You should architect and design software solutions with maintainability in mind. "If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." - Gerald Weinberg
0 Comments
Leave a Reply. |