IS480 Team wiki: 2013T2 Zora MidTerm Wiki

From IS480
Jump to navigation Jump to search

Project Progress Summary

Deliverable Versions
Mid Term Presentation Slides
Current Phase Current Iteration
  • Development: Mid-Term Presentation & 100% Completion of Secondary Features
  • Starts 17 Feb 2014
  • Ends 16 Mar 2014
  • Iteration 9
  • Starts 17 Feb 2014
  • Ends 2 Mar 2014
  1. Preparation of Live deployment
  2. Live deployment
  3. Preparation of Mid-Term Presentation
  4. Mid-Term Presentation
  5. Claim Analysis Report
Iterations Remaining (Excluding Current Iteration) Phases Remaining (Excluding Current Phase)



  • User Test 3 & Final Presentation


Completed Milestones Remaining Milestones
  • Heuristics 1 (18 Sep 2013)
  • User Test 1 (18 Oct 2013)
  • Proposal Submission (28 Oct 2013)
  • Acceptance Presentation (8 Nov 2013)
  • User Test 2 (3 Feb 2014)
  • Live Deployment 1 – Leave, Claim, Administration (19 Feb 2014)
  • User Test 3
  • Live Deployment 2 – Remuneration, Performance Management & Appraisal, Training & Development
  • Poster Submission
  • Final Presentation

Completed Functionalities

Project Scope & Progress
View detailed progress of completed features
Core Features Secondary Features
  • Basic Remuneration (Payment slip, report generation, timesheet)
  • Claims (Submission & approval of claims)
  • Leave( Submission & approval of leave)
  • Basic System Administration (Manager user profile & configuration of user controls)
  • ACL
  • Training & Development (Propose training course, add employee course feedback)
  • Performance Management & Appraisal (Manage & approval of employee appraisal)

Project Highlights

Issue Description Consequences Mitigation Plan
Interactive graphical analytics for claims report has steep learning curve. Use up of precious manpower resource that can be adequately used to be allocated to other tasks that brings about higher value to the sponsor.
  • Drop of previous X-Factor of claim analysis interactive graph to free up manpower resources
  • Change of X-Factor to 3 other x-factors
Intensive testing after pilot user test on 25 Jan 2014 as we discovered that the user environment and configurations are different from how we usually test our applications. Hence, more testing is done before the actual user test. Delay of iteration 7 by 4 days
  • Drop of previous X-Factor of claim analysis interactive graph to free up manpower resources
  • Reschedule of plans to include more testing to be done before user testing and live deployment

Project Management

Project Schedule
View Full Project Schedule Details
Project Scope & Progress
View Full Project Scope Details
Planned VS Actual Schedule
View Planned VS Actual Schedule Details

Project Status

Project Scope & Progress
View Full Project Scope Details
Core Features
Module Features Status Confidence Level (0 to 1) In-charge / Comment
Basic Remuneration All features Fully deployed and tested 100% 1 Yun Xi
Claim All features Fully deployed and tested 100% 1 Yi Xian & Mei Zhen
Leave All features Fully deployed and tested 100% 1 Fiona
System Administration (Basic) All features Fully deployed and tested 100% 1 Yi Xian
Other features: ACL All features Fully deployed and tested 100% 1 Ken Khoon
Secondary Features
Module Features Status Confidence Level (0 to 1) In-charge / Comment
Performance Management & Appraisal All features Fully deployed and tested 100% 1 Darryl
Training & Development 6 out of 13 features completed 50% Complete (To be completed by Iteration 10) 1 Yi Xian & Darryl
Claim Claim Analysis Report 40% Complete (To be completed by Iteration 10) 0.8 Ken Khoon will be researching on how to approach this feature
Advanced Remuneration All 4 features incomplete 0% Complete (To be completed by Iteration 10) 1 Yun Xi
Good To Have Features
Module Features Status Confidence Level (0 to 1) In-charge / Comment
System Administration (Advanced)
  • Audit Log
  • Manage Performance Management
0% Complete (To be completed by Iteration 10) 0.7 Darryl
Other Features
  • Portal Notification
0% Complete (To be completed by Iteration 10) 0.5 Module is suggested while we are taking IDP. It may not be as a much value-added feature compared to the rest of the features.

Project Schedule

Planned Project Timeline
Expanded project schedule overview.png

Project Metrics

Schedule Metrics

Schedule Metrics
Zora sm score.png

Highlights of Project Schedule

Iteration Category Reasons Action Taken
2 C (SM > 1.1)
  • Apply Leave: It is more complex that it initially was anticipated. Leave consist of annual, maternity, unpaid and others. All of which requires different business rules. We took longer than we expected for this section.
  • Upload file for Leave & Claim: It is of a high difficulty level for the team due to the lack of knowledge and time to research.
  • PM shifted incomplete tasks to other iteration.
  • All other tasks are being reviewed to ensure that they are broken down to the simplest task possible.
