Parks and Playgrounds Management System.

Full Name Student IDZHOU KAN KAN 73967SHAFIQ H SAJID 70496

MUHAMMAD GHADAFFI B HAMZAH 70244LUQMAN HAQIM B AB RAHMAN 71647

1G301 :: C2009137

Contents.

• Project Planning• Specifications• Design System• Code and Implement system

– Demonstration of the niche features• System Test• Project Conclusion • System Demonstration

G301 :: C2009137 2

Project Planning.

G301 :: C2009137 3

Project motivations.

• No specific software exist in the market• Through innovative computerization, we seek

to improve both manpower saving and efficiency in operation

4G301 :: C2009137

What Is The Project About?

• An online website that allows NParks park operators to manage the parks and playgrounds

5G301 :: C2009137

Communication Channels.

• Face to Face• Online Forum• E-mail• Skype• SMS• MSN

6G301 :: C2009137

Project Specification.

G301 :: C2009137 7

System Key Features.

• History of staff involved in specific parks• Background info & park development history• Species inventory• Maintenance regimen • Financial expenditure• Event schedules and history of past events• Profiles and particulars of volunteer groups

8G301 :: C2009137

Project Objectives.

• Enhance efficiency in managing parks• Eliminate & Reduce human error• Prevent Loss of management data• Seamless & immediate archival of park

management information• Convenient • User friendly

9G301 :: C2009137

Business Analysis.

• Enable NParks to modernize the way they manage their parks and playgrounds

• User and business friendly

10G301 :: C2009137

Business Assumptions.

• Not technical users

11G301 :: C2009137

G301 :: C2009137 12

System Analysis &

Design.

System Overview.

13G301 :: C2009137

Roles.

Role Name Position

POM Park Operations Manager

PGS Park Grounds Supervisor

FD Financial Department

PRM Park Relations Manager

14G301 :: C2009137

Access Control List.  Worker

data Manageme

nt data Park

information Maintenance

DataSpecies

Inventory Financia

l DataEvent Data

Volunteer Group

Data

POM W W W W W W W W

PGS R R R R R Nil Nil Nil FD Nil Nil Nil Nil Nil W Nil Nil

PRM Nil Nil Nil Nil Nil Nil W W

Legend: R – Read || W – Write ||Nil – Not applicable15G301 :: C2009137

Waterfall Methodology.

16G301 :: C2009137

Entity Relationship Diagram.

17G301 :: C2009137

Entity Relationship Diagram.

18G301 :: C2009137

Entity Relationship Diagram.

19G301 :: C2009137

Entity Relationship Diagram.

20G301 :: C2009137

Class Diagram.

21G301 :: C2009137

Code & Implement System.

22G301 :: C2009137

Why CakePHP?

• CakePHP is a free, open-source, rapid development framework for PHP– Code Generation– Extremely Simple– Active, Friendly Community– Flexible License– Clean IP– Best Practices– OO approach– MVC Architecture

23G301 :: C2009137

Project Tracking & Control.

• Weekly Progress meeting• Document Progress

– Meeting Minutes– Weekly log

• Peer progress updates/Checking

24G301 :: C2009137

System Test.

G301 :: C2009137 25

Testing Methods.

Unit Testing• Create Test Plans• Selenium IDE used to test

each modules• Execute the test suites• Document the results

System Testing• Reran the integrated project

with the same test plan in unit testing to ensure that they produce similar results

26G301 :: C2009137

Project Conclusion.

27G301 :: C2009137

Achievements.

• Learning a framework• Solid understanding of MVC• Able to work with different people• Able to extend the capabilities of CakePHP• Able to work under pressure

28G301 :: C2009137

Difficulties.

• Complex CakePHP ACL• Not being able to overwrite CakePHP’s

conventions accordingly• Difficulties in developing in CakePHP• Difficulties in agreeing on a MVC and coding

styles• Validation error messages does not display for

Items

29G301 :: C2009137

Improvements.

• Enabling a finer access control into the system• Include SSL into the site• Not being able to implement dynamic park list

into finances

30G301 :: C2009137

Conclusion.

• Picking up CakePHP was hard, but we get used to it with more practice

• G301 was an everlasting personal and professional experience

31G301 :: C2009137

Acknowledgement.

We would like to thank our G301 advisor for the support,

encouragement, understanding during the whole project

32G301 :: C2009137

References.• http://book.cakephp.org/view/8/What-is-CakePHP-Why-Use-it• http://www.bsu.edu/web/LGREEN/Computer2.jpg• http://www.dalzine.com.au/Images/world-wide-web.jpg• http://www.campusaccess.com/images/business-school.jpg• http://www.canadorec.on.ca/ProgramInfo/FullTime/Business/images/

businessWelcome_4.jpg• http://cakephp.org/• http://www.myplaceoryours.org.uk/wp-content/uploads/2009/01/work-in-

progress.jpg• http://www.technologic.be/UserFiles/Uploads/Images/Afb_Hoe/test.jpg• http://casualgamerchick.com/wp-content/uploads/2007/06/

achievement.jpg• http://www.artsjournal.com/dewey21c/graph_improvement.jpg

33G301 :: C2009137

Questions?

34G301 :: C2009137

?

?

Project Demonstration.

35G301 :: C2009137