Final Presentation

Hey everybody, it's been a long semester full of meetings, diagrams, and planning.  This isn't a final product but this is what HPU's IT Dept. and I have come up with so far.  Hopefully in the coming months I will be working with them to creating a useful and intuitive tool that everyone can use and enjoy.  I know the video ran a bit long but honestly I felt like it could have been longer :-)

Here's the link to my final presentation video.
Also here's the link to my slides.

Presentation Plan

My presentation for my project is coming up within the next week.  Here are few things I want to talk about:

• Project objectives
• Stakeholders
• Meetings
• Stages of development so far
• Difficulties I faced (communication, scheduling conflicts, etc.)
• The likelihood of this becoming a reality

Thanks for reading my blog and stay tuned for my video presentation!

Here's the editable link to the presentation.

HTML Mockup Client Meeting

I just met with Vlad from HPU's IT Department this morning and he looked over my HTML mockup.  Unfortunately, like most prototypes this was not quite what he had in mind.  Vlad mentioned that the great thing about having it reside inside of Google Apps is that much of the functionality that we want the system to have is already available to us through Google.  Google has a number of ways to share your calendar others and students, academic advisors, and student organizations already possess a Gmail account through the Pipeline.  Having much of the work done for us allows us to concentrate on creating "glue" or a link between HPU's Banner (Class Scheduling System) and Google Apps.  It also frees us up to work on an interface that users will enjoy.  He did however, say that starting with the very basics is the way to go when first trying to create something.

Here's a short recording of our meeting.

Low Fidelity Drawings

I know it took me a while to get these up but I finally have some sketches regarding the look and flow of how the scheduling system.  These images are mostly from the students view because the Student Organization or Academic Advisor would only have a slight modification to how things would look and work.

This first image shows the how things will function together from a high level.  It shows our final goal get information from Registration/Build Class Schedule to @my.hpu.edu.

The next drawing is a basic view of how it could look like.  A student's calendar filled in with both personal events (i.e. work schedule, meetings, lunches, appointments, etc..) and also their respective class schedule for that particular month.

The last drawing shows the relationship between the Class Scheduling system and the proposed Event Publisher to create this Unified Google Calendar View.     :-)

Here's the link to my short explanation.