Web Application Development Project: Medical Store Management System

Desklib provides past papers and solved assignments for students. This project details the development of a medical store management web application.

Web Application Development
1

Contents
Introduction:...............................................................................................................................2
LO1: Understand the concepts of web application development...............................................3
1.1: Critically evaluate the functions and advantages of web applications............................3
1.2: Critically compare different types of server-side and client-side scripting languages.. .5
1.3: Examine web security concerns and make recommendations for security
improvements.........................................................................................................................6
LO2: Be able to design web applications...................................................................................8
2.1: design a web application to meet a given requirement...................................................8
2.2: Synthesis client-side and server-side functionality in a web application......................11
2.3: Apply a database design for use in a web application..................................................12
2.4: evaluate alternative designs and solutions to meet a given requirement......................12
LO3: Be able to implement web applications..........................................................................14
3.1: Implement a web application to a prepared design using client-side and server side
scripting language................................................................................................................14
3.2: Implement a web-enabled database management system to store, retrieve and
manipulate data in a web application...................................................................................19
3.3: Identify and implement opportunities for error handling and reporting.......................22
LO4: Be able to test web applications......................................................................................24
4.1: critically review and test a web application using a web-enabled database management
system...................................................................................................................................24
4.2: Analyse actual test results against expected results to identify discrepancies..............26
4.3: Critically evaluate independent feedback on a developed web application and make
recommendations for improvements....................................................................................26
4.4: Create user documentation for a developed web application.......................................27
Conclusion:..............................................................................................................................31
References:...............................................................................................................................32
2

Figure 1: Architecture of web application.................................................................................4
Figure 2: MVC architecture.......................................................................................................5
Figure 3: Login page..................................................................................................................9
Figure 4: Home page..................................................................................................................9
Figure 5: View medicine page.................................................................................................10
Figure 6: Add medicine page...................................................................................................10
Figure 7: view supplier page....................................................................................................11
Figure 8: sale medicine page....................................................................................................11
Figure 9: E-R diagram of the project.......................................................................................13
Figure 10: server side code......................................................................................................15
Figure 11: client side in php.....................................................................................................15
Figure 12: CSS code.................................................................................................................16
Figure 13: session management in php....................................................................................16
Figure 14: logout code.............................................................................................................17
Figure 15: sale medicine page code.........................................................................................17
Figure 16: Stock pharmacist page code...................................................................................18
Figure 17: login page...............................................................................................................18
Figure 18: view medicine page................................................................................................19
Figure 19: manage pharmacist page.........................................................................................19
Figure 20: view supplier page..................................................................................................20
Figure 21: admin table.............................................................................................................20
Figure 22: main_sale table.......................................................................................................21
Figure 23: medicine table.........................................................................................................21
Figure 24: sub_sale table..........................................................................................................22
Figure 25: supplier table...........................................................................................................22
Figure 26: login page...............................................................................................................28
Figure 27: Homepage...............................................................................................................29
Figure 28: view medicine page................................................................................................29
Figure 29: add medicine page..................................................................................................30
Figure 30: view supplier page..................................................................................................30
Figure 31: add supplier page....................................................................................................31
Figure 32: sell medicine page..................................................................................................31
3

Table 1: client and server side scpriting language comparison..................................................8
4

Introduction:
This document contains information about web applications. Learner will deeply go through
details about web applications, functionalities of web applications, its advantages.
It also contains information about client and server-side scripting languages, differences
between client and server-side scripting languages and its type.
Learner will gain information about web security and how to improve web security in a given
website.
Learner will be able to design a website, completely from scratch to meet the desired
requirements. They will further learn what are the functionalities about client side and server
side scripting language in a website. Learner will gain deep knowledge about database and its
connectivity in the website.
Alternative languages could be studied which could have been used instead.
Learner will be able to implement the gained knowledge in order to develop a website or web
application completely with the help of this document.
Learner will gain thorough information about various testing that could be performed on a
website. How to improve a web content and what are the different feedback which would be
beneficial to remember while implementing a web application.
5

