I. Content Management

- Develop Content Management Interface

      We will create a database table of merchandise 'items'. The content management interface will be a data entry form to that database. The form will have input fields for price, item name,  image_name and other related data. The merchandise page content will be rendered from the 'items' data table. 

     Selected merchandise will be added periodically when new products that are deemed available by both product management and website management. The responsibility of the product provider is to provide information pertaining to the product and cost, so that descriptions and pricing can be posted on the website.

II. Deployment Plan and Schedule

- Site Deployment

     Due to the lack of funds, the website will be deployed on external servers. If and when the website is overloaded with queries or cannot maintain the traffic we should consider redeploying the website on internal servers, to maintain traffic and ensure integrity and responsibility of customer data.

- Develop Database Table for Merchandise Items

     The interface for Adding and Removing Merchandise' in the Content Management Plan will be integrated with the organization of merchandise images and site content.  When a new merchandise item is added , the image information will be added and stored also. The form interface will have a 'browse' and 'upload' button for selecting image files.  The image gets uploaded into a repository on the host server, and a path to that image will be stored in a merchandise 'items' table that has these fields:

item_name varchar(30),

item_code varchar(10),

price decimal(6.2),

image_path varchar(65),

description varchar(250),

search_keywords varchar(250),

quantity int,

item_category varchar(30),

enabled int 

      We will need to rename the images uploaded to our repository to something unique or serial generated to avoid duplicate image names or overwriting. The new generated image name is what goes in the image_path field of our merchandise 'items' table.

- Persons Responsible for Deploying Site.

      Website creator is to be responsible for deploying website and ensuring that all expectations of website are met by customer standards.

 - Website Testing.

      Website will be throughly tested on a set of standards, one, being site functionality. Functionality is to be tested by having the website creator testing purchases of products. Second, site layout or ease of navigating the site can be tested by having test individuals navigate the site and take what advice we can to make improvements to the site. Any glitches encontered she be fixed as soon as possible, as to not to delay deployment.

 - Website release date

Once development and testing are complete, and with approval of customer, the website will be deployed.

III. Contingency Plan

 - What will you do if the new site does not work ?

     Our Contingency plan in the event in a site failure is to first notify customers of a site downage by redirecting their browser to an external server with a notification of a error within the page. Second, we will address the cause of the problem, and from there, troubleshoot the problem as quickly as possible. Lastly, we will conduct a group meeting as to identify the problem and the causes that led up to the site downage, and ensure everyones' understanding of what happened, and how the problem was fixed, so that in the future it can be avoided.