Difference between revisions of "IS480 Team wiki: 2013T2 Zora Final Wiki"
Line 206: | Line 206: | ||
|} | |} | ||
− | [[IS480_Team_wiki:_2013T2_Zora_Metrics#Bug_Metric|<font color="#069" face="">'''View more details on bug metric here'''</font>]] | + | [[IS480_Team_wiki:_2013T2_Zora_Metrics#Bug_Metric|<font color="#069" face="">'''View more details on bug metric here'''</font>]] |
+ | |||
+ | ====Change Management Plan==== | ||
+ | 2 new additional changes updated in the change tracker: | ||
+ | {| cellpadding="2" style="margin: 1em auto 1em auto" "height: 100px" width="750px" | ||
+ | ! scope="col" width="50" bgcolor="#800000" |<font color="white">Iteration</font> | ||
+ | ! scope="col" width="400" bgcolor="#800000" |<font color="white">Feature Description</font> | ||
+ | ! scope="col" width="500" bgcolor="#800000" |<font color="white">Function Feasibility</font> | ||
+ | ! scope="col" width="500" bgcolor="#800000" |<font color="white">How does it value add?</font> | ||
+ | ! scope="col" width="200" bgcolor="#800000" |<font color="white">Priority level</font> | ||
+ | |||
+ | |- align="center" | ||
+ | |bgcolor="#f9b39a"|11 | ||
+ | |align="center" bgcolor="#f9b39a"| | ||
+ | Additional Features for Leave | ||
+ | * Generate Leave Report | ||
+ | |align="left" bgcolor="#f9b39a"| | ||
+ | *Include 1 additional page for HR Personnel to view all the leave applied | ||
+ | *Filtering to of the dates to be done | ||
+ | *Information include leave details, date duration, applied by whom, approved/rejected by whom, status | ||
+ | |align="left" bgcolor="#f9b39a"| | ||
+ | *HR can view the different leave of all employee at one go | ||
+ | |align="left" bgcolor="#f9b39a"|'''3''' <br/>(Instead of creating one additional page, allow HR personnel to access to feature "View Approved & Rejected Leave" | ||
+ | |||
+ | |||
+ | |- align="center" | ||
+ | |bgcolor="#f9b39a"|11 | ||
+ | |align="center" bgcolor="#f9b39a"| | ||
+ | Additional Features for Claims | ||
+ | * Claim summary report | ||
+ | |align="left" bgcolor="#f9b39a"| | ||
+ | *Include 1 additional page for HR Personnel to view the summary of all claims | ||
+ | *Filtering to of the dates, claim type, claim name to be done | ||
+ | *Information include claim date, approved by whom, validated by whom, receipt link | ||
+ | |align="left" bgcolor="#f9b39a"| | ||
+ | *HR can view all the claims in a page | ||
+ | |align="left" bgcolor="#f9b39a"|'''4''' <br/>(Rejection of change due to lack of time & high complexity) | ||
+ | |} | ||
+ | |||
+ | [[IS480_Team_wiki:_2013T2_Zora_Metrics#Change_Management|<font color="#069" face="">'''View more details on the Change Management Plan & Results'''</font>]] | ||
===Technical Complexity=== | ===Technical Complexity=== |
Revision as of 12:35, 13 April 2014
Contents
Project Progress Summary
Deliverable | Link |
---|---|
Final Presentation Slides | |
Deployed Site Link |
Completion of project |
100% (Core, Secondary, Good to Have) |
Number of Iterations |
|
Number of Heuristics |
1 |
Number of User Testing |
3 |
Deployment |
|
Changes since Mid-Term |
|
Milestones
Completed Milestones | Remaining Milestones |
---|---|
|
|
Completed Functionalities
Project Scope & Progress |
---|
View detailed completed features |
Core Modules | Secondary Modules | Good to Have Modules |
---|---|---|
|
|
|
Project Highlights
Issue Description | Consequences | Mitigation Plan |
---|---|---|
Client request for 2 additional features in leave module and claim module. | If not handled appropriately, might result in big delay in schedule and project not being able to complete by final presentation. |
|
Project Achievements:
- Able to get users to use our early live deployed copy with 41 Claims, 14 Leaves being submitted as of 13 April 2014.
- Conducted a training session on 17 April 2014
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 (Finals) |
Project Risks |
---|
View Project Risks |
Project Schedule
Final Project Timeline |
---|
Project Metrics:
Schedule Metric
Schedule Metrics |
---|
Highlights of Project Schedule
Iteration | Category | Reasons | Action Taken |
---|---|---|---|
2 | C (SM > 1.1) |
|
|
7 | C (SM > 1.1) |
|
|
View more details on schedule metric here
Bug Metric
Bug Score Tracking |
---|
View more details on bug metric here
Change Management Plan
2 new additional changes updated in the change tracker:
Iteration | Feature Description | Function Feasibility | How does it value add? | Priority level |
---|---|---|---|---|
11 |
Additional Features for Leave
|
|
|
3 (Instead of creating one additional page, allow HR personnel to access to feature "View Approved & Rejected Leave"
|
11 |
Additional Features for Claims
|
|
|
4 (Rejection of change due to lack of time & high complexity) |
View more details on the Change Management Plan & Results
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
k-nearest neighbor algorithm |
---|
We have used the k-nearest neighbor (kNN) algorithm to classify and detect fraudulent claims. Based on past claims data, we have built a training set on fraudulent claims. When a claim is submitted, our application will calculate the distance of the new claim in relation to all the claims that is already classified. Based on the nearest k - neighbours, the algorithm will classify the claim. As shown in the picture above, where k is 3, the new claim is classified as fraudulent as 2 out of the 3 neighbours is fraudulent.
We have used the following variables in calculating distance:
|
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 | |
|
||
|
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
Project 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 |
Handover | Manuals | User Manuals |
Deployment Diagram | System Architecture |
Quality:
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
Deployment:
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.
Testing
User Test 3
User Test 3 | |
---|---|
Details |
|
Objectives |
|
Scope of Test | ||
---|---|---|
Claims |
|
|
Leave |
|
|
Remuneration |
|
|
Performance Management & Appraisal |
|
|
Training & Development |
|
|
System Administration |
|
Common Feedback (Before & After) | ||
---|---|---|
Claims |
Before
|
|
Leave |
Before
|
|
Training & Development |
Before
|
Quantitative Feedback - User Test 2 versus User Test 3 | ||
---|---|---|
Ease of Use |
|
|
Overall Layout |
|
|
Analysis for the same 5 participants from user test 2 |
This is the analysis done from user test 2: Reasons for the time taken:
Reasons for changes in timing:
|
User Test 2 Analysis |
---|
Bug Log
Bug Log |
---|
Click here to view the Bug Log & Metrics file. |
Reflections
Team Reflection
Individual Reflections
Fiona Woo | Lim Ken Khoon | Tan Yun Xi |
|
|
|
Lee Yi Xian | Tan Mei Zhen | Darryl Leong |
|
|
Sponsor Comment:
-Watch this space-