Skip to content

Project Proposal

Jump to bottom
katherineshaw edited this page Jul 7, 2016 · 3 revisions

#Project Proposal

A. Project Description

Adam Kozie, Kate Heesun Lee, and Katherine Shaw (herein referred to as the Vendor) have been asked by Kyle Cruver of the Kitsap Peninsula Opera Guild, the Client (herein referred to as Kitsap Opera), to redesign, produce and develop the website for the Kitsap Opera, the Project, to be viewed publicly via the world wide web. Said Project is intended to improve the effectiveness of the Kitsap Opera public website as to showcase the mission and services of the Kitsap Opera with the following requirements:

  1. Design: Creation of an on-brand website design representative of the mission and services of the Kitsap Opera.

  2. Technology: Implementation of a Content Management System (CMS) powered by WordPress as to allow the Client to update and manage their own content.

B. Functional Requirements

Said Project will be produced by the Vendor with the following functional requirements:

  1. Home Page Slider: Rotating banner on the front page to highlight new shows, marketing and fundraising campaigns.

  2. Donations: The Project will have the capability to accept monetary donations from visitors, for the Kitsap Opera. This will be accomplished through a plug-in.

  3. Tickets: Ticketing will be done through a third party service. This service will be linked to through the Project website. Beyond displaying this external link, the Project will not be involved in the selling of tickets.

  4. Responsive Design: Create a website design that renders correctly on (a series of) mobile devices.

  5. Costume Rental Display: A section of the Project will display photos of costumes available for rental. This section will include captions describing said costumes and their associated shows, and will have a link to contact/inquire about the items.

C. Content Requirements

Said Project will be produced by the Vendor with the following content requirements:

  1. Brand Imaging: Said Project will incorporate the existing Kitsap Opera logo and brand specifications as supplied by the Client.

  2. Photographic Images: Photos for said Project will be supplied to and or will be chosen by the Vendor to be incorporated into the design of said Project. The Client will be responsible for approval and license of each photograph.

  3. Written Copy: Written information for said Project will be incorporated into said Project by the Client via the Wordpress Content Management System (CMS).

D. Technology Requirements

Said Project will be produced by the Vendor with the following technology requirements:

  1. Markup Code: Markup code for said Project will be written in valid HTML5 as to control the structure of website components. Said markup code will adhere to standards as set forth by the W3C.

  2. Presentation Code: Presentation code for said Project will be written with Cascading Style Sheets (CSS) as to control the design and layout of the website components. Said Presentation code will adhere to standards as set forth by the W3C.

  3. Client-Side Scripting: Client-Side Scripting code for said Project will be written in Javascript as to control website item applications.

  4. Server-Side Scripting: Server-Side Scripting code for said Project will be written in PHP as to control elements that interact with the server and database component.

  5. Database Component: Database components for said Project will be written in MySQL as to control functionality that stores and retrieves content data.

E. Project Phases

Said Project will be produced by the Vendor as described in the following phases:

1. Discovery:

The Vendor will meet with the Client to clarify objectives, identify preferences, discuss goals, and analyze overall needs for said Project.

2. Content Audit:

The Vendor will conduct a content audit as to assess how present and potential written and visual content will satisfy user needs assessed during the discovery phase for said Project.

3. Information Architecture:

The Vendor will create an information architecture to describe how the structure of the (website) content will be presented based on data collected during the Discovery and Content Audit phases of said Project for the Client’s review, approval and sign off.

1. Content Design:

The Vendor will create and present a (wireframe) content design study for all in- scope pages that will illustrate blocks of content, navigational schemas and user functionality that will adhere to the information architecture of said Project for the Client’s review, approval and sign off.

2. Visual Design:

The Vendor will create and present a visual design study consisting of at least three initial visual design concepts that incorporate the Content Requirements in the manner as stated above for all in-scope pages of said Project for the Client’s review, approval and sign off.

3. Production & Development:

The Vendor will be responsible for producing said Project on the Vendor’s development server with the Content and Technology Requirements in the manner as stated above for all in-scope pages of said Project for the Client’s review, approval and sign off.

4. Testing:

The Vendor will be responsible for testing all website pages as to ensure functionality across multiple platforms and browsers for all in-scope pages of said Project for the Client’s review, approval and sign off.

5. Style Guides: The Vendor will be responsible for producing design style guides for all in-scope pages of said Project for the Client’s review, approval and sign off.
6. Launch: The Vendor will be responsible for launching said Project to the Client’s server space.

F. Rights of Usage

Rights of usage for said Project described as follows:

1.The Client is granted usage rights of said Project as designed and produced by the Vendor via the World Wide Web.

2.The Vendor reserves the right to use design and development elements of said Project as case study and training materials.

G. Project Fees

The Client, will adhere to fees for said Project described as follows:

1.Fees are to incorporate terms of said proposal only and will be billed as a “Pro-Bono” project.

2.All Vendor work that is being performed on a Pro-Bono basis may come to an end on August 19th, 2016, the end of the summer quarter at Seattle Central College. Additional work and associated costs must be negotiated separately.

3.Any other Vendor fees such as domain registration, ISP, etc. are to be negotiated and billed separately by the respected vendors and are not the responsibility of Seattle Central College.

H. Project Responsibilities

The Client, will adhere to responsibilities for said Project described as follows:

1.The Client is expected to participate and be available for review and approval of all project deliverables, as described in the project phases section, according to the proposed schedule. If at any time the Project is delayed or halted by the Client, including but not limited to phase acceptance delay longer than 7 days, work on said project may be cancelled.

2.The Client is required to purchase and/or provide their own web hosting space for the Project to be hosted on.

3.The Client is to understand that this is a class project that is being worked on by students as a learning experience. A reasonable attempt will be made by both instructors of the class and students enrolled in the class to complete the project in a professional and timely manner. However, Seattle Central College cannot guarantee nor be responsible for the quality of work produced in this class.

I. Project Approval

By signing this document, this Project Proposal is considered “agreed upon” by the Client and Vendor.

Name: _________________________________ Date: ______________ Kyle Cruver, Kitsap Peninsula Opera Guild

Name: _________________________________ Date: ______________ Adam Kozie

Name: _________________________________ Date: ______________ Kate Heesun Lee Name: _________________________________ Date: ______________ Katherine Shaw

Clone this wiki locally