![]() ![]() When the creation cost is low, the feedback loop is short, and we can routinely use sequence diagrams to appreciate the impact of code changes on the overall system design. Our aim is to automate the sequence diagrams generation from run-time measurements. The designer must ultimately decide if the increased complexity (new classes) is justified. It is tempting to create layers of abstractions everywhere to increase flexibility, I made a more complex proposal in the use case above. method START( ), there is no ripple effect of change through the system. As long as they abide by the contract, e.g. With a stable interface, caller and called actors can change independently. The design pattern here is to evaluate which parts of the system are likely to change and to isolate those parts in new actors with carefully crafted interfaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |