In addition to the tactics for performance that we have just discussed, the authors of our book provide an interesting checklist to improve the design that covers some other hints for steps that a designer could take.
This design checklist for performance is provided as additional material in Moodle and we just want to have a look over it. This will not be covered by the exams, however I consider it as a valuable material for your professional work.
This design checklist is again structured according to the categories of design decisions, so starting with allocation of responsibility and then the coordination model, data model and so forth.
If we just have a look over it, then this allocation of responsibilities category helps us or asks us that we identify what are the requirements that are important here, that we recognize and that we assess the things to recognition and processing requests or controls,
how to manage them, to think over shared resources and this helps us in organizing the tactics. Coordination model, you remember hopefully to this category, is about dynamics, is about behavior, is about operation regarding communication.
And so the choice of communication mechanisms has a big impact on the efficiency of the operation, so concurrency is important, can we do some insurance here, how can we do this with this sequence of events, periodic and so far.
The data model is important for success for the efficiency, as well for example, the partitioning data or multiple copies of data or we could care about bottlenecks regarding the data processing.
Okay, let's go to the next. Mapping is for deployment, is for structuring the system into parts. Resource management has a big impact on performance as well.
So just check here, they introduce some interesting questions and binding time is not so important, however, the other things are quite helpful. So this is, again, this will not be asked in the exam, however, it's very valuable.
In our book we have two of these design checklists, one for performance and one for modifiability.