SYSTEM OVERVIEW

The Student Union Voting System is the software system

allows voters (students) to vote online without having to
go to an election site, while maintaining their privacy and
security.
It is critical to select the president and other executive
managers who will lead the various sectors of the student
union at the University.
Some Functionality of the System
Registration
Login
Post Announce
Approve Chairperson or election committee
View Notice
Logout
Cast Vote
SYSTEM ARCHITECTURE
The architectural pattern of our system is 3-tier architecture model.
Those are presentation tier, application tier and data tier.
After the selection of architectural pattern, we perform the system
decomposition into different sub system.
 Administrator
 Voter Chairperson
 Candidate
Each of this subsystem have different component
Architectural Design
The system is consisting of 3-tier architecture model.
The presentation layer is client layer and top most layer of the application.
This is the layer we see when we use this system. it is the interface to the
system.
Business logic layer: it is application layer which interacts with data layer
and sends information retrieved from database toward to presentation layer;
it acts as the mediator between presentation layer and data layer.
The third one is data layer which used to store data entered by the user.
4+1 view model
Logical view: The logical view is concerned with the functionality that the
system provides to end-users. We depict by using class diagram.
Process view: The process view deals with the dynamic aspects of the
system, explains the system processes and how they communicate, and
focuses on the run time behavior of the system. The process view addresses
concurrency, distribution, integrator, performance, and scalability, etc. We
depict by using sequence diagram.
Development view: The development view illustrates a system from a
programmer’s perspective and is concerned with software management.
This view is also known as the implementation view. We depict by using
component diagram.
Cont…
Physical view: The physical view depicts the system from a system
engineer’s point of view. It is concerned with the topology of software
components on the physical layer as well as the physical connections
between these components. This view is also known as the deployment
view. We depict by using deployment diagram.
Scenarios: The description of an architecture is illustrated using a small set
of use cases, or scenarios, which become a fifth view. The scenarios
describe sequences of interactions between objects and between processes.
They are used to identify architectural elements and to illustrate and
validate the architecture design. They also serve as a starting point for tests
of an architecture prototype. We depict by using use case diagram.