Visula studio 2008 for web

Our Client is has a web project which need to be written in VS with MSsql.

Project will be web based.

Our client have a new promotion this spring – they are giving away MP3 player speakers to consumers who collects 3 special tops from their range of products. The purpose of the project is brand promotion and there will be no collection of data for marketing purposes.
We need a Web Application that will accept these orders, email the consumer and store the data in an SQL 2000 database. At the moment there is a requirement for translation for up to 32 languages – translation will be provided by the client but the design must take into account the incorporation of right to left languages using non Western character sets.
1.1 Summary
The form will be nothing more than a traditional order form – with the fields - detailed in 1.3 below – arranged in a design incorporating client supplied graphics.
1.2 Number of Pages
The site will have no more than 4 pages per language – Order Form (Home) – FAQ – FAQ Web Form – FAQ Contact Us page. There will also be a language specific page informing the consumer of the end of the promotion.
1.3 Fields
The following fields must be on the Order Form and FAQ Contact Form.
Request ID (Only applicable to the FAQ Contact Form) First Name Last Name Address
City Country
Post Code Email Address x 2 Captcha
1.4 Graphics
All graphics on the site will be supplied by the client.
1.5 Layout
The form will be laid out in a traditional format – Name, Address etc with a Captcha field at the end. There will also be two links to the client terms and conditions and privacy pages on the client main site. Validation is covered in Section 2 later.
The FAQ page will be a list of FAQs linked to anchored links further down the page. If the FAQs do not answer the consumer’s questions then they have two options – complete a web form on a separate page or click a link for contact telephone numbers. The Contact page will not be a traditional one, the only reason the consumer will arrive at the page is because their speakers have not arrived or are malfunctioning – therefore, we are going to ask them to key in their Request ID (sent with the confirmation email). The form will then do a lookup on the SQL table and pre-populate the fields from the original order form, they will be asked to confirm that the address is correct and choose from a drop down with the following options:

Speaker did not arrive
Speaker is damaged
Speaker not working
If the consumer chooses speakers did not arrive then the form cannot be submitted if the date is less
than 21 days from the ship date then a message should be displayed on the screen informing the
consumer.
The form must have three links on it – client’s corporate T&Cs and Privacy pages and a link to
download Adobe Acrobat as the label attachment will be in PDF format.

1.7 Localisation
At the moment there is a requirement to translate the site into at least 23 different languages (the
translation will be done by our client) – these include non-Western languages. Our client has informed
us that they will host the language specific page and each countries link on this page will refer to a page
hosted on our site, eg, default_en_gb.aspx.
As some of these languages will also be right to left languages this must be factored into the design.

2. Validation
2.1 Field Validation
The Order page will have multiple validations to ensure the integrity of the data.
There will be validation on the following fields: Field Validation Mandatory
First Name
Text
Yes
Last Name
Text
Yes
Address
Text
Yes
City
Text
Yes
Post Code
Alpha Num
Yes*
Country
Prepopulated
Yes
Email 1
= Email 2
Yes
Email 2
= Email 1
Yes
Captcha
= Image
Yes
* Only for countries that use Post Codes.
The FAQ Contact form will have multiple validations to ensure the integrity of the data.
The fields below the Request ID will not be available until a valid number is entered and a reason is chosen from the drop down.
There will be validation on the following fields: Field Validation Mandatory
Request ID
Numeric
Yes
Reason
Choice
Yes
First Name
Text
Yes
Last Name
Text
Yes
Address
Text
Yes
City
Text
Yes
Post Code
Alpha Num
Yes*
Country
Prepopulated
Yes
Email 1
= Email 2
Yes
Email 2
= Email 1
Yes
Captcha
= Image
Yes
* Only for countries that use Post Codes.
2.2 Form Validation
The Captcha field will ensure human completion of the form.

2.3 Client Acceptance
The consumer must accept T&Cs before the Submit button is clickable.
After the form has been completed and the submit button is clicked a popup will appear that contains all the data entered and it will ask the client to confirm the details are correct – the entry is not made in the database until this final confirmation is complete and the email is sent.

3. Systems
3.1 Servers
The application will be hosted on Windows 2003 Servers with IIS 6 – the backend database runs on a Windows 2003 server with MS SQL Server 2000 – the developed application must support these two environments.
3.2 Development Environment
The preferred development tool is Visual Studio 2008, the application must be written in Visual Basic supporting .Net Version 2.
The project file containing all project elements must be supplied.
3.3 Web Standards
The web application must comply with modern standards and accessibility laws.
3.4 SQL
Below are the fields in the main SQL table
Field Type Front End Backend
Request ID
Numeric
Yes
Yes
First Name
Text
Yes
Yes
Last Name
Text
Yes
Yes
Address
Text
Yes
Yes
City
Text
Yes
Yes
Post Code
Text
Yes
Yes
Country
Code
Yes
Yes
Email
Email
Yes
Yes
Order Date
Date/Time
Yes
Yes
Mail Sent
Date/Time
Yes
Yes
Status
Choice
No
Yes
Status Date
Date
No
Yes
Order Count
Numeric
No
Yes
Reject Reason
Text
No
Yes
There is a correlation between the field names of the web form and SQL table – but the extra fields
will be used for validation and order checking, eg, no re-orders can be placed if the difference between
Status Date field and current data is less than 21days (or whatever the promotion T&Cs state).

4. Processes
4.1 Order Process
The order process can be split into frontend and backend processes – the backend processes are beyond
the scope of this document.
The agreed order process involves the consumer completing a web form, receiving an email with a PDF
attachment that contains a label, the consumer prints the pdf, attaches it to an envelope containing the 3
special tops and sends it for fulfilment.
4.2 Web Process
The consumer will arrive at our website via a link from the client’s website, where they will be
presented with the order form. After completing the form, accepting the T&Cs and verifying the details
are correct the web application will do two things:
Generate an email with a PDF attachment that is then sent to the client
Update the SQL table with the order details
There is complexity involved in this process as the application needs to capture the data from the form,
generate a PDF containing the captured data along with mailing details, a unique ID represented in
numerical and barcode formats and then send it in an email to the client in the same language as their
order form page. We envisage this being done via a mail-merge process on the web server, but we are
open to suggestions on alternative methods of creation.
In order for us to keep track on the process the SQL table must be updated with the record first, then
the consumer will be emailed, both these timestamps should be recorded in the table in the appropriate
fields – these details will be used by our backend processes when the client sends in the pack tops.
Client Site
Order Entry Page
Validation
Popup
Complete Form
SQL 2000 Server
No, Return to Form
Order Process
Email User
Update SQL