A Trace Metamodel Proposal Based on the Model Driven Architecture Framework for the Traceability of User Requirements in Data Warehouses - Advanced Information Systems Engineering - page 132

Fig. 8. Requirements modeled by using our i* profile for DW and its corresponding
multidimensional model

per week. These requirements are recorded in a CIM which acts as the starting
point for the process.
In figure 8, we can see the requirements on the left side, where the business
process (focus of the analysis) in this case is the student success. Its correspond-
ing contexts are the students and the students grouped by hours of study per
week (shown in the figure), the subjects and the professors (omitted due to
space constraints). On the right hand of the figure, we can see the PIM with
the StarPackage “SP student success, the FactPackage “FP student success and
the Fact “Student success”, associated with the business process. The measure
“student grades” is associated with its corresponding FactAttribute, whereas
the “student” context derives into the DimensionPackage “DP Student”, the
Dimension “Student”, the base level “Student” and its association with the di-
mension. Lastly, the aggregated context “Students by hours of study” derives
into its corresponding level and the association towards the previous level in the
dimension (in this case “student” level). Table 2 summarizes the relationships
between elements and its corresponding transformation rule.

Table 2. Elements linked between CIM and PIM models by satisfiability links

Satisfiability link rule name Source Elements (CIM) Target Elements (PIM)

BusinessProcess2Fact Student success SP Student sucess,

FP Student sucess,
Student sucess

Measure2FactAttribute Grades Grades

Context2Dimension Student DP Student,Student(Dime)

Student(Level),Association

Context2Base Students by hours of study Students by

hours of study (Level),
Association