Figure Cal.02– iCalendar UML interpretation

<font color="#29313b"><b>eTOM Requirements</b></font><br/><font color="#29313b">The eTOM has direct references to Time Management in the following process definitions:</font><br/><ul>
<li><font color="#29313b">CRM Operations Support & Process Management (CRM – OSR) – “employee schedules”</font></li><li><font color="#29313b">RM&O Support & Process Management (RM&O - OSR) – “employee schedules”</font></li><li><font color="#29313b">S/PRM Operations Support & Process Management (S/PRM - OSR) – “employee schedules”</font></li><li><font color="#29313b">Marketing Communications & Promotion (M&OM - PLM) – “schedules press interviews, manages an editorial calendar to plan placements”</font></li><li><font color="#29313b">RM&O People Support & Scheduling (RM&O – OSR) - “employee schedules”</font></li><li><font color="#29313b">Resource Maintenance & Repair (RM&O – OSR) – “scheduled maintenance activities”</font></li></ul>
<font color="#29313b">Since the eTOM doesn’t give detailed requirements for Time Management, this model will provide a level of functionality that could be reasonably be expected to be required by eTOM based use cases.</font><br/><font color="#29313b"><b>Calendar Introduction</b></font><br/><font color="#29313b">One of the few publicly defined Calendar specifications is the iCalendar spec [iCalendar]. Unfortunately, the specification is implementation focused (not problem domain concept focused) and defines standard information interchange messages rather than entity definitions.</font><br/><font color="#29313b">The iCalendar specification is significant enough, however, that it is worthwhile to try and interpret the document and convert it to a SID compatible format (refer Figure 2).</font><br/><font color="#29313b">One other issue with the iCalendar specification is that the main concept is called “Calendar”, which clashes with the Calendar Java class name (which is focused on implementing “calendrical systems” such as the Gregorian Calendar). We will use the term Calendar in this document, the other option would be to name the entities using “schedule”, which aligns with Fowler’s naming and would be more compatible with uses such as in the Project management area. </font><br/>