Courseware

Paul Pietkiewicz, James Wong, Michael Wood, Richard Zak,

Michael Zyvoloski

Introduction

• Time Management Issue and UMBC– Academic Deadlines (exams, papers, etc.)– Athletic Events– Administrative Deadlines– Appointments/Meetings

• Individual Organizational Tool

Analysis

• Current Options – Blackboard

• Basic Calendar• Split between each class• Allows straightforward event posting

– Web Events• Campus Events• Administrative only

Analysis (part 2)

• Problems with the systems– Lack of Integration– Minimal error checking– Inaccessible– Limited functionality– Static environment– Too simple

Project Goals

• Campus Awareness

• Seamless functionality

• Complementary to Blackboard

• Improved Organization and Time Management

• Better accessibility

Feasibility Analysis

• Operational

• Economic

• Technical

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

Requirements Analysis

• Nonfunctional– Operational

• Compatibility• Must be part of Blackboard

– Performance• 95% uptime• Manageable load times• File Size Limits

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

Current System Overview

• Unique Calendar for each course

• Two Basic Functions– Post/View Events– “Quick Jump” to Events

• Customization– Multiple Views only

Data Flow Diagram

Screen shots

Screen shots 2

Alternative Solutions

• Custom Development– Similar Interface– Organizational Options– Basic Search functionality– Help Page

• Packaged Software– Oracle Calendar– OfficeCalendar

Proposed System Overview

• Justification– Flexibility– Lower Costs– Meets all requirements– Open Source expertise

• Methodology – Phased Development

• Faster Deployment• Higher Quality• Immediate Feedback

Proposed System DFD

User Interface (1)

User Interface (2)

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

Implementation

• Conversion Plan

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

Maintenance Plans

Thank You

• Questions?