Final Project Proposal: Punjab University College of Information Technology
Final Project Proposal: Punjab University College of Information Technology
0
Final Project Proposal Date: 24 February, 2021
PUCIT
Punjab University College of Information
Technology
TABLE OF CONTENTS
1. Introduction
a. Project Title
b. Project Overview Statement
c. Project Goals
d. Project Objectives
e. High Level System Components
a. Component no.1
b. Component no.2
c. Component no.3
d. Component no.4
i. ………..
f. List of optional functional units
g. Exclusions
h. Application Architecture
i. Gantt chart
administrator by comparing their details submitted with those in existing databases such
as those as the Registrar of Persons, the citizen is then registered as a voter.
After registration, the voter is assigned a secret Voter ID with which he/she can use to log
into the system and enjoy services provided by the system such as voting. If
invalid/wrong details are submitted, then the citizen is not registered to vote.
Voters Qualification
o Country Citizenship
o Age: at least 18 years
o Legally competent persons
o Registration on the voters' list
Candidate Qualification
o At least Graduation (B.A/B.sc)
o Country Citizenship
o Age: at least 28 years
Power failure.
Failure of security mechanisms (e.g., breach of electronic voting machine security).
Late or failed delivery of equipment and services.
Obstacles:
Signal Problems.
Network Slowdown
Organization Address (if any):
Govt. Post Graduate College Gojra
Type of project: Research Development
Target End users:
Goals:
Less effort and less labor intensive, as the primary cost and focus
primary on creating, managing, and running a secure android
voting portal.
Increasing number of voters as individuals will find it easier and
more convenient to vote, especially foreigners or army officers.
1.7 Exclusions
• Other than Android all platforms are restricted. For example, in IOS,
there is limited freely accessible library and creating an IOS
application required the user with the IOS account which was
controversial with the Android platform that was open source and has
free access to the library.
Three-Tier Architecture:
The Three-tier Architecture is divided into 3 layers:
Presentation layer
Business layer
Database layer
1. Presentation layer:
It is also known as Client layer. Top most layer of an
application. The main functionality of this layer is to communicate with
Application layer. For example, login page of Facebook where an end user could
see text boxes and buttons to enter user id, password and to click on sign-in. This
is also called view of the application.
2. Business layer:
It is also called business logic layer or logical layer. As per the Facebook
login page example, once user clicks on the login button, business layer interacts
with Database layer and sends required information to the Presentation layer. It
controls an application’s functionality by performing detailed processing. This
layer acts as a mediator between the Presentation and the Database layer.
Complete business logic will be written in this layer.
3. Data layer:
The data is stored in this layer. Business layer communicates with
Database layer to retrieve the data. It contains methods that connects the database
and performs required action e.g.: insert, update, delete etc.
Step 1: Whenever we submitting the request from client (Browser) to Server component
then controller receives the request from Browser. So you must remember every request
will reach to controller component.
Step 2: The controller receives the request from Browser then Controller has to identify a
particular model. Then it will execute business logic. Here model is might be java class
or business logic's available. Here controller acts as mediator between view and the
model. Finally, after performing some action on server side then controller identify
respective view component. That means JSP page has view part.
Step 3: After executing model part if it is required to interact with database then model
part interact with database.
Step 4: Then view layer displays of the model to the end user. Then generate the required
dynamic web page return to Browser. Finally view part sends to the response to the client
(Browser)