Difference between revisions of "IS480 Team wiki: 2013T2 Zora MidTerm Wiki"
Jump to navigation
Jump to search
(19 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
==Project Progress Summary== | ==Project Progress Summary== | ||
− | + | {| cellpadding="2" style="margin: 1em auto 1em auto" "height: 100px" width="600px" | |
+ | ! scope="col" width="200" bgcolor="#280063"|<font color="white">Deliverable</font> | ||
+ | ! scope="col" width="250" bgcolor="#280063"|<font color="white">Versions</font> | ||
+ | |- align="left" | ||
+ | |bgcolor="#8275aa"|Mid Term Presentation Slides | ||
+ | |bgcolor="#dbdbdb"| | ||
+ | *[[Media:Zora_Mid-Term_Presentation.pdf |v1: 26 Feb 2013]] | ||
+ | |} | ||
{| cellpadding="2" style="margin: 1em auto 1em auto" "height: 100px" width="750px" | {| cellpadding="2" style="margin: 1em auto 1em auto" "height: 100px" width="750px" | ||
! scope="col" width="500" bgcolor="#1c90bf"|<font color="white">Current Phase</font> | ! scope="col" width="500" bgcolor="#1c90bf"|<font color="white">Current Phase</font> | ||
Line 105: | Line 112: | ||
|- align="left" | |- align="left" | ||
! scope="col" bgcolor="#ffffff"| [[IS480_Team_wiki:_2013T2_Zora_Scope|<font color="#069" face="">'''View Full Project Scope Details'''</font>]] | ! scope="col" bgcolor="#ffffff"| [[IS480_Team_wiki:_2013T2_Zora_Scope|<font color="#069" face="">'''View Full Project Scope Details'''</font>]] | ||
+ | |} | ||
+ | |||
+ | {| align="center" cellpadding="2" style= width="750px" | ||
+ | |- align="left" | ||
+ | ! scope="col" bgcolor="#4D4D4D"| <font color="white">Planned VS Actual Schedule</font> | ||
+ | |- align="left" | ||
+ | ! scope="col" bgcolor="#ffffff"| [[IS480_Team_wiki:_2013T2_Zora_Project_Schedule#Planned_VS_Actual_.28Acceptance.29|<font color="#069" face="">'''View Planned VS Actual Schedule Details'''</font>]] | ||
|} | |} | ||
Line 355: | Line 369: | ||
*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. | *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=== | ===Technical Complexity=== | ||
{| cellpadding="0" style="margin: 1em auto 1em auto;" "height: 317px" width="750px" | {| cellpadding="0" style="margin: 1em auto 1em auto;" "height: 317px" width="750px" | ||
− | |||
− | |||
|- align="left" | |- align="left" | ||
|bgcolor="#cedad1"|Application | |bgcolor="#cedad1"|Application | ||
Line 367: | Line 377: | ||
*PHP 5.2.17 | *PHP 5.2.17 | ||
*Apache | *Apache | ||
− | + | *TCPDF | |
+ | *PHPass | ||
| | | | ||
|- align="left" | |- align="left" | ||
Line 376: | Line 387: | ||
*Javascript | *Javascript | ||
*Jquery Library | *Jquery Library | ||
− | *Jquery Validation | + | *Jquery Validation Plugin |
| | | | ||
|- align="left" | |- align="left" | ||
Line 384: | Line 395: | ||
*phpMyAdmin | *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 | ||
+ | <br/> | ||
+ | ===Change Management Plan=== | ||
+ | [[IS480_Team_wiki:_2013T2_Zora_Metrics#Change_Management|<font color="#069" face="">'''View Change Management Plan & Results'''</font>]] | ||
+ | |||
+ | ==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 | ||
+ | |||
+ | {| cellpadding="0" style="margin: 1em auto 1em auto;" "height: 317px" width="750px" | ||
+ | |- align="left" | ||
+ | |bgcolor="#a7b1aa"|<font color="white">Nielsen's Heuristics </font> | ||
+ | |bgcolor="#a7b1aa"|<font color="white">Screenshot</font> | ||
+ | | | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"| | ||
+ | *Error prevention | ||
+ | *Help users recognize, diagnose, and recover from errors | ||
+ | |bgcolor="#cedad1"| | ||
+ | [[Image:Zora midterm errorprevention.jpg|300px|center]] | ||
+ | | | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"| | ||
+ | *User control and freedom | ||
+ | |bgcolor="#cedad1"| | ||
+ | [[Image:Zora midterm redo.jpg|150px|center]] | ||
+ | |} | ||
+ | |||
+ | |||
+ | ===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=== | ===Intermediate Deliverables=== | ||
Line 596: | Line 656: | ||
! scope="col" bgcolor="#ffffff"| [[Image:zora_bug_log_all_iterations.png|550px|center]] | ! scope="col" bgcolor="#ffffff"| [[Image:zora_bug_log_all_iterations.png|550px|center]] | ||
|- align="left" | |- align="left" | ||
− | ! scope="col" bgcolor="#ffffff"| [[Media: | + | ! scope="col" bgcolor="#ffffff"| [[Media:ZORA BUG LOG METRIC SECOND.xlsx|Click here to view the Bug Log & Metrics file.]] |
|} | |} | ||
Latest revision as of 11:39, 13 April 2014
Project Progress Summary
Deliverable | Versions |
---|---|
Mid Term Presentation Slides |
Current Phase | Current Iteration |
---|---|
|
|
Iterations Remaining (Excluding Current Iteration) | Phases Remaining (Excluding Current Phase) |
---|---|
3 |
1
|
Milestones
Completed Milestones | Remaining Milestones |
---|---|
|
|
Completed Functionalities
Project Scope & Progress |
---|
View detailed progress of completed features |
Core Features | Secondary Features |
---|---|
|
|
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. |
|
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 |
|
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) |
|
0% Complete (To be completed by Iteration 10) | 0.7 | Darryl |
Other Features |
|
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 |
---|
Project Metrics
Schedule Metrics
Schedule Metrics |
---|
Highlights of Project Schedule
Iteration | Category | Reasons | Action Taken |
---|---|---|---|
2 | C (SM > 1.1) |
|
|
3-6 | B (0.9 <= SM <= 1.1) |
|
|
7 | C (SM > 1.1) |
|
|
Bug Metrics
Bugs Per Iteration |
---|
Bug Score Tracking |
---|
Project Risks
Past Activated Risks
Risk Statement | Consequence | Likelihood | Impact | Level | Mitigation Strategy &/or Contingency Plan |
---|---|---|---|---|---|
(High/Medium/Low) | (Derived) | ||||
Project Management | |||||
|
|
Medium | Medium | B |
|
|
|
High |
Medium |
A |
|
Future Anticipated Risks
Risk Statement | Consequence | Likelihood | Impact | Level | Mitigation Strategy &/or Contingency Plan |
---|---|---|---|---|---|
(High/Medium/Low) | (Derived) | ||||
Testing | |||||
|
Inaccurate feedback as it may not be what the real users experience |
High |
Medium |
A |
|
Technical Complexity
Application |
|
|
Browser |
|
|
Database |
|
- 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 | |
|
||
|
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 | |
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 |
Deployment
Live Deployment 1 | Deployed Modules | Details |
---|---|---|
19 February 2014 | Leave, Claims, System Administration (Limited) | Live Deployment |
Testing
Pilot Testing
Pilot Testing | |
---|---|
Details |
|
Objectives |
|
User Test 2
User Test 2 | |
---|---|
Details |
|
Objectives |
|
Scope of Test | ||
---|---|---|
Claims |
|
|
Remuneration |
|
|
Leave |
|
|
Performance Management & Appraisal |
|
|
System Administration |
|
Common Feedback | |||
---|---|---|---|
Claims | |||
Leave | |||
Remuneration | |||
Performance Management & Appraisal |
Quantitative Feedback | ||
---|---|---|
Ease of Use | ||
Overall Layout |
User Test 2 Analysis |
---|
Bug Log
Bug Log |
---|
Click here to view the Bug Log & Metrics file. |
Bug Mitigation Plan |
---|
Reflections
Team Reflection
At this juncture, as a team, we have learnt that changes inevitable. We have learnt how to manage changes. |
Individual Reflections
Fiona Woo | Lim Ken Khoon | Tan Yun Xi |
|
|
|
Lee Yi Xian | Tan Mei Zhen | Darryl Leong |
|
|
|