The Online Smith Family Recipe Program Shannon Smith CS 470 11/25/02

System Overview Goal. Why Develop a program to provide online access for recipe sharing and storage. Client is the Smith Family. Why It will aid in the development of recipes. To replace the method of storage for recipes that is currently used by the Smith family.

Data Files Provide Recipe Name Provide Ingredients List Provide a List of Steps Occasionally the data files will provide the name of the Author or National Type.

Data File Format Traditionally written on small scraps of paper. Older scraps of paper have faded, eroded, or been lost. The entire Smith family recipe collection is easily over 2,000 recipes. The recipes are divided among more than five different family units.

The Final Product

Technical Overview The programs I used: Macromedia Dreamweaver MX Microsoft Access 2002 Internet Information Services (IIS) 5.1 for Microsoft Windows XP Professional Adobe Photoshop 5.5 VBScript and HTML coded ASP web pages were used to create the web site.

How it was Created Set up an Access Database with the basic relationships required. Set up and configured an internet server on my computer system using IIS. Developed the ASP pages with Dreamweaver MX. Used Adobe Photoshop 5.5 to create the graphics used on the site. Went back through VBScript code to add extra functionality desired on each web page.

Architecture of the Database

Architecture of Web Site

What it can do. Allows Users To: Login View the top 5 recipes View the newest recipe entered into the database Add Recipes Edit Their Recipes Delete Their Recipes Search for Recipes Rate other user’s Recipes Get Help information on program

Obstacles and Solutions Multiple data outputs to the same data source destination. Solution was to force the database connection to close and then reopen, so that the tables and queries were updated, before each insert into the same data source destination. This problem is quite common with connections to an Access database and the usual solution is a complete work-around, which is undesirable.

Prototyping Originally, prototyping was used because the client only had very general requirements. Vague requirements lead to difficulties in implementation. Requirements changed, had to implement a delete page instead of a credit page.

Schedule

Conclusion Successfully delivered the product to the Smith family. I learned: Databases: relationships, queries, cascading updates and deletes, and referential integrity. VBScript and how to make remote insert, delete, and update commands on a database. Programs: Microsoft Access & Dreamweaver. More about HTML.