Requirements

Entity Relationship Diagram

The following visio document shows the ER Diagram for the database used in each profile. CSE598Capstone_EntityRelationshipDiagram.vsd

For the benefit of anyone attempting to recreate the research here is the SQL creation script.

create database ClownSoft;
use ClownSoft;
CREATE USER webuser IDENTIFIED BY 'changeme';
set password for webuser = old_password('changeme');
GRANT SELECT, INSERT, UPDATE, DELETE ON ClownSoft.* TO 'webuser';
create table Job(
ID INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY(ID),
OwnerLoginID INT,
Title VARCHAR(50),
Department VARCHAR(50),
AnnualSalary NUMERIC(15,2),
JobDescription VARCHAR(255),
ExpectedStartDate DATETIME);

create table Login(
ID INT NOT NULL AUTO_INCREMENT,
PRIMARY KEY(ID),
Name VARCHAR(50),
Username VARCHAR(50),
EMail VARCHAR(50),
Password VARCHAR(50));

Side note: ClownSoft.com is a domain that Mr. Ellermann owns and has used to have a shell for side consulting projects. The fictionalish slogan is: "Where good software is written for all the clowns on the Internet." This company is fictional for the purposes of this job board application.

Use Case Diagrams

CSE598Capstone_UseCaseDiagrams_2002.vsd

Use Cases

CSE598Capstone_UseCases.pdf You will find the HTML prototype under the Code portion of the website. Below is a screen shot of the Clownsoft Job Board that is being built in the profile 2 or Three Tier Web Application.

Profile 1: Simple Web Application

This application is intended to exemplify the simple functionality that a small office or home office (SOHO) would like to add to their static informational website. Fundamentally, this profile is the first step from a pure static website to an interactive website, which allows a user to fill in form data and submit their contact information.

Profile 2: Three-Tier Database-Driven Web Application

This application is intended to exemplify the standard web application that is common across all sizes of businesses. Examples of some common Three-Tier Database-Driven Web Applications include a social network, shopping cart, blog, wiki, guestbook, or corporate job board. We chose to implement a corporate job board with standard functionality like account creation, login/logout, and the ability to create, edit, and delete job postings. This selection allows comparisons of how each WATP does validation, session management, database CRUD (Create Read Update Delete), security, and paging.

Profile 3: Enterprise Web Application with Multiple Integration Points

We ran out of time to implement this profile, but the Use Case Requirements are here. This additional profile would include additional objectives such as integration, internationalization (UTF-8), production support availability and cost, code reuse, legacy system connectivity, distributed transactions and the use of existing database tables. This profile would represent the needs of enterprise-class technology companies and projects. This is where many of the scripting and ORM based solutions would start to fall down.