System Architecture and Security Requirements

This document provides information about the system architecture and security requirements for an online library. It includes details about the client-server architecture, components of the architecture, and security measures to protect the system from exploits and attacks. The document also discusses non-functional requirements and quality metrics for evaluating the software quality.

Table of Contents
ER diagram......................................................................................................................................2
System architecture..........................................................................................................................2
Security requirements..............................................................................................................................3
Non-functional requirements...................................................................................................................4
Quality metrics.................................................................................................................................4
References........................................................................................................................................7
1

ER diagram
System architecture
The architecture would be based on a client-server architecture using deployment diagram of
UML notation. A typical client server consists of several clients that connects to the server to
request information. The client systems through an interface access information and perform
functions and actions based on the available inputs provided by the server. The clients may be a
web browser accessing via Desktop computer, a mobile phone, a tablet or even a dedicated
application through the respective client systems.
2

The following components are included in the entire architecture:
 Web Server: The web server is primarily meant to handle the HTTP requests made by the
clients and helps in displaying the site’s content as well as the information requested by
the user.
 Application Server: The application server on the other hand handles the bulk of the logic
and processing needs for the client (Boehm, Brown & Lipow, 2019).
 Database server: The database server is responsible for storage and hosting of the datasets
for the system. So, the bulk of the data would be provided by the database server.
 Clients: The clients on the other hand are the end-users who would be connected to the
web-server via browsers or applications on their mobile, tablet or desktop computing
devices.
The web-server would be based on Apache on Linux based server, the application server would
consist of the PHP language which will handle the bulk of the application logic and the database
server on the other hand would consist of MySQL for storage of datasets.
Security requirements
 Outdated system: Outdated systems and technologies are a major cause for 0-day exploits
and other exploits that could ultimately disrupt the system, steal data or cause damage.
 Firewall: A sever without a firewall system would be more prone to attacks via rogue IPs
either through deliberate or otherwise means.
3

 Unused ports: Unused ports are another major cause for concerns as hackers could find
such ports and plan an attack via those routes.
 Cross-site scripting: Cross-site scripting-based attacks are those that exploit the
vulnerabilities inherent to an unprotected scripts on the website. The same can be used to
steal user data, put an immense load onto the server or corrupt the database.
 DDoS: A Distributed Denial of Service Attack is a type of attack wherein the entire
website could be brought to a halt by increasing the load on the server via rogue systems
spread across the world (Dr.M. Balasundaram & K.Poongodi, 2012).
Non-functional requirements
Following are key non-functional requirements of the proposed system:
Performance requirements:
 Increased customer satisfaction
 Reduction in overall costs
Safety requirements
 Backup recovery and business continuity
Security requirements
 Account ID and password protection
 Failed log-on attempts
 Encryption
 Auto-timeout screen blanking
Quality metrics
Quality metrics for evaluating the software quality:
Primitive
characteristi
cs
Metric
definition
Correlatio
n with
quality
Potential
advantage
s
Quantifiabilit
y
Ease level
for
automated
evaluation
developme
How
complete
is the
automate
d
4

nt evaluatio
n
Device-
dependency
Do the
functionaliti
es of the
proposed
software
independent
of the
underlying
computer for
achieving
required
objectives
such as
precision,
storage
scheme?
Self-
containednes
s
Does the
developed
software has
a facility to
for correct
positioning
of required
input or
output
devices?
Robustness Does the
proposed
5

software
have the
capability to
assign
default value
to non-
specified
parameters?
Consistency Does the
software
initialize all
specification
s identically
as per the
requirements
?
6

References
Boehm, B., Brown, J., & Lipow, M. (2019). Quantitative Evaluation of Software
Quality [Ebook] (1st ed., pp. 12-14). US. Retrieved from
https://csse.usc.edu/TECHRPTS/1976/usccse76-501/usccse76-501.pdf
Dr.M. Balasundaram, D., & K.Poongodi, K. (2012). Customer Satisfaction With Internet
Banking - An Analytical Study with Special Reference to the Selected Customers in
Namakkal District. Global Journal For Research Analysis, 3(8), 18-20. doi:
10.15373/22778160/august2014/6
7