LO1: Understand the concepts of web application development.
1.1: Critically evaluate the functions and advantages of web applications
Web application is a computer based program which is able to perform any particular
function with the help of client browser and web server. Web applications can be executed on
any platform. It is not bound to any particular platform. It is platform independent. There is
specific application for every specific task. Web applications can be related to anything,
either gaming or shopping or Govt. sites etc. Web applications provide a common platform
where all the customers as well as different organizations can interact with each other. Also,
various business can pitch their products on the website and gather enough interested crowd
(Nations, 2007).
Functions of Web-applications:
Figure 1: Architecture of web application
Source: (adminqa, 2017)
 It follows Client-server architecture: Client server architecture is used to establish the
communication between client’s browser and server. The connection is established
using internet. The main benefit of using client-server architecture is that it provides
scalability to the web application. Resources can later be added.
 MVC model: Web applications are strictly based on MVC model. MVC stands for
Model-View-Controller. It is a framework, where, controller is the brain of the model.
It communicates within the framework with the model and view component as well as
with client. It accepts requests and then forwards it to the model, where model is used
to interact and establish a connection with the database. After retrieving the data it
6

reverts back to the controller where controller further sends it to the view component,
where View is used to build UI for the client. Whatever is shown at the front end is
actually developed using View. After, it reverts back to the controller which then
combines everything and sends it to the client.
Figure 2: MVC architecture
Source: (Topic, 2005)
 Platform Independent: Web applications are platform independent. They can be
accessed on any platform like desktop application, mobile, tabs etc. They can be
executed on any platform without any difficulties. Web applications are easily
accessible at anytime anywhere.
 Offline Web-applications: Nowadays, web-applications do not always require an
active internet. There are many websites available which require no internet. These
are used for simple tasks such as camera, contact etc. They have relations with their
own database (adminqa, 2017).
Advantages of Web applications:
i) DORA- It stands for Develop once run anywhere. In this, developer develops
web-applications once and permits the user to access the website from any remote
location. And for this, the user only requires to install the web-application on their
personal devices. The main benefit of DORA is the application is not dependent
on any software. The web application will run in a similar manner among different
devices.
7

ii) Upgradable: Web applications are very easy to upgrade, the reason being that the
code is stored on the server, the part which needs improvement will only be
upgraded, the rest of the code remains same.
iii) Execution: Web application is a smart approach to process and manage huge
amount of data. In market, there’s a large amount of data available which needs to
be managed in a proper way, client-server architecture is a centralized system
which helps to systematically manage the data. Otherwise, managing such data
would require expensive equipment and investment.
iv) Open Source: Half of the frameworks available for developing a web application
is in fact an open source. It helps to develop another application using existing one
at a low cost. Frameworks also provide additional features which helps enhancing
the web application. Some of those frameworks are AngularJS, VueJS, NodeJS,
ReactJS, etc. These frameworks helps by saving a lot of time and effort required
to build a website.
v) Maintenance: Web application has various standards which further requires
market based standards. In addition, there are different resources available in the
internet which helps building a web application in an easier way. Further, this
requires very low cost and efforts for maintaining a website.
vi) Web applications are also faster to access.
vii) No installation of any web application is required. Also, they are secure and free
from malware activities (Baca, 2017).
1.2: Critically compare different types of server-side and client-side scripting
languages.
Client side scripting language runs on the client’s browser, it is used to dynamically generate
pages by automating the code sent by the server. Generally the languages used are JavaScript,
with a combination of CSS and HTML. Client side scripting language need not any
additional functionalities once the page is loaded, all the tasks are performed on the browser
by itself. Client-side code is embedded within a HTML code. Client side scripting languages
could be used to manipulate HTML elements and help in giving an interactive user
experience. CSS could also be used to style the look and feel of the page. Another major
benefit of using client-side scripting language is that it doesn’t put too much stress on the
8

server, again the reason is that once the page is loaded onto the client’s browser then the
processing is not further required (Thoms, 2018).
Server-side scripting language: It is used for validations on the forms. Also, server side
scripting languages provide access to backend. They are used for manipulating data on the
database. They are used to provide response to the request made by the client on the website.
Server-side scripting languages provide functionalities to the client-side scripting languages.
While running JavaScript pages and various plugins, the user’s computer get through a lot of
load to process at a time, this load on the client’s devices could be removed with the help of
server side scripting language. Also, not all browsers completely support JavaScript, in such
situations server-side scripting languages help dynamically generate the page.
Difference between server-side and client-side scripting language:
Table 1: client and server side scripting language comparison
S.No. Server-side scripting
language
Client-side scripting
language
1. Server-side scripting
languages allow dynamic
pages to be generated when
a request is sent to the server
by the user’s browser.
Client-side scripting
language allow pages and all
the codes to be executed on
the client’s browser only.
2. Server-side scripting
languages deals with the
backend which is not
presented to the client.
Scripts in client-side
scripting languages are
visible to the client’s or
users.
3. It requires interaction with
the server.
It does not require any kind
of interaction between the
server.
4. It is relatively secure and
could be used to
dynamically provide
websites.
Client-side server scripting
language is not very secure.
5. Examples of server-side are:
Php, Ruby on Rails, Python,
JavaScript, HTML, CSS,
9

ASP.net etc. etc.
1.3: Examine web security concerns and make recommendations for security
improvements.
No matter how many antivirus or software are installed, there are always vulnerabilities when
it comes securing data on the Web. Some of those security concerns are listed below:
 SQL Injection: It a kind of security vulnerability in web application. In this, the
hacker tries to corrupt or manipulate the content of the database with the help of an
application code. Hackers tries to gain access by inserting malicious code which
exploits the database.
 XSS: It stands for Cross-site scripting. The target of XSS is injecting harmful script
generally JavaScript to the user’s end by the end of the application. Attacker hijacks
the entire validation, destroys sessions and keeps the credentials in such a way that the
user transits from client’s own browser to another malicious browser without even
knowing.
 Session Management: Session could be described as a timestamp which notifies the
time from the user has been logged in till the time the user has logged out. It also
identifies the user with the provided credentials and helps secure the website. Attacker
can manipulate the data if the session or authentication of user’s credentials is not
protected.
 Security Misconfiguration: It defines various kind of vulnerabilities focusing on the
lack of maintenance and attention provided to the web application. It can provide
attackers access to important and private data which can further result in the
compromise of the entire system.
 CSRF: It is an abbreviation of Cross-Site request forgery, is in fact a very malicious
attack. In this the client gets tricked into doing an action they did not mean to
perform. Attacker can gain access by targeting the client’s already authenticated
browser by sending a third-party request (Bassi, 2017).
Recommendations for security improvements:
1. Regular Updates: Websites need to be regularly updated in order to keep them safe
from various threats. This process is carried out with the help of virtual patching. It
makes sure that the website is secure and that it is protected from several exploits.
10

2. Backups: Performing backups from time to time saves the website from the worst. If
any attack happens at least the whole system won’t come crashing down. Websites
require a proper backup strategy to ensure that they are kept safe.
3. Limiting User Access: It is important to make sure which user has access and up to
what content. Access should be granted on the basis of hierarchical order. New user’s
should not be granted access to the entire website.
4. Https protocol: All the websites nowadays are being accessed by HTTPS protocol. It
is safe and the content is not changed at the time when the user is accessing it. It is
safe to provide user’s credentials in, websites which are not accessed by HTPPS
should be avoided (Arsenault, 2017).
LO2: Be able to design web applications.
2.1: design a web application to meet a given requirement.
Figure 3: Login page
11

Figure 4: Home page
Figure 5: View medicine page
12