Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Software Engineering

E-Voting System

Omar Saadi

on 8 June 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software Engineering

King Fahd University of Petroleum & Minerals
Department of Information and Computer Science
SWE-311: ‘Principles of Software Engineering’

E-Voting System Saad Al Eid & Omar Al Saadi Introduction Implemetation Vision Document Project Plan SRS Stakeholders 1-Transportation department (administration)
2-Student (User)
Product functions 1-Students
a. ID
e.Password (Assumption)

2-Close registration phase before voting.

3-Only registered students are allowed to cast
a vote

4-Student vote is hidden

5-Students can cast two votes

6-Vote items:
a.Times (Pick-up, drop-off)
b.Place (Pick-up, drop-off)

a.The administrator is required to print a list of sources and destinations
b.The administrator is responsible for opening and closing phases.
c.Phases should be opened in order
Constraints •Time Constraint: We may face some challenges in being on time since we are only two members and we have other projects submissions, or we may have an exam which forces us to delay our submission.

•Tools Limitation: We cannot use some tools (Enterprise architect, MS Project) except if we are in the universities labs. Risk analysis 1.“Delay in delivery” risk (Very High):

Within this semester, we are expecting to have delays with some of the tasks because of having different projects to submit. We reduced that risk by:
•Early preparation by assigning the tasks early so that each member will organize his own time.
•Adding extra day(s) for each task so that we can catch up if we forced to delay any task.

2.Our documents can be deleted or corrupted (for some reason) so we will copy our work in an external hard disk. (Very Low)

3.We planned to use php language. So we may face some challenges because we don’t have much knowledge about it. (High)
Hardware and Software requirements Hardware:

CPU speed 1 GHz or more, 512 Mb of RAM, and CD writer.


1.Microsoft Office 2007
2.MS Project 2003
3.Enterprise architect
Process Model Water fall model

We understand all requirements and no requirements change will occur. User requirements: Functional Non-Functional •Students shall register before the voting.

• The system requires the following information from the students; Student-ID, Name, Email Address, Location of stay on-campus and Password.

•The System shall close registration phase before voting.

•The System shall hide the student vote.

• Students can cast two votes.
•Students should choose the (Pick-up, drop-off) time and place.
•The administrator is required to print a list of sources and destinations
•The administrator is responsible for opening and closing phases
•Phases should be opened in order
Product requirement


Organizational requirement

Delivery: all submission should be a soft copy on Web Site.
Implementation : it may be either on PHP or Java
Process: it should be a waterfall model.

Use case diagram Actors discription Student:

He should be any KFUPM student.
He should registers for this system.
He should log in
He can cast two votes.


The transportation department will administrate this system.
He has to log in
He should open and close phases
He should print a list of sources and destinations.

SDD System Architecture Control Architechture The client-server model will be used as a system organization, because we have two clients (Student and Administrator) to be connected to the servers (login, voting, opening & closing phases, and counting) using internet network. Centralised control (manager model) is going to be used, since we have one sub-system that is responsible for starting, stopping and coordination of other subsystems. Class Diagram Sequence Diagram Voting State Transition Diagram System Interface Prototyping Deliverables i. Vision Document.
ii. Project Plan Document
iii. SRS Document
iv. Design Document
v. Prototype
E-VOTING SYSTEM Use Case Discription EER Diagram Project schedule
Full transcript