5.4.4 Analysis of MCCGen

Figure 5.2: ProcessMan’s domain model.

(shown at the top-right of the figure) is placed in the package processstructure.model of the software module named processstructure.

As shown in the figure, the domain module processstructure consists of three domain classes (Process, Task, Action) that together describe the general structure of a process, and two other domain classes (Task4Subject, Action4Subject) that describe a specialised structure for the teaching and assessment processes. Task4Subject specialises Task, while Action4Subject specialises Action. The reason that we only specialise Task and Action and not Process is because class Process suffices for use as a common abstraction for all types of processes. At the process level, there is no real distinction between the processes.

The domain module processapplication consists of four domain classes: two of which (OrgUnit and ProcessApplication) represent the periodic application of a Process, while the other two (SubjectTask and SubjectAction) serve as intermediate classes that resolve the two many-many associations between Task4Subject and Action4Subject and SubjectBySemester (resp.). Note that class OrgUnit plays another role, which is the creator

124