ourse Project Background

Because of the great work we did on the WEB460 Book Store in the iLabs, our company, Web460 Creations, has been asked to build a web application for the online support group Programaholics Anonymous (PA). PA is for software developers who are addicted to software development to the point that their social lives have disappeared and they have forgotten what food other than Twinkies and Coca-Cola tastes like. Your task is to build the application they need without becoming a member of the support group.

Here is an outline of the application PA is looking for.

The website must use an N-tier design for easy future expansion.
There are three web forms used in the application.
Log In page
User Account Details page
User Account Confirmation page
The Log In page allows registered users to log in and allows new users can create an account. This page has username and password fields that everyone (returning and new users) must complete. There should be two buttons: Log In and Create Account.
Clicking Log In validates the user information. If it is a valid user, the user is taken to the User Account Details page and the information is filled in.
Clicking Create Account creates a new user in the database with the username and password supplied on the Log In page. The user is then taken to the User Account Details page with the username field filled in.
The User Account Details page lists the following information on a user.
Username (users are anonymous, so there should not be any link to their actual names)
City
State
Favorite programming language
Least favorite programming language (useful in breaking the programming addiction with negative therapy)
Data last program was completed (to figure out how long they have been clean)
An Applications Completed table (GridView control) that lists all applications they have completed in the last year along with the date completed and programming language used
The data for the GridView can be entered directly into a database table and then displayed in the GridView. Your application does not need to provide functionality to add records to the GridView (but you can if you want to).
The User Account Details page gives the user the following options for modifying information.
Update Account Information
Delete Account
The User Account Details page also should have a Find User button to help with testing. This will let you find user account info based on the username. Normally this data would be populated after logging in, but we are implementing the User Account Details page 2 weeks prior to the Log In page.
For federal auditing purposes, PA is required to report on all applications that users have completed along with the programming language. The User Account Details page must provide an Export Stats button that writes the Applications Completed data to an XML file in the App_Data directory. The XML file name should in the format username.xml. Once per quarter, these files will be summarized and sent to the Federal Programmer Safety Commission (FPSC). (Summarizing and transmitting these files is out of scope for this project.)
The User Account Confirmation displays the basic user account information (not the GridView) for the user to confirm any changes before they are made permanent in the database.

The sections below have additional details on the application and weekly milestone deliverables.
Week 1 Milestone: No Required Deliverable This Week
Back to Top

There is no formal milestone deliverable for the Course Project at the end of Week 1, but it is to your benefit to aggressively begin work on the Course Project. Plan your time well. The course moves quickly, and the Week 4 deliverable requires a significant level of effort. The sooner each deliverable is completed, the sooner you can begin the next.
Week 2 Milestone: Course Project Design Proposal
Back to Top

A good design can make the software development process flow smoothly. The Course Project Milestone for Week 2 is a design document. The level of detail in your design document should be enough that you could pass the document off to a classmate and he or she could build the web application you have in mind. The deliverable must includes at least the following.
Presentation Layer Design

Wireframe diagrams or screen captures for
Log In/Account Creation page;
User Account Details page; and
User Account Confirmation page.

List of control names, IDs, and types for each page (See Week 1 iLab Step B.2 for an example.)

Identification of links and other navigation aids

Data Layer Design

An entity-relationship diagram (ERD) or other document that identifies the tables and fields in the database. You should have tables for user account information, past purchases, and any other tables you feel are necessary.

Prototypes of methods (or behaviors) for accessing the database

Business Layer Design

Validation rules for web form input fields

WHAT TO SUBMIT

All design documents in a single zipped archive

Week 3 Milestone: Home (Landing) Pages and Site Master Pages
Back to Top

Deliverables for this week's milestone are

.ASPX and .CS files for the site's master page;

the User Account Details page ASPX and CS files (using a site master page); and

the User Account Details Confirmation page ASPX and CS files (using a site master page).

For this deliverable, these pages do not need to connect to the database. When a user enters data on the User Accounts Details page and saves it, you use the application PostBack to display the account information on the details confirmation page.

The Completed Applications GridView does not need to be populated for this deliverable but should be present on the User Account Details page.

WHAT TO SUBMIT

It should contain a zipped archive of the website folder for your Course Project. It should contain all ASPX and CS files for your project in the correct folder hierarchy. Your instructor should be able to unzip and run your web application as is.

Week 4 Milestone: Data Layer
Back to Top

Deliverables for this week's milestone are as follows.

The Data Layer class for your application. The Data Layer class should implement the functionality needed to

find user account information;
update account info; and
delete an account when the user graduates from the program.
(Note: Be sure to delete any Completed Applications connected to the user's account.)

The User Account Details page should provide an interface for the Find, Update, and Delete user account information.

Microsoft Access database with all tables and fields in the design populated with sample data.

For this deliverable, the data layer methods may be called directly from the presentation layer. But because the Week 4 iLab introduces the business layer, you can get a head start on future deliverables by implementing the business layer also this week.

The Completed Applications GridView does not need to be populated for this deliverable but should be present on the User Account Details page.

WHAT TO SUBMIT

Submit a zipped archive of the website folder for your Course Project. It should contain all files for your project in the correct folder hierarchy. This includes at least the ASPX and CS files for the web forms, the data layer class, and the Microsoft Access database you created for your application. Your instructor should be able to unzip and run your web application as is.

Week 5 Milestone: XML Data Exchange
Back to Top

Deliverables for this week's milestone are as follows.

Bind the GridView on the User Account Details page so that it displays the required information on Completed Applications from the database.

Implement the Export Stats feature on the User Account Details page. You may need to implement additional methods in your business layer and data layer classes.

WHAT TO SUBMIT

Submit a zipped archive of the website folder for your Course Project. It should contain all files for your project in the correct folder hierarchy. Your instructor should be able to unzip and run your web application as is.

Week 6 Milestone: Security Management
Back to Top

Deliverables for this week's milestone are as follows.

Submit the completed Log In page and any necessary supporting methods in the business layer and data layer.

You can optionally remove the Find User button from the User Account Details page because it is no longer needed. User account information should be filled in based on the log in username.

WHAT TO SUBMIT

Submit a zipped archive of the website folder for your Course Project. It should contain all files for your project in the correct folder hierarchy. Your instructor should be able to unzip and run your web application as is.

Week 7 Milestone: System Quality Assurance and Test Plan
Back to Top

Deliverables for this week's milestone are as follows.

Submit a test plan that has at least 10 different workflows to test. You can test more—being thorough is a good thing! Your test plan should be in an Excel spreadsheet similar to the Week 6 iLab Test Plan spreadsheet (Wk6_Test_Plan.xlsx) in Doc Sharing.

Execute the tests in your test plan and record the results in the spreadsheet. Upload the completed spreadsheet as this week's Course Project Milestone deliverable.

WHAT TO SUBMIT

Submit a zipped archive of the website folder for your Course Project and the Course Project Test Plan spreadsheet. The archive should contain all files for your project in the correct folder hierarchy. Your instructor should be able to unzip and run your web application as is.