Project Plan
University’s election system is an internal system used to run online elections for all kinds of ballots and for different collections of staff and students. The existing election system (below referred to as “the system” or “system”) is deemed to be unsustainable, very dependent on manual implementation and does not meet the architectural standards of CQUniversity`s IT unit. A decision has been made to replace the current election system with a new system which is more reliable, efficient, intuitive, less costly to maintain and meets ITD’s 1architectural guidelines. The new election system will eventually be integrated into the current Student Handbook for resource reuse and ease of maintenance. However, because this project also serves the purpose of being a real life practical project for course COIT23004, the end deliverable will be extracted into a standalone application for the demonstration of developing multi-tiered software.
1 Objectives and Constraints
1.1 Objectives
The objective of this project is to replace the current election system with a new system which is more reliable and efficient in performance, more intuitive in design, less costly to maintain and abide by ITD’s architectural guidelines. Through this integrative capstone project, students’ ability of applying skills developed in previous IT courses will be thoroughly assessed at the same time challenging students’ ability of self-learning, project management, team working, problem solving, effective communication and other relative skills which will all be valuable in future workplaces.
The new election system should meet the following requirements:
Voters should be able to:
•Login and view assigned polls
•Vote for a candidate or a combination of candidates for designated polls
•Log off the system
Administrators should be able to:
•Create/view/edit/delete polls
•Assign candidates/options to polls with accompanying “user spiel” or explanation of each option
•Assign polls to eligible voters through imports of staff or student
•Close and declare winners of polls
1 ITD refers to CQUniversity’s Information and Technology Division.
Initial non-functional (system) requirements:
•Security must be appropriate
•Authentication and authorisation must be appropriate
•Framework and language must be appropriate
•User interface must be responsive and intuitive, in line with the look and feel of CQUniversity’s branding and meet the architectural guidelines of ITD
•System must be fast, efficient and reliable in terms of performance
•Database design must be normalised
•Import scripts (student/staff data) must be functional, accurate and efficient
•Code must be documented, readable and meet CQUni standards
1.2Constraints
Time and staff resource are the major constraints. Timeline of this project must be aligned with deadlines specified in the course profile of COIT23004. Staff resource assigned to this project includes two developers: Alice and Julinette. However, Julinette will not join the team until early September to help out the implementation.
Cost of this project is the labour cost of developers. Time allocated for this project is ten hours per week however this is subject to change in need of the project.
Performance (scope and quality) is preferably to be remained high standard yet can be adjusted to meet timelines.
Based on the analysis of the above constraints, a project priority matrix is presented below:
Figure 1 Project Priority Matrix2
2 Larson, EW, Honig, B, Gray, CF, Dantin, U & Baccarini, D 2014, Project management: the managerial process, 1st edn, McGraw-Hill Education, North Ryde, NSW.
As shown in figure 1, time is the constraint, cost is acceptable and therefore performance can be enhanced within the constraint of time and the flexibility of cost. Time is the first priority in this project, performance second and cost the last.
2 Hardware and Software Requirements
Hardware requirements:
•PC/Laptop with Windows 7 OS installed
•Processor Intel® i5 or equivalent
•RAM 4G or above
•HDD 100G or above
•Internet access
Software requirements:
•Sublime Text 2 Version 2.0.2
•CakePHP
•WampServer Version 2.2 (includes Apache, MySQL and PHP)
•Web browser that supports HTML5
•Tortoise SVN
•MS Office Pack
•MS Project
•MS Visio
•Adobe Reader X
•Bootstrap 2
3 Project Organisation
Client: CQUniversity
Client Representative: Lily Li
Project Owner: ITD
Project Manager: Luke Parsons
Business Analyst: Alice Hu
User Interface Designer: Alice Hu
Software Developer: Alice Hu, Julinette Carillo
Software Tester: Alice Hu
Project Evaluator: Dennis Jarvis, Lily Li
4 WBS
Below is the Work Breakdown Structure for this project:
|
|
Task
|
|
|
WBS
|
|
|
Task Name
|
|
|
Predecessors
|
|
|
|
Number
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1
|
|
1
|
|
|
New Election System
|
|
|
|
|
2
|
|
1.1
|
|
|
Phase I - Planning
|
|
|
|
|
3
|
|
1.1.1
|
|
|
Meet with project manager
|
|
|
|
|
4
|
|
1.1.2
|
|
|
Meet with client representative
|
|
|
|
|
|
|
|
1.1.3
|
|
|
Confirm system architecture, language and development
|
|
|
|
|
5
|
|
|
|
environment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6
|
|
1.1.4
|
|
|
Leadtime of gaining approval from course coordinator
|
3,4,5
|
|
|
7
|
|
1.1.5
|
|
|
Identify problems with current system
|
51
|
|
|
8
|
|
1.1.6
|
|
|
Develop project plan
|
7
|
|
|
9
|
|
1.1.7
|
|
|
Present to client
|
52
|
|
|
10
|
|
1.2
|
|
|
Phase II - Analysis
|
2
|
|
|
11
|
|
1.2.1
|
|
|
Identify functional and non-functional requirements
|
|
|
|
|
12
|
|
1.2.2
|
|
|
Construct progress report 1
|
|
|
|
|
13
|
|
1.2.3
|
|
|
Map requirements to use cases
|
11
|
|
|
14
|
|
1.2.4
|
|
|
Draw use case diagrams
|
13
|
|
|
15
|
|
1.2.5
|
|
|
Document workflows and description for each use case
|
14
|
|
|
16
|
|
1.2.6
|
|
|
Present to client
|
54
|
|
|
17
|
|
1.3
|
|
|
Phase III - Design
|
10
|
|
|
18
|
|
1.3.1
|
|
|
Software architecture design
|
|
|
|
|
19
|
|
1.3.2
|
|
|
Layer modelling
|
18
|
|
|
20
|
|
1.3.3
|
|
|
Database design
|
19
|
|
|
21
|
|
1.3.4
|
|
|
Class modelling
|
20
|
|
|
22
|
|
1.3.5
|
|
|
Behaviour modelling
|
21
|
|
|
23
|
|
1.3.6
|
|
|
User Interface Design
|
22
|
|
|
24
|
|
1.3.7
|
|
|
Document interactions between all layers
|
23
|
|
|
25
|
|
1.3.8
|
|
|
Requirements mapping
|
24
|
|
|
26
|
|
1.3.9
|
|
|
Construct progress report 2
|
25
|
|
|
27
|
|
1.3.10
|
|
Present to client
|
55
|
|
|
28
|
|
1.4
|
|
|
Phase IV - Implementation
|
17
|
|
|
29
|
|
1.4.1
|
|
|
Data access layer implementation
|
|
|
|
|
30
|
|
1.4.2
|
|
|
Construct progress report 3
|
29
|
|
|
31
|
|
1.4.3
|
|
|
Application layer implementation
|
30
|
|
|
32
|
|
1.4.4
|
|
|
User interface implementation
|
31
|
|
|
33
|
|
1.4.5
|
|
|
Document source code
|
30
|
|
|
34
|
|
1.4.6
|
|
|
Construct test plan
|
30
|
|
|
35
|
|
1.4.7
|
|
|
Construct user manual
|
30
|
|
|
36
|
|
1.4.8
|
|
|
Evaluate the mapping of design to implementation
|
30
|
|
5 Schedule
Below is the project schedule exported from MS Project:
<td class="tr1
|
|
Task Name
|
|
|
Duration
|
|
|
Start
|
|
|
Finish
|
|
|
Predecessors
|
|
|
Resource
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Names
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
New Election System
|
63.13
|
|
|
Mon
|
|
|
|
|
|
|
|
|
|
|
|
|
days
|
30/06/14
|
|
|
Thu 25/09/14
|
|
|
|
|
|
|
|
|
Phase I - Planning
|
13.63
|
|
|
Mon
|
|
|
|
|
|
|
|
|
|
|
|
|
days
|
30/06/14
|
|
|
Thu 17/07/14
|
|
|
|
|
|
|
|
|
Meet with project
|
|
|
|
|
Mon
|
|
|
|
|
|
|
|
|
|
|
|
manager
|
|
1 hr
|
30/06/14
|
|
|
Mon 30/06/14
|
|
|
|
|
Alice Hu
|
|
|
Meet with client
|
|
|
|
|
Mon
|
|
|
|
|
|
|
|
|
|
|
|
representative
|
|
1 hr
|
30/06/14
|
|
|
Mon 30/06/14
|
|
|
|
|
Alice Hu
|
|
|
Confirm system
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
architecture, language and
|
|
|
|
|
Mon
|
|
|
|
|
|
|
|
|
|
|
|
development environment
|
|
1 hr
|
30/06/14
|
|
|
Mon 30/06/14
|
|
|
|
|
Alice Hu
|
|
|
Leadtime of gaining
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
approval from course
|
|
|
|
|
Mon
|
|
|
|
3,4,5
|
|
|
|
|
|
|
coordinator
|
|
5 days
|
30/06/14
|
|
|
Mon 7/07/14
|
|
|
|
|
Alice Hu
|
|
|
Identify problems with
|
|
|
|
|
|
|
|
|
|
51
|
|
|
|
|
|
|
current system
|
|
1 hr
|
|
Mon 7/07/14
|
|
Mon 7/07/14
|
|
|
Alice Hu
|
|
|
|
|
|
|
|
|
|
|
|
Develop project plan
|
|
8 days
|
|
Mon 7/07/14
|
|
Thu 17/07/14
|
7
|
|
|
Alice Hu
|
|
|
Present to client
|
|
1 hr
|
|
Thu 17/07/14
|
|
Thu 17/07/14
|
52
|
|
|
Alice Hu
|
|
|
Phase II - Analysis
|
|
|
|
|
|
|
|
Wed
|
2
|
|
|
|
|
|
|
|
9.25 days
|
|
Thu 17/07/14
|
30/07/14
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Identify functional and
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
non-functional
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
requirements
|
|
2 days
|
|
Thu 17/07/14
|
|
Mon 21/07/14
|
|
|
|
|
Alice Hu
|
|
|
Construct progress
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
report 1
|
|
1 hr
|
|
Thu 24/07/14
|
100% Plagiarism Free & Custom Written,
Tailored to your instructions
Details
- Title: TO REPLACE THE CURRENT ELECTION SYSTEM WITH A NEW SYSTEM
- Price: £ 109
- Post Date: 2018-11-09T12:11:23+00:00
- Category: Assignment
- No Plagiarism Guarantee
- 100% Custom Written
Customer Reviews
TO REPLACE THE CURRENT ELECTION SYSTEM WITH A NEW SYSTEM
Reviews:
5
A masterpiece of assignment by
Hennah, written on
2020-03-12
I have been taking help from Insta Research since 2015 and believe me, this place is incredible in giving the best help in assignments and essays. I also ask them to run plagiarism in my essays that I have written, and they always gave me accurate results. I am literally blessed to have a strong bonding with this site so that in any need of urgency, I contact them and find them always beside me. Thank you!
Reviews:
5
A masterpiece of assignment by
Sean Zhang , written on
2020-03-12
My writer did a small error in my work but it was fixed by him shortly. The work is admirable and I have submitted it. Now hoping for the best results. I would inform you soon.
|