3-6 B (0.9 <= SM <= 1.1)
  • The iteration score is greatly reduced as the tasks are planned with a more realistic approach. (e.g. in the past, tasks are given very limited number of days to complete – at most 9 days, currently tasks are given about 13 days to be completed) . This will in turn maximize the entire 14 days of iteration period.
  • Continue with this approach of planning the subsequent iterations’ coding tasks.
7 C (SM > 1.1)
  • User Test: Time is taken up to do intensive test on the deployed application using the user test task instructions.
  • Other commitments: Team members have other submissions and presentation with other modules during iteration 7. As such, some tasks are delayed.
  • Drop of previous X-Factor of claim analysis interactive graph to free up manpower resources
  • Allocate time to do intensive user test using task instructions in the user’s environment before the next user testing
  • PM to find out commitments in other modules other than FYP for later iterations and reschedule tasks accordingly/re-allocate tasks

Bug Metrics

Bugs Per Iteration
Zora no of bugs in each iteration.png
Bug Score Tracking
Zora total bug score value in each iteration.png

Project Risks

Past Activated Risks

Risk Statement Consequence Likelihood Impact Level Mitigation Strategy &/or Contingency Plan
(High/Medium/Low) (Derived)
Project Management
  • Major Changes in Client Requirement.
  • Initial tasks may not be completed on time.
  • Project Schedule is Delayed.
  • Additional work and effort required.
Medium Medium B
  • PM to re-plan coding tasks to add in additional requirements. In cases where new/edited tasks are unable to fit into schedule, team to re-negotiate project scope with sponsor.
  • Further changes to be documented by business analyst.
  • For new development modules, there will be a steep learning curve as team may be unsure of how to start on the module.
  • This may result in project being delayed as team members have not fully understand the modules.




  • PM to allocate additional time when a new module is being started in iteration to allow for team members to better understand the module first.

Future Anticipated Risks

Risk Statement Consequence Likelihood Impact Level Mitigation Strategy &/or Contingency Plan
(High/Medium/Low) (Derived)
  • Insufficient & inappropriate users to test our application

Inaccurate feedback as it may not be what the real users experience




  • PM to allocate additional time when a new module is being started in iteration to allow for team members to better understand the module first.
  • Team to notify participants earlier on pilot test days and send a reminder to ensure that participants turn up on the actual day of testing.
  • Team to get participants who have the same characterics as the real users (e.g. non-tech savvy). If possible, team to get real users to test out application.

Technical Complexity

  • Codeigniter Framework
  • PHP 5.2.17
  • Apache
  • PHPass
  • HTML
  • CSS
  • Javascript
  • Jquery Library
  • Jquery Validation Plugin
  • MySQL 5.1.66
  • phpMyAdmin
  • One challenge faced is the integration of various libraries into our application. We would need to figure out how to utilise the various libraries. While there are documentation for the libraries, they are sometimes not adequate when we are debugging our application
  • The 2 libraries we have used so far is TCPDF and PHPass
    • TCPDF is used to generate PDF documents such as claim slips, pay slips etc.
    • PHPass is used for password hashing and encryption

Change Management Plan

View Change Management Plan & Results

Quality of product

Design Considerations

  • We have chosen to use Twitter Bootstrap for our User Interface (UI) as users a familiar with the layout of the design.
  • Our team can move away from reinventing the wheel and focus on providing our users a more intuitive interface instead.
  • In the design of our UI, we use the Nielsen's 10 heuristics as our guideline
Nielsen's Heuristics Screenshot
  • Error prevention
  • Help users recognize, diagnose, and recover from errors
Zora midterm errorprevention.jpg
  • User control and freedom
Zora midterm redo.jpg

Design pattern

  • We have chosen to use the Singleton design pattern where an class is only instantiate once for the application
  • Whenever an class is loaded, an check would be done to see if the class has been previously instantiated
  • If the class is already instantiated, the instantiated class would be used instead
  • This allow the system to operate more efficiently as only one object exists

Security considerations

  • Password salting and hashing
    • Using PHpass library, each password is assigned a unique salt and hash
  • Cross Site Scripting Validation
    • Validation is done at input to prevent cross site scripting
  • Dynamic Access Control

Intermediate Deliverables

Stage Specification Links
Project Management Meeting Minutes Meeting Minutes
Metrics Metrics
Requirement Gathering Business Requirements

Business Requirements

Analysis Use Case Business Requirements
System Sequence Diagram System Architecture
Business Process Diagram Business Requirements
UI Protoypes UI Prototypes
Design ER Diagram System Architecture
Class Diagram System Architecture
Testing Test Plans Testing


