Evaluating for User Case Requirements
Evaluating the ability of the architecture to provide the use cases can be done by walking through the use cases. A recommendation is to do these walks quickly, because if they are done in great detail, the effort is equivalent to doing a collaboration-irreparability behaviour model with the components as objects. While this is feasible, it reduces the independence the user requirements and the development sponsor requirement.The question is, for each use case, can we start with a user and see a path through the components that looks like it will provide the required behaviour? Here, "looks like" means that the subsystem names imply they can do what is needed.
Jorge Luis Ortega Arjona.