Web Application Development for Shore Project

Introduction: -
Web application is a web apps. It is access over the network connecting using HTTP.
The web apps run inside a web browser. The web application there are two side
client-side scripting and server-side scripting. The client-side scripting generally views
the visitor site and server-side scripting cannot view the visitor site.
In this project, there are four sections, in the first section I will discuss about web-
based application and their requirements and types, also site analysis and discuss
about the server and client-side functionality. In the second section, I will discuss
about the will created wireframes of my website and their use case diagrams. In the
third section, I will discuss about the data store, data retrieve and data manipulation.
And describe about the error handling. In the last section I will discuss about the
functionality testing, browser compatibility testing and user documentation.
P2.1 design a web application to meet requirements given in the case study.
Wireframes of my Shore Project Website
Wireframe of the Register Page: -
Figure 1 Register Page

Wireframe of the Login Page
Figure 2 Login Page
Wireframe of the Product Page
Figure 3 Product Page

Wireframe of the Shopping Cart Page
Figure 4 Shopping Cart
P2.2 Synthesise client-side and server-side functionality in a web application
Client-side Functionality: - In the client-side functionality, it validates users inputs and
reduces the request to pass the server. And accessing the browser like visual basic script and
java script. It does not involve the server processing. The client usually browses execute
locally, it adds the functionality to the web pages.
Server-Side Functionality: - It generate the response for the customers. It provides the
flexibility to the programmers. It runs on the web server and any server side can be used. Its
pages create dynamically. It interacts with only back-end. It capability to serve execute
programs to the server site, it allows to run on the website. Also, it reduces the burden of
the website pages. It makes the site faster and decrease the size of the web pages.
Client Need: - In the user check and analyse requirement and fulfil their requirement. In the
analyst understand and listen carefully the all requirements of the client and then they start
their process.
In this, the analyst first checks the all requirement then they planned for the application
after making the application they check the implementation of the application and then
they run the application on the client site.

User needs: - In the user need, for the customer should be easing to register on the
website, ease to register, and comfort in usability. The customer wants online chats for any
issue. Also they want historical information about the website, they check that they are on
social media or not.
Server-Side Needs: - Apache Tomcat is an open-source software, it is a framework where
the server-side codes run.
https://theblog.adobe.com/qa-with-anton-sten-author-of-user-experiences-that-matter/
P2.3 Apply a database design for the given scenario.
ERD Diagram: - It is also called entity-relationship diagram, in this the diagram presents
graphical representation of entity and their relationship to each other.
It is a conceptual model data used to present the entity framework.
https://medium.com/omarelgabrys-blog/database-modeling-entity-relationship-diagram-
part-5-352c5a8859e5

Figure 5 ERD diagram of Shore Project
Use Diagram: - It represents the both textual and visual representation. It is the dynamic
diagram in UML.
Use case: - it represents the system Function.
Actor: - It is user of a system. In the use case diagram, one system is Actor and another one
is system.
Relationship: - the relationship represents relationship between actor and use case with a
simple line.

Normalisation: - It reduce the data problem and set of relation with the help of data
redundancy and data integrity. The normalisation removes the data redundancy help to
insert, delete, update errors.
https://www.sqa.org.uk/e-learning/MDBS01CD/page_26.htm
1 NF: - In this normalisation,
 column must be unique,
 no rows will be duplicated,
 No column will be duplicated
 Each table must be identified with unique column and concatenated column called
Primary Key.
Figure 6 1 NF
2 NF: - In this normalisation,
 In this single column should be Primary Key,
 I should not have Partial dependency.