Project:
|
![]() Figure Proj.08 - Project Calendar : Class diagram
A Project has two different Calendar related requirements. <br/>The first is to have a Calendar that shows the working time periods, used to convert between working hours and elapsed days. For example, if we have a 10-hour Activity, that is due to start at noon on a Friday, and if working hours are 9:00am –12:00am and 1:00pm ‘till 5:00pm Monday to Friday, then the Activity will not be completed until 4:00pm on Monday.<br/>A Project also needs to keep track of working days and holidays. Each Project may wish to have its own working time Calendar (e.g. for projects in different countries with different hours of work), but it will be most effective for a Project to utilize or modify a standard calendar.<br/>The second requirement is to be able to show Activities on a Gantt chart. To do this, we can store the Activity start and end dates in a Calendar Entry<br/>For more details of the Calendar core model, refer to the SID Time Addendum.<br/>Following Figure shows Project linking to Calendar. A Project links to a single ProjectCalendar, which is a type of CompoundCalendar. The CompoundCalendar would normally be made up of a Standard Work Calendar storing all the public holidays for a Country or a State (refer SID Location model). In addition, changes to the standard calendar can be made in a ProjectSpecificWorkCalendar. The intention is to reduce work calendar maintenance by allowing for the sharing of standard work times.<br/>For Projects that span multiple Countries, then a Project may need to use more than one StandardWorkCalendar. In that case then the project will need to associate Activities with Countries and use the correct StandardWorkCalendar for scheduling.<br/>
|