The Online Smith Family Recipe Program Shannon Smith

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

System Overview 4 Goal. – Develop a program to provide online access for recipe sharing and storage. – Client is the Smith Family. 4 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 4 Provide Recipe Name 4 Provide Ingredients List 4 Provide a List of Steps 4 Occasionally the data files will provide the name of the Author or National Type.

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

The Final Product

Technical Overview 4 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 4 VBScript and HTML coded ASP web pages were used to create the web site.

How it was Created 4 Set up an Access Database with the basic relationships required. 4 Set up and configured an internet server on my computer system using IIS. 4 Developed the ASP pages with Dreamweaver MX. 4 Used Adobe Photoshop 5. 5 to create the graphics used on the site. 4 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. 4 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 4 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 4 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 4 Successfully delivered the product to the Smith family. 4 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.