Write fully functioning server-side prototype for a site development report

Background

You are working in a development role at the organization Website Implementation Perfection (WIP). One of WIPs clients is an Australian plant nursery named Good Gums. Good Gums already have a client-facing website, but they are now interested in developing an internal site that will assist in the management of the business. Your manager has asked if you might be able to put together a fully functioning server-side prototype based on the requirements outlined below.

The site development is broken up into eleven separate tasks

• the site should show, and what the pages will do.
• Tasks7-11arethenon-functional requirements of the site.ThesearethehighstandardsthatWIPwant to have for all the sites they develop.

It is recommended that you read through all the tasks prior to commencing work.

Task 1: Log in

This page provides a login feature so that Good Gums staff can securely access the website. The page will have the following features:

• This means for users enter their username and password.
• A list of usernames and corresponding passwords in a text file named loginfo.txt. Each line in the file will have a combination of username and password separated by a colon i.e.username: password refer to the example below
• A comparison of any entered username and password combination against records in the loginfo.txt file. If there is a match the user is permitted to enter the site.
• Usage of the session feature to enable users to maintain logged-in sessions across pages of the site.
• Users that attempt to access any pages on the site without logging in should be redirected (Response. Redirect) to log in.aspx
• Once a user has successfully logged in, they should be redirected to the index. aspx page.
• A user should have the ability to log out. When a user selects this option, the session should be cleared by calling the same login. aspx page with the URL parameter logout=1 (e.g.http://localhost:8080/login.aspx?logout=1)

Table 1: Example loginfo.txt File Content

Task 2: Home

• The home page is the entry point for the website. As this is the first page that will be viewed by users it should be designed in an attractive manner.
• The home page should include a GridView control that will be used to display a list of customer purchases. The purchase data will include the following data:
  • ID
  • Full name
  • Email address
  • Product Name
  • Unit Price
  • Quantity
• Data for the GridView will be taken from an XML data file and populated into the GridView using data binding a sample data file can be downloaded from where you obtained this assignment document. You must also demonstrate your familiarity with working with the data file format by adding extra records to the data.
• The home page should include a Label control. The Label control should display the number of Large Orders, which is defined as any order where the customer has ordered 10 or more plants. Note the following:
  • The Label only needs to display how many Large Orders exist you do not need to provide any extra info.
  • Make sure that you include some larger orders in your sample XML data.

Task 3: Add record

This page is used to add details of new customer orders.

• The page should contain a form that allows the user to make changes to the XML data file by adding records one at a time.
• An appropriate form field should be used for each separate field of the record.
• There is no need for the user to enter the ID field when adding records (this should be automatically determined depending on other ID fields). The ID field should be unique for each record.
• All form fields should be appropriately validated.
• A Submit button should be used to write changes to the XML data file.
• A Label control should be used to display a message when the XML data file has been successfully updated.

Task 4: Invoice

This feature is intended to allow staff to prepare a printable invoice. It is divided into two pages

• of invoice.aspx
• print.aspx

Note that it is not expected that this page is data-bound to the XML file used in previous tasks.

nvoice.aspx page:

This page collects details about the invoice items. The form is designed to accept 3 rows of data for the invoice. A mock-up of the interface is below:

Some notes about the interface:

• Full name of Customer: Must be no longer than 50 characters to be valid. Required.
• Item name: Must be no longer than 100 characters to be valid.
• Unit price and quantity: Text boxes that must be validated to receive non-negative numbers only. A maximum of 1000.00 is allowed for the unit price and a maximum of 100 is allowed for quantity.
• Submit: Validates the form and submits the form is valid. The user is taken to print.aspx page after submission.

The interface must also have appropriate validation controls and a ValidationSummary control at the end. Validation for individual inputs will be sufficient. A mock-up of the interface showing these is shown below

the print.aspx page:

This is the destination page after the form is submitted.

• This page will be a print-friendly version of the invoice form with simple labels and totals. All non-essential header, navigation, and footer page components are omitted for print-friendliness.
• The invoice must include the name and contact details of the organization at the top. A mock-up of the remaining output format is shown on the page:

Task 5: Stocktake

This page allows administrators to take a general stock inventory for any day-to-day items related to the organization. It is expected that you will use examples from Good Gums's range of products. Refer to the assessment appendix for these examples.

The stocktake form will allow the user to enter up to three rows of items. The form will be pre-loaded with dummy data to simulate taking the data from a data source.

The stocktake form also has a text input for the reorder level. The reorder level is the level that the stock must be replenished. The only stock that has dipped below the reorder level needs to be replenished back to the reorder level.

A mock-up of the interface is below:

Some notes about the interface:

• Reorder level: Read-only. Default 10. Modified with - and + buttons. The range is 0 to 1000. Additionally performs the function of the Calculate button (see below).
• Item name: Must be no longer than 100 characters to be valid.
• Stock quantity and unit price: Required. Text boxes must be validated to receive non-negative numbers only. A maximum of 1000.00 is allowed for unit price and a maximum of 100 is allowed for stock quantity. May be set to zero to indicate unused rows.
• Reorder quantity, subtotal and total: Derived data in labels.
• Calculate: Validates the form and recomputes calculations (if valid).

The interface must also have appropriate validation controls and a ValidationSummary control at the end. A mock-up of the interface showing these is below:

Task 6: Chart

This page includes an ASP.NET Chart control to model data for the organization with the Chart Type is set to Line. The data will model the total earnings for the last 5 years.

You only need to populate the chart with static data. i.e. You are not expected to perform any data binding. It does not matter if your data does not automatically update to remain consistent with any other page on the site.

The chart must be given attention to detail for its presentation, including all components that you may expect for this type of chart: title, axis labels, and data labels.

Task 7: Organisation

The following organizational aspects must be put in place for your solution:

1. Programming language:

The website will be a server-side website using ASP.NET for the web forms and C# for the code-behind functionality. Some HTML and CSS may also be used where appropriate.

2.  Third-party components:

The website will be hand-coded by yourself. Therefore, you may not include any third-party components except for those mentioned in the assignment.

1. mages:

Even though this internal website is not public-facing it is still expected that you would make use of some images as part of your website design. Store the images in a subfolder called images. Note that the website cannot use copyrighted images. To avoid this problem, you had been provided with the necessary images of the different plants sold by Good Gums and of its employees. The images are available for download as a separate zip file within the assessment activity, where you downloaded this assessment file. Note: you are not allowed to use these images anywhere other than for this assessment

1. integrated development environment:

The website must be built using Visual Studio

2.  Template:

The website will be built from scratch beginning with an empty folder. Follow these steps:

1. 1. Create a new folder called xxx_cse2icx_assignment3, where xxx is your student ID.
   2. Open Visual Studio. Select File -> Open -> Website… and select the new folder.
   3. Select File -> Close Solution immediately. This will prompt you to save a solution file (*.sln suffix). This must be saved in your new folder. Close Visual Studio.
   4. Double-click on the solution file to open Visual Studio and your solution again. Continue to use this method for opening your solution going forward for convenience.
   5. You are now ready to go. Add your project assets next.

Task 8: Layout

The body of the website pages must be organized to include distinct header, navigation, main, and footer semantic tags with the following content:

1. Header: Site name and branding.
2. Navigation: Navigation bar.
3. Main: This is the main content of each page.
4. Footer: Copyright statement.

Task 9: Navigation

The navigation bar appears on every page of the website and contains the following aspects:

1. The navigation bar has links to the five main pages of the website (Tasks 1-6).
2. Each navigation item must be the same size.
3. The link for the current page is disabled and has a different color/appearance.
4. The links for the non-current pages have a different color/appearance when hovering.
5. The navigation bar is responsive, meaning that the menu options gracefully wrap to the next line when they cannot all fit horizontally on the screen.

Task 10: Presentation

The presentation of the website will largely be controlled by CSS with the following aspects:

1. All CSS code will be stored in a site-wide style file called styles.css and referenced on each web page.
2. The styling will include a variety of styling for layout.
3. The styling will include a variety of styling for content.
4. The presentation will endeavor to give the site a contemporary appearance, including HTML version 5 and CSS version 3 where practical.

A good way to test presentations is to perform cross-browser testing. I.e.: View your website in a range of popular web browsers and check that the presentation is consistent.

Task 11: Code

This task will award marks according to the quality of your code according to these aspects:

1. Code indentation is consistent with one level of indentation per block.
2. All ASP, C# and CSS file types each use some comments (<%-- comment --%>, <!-- comment -->, /* comment */ or // comment as appropriate, minimum of 3 per file type).
3. The Visual Studio Error List reports zero errors and zero warnings.

Although marks are not allocated, it is also good practice for code to consistently use best-practice casing (lowercase, camelCase, TitleCase as needed).

Task 12: Site Testing

1. Briefly explain the two main types of testing.
2. What are the specific testing methods for web application testing? Briefly explain each method and its relevance with respect to the website created in this assessment.

This  IT Computer Science  Assignment has been solved by our IT Computer Science Expert at Exam Question Bank. Our Assignment Writing Experts are efficient to provide a fresh solution to this question. We are serving more than 10000+ Students in Australia, UK & US by helping them to score HD in their academics. Our Experts are well-trained to follow all marking rubrics & referencing Styles. Be it a used or new solution, the quality of the work submitted by our assignment experts remains unhampered. You may continue to expect the same or even better quality with the used and new assignment solution files respectively. There’s one thing to be noticed you could choose one between the two and acquire an HD either way. You could choose a new assignment solution file to get yourself an exclusive, plagiarism (with free Turn tin file), expert quality assignment or order an old solution file that was considered worthy of the highest distinction.