CS CapstoneSpring 2004

Tiffany Bonneau

Gail Horwitz

Latrenda Holt

Signup System for Meetings of Organizations

• Web Based System to handle notifications of meetings via email and allow attendees to RSVP via a web page

• System has to be able to create unique Ids linking it to a specific event RSVP web page

Basic System Design

Create Event Form

Database

Confirmation of Event Created

Confirmation of Response Recorded

Respond to Event Form

Response to Event

Email Sent

Event Invite

Email Sent

Web Form

Confirmation Screens/Backend Action

Database

Key

Potential Functionality

• We have divided our functionality into three categories: Phase I, Phase II, and Phase III

• Phase I: things we see as being necessary and most likely accomplished during this semester

• Phase II: would be nice if we have time

• Phase III: potential later versions or other capstone projects

Phase I

• Emails to Attendees about Meeting• Create Event Form• Respond to Event Form• Confirmation Pages for Create Event & Respond

to Event• Basic Logistic Info for Meeting (Dinner, Guests)• Links & Advertising• Basic Help Cues

Phase II

• More developed logistical details

• More detailed scheduling abilities

• Calendar

• Password Access

• Dynamic form fields

• More developed email notifications

Phase III

• Handling events other than meetings

• To-Do Task List for Event

• More advanced dynamic style

Technical Plan

• We have been discussing the possibilities of using either SQL server or MS Access as the database and using ASP as way of communicating with the database.

• We have a more developed technical plan once we have met with our customer.

Questions to Ask Customer

• How do you plan to use the system?• What is different about this product than what

is currently out there for handling meeting details?

• How many users do you see potentially using this system?

• What types of users will use this system?• What functionality do you want/expecting?

• Who will be using this system?

• Do users need to be registered in the system to be able to respond to an event?

• What browser types should we support?

• Do we need to make sure events are not overlapping?

• What kind of privacy issues need to be addressed?

• Does the invitee get to see who else is coming and are names and/or emails

displayed?

• Does an address book need to be created?

• What kind of additional meeting options need to be handled (guests, dinner, items to

bring)?

• Do you have any preference on how unique Ids are to be created?

• Can invitees add guests or do guests need to add themselves. If an invitee adds a guest,

what needs to happen?

Plan of Attack

• .Meet with Customer (Bob Harbort)

• .Write Requirements Document

• .Storyboard Use Cases

• .Write Design Document

• .Develop Test Plan

• .Develop Product

• .Test Product

• .Write User Manual/Help Files

• .Deliver Product

Planned Deliverables

• Requirements Document

• Design Document

• Test Plan

• User Manual

• Prototype/Product