Chapter 2 presents the final version of the thesis of this dissertation: Thesis statement of dissertation (final version, taken from Chapter 2) Role modeling for framework design makes the following activities easier to carry out for the expert framework developer and user than is possible with traditional class-based approaches: This form of the thesis helps to determine what to prove and which constraints to adhere to while doing so.
These are separate activities that can be discussed and validated independently.
Finally, the thesis defines in which respect role modeling eases the different activities by stating which problems it addresses: class complexity, object collaboration complexity, and clarity of requirements and constraints put upon use-clients.
The experiences with designing the Geo frameworks and the Tools framework support this argument.
For example, the Geo system has several complex service interfaces.
Unless stated otherwise, role modeling always means "role modeling for framework design as defined in this dissertation".
Traditional class-based approach means what you can natively express using classes as the only central modeling concept (for example, UML).
It follows the validation strategy outlined above: it first walks through a set of key properties of the role modeling method, and then consolidates the resulting arguments for each sub-validation.
The thesis validation follows as the conjunction of the sub-validations.
On the other hand, they focus on the composition of the role types to understand what makes up the class as a whole and how acting in the context of one role will cause actions in the context of another role of instances of that class.
Describing a class as the composition of role types and breaking up a class interface into role types separates design concerns along the lines of object collaboration tasks.