Project Home

News/Updates

• 11/20: Use case narratives added Use Case Narratives.docx
• 11/01: Requirements elicitation completed, see the Requirements page for our completed report
• 10/15: Risk Log Added
• 10/15: Action Items page updated, survey/interview status changed
• 10/08: Faculty and student surveys completed! Check the Requirements page for URLs
• 10/05: New survey software selected. Check the Action Items for details
• 10/01: Notes from the Stakeholder meeting with Professor Schedlbauer are available here
• 10/01: Action Items page created. Check it out and be sure to complete survey/interview questions and virtual classroom candidates by 10/02/2009 at 16:00
• 9/30: Meeting on 10/01 at 14:40, WVH
• 9/30: Check out the Meeting Log for notes from today's meeting with Professor Schedlbauer. Please direct any questions to Jackson or Alexa via email or the Discussion page.
• 9/24: Anthony suggested that we share our schedules using Google Calendar. Once this is done, we can set up a meeting with Professor Schedlbauer
• 9/24: Record all Meetings and plan for future meetings with specific goals and objectives.
• 9/24: Begin recording potential candidates for the software on the Research page, including pros, cons, and any other relevant information.
• 9/23: Setup outline for Main Document. This will be filled in as we move forward.

Mission Statement

• To provide an affordable and easy to use interface for both students and faculty
• To provide a solution that closely mimics a real classroom environment
• Minimal maintenance and support so that no separate IT or Helpdesk divisions are required

Approaches & Structure

• Project Manager
• Work together as a group and define individual roles for smaller projects
• Iterative approach with frequent, but agile management

Requirements Elicitation Techniques

• Brainstorm: to develop ideas both amongst ourselves and with stakeholders on what this system will need and how the requirements may change as the project progresses.
• Interviews: to work closely with stakeholders, including students and instructors, to determine what their individual needs are and how their requirements can be met.
• Prototypes: allows for users to interact with and understand the system without it being fully functional. This will create an opportunity to make changes and requirements decisions early on.
• Interface Analysis: important for choosing how the system will look and feel for all of its users. In this case, the functionality of the system will heavily rely on its interface.