Deployment Diagram

The deployment diagram shows how a system will be physically deployed in

the hardware environment. Its purpose is to show where the different
components of the system will physically run and how they will
communicate with each other. It is used to identify performance bottlenecks,
and is developed by architects, networking engineers, and system engineers
(24).
3.1. Design Goals of the system

The design of the system is highlighted as follows, in terms of performance, maintenance, end user
criteria and security

Performance

The system will complete the task quickly to allow easy input of data and to retrieve data from the
server. The system will be accessible from any computer with internet and will be accessible anytime a
user would want to use the program. In terms of performance, the system will help the user quickly
accomplish their task.

Maintenance

It does not need expertise person but just it needs any professional person in IT who can use database
and internet. The system will require minimal upkeep and maintenance to stay working at optimal
levels.

End user

This project is very simple to use. Anyone who can read English language can use the system, because,
to use the system only clicking a button, it does not need to write commands and to think how to use it.
This program will have a well-defined and easily understood interface. The processes will be easy to
understand and use by a user of any level. 

Security requirement

Since the system will require strong security features to protect that valuable information. To use it, it
needs user name and password when they try to login to the system. Therefore, it is very secured
system. In general, to make the system asset safe, the system will follow a role-based security, which
means the access level, and the system administrator predefines privilege for each users of system. The
end user of the system most of the time will be asked for authorization login