1. Courseware Paul Pietkiewicz, James Wong, Michael Wood, Richard Zak, Michael Zyvoloski

2. Introduction Time Management Issue and UMBC –Academic Deadlines (exams, papers, etc.) –Athletic Events –Administrative Deadlines –Appointments/Meetings Individual Organizational Tool

3. Analysis Current Options –Blackboard Basic Calendar Split between each class Allows straightforward event posting –Web Events Campus Events Administrative only

4. Analysis (part 2) Problems with the systems –Lack of Integration –Minimal error checking –Inaccessible –Limited functionality –Static environment –Too simple

5. Project Goals Campus Awareness Seamless functionality Complementary to Blackboard Improved Organization and Time Management Better accessibility

6. Feasibility Analysis Operational Economic Technical

7. Requirements Analysis Functional –Necessity for all inclusive calendar –Organizational Options –Event Subscriptions –Intuitive User Interface –Provide for wide variety of events –External Links –User guidance

8. Requirements Analysis Nonfunctional –Operational Compatibility Must be part of Blackboard –Performance 95% uptime Manageable load times File Size Limits

9. Requirements Analysis Nonfunctional (cont.) –Security Privacy Administrative Control –Cultural and Political All entries are created equal Campus wide events must be approved Fits UMBC’s goals

10. Current System Overview Unique Calendar for each course Two Basic Functions –Post/View Events –“Quick Jump” to Events Customization –Multiple Views only

11. Data Flow Diagram

12. Screen shots

13. Screen shots 2

14. Alternative Solutions Custom Development –Similar Interface –Organizational Options –Basic Search functionality –Help Page Packaged Software –Oracle Calendar –OfficeCalendar

15. Proposed System Overview Justification –Flexibility –Lower Costs –Meets all requirements –Open Source expertise Methodology –Phased Development Faster Deployment Higher Quality Immediate Feedback

16. Proposed System DFD

17. User Interface (1)

18. User Interface (2)

19. Physical Design Hardware –Processor: Intel® Xeon™ processor at 3.0GHz/2MB Cache, 800MHz FSBb –RAM: 2GB DDR2 400MHz –Primary Storage: (80GB 7200RPM Serial ATA Hard drives) x 3, RAID-5 –Media Drive: DVD-ROM Software –Operating System:CentOS 4.3 Linux –Web server:Apache 2.2.0 –Database:MySQL 5.0 –Web Scripting Language:PHP 5

20. Implementation Conversion Plan

21. Training Plans Information Session –Open to users –Usage Demo –Q & A OIT Training –Classroom Setting –3 Sessions Usage/Administration Tutorial Maintenance Primer Online Help Resources

22. Maintenance Plans

23. Thank You Questions?