Project Plan

Prepared by Team Aquarius
for a UCI ICS course listings webpage proposed by Professor Michael Carey.

Kyle Chong
Danny Kim
Derek Lyons

February 11, 2011

Release Information

Project: UCI ICS Course Listing Replacement
Revision: 3.0.1
Related Documents:

Revision History

Version 3.0.1
-Edited portions of the Stackholders section (modified plural/singular verbs/nouns, etc)
-Made capitalization consistent for section titles under Scope of Work
-Modified wording in Scope of Work
Version 3.0.0
-Expanded Statement of Work
-Fixed Revision History numbers to be compliant with the new revision numbering from version 1.1.1
-Updated Work Break Down Structure
Version 2.0.0
-Added Technical Constraints.
-Added Work Break Down Structure; created Gantt Chart.
-Added Communication Covenant.
Version 1.1.0
-Clarified revision numbering. X.Y.Z: X is a major version; Y is a minor version (iteration); Z is a patch to an iteration.
Version 1.0.0
-Initial release.

Business Need

The UCI ICS course listing is a tentative schedule of CompSci, CSE, ICS, Informatics, and Statistics courses that the Bren School offers for the current academic year. However, there are many issues with the current implementation. These issues generally fall under the usability umbrella, due to the presentation of extraneous information in a cluttered interface. If students have to scan across multiple vertical listings to plan a schedule, the task takes much more time and effort than it should. There is a need for a better design such that students can clearly see the course offerings for an academic year at a glance. A better design would be valuable because it could improve student satisfaction by reducing the work involved in planning their schedule for the coming year. Additionally, this could alleviate the workload of counselors who would otherwise have to fix students' schedules to remain on track.


UCI Students
Students at the University of California, Irvine will be the primary users of this interface. As students plan their academic calendars, they will want to view classes that will be offered during the current academic year. With this course listings, students should have additional information regarding the course, instructor, or coursebooks required in the course.
Bren School of ICS Website Visitors
As prospective students view the UCI ICS website, they may want to view the types of courses offered by the school. As such, they will also be a common user for our interface. With detailed views of the courses offered, the visitors to the website should have a better perspective on the courses they will be taking in the future should they attend the Bren School of ICS.
Bren School of ICS Academic Counselors
Counselors at the Bren School of Information and Computer Science will often refer to courses available during the academic year to assist students in planning their academic schedules. With the current interface available, counselors will sometimes resort to using the General Catalogue in order to show students detailed information about a course. By placing all desired information in one easily accessible location, counselors should be able to save time on counseling sessions by eliminating the need to use other resources.

Statement of Work

Scope of Work

The following represents the scope of work that will be performed during the course of the project:

Market Studies
By observing currently implemented interfaces, the team will be able to learn more about the usability of different interfaces to tailor them to ensure the satisfaction of our stakeholders.
Requirements Engineering
Requirements will be elicited from involved stakeholders, as well as our project sponser through interviews, surveys, and developing prototypes. Through this process, we will learn the functional, non-functional, and technical goals for the system.
System Design
The system architecture as well as implementation to database systems will be designed by the team.
System Programming
Implementation of the system design will be performed as well as integration between all necessary components, such as databases.
System Testing
Testing of the system components will be incrementally performed throughout the implementation process.
The deployment of the software will be performed on the UCI ICS course listings website.

Location Of Work

Meetings with the team and project sponsor will be held on the UCI campus. Assessments that include interviews with users of the system will also be held on campus at UCI. Deployment of the system will take place at the Donald Bren School of Information and Computer Sciences.


Our system will include several documents which will be presented to the sponsor. These documents include:

  • Software Requirements Document
  • Software Design Document
  • Project Plan Document
  • Software Test Plan

Technical Constraints

This project will be created for use on the UCI ICS Website.

The dimensions of the layout will be structured so that it will not interfere with the current website layout. The links and banners will remain on the layout as such in the current version of the course listings. If necessary, the course listings will have scroll bars within its allotted content frame.

Currently, the system is designed to have administrators manually enter new courses as they are decided upon by the UCI ICS Student Affairs Office. Therefore, administrators must constantly add courses to the database in order to keep the course listings up to date.

Our system will be developed on a website, therefore it will not have any operating system requirements. Our system will operate on commonly used web browsers such as Firefox 3+, Chrome 6+, Internet Explorer 7+, Safari 5+.

Work Break Down Structure

  1. Project Initiation (Weeks 1-2)
    1. Market Studies
    2. Sponsor Requirements
  2. Requirements Engineering (Weeks 2-4)
    1. System Specifications
      1. Technical Requirements
      2. Functional Requirements
      3. Non-Functional Requirements
    2. Interaction and Interface
      1. Use Cases
      2. UML Modeling
      3. Sequence Diagramming
      4. User Testing
      5. Interviews
  3. Design (Weeks 3-5)
    1. System Design
      1. High Level Architecture
      2. Low Level Architecture
      3. Deployment
    2. Interaction and Interface
      1. User Testing
  4. Implementation (Weeks 4-7)
    1. Back-End Coding
    2. Database Coding
    3. User Interface
  5. Integration (Week 8)
    1. Q&A Testing
      1. Integration Testing
  6. Testing (Week 9-10)
    1. Use Case Testing
    2. User Testing
    3. System Testing
  7. Deployment (Week 10)
    1. Demo with Sponsor
    2. Software Installation

Gantt Chart of Project Deliverables

This Gantt Chart represents all document deliverable due dates and milestones required from this project. Each assignment has been assigned an alloted time span in which the deliverable must be completed.

Communication Covenant

  1. For all non-urgent messages, E-mail will provide as the primary means of communication.
  2. All urgent messages will be directed via direct phone calls.
  3. Team members are expected to check e-mails multiple times throughout the day and regularly reply to group e-mails.
Communication Guidelines
  1. Emails should be written formally in complete and correct English sentences. Use of slang, insults, or arguments are not permitted
  2. Emails that contain a time-commitment should be replied to with a confirmation or request to extend the time limit with a valid reason.
  3. Team members should notify the entire team if unable to attend a meeting, lecture, or discussion ahead of time.
  1. All class documents will be uploaded and shared with all team members on Google Docs.
  2. Any modifications to documents should be noted on the team log as well as the revision history found at the top of each document.
Group Responsiblities
  1. When work is divided among the team, each member is required to do his part within their alloted time. Should a team member be unable to finish their part by the allotted time, they should notify team members at least 24 hours before the deadline.
  2. Team members should regularly be in contact with each other to discuss project progress.
Client Meetings
  1. Client meetings will be held every Thursday unless otherwise notified.
  2. Should a team member be unable to attend the meeting, other team members should be notified ASAP.
  3. One person shall take notes during the entire meeting
  4. Before each meeting, team members should brainstorm ideas to be discussed at the meeting so that time is not wasted during the meeting.
  5. All team members are responsible for information discussed during meetings. If a team member does not attend, it is his responsibility to request notes taken during the meeting.
Team Aquarius.