br.usp.ime.xpusp.om.map

Overview

Package

Class

Use

Deprecated

Index

Home >> All >> br >> usp >> ime >> xpusp >> om >> [ map overview ]

PREV PACKAGE NEXT PACKAGE

Package br.usp.ime.xpusp.om.map

This package contains the object-model for XPUSP project.

See:
Description

Class Summary

CourseElectiveMapBuilder This class was autogenerated by Torque.

CourseMapBuilder This class was autogenerated by Torque.

CourseRequiredMapBuilder This class was autogenerated by Torque.

DefaultCapabilityMapBuilder This class was autogenerated by Torque.

DepartmentMapBuilder This class was autogenerated by Torque.

DisciplineInfoMapBuilder This class was autogenerated by Torque.

DisciplineMapBuilder This class was autogenerated by Torque.

DisciplineTypeMapBuilder This class was autogenerated by Torque.

DoubleDisciplineMapBuilder This class was autogenerated by Torque.

ElectivePoolMapBuilder This class was autogenerated by Torque.

PeriodMapBuilder This class was autogenerated by Torque.

PoolResultsMapBuilder This class was autogenerated by Torque.

ProfessorCapableMapBuilder This class was autogenerated by Torque.

ProfessorChoiceMapBuilder This class was autogenerated by Torque.

ProfessorMapBuilder This class was autogenerated by Torque.

ProfessorPeriodMapBuilder This class was autogenerated by Torque.

RequiredPoolMapBuilder This class was autogenerated by Torque.

SourceMapBuilder This class was autogenerated by Torque.

StudentElectiveMapBuilder This class was autogenerated by Torque.

StudentMapBuilder This class was autogenerated by Torque.

StudentRequiredMapBuilder This class was autogenerated by Torque.

UnitMapBuilder This class was autogenerated by Torque.

YearMapBuilder This class was autogenerated by Torque.

Package br.usp.ime.xpusp.om.map Description

This package contains the object-model for XPUSP project. The model becomes a bit tricky because it models the same structure comming from two different sources, namely Jupiter and Fenix. The model used by these two systems differ a bit, so here is a short explanation of the model for both systems.

Model description for Jupiter and Fenix

The objects from the model that can come from more than one structure have a relation to a Source. The Source table in the database is filled on project initialization. Today (Saturday February 23 2002) there are four possible sources:

USER 55 is the source id used for Objects that were inputed by a system user
JUPITER 55 is the source id used for Objects that were fetched from the jupiter system
FENIX 55 is the source id used for Objects that were fetched from the fenix system
JUPITER_FENIX 55 is the source id used for Objects that were fetched from either fenix or jupiter system, but were also present on the other system.

Several methods use this information, for instance Unit.getJupiterInfoUrl() 55 will return null if this unit has neither JUPITER nor JUPITER_FENIX as it's source.
The model structure is very similar to the Jupiter model and the data fetched from Fenix had to be adapted. The following table tries to describe the data comming from both systems and its diferences.

Class	Description	Jupiter role	Fenix role
Unit	Represents a university unit like: Institute of Mathematics and Statistics Institute of Phisics Each unit has several courses and departments	Same for both systems
Department	Represents a Unit sub category. Every department has several disciplines	Same as description	Fenix does not classify its disciplines by department, it uses areas instead. What happens in fenix is that areas are grouped. So a fenix department actually represents a group of areas. The disciplines that come from fenix and are of a department actully come from an area that is grouped by this department. Note that if a discipline used by a fenix area exists on the system (ie: fetched from jupiter) it will be used and will be of a jupiter department.
Course	A course is a course :-). Like: Computer Science Mechanic engeneering A course has several required disciplines and several elective disciplines	Course is not related to a department	Fenix does not have courses since it has information for postgraduate studies. So for fenix a course is actually an area of postgraduate studies. Since in fenix the areas are grouped (we use departments to group them), the fenix courses have a relation to its group (a department).
Discipline	A discipline	Same for boty systems
CourseRequired	A course has several required disciplines and this represents it	See description	Postgraduate studies do not have elective/required courses. Fenix has a catalog of disciplines for each area (course). This represents it.
CourseElective	A course has several elective disciplines and this represents it	See description	Postgraduate studies do not have elective/required courses. Not all catalog disciplines are avaliable, this relationship represents all avaliable disciplines for an area (course).