Live Deployment 1 Deployed Modules Details
19 February 2014 Leave, Claims, System Administration (Limited) Live Deployment


Pilot Testing

Pilot Testing
Zora pt 1.jpg
Zora pt 2.jpg


  • 25 Jan 2014, Saturday
  • 10am – 1pm
  • Sterling Engineering Pte Ltd (Client’s Office)
  • No of Participant: 1
  • Participant Profile: Constructor (Administrator)


  • Participant to trial test the entire system and feedback to us on how he think of the entire user test experience, whether a not our instructions are clear to understand and whether we are doing a lot of unnecessary things which could be minimized.
  • Use advice and feedback and improve user test 2where needed before we conduct the actual test with more than 1 participant.

User Test 2

User Test 2
Zora ut2 1.jpg
Zora ut2 2.jpg


  • 03 Feb 2014, Monday
  • 10am – 2pm
  • Sterling Engineering Pte Ltd (Client’s Office)
  • No of Participant: 4
  • Participant Profile: HR Personnel, Contract Manager (Higher Management), Technical Coordinator (Line Manager), Quality Surveyor


  • Determine usability of application.
  • Obtain both qualitative and quantitative feedback from system users.
Scope of Test
  • Submit New Claim
  • Validate Submitted Claim
  • Edit Payment Method
  • Approve/Reject Submitted Claim
  • View Personal Claim Status
  • View Past Payment Record for Employees
  • View Past Payment Record for Workers
  • View Past Payment Record for Drivers
  • Generate All Payment Records for Employees
  • Generate All Payment Records for Workers
  • Generate All Payment Records for Drivers
  • View Personal Payment Record
  • Input Timesheet for Workers
  • Input Timesheet for Drivers
  • Apply Annual Leave
  • Edit Leave
  • Apply Other Leave
  • Approve/Reject Leave
  • View Status of Leave & Cancel Leave
  • View Leave History
  • Record Medical Leave
Performance Management & Appraisal
  • Create Employee Appraisal
  • Approve/Revise Salary Increment Request
  • Distribute Bonus
  • View Scheduled Increment/Bonus
  • View Increment History
System Administration
  • Create New Profile
  • Update Profile
  • Manage Default Number of Leave
Common Feedback
Performance Management & Appraisal
Quantitative Feedback
Ease of Use
Overall Layout
User Test 2 Analysis

View Full Analysis.

Bug Log

Bug Log
Zora bug log all iterations.png
Click here to view the Bug Log & Metrics file.
Bug Mitigation Plan
Zora bug mitigation plan.png


Team Reflection

Zora team photo.jpg

At this juncture, as a team, we have learnt that changes inevitable. We have learnt how to manage changes.

Individual Reflections

Zora learning fiona.jpg
Zora learning kk.jpg
Zora learning yunxi.jpg
Fiona Woo Lim Ken Khoon Tan Yun Xi
  • Learnt the importance of proper project management as it can affect the progress of the project. The metrics are not just merely numbers but rather important values that can bring about actions to improve the progress of the project.
  • I also learnt the importance of being flexible. Whatever that is planned may not be appropriate when we execute it. Instead, we should always be open to changes.
  • As a project manager, I learnt that it is important to understand the morale of the team and other commitments during this entire project. Instead of blindly assigning work, I have to ensure that each member has fair share of work and he/she is not overloaded.
  • Learnt the importance of communicating with team members on the usage of technology tools as all team member have to utilize it in order to leverage the full potential of the tool.
  • When facing obstacles, we should confide in other team members as the can be a source of inspiration for overcoming them. Two heads are better than one, six heads are better than two!
  • During the development phase, there can be unavoidable change of requirements that will result in the expansion of the project. I learned to balance more effectively between meeting the client's need and at the same time, meeting the project deadlines.
  • I learned that teamwork is important, and there is a constant need to motivate one another during this (long and arduous) FYP journey, especially during hectic school semester.
Zora learning yixian.jpg
Zora learning meizhen.jpg
Zora learning darryl.jpg
Lee Yi Xian Tan Mei Zhen Darryl Leong
  • Learnt the importance of knowing how much time each and every members can commit to the project during each period/phase.
  • Learnt the importance of having a prototype as client/user will be able to provide more feedback on the system.
  • Learnt the importance of communicating with project group members to refine understanding through discussion as well as to feedback on each member's performance to better manage milestones of the project.
  • Learnt that testing is not just about finding bugs and evaluating functionalities. It is also about conducting user test and following up with the execution of user test to collate feedbacks gathered and improve the user's experience on the application.
  • Learnt the importance striking a balance between completing project tasks and other constrains (e.g. time available)
  • Learnt the importance of regular communication with the client to ensure our project is aligned with business requirements
  • Learnt the importance of staying focused and to see the big picture - the completion of the project.