ISU Alumni Association Online Store - ECpE Senior viewProject Number May05-39 Final Report Client: Iowa State University Alumni Association Faculty Advisor Dr. Srinivas Aluru, CprE

  • View

  • Download

Embed Size (px)

Text of ISU Alumni Association Online Store - ECpE Senior viewProject Number May05-39 Final Report Client:...

ISU Alumni Association Online Store

May05-39Final ReportRevision 1.0

ISU Alumni Association Online Store

Project Number May05-39

Final Report

Client:Iowa State University Alumni Association

Faculty Advisor

Dr. Srinivas Aluru, CprE

Team Members

Keith Dahlby, CprE

Jordan Jump, CprE

Andrew Kirpalani, CprE

Jonathan Ruhnke, CprE

DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa. This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification requirements. This use includes any work resulting from this student-prepared document that is required to be under the responsible charge of a licensed engineer or surveyor. This document is copyrighted by the students who produced this document and the associated faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.

April 1, 2005

Table of Contents

ivList of Figures

vList of Tables

viList of Definitions

1Introductory Materials

1Executive Summary





2Conclusions and Benefits


2Problem Statement

2General Problem Statement

3General Solution Approach

3Operating Environment

3Intended Users and Intended Uses

3Intended Users

3Intended Uses

3Assumptions and Limitations

3Technical Assumptions

4Non-Technical Assumptions


4Expected End Product and Other Deliverables

5Product Approach and Results

5End Product Functional Requirements

5Resultant Design Constraints

5Approaches Considered and One Used

5Technical approach used

6Other technical approaches considered

6Implementation Process Description

7Project Infrastructure

7Development Framework and Common Component Creation

7Peripheral Component Creation

8Implementation Improvements

8End-Product Testing Description

8Integrated Testing Procedures

9Client Testing and Feedback

9Future Testing

9Product End Results

9Database / Data Access


10Administrative Interface


10Other Areas

11Detailed Design

11Design Overview

11Business Model

12Database Abstraction Layer

14Business Logic Tier

15Presentation Tier

21Resources and Schedules


21Personal Effort Requirements

22Financial Requirements

24Project Schedules

24Fall 2004 Schedules

26Spring 2005 Schedules

28Closure Material

28Project Evaluation

28Project Definition

28Technology Considerations and Selection

28End-product Design

28End-product Implementation

29End-product Testing

29End-product Documentation

29End-product Demonstration

29Project Reporting/Deliverables

29Overall Project Score


30Recommendations for Additional Work

30Multiple Product Images

30Extended Category Structuring

30Frequent Use of Stored Procedures

30Database Backup/Recreation Script

30Lessons Learned

30What Went Well

30What Didnt Go Well

31What Technical Knowledge Was Gained

31What Non-Technical Knowledge Was Gained

31What Would Be Done Differently Next Time

31Risk and Risk Management

31Anticipated Potential Risks and Planned Management

31Anticipated Risks Encountered and Success in Management

32Unanticipated Risks Encountered, Attempts to Manage and Success

32Resultant Changes in Risk Management Made Because of Encountered Unanticipated Risks

32Project Team Information

32Client Information

33Faculty Advisor Information

33Student Team Information

33Closing Summary

List of Figures

11Figure 1: Architectural Overview

13Figure 2: Database Schema

15Figure 3: Class Diagrams for Business Logic Tier

16Figure 4: Old Front Page

17Figure 5: New Front Page

18Figure 6: Original Item Description Page

18Figure 7: New Item Description Page

23Figure 8: Project Schedule Fall 2004

23Figure 9: Project Deliverables Fall 2004

24Figure 10: Revised Project Schedule Fall 2004

25Figure 11: Project Schedule Spring 2005

25Figure 12: Project Deliverables Spring 2005

26Figure 13: Revised Project Schedule Spring 2005

List of Tables

20Table 1: Previous Estimated Personal Effort

20Table 2: Revised Estimated Personal Effort

21Table 3: Final Personal Effort

21Table 4: Previous Estimated Financial Budget

21Table 5: Revised Estimated Financial Budget

22Table 6: Final Financial Budget

List of Definitions

ASPActive Server Pages, a Microsoft technology that allows web pages to be dynamically generated. ASP is commonly used to allow web pages to interface with database systems and other external data sources.

ASP.NETASP.NET is the newest version of ASP, implemented as part of the .Net Framework. ASP.NET offers many significant improvements over classic ASP, and allows scripting to be written using several languages including C#. More information:

C#C# is a Microsoft-created object-oriented programming language similar to Java. C# was created for use with the .Net Framework and has many features designed specifically to interact with various technologies available within the framework.

CSSCascading Style Sheets is a simple text-based mechanism that allows style information (e.g. fonts, colors and spacing) to be attached to HTML and XML documents. More information:

MSDEMicrosoft SQL Server 2000 Desktop Engine is a free, redistributable version of SQL Server for client applications that require an embedded database and Web sites serving up to 25 concurrent users. It integrates well with the Windows operating system and the .NET Framework. More information:

MySQLMySQL is an open-source database server that is frequently used in small- and medium-scale web application development. MySQL doesnt support many of the advanced features supported by DB/2, but it is just a robust and has enough features for most applications. More information:

.Net FrameworkThe .Net Framework provides a common set of tools for developers on the Windows platform. These tools can be accessed using a variety of languages, including C#. ASP.NET is part of the .Net Framework. More information:

SVNSubversion - a version control system for controlling access to a software project and its files.

Introductory Materials

Executive Summary


The Iowa State University Alumni Association is an organization meant to promote and publicize Iowa State University. One of the ways that the Alumni Association fulfills its function is by selling Iowa State branded merchandise. The merchandise directly promotes Iowa State as well as providing revenue to fund the organization. This merchandise is marketed through an online store ( The previous store was barely adequate for the purpose and the Alumni Association asked for a new system to be put in place. This senior design project was created to that end.


The goal of the project was to create three product deliverables:

An attractive online storefront

An integrated and comprehensive database system

A management tool suite

The storefront presents the articles available for sale by pulling appropriate information from the database system. In addition it provides comprehensive ordering capabilities by interfacing with the same database system.

The database system replaces several disparate databases that had been required to display merchandise, process orders, and maintain vendor information.

The management tool suite allows the Alumni Association staff to administer the online catalog after project completion. They are able to add, delete, and change items and prices and update vendor information without having to directly interact with the database system.


The team used the following approach to facilitate successful implementation of the design objectives:

Improved processing flow for orders

Easily manageable catalog

Intuitive storefront

The team identified certain assumptions and limitations, and chose the development environment. The project proceeded as planned.


The design follows an object oriented approach that divides the development into three tiers: the presentation tier, business logic tier, and the data access tier. The presentation tier handles interaction with visitors to the store. The layout can be manipulated to best fit the requirements of the teams customer, but it has been modeled after several successful, existi