Difference between revisions of "IS480 Team wiki: 2011T1 The PIEs"
(6 intermediate revisions by 2 users not shown) | |||
Line 515: | Line 515: | ||
===Ongoing Functions=== | ===Ongoing Functions=== | ||
Our team is currently preparing for Final Presentation on 24 Nov 2011, 10am. | Our team is currently preparing for Final Presentation on 24 Nov 2011, 10am. | ||
+ | |||
+ | |||
==<font size=6 color="#FBB117">User Acceptance Test</font>== | ==<font size=6 color="#FBB117">User Acceptance Test</font>== | ||
Line 642: | Line 644: | ||
Visit http://portal.pipl.com.sg/ today! | Visit http://portal.pipl.com.sg/ today! | ||
+ | |||
+ | |||
==<font size=6 color="#FBB117">Technology</font>== | ==<font size=6 color="#FBB117">Technology</font>== | ||
Line 679: | Line 683: | ||
===Individual Reflection=== | ===Individual Reflection=== | ||
− | [[Image:PIE.jpg|| | + | [[Image:PIE.jpg||600px||center]] |
[[Jayner's Reflection]] | [[Jayner's Reflection]] | ||
Line 692: | Line 696: | ||
[[Joanna's Reflection]] | [[Joanna's Reflection]] | ||
− | |||
− | |||
==<font size=6 color="#FBB117">Minutes</font>== | ==<font size=6 color="#FBB117">Minutes</font>== | ||
Line 706: | Line 708: | ||
Mid-Term Presentation Slides: [[Media:PIE_mid-term.pdf]] | Mid-Term Presentation Slides: [[Media:PIE_mid-term.pdf]] | ||
+ | |||
+ | |||
+ | ==<font size=6 color="#FBB117">Final Presentation </font>== | ||
+ | |||
+ | [[Image:Finalpresentation.JPG||600px||center]] | ||
+ | |||
+ | [http://youtu.be/7EV74PbuN84 Final Presentation Video - Our Journey] |
Latest revision as of 02:08, 27 November 2011
Contents
Welcome to The PIEs
The PIEs Team Members
Roles & Responsibilities
Stakeholders
Supervisor
- Professor Zheng Bai Hua
Client
Positive Intentions Pte Ltd, our client is an events social enterprise that specializes in life-coaching, people development, corporate and community training and consultancy services. Through this project, we hope to help the company to integrate their HRM and CRM portal to achieve a fuss free business dealings with client.
Sponsor
- Ethen Ong, Operations Manager & Trainer
Our client is Ethen Ong, who is the Owner, Co-Founder and a trainer, at Positive Intentions Pte Ltd. Due to the growing needs of their company, our client see the need to initiate a project which requires our team to develop an online human resource management to better manage volunteers, facilitators, staffs and trainers for their training events, workshops, talks and camps. As the number of projects accepted surged over the past few years, our client also see the need to have an project management portal to manage their projects with their projects' client more effectively and efficiently. As our main stakeholder and client, our team strive to develop human resource management portal and project management portal with our client's requirements.
Project Overview & Diagrams
Project Overview provides the Project Description and Scope for our project. In addition, diagrams with different version will also be available in this section.
Project Description and Scope
Click to visit Project Description and Scope page
Use Case Diagram
Click to view Version 1 of our Use Case Diagram
Click to view Version 2 of our Use Case Diagram.v2
Click to view Version 3 of our Use Case Diagram.v3
Sequence Diagram
Please download the compiled version of our Sequence Diagram Media:PIE_SEQUENCE_DIAGRAM.pdf
Entity Relationship Diagram
Click to view Version 1 of our Entity Relationship Diagram
Click to view Version 2 of our Entity Relationship Diagram.v2
Click to view Version 3 of our Entity Relationship Diagram.v3
Click to view Version 4 of our Entity Relationship Diagram.v4
Logical Diagram
Click to view Version 1 of our Logical Diagram
Click to view Version 2 of our Logical Diagram.v2
Click to view Version 3 of our Logical Diagram.v3
StoryBoard
Storyboards are used to illustrate how our portal will look like with all the functions put in placed. This is especially important when having meetings with client. It is hard for client to visualize how the portal will look like by just describing the functions available. With the storyboard as a visual aid, client could clearly point out the areas we should improve on.
Example:
Click to visit our StoryBoard page where different versions of StoryBoard are available due to changes in client's requirements.
Project Management
Project Schedule Overview
Our team has identified 5 milestones and 9 iterations for our portals development in this project. After each iteration, our team will conduct a review on our schedule to see if we are on schedule.
Within each phase of iteration, we will have a consistent form of :
- Reviewing our project Schedule
- Development and integration of functionalities
- Testing and debugging of portals on localhost
- Releasing functions to client/sponsor for feedback
- Reviewing and evaluating our functions according to client/sponsor's feedback
Project Timeline and Schedule
Click to visit Project Timeline & Schedule page
Team Work Assignment
Milestone | Task(s) | Member(s) Allocated |
---|---|---|
1 | Diagram Presentation |
All All
|
2 | Documentation & Diagram Schedule |
Jayner, Wan Jun, Sook Xian Jayner |
3 | Diagram Schedule |
Wan Jun, Sook Xian Jayner |
4 | Documentation & Diagram Schedule |
Wan Jun, Sook Xian Jayner |
5 | Documentation & Diagram Schedule |
Wan Jun, Sook Xian Jayner |
Schedule Metric
Goal:
To ensure that schedule index (days delayed/total estimated time) is kept <= 0.5
Calculation:
Delayed Days = Actual days taken to complete task - Estimated days to complete task
Schedule Index = Delayed Days/ Estimated Days to complete task
Schedule Index | Description | Action |
---|---|---|
Schedule Index < 0 | Early | •PM checks if he/she over-estimated the duration of tasks
•The PM will adjust the schedule to ensure that each task is given a rightful amount of time accordingly •PM allocates new task to the people to keep the pace. |
Schedule Index = 0 | Punctual | •There is no need for change in the current schedule
•Continue with the next task on the schedule |
0 < Schedule Index<=1 | Slightly Late | • PM checks if team members/pair programmers are having any difficulty with task and review the workload of tasks.
• If there are any difficulties, PM checks with developers the amount of time needed to complete the task • If PM under-estimated time given for the task, adjust the schedule according to developers’ estimate of time they will need to complete tasks assigned to them • PM will then re-schedule the project schedule |
Schedule Index> 1 | Very Late | • PM checks with developers reasons why the task is not completed on time
• If developers are really having difficulty, PM checks with developers the amount of time needed to complete the task • If current task is not an essential task, PM may consider redefining scope by dropping the task • If current task is an essential task, PM organize urgent meeting discuss the issue and provide help • PM re-schedule project & redefine scope if needed |
Click to view Schedule Log Media:PIE_Schedule_Log.xlsx
Bug Metrics
Goal:
To ensure that our bug's total points is kept <= 0.5
Calculation:
Total Points = (1 x num of Lows) + (5 x num of Highs) + (10 x num of Criticals)
SEVERITY
Severity | Description |
---|---|
Low Impact (1 point) | - Unimportant.
- Typo error or small user interface alignment issues. |
High Impact (5 point) | - The system runs. However, some non-critical functionality is not working.
- Error due to programming logic. |
Critical Impact (10 point) | - The system is down or not usable.
- Error due to design logic. |
POINTS
Points in iteration | Action |
---|---|
Points <=5 | - Fix during meeting or buffer time. |
5 < points < 10 | - QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. |
5 < points < 10 | - PM hold an emergency meeting to fix the bug together.
- PM might need to reschedule project and review time allocated in the project for future tasks. |
Bug Log
Bug Id | Iteration | Date | Description | Function(s) | Severity | Point | Actions | Kill |
---|---|---|---|---|---|---|---|---|
1 | 1 | 10/7/2011 | NRIC is not validated | Registration | Low Impact | 4 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
2 | 1 | 10/7/2011 | DOB is not validated | Registration | Low Impact | 4 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
3 | 3 | 25/8/2011 | Date and Time Retrieval Error | Edit Event | High Impact | 6 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
4 | 4 | 30/8/2011 | Page Redirection Error | Edit Profile | High Impact | 6 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
5 | 5 | 9/9/2011 | View Schedule is not functioning | View Program | Critical Impact | 10 | PM hold an emergency meeting to fix the bug together | √ |
6 | UAT | 15/9/2011 | Failure to display user's display picture | View All VFT By Events | Low Impact | 2 | Fix during meeting or buffer time. | √ |
7 | UAT | 15/9/2011 | Calendar Alignment Issue | View Calendar | Low Impact | 1 | Fix during meeting or buffer time. | √ |
8 | UAT | 15/9/2011 | Navigation bar has alignment issue | Edit Event | Low Impact | 2 | Fix during meeting or buffer time. | √ |
9 | UAT | 15/9/2011 | No display of images and play slideshow buttons | Photo Gallery | High Impact | 7 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
10 | 6 | 5/10/2011 | Empty title and message fields not validated | Forum - Reply Personal Message | Low Impact | 2 | Fix during meeting or buffer time. | √ |
11 | 6 | 5/10/2011 | Empty name and description fields not validated | Forum - Create Category | Low Impact | 3 | Fix during meeting or buffer time. | √ |
12 | 6 | 5/10/2011 | Empty title and message fields not validated | Forum - Create Topic | Low Impact | 2 | Fix during meeting or buffer time. | √ |
13 | 6 | 5/10/2011 | Count of new personal Message not updated | Forum - Personal Message | High Impact | 9 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
14 | 9 | 26/10/2011 | Misalignment and Layout Issue | IE Browsers Compatibility | High Impact | 7 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
15 | Final UAT | 10/11/2011 | Validation for Contact Number Field | View Future Partnership | High Impact | 7 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
16 | Final UAT | 15/11/2011 | Unable to view posted testimonial | View Partnership | High Impact | 7 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
17 | Final UAT | 15/11/2011 | View details of Past participated record | View Past Participated | High Impact | 5 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
18 | Final UAT | 15/11/2011 | View details of Past participated record | View Past Participated | High Impact | 5 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
19 | Final UAT | 15/11/2011 | Join project has got errors | All Projects | High Impact | 9 | QA informs respective pair and resolve the error during buffer time of iteration or within 24 hours. | √ |
Risk and Mitigation
Project Updates
Weekly Updates
Weekly Updates section display decisions and changes made or record on what the team did for the week. For more details, please refer to our minutes.
Click to visit Weekly Updates page
Ongoing Functions
Our team is currently preparing for Final Presentation on 24 Nov 2011, 10am.
User Acceptance Test
Goals for UAT
- To get a group of end users who will/may be using the portal to test the system to ensure that requirements are met
- To nail bugs related to the usability of the portal
- To gather feedback and suggestions on how to improve the portal
Mid Term UAT | Final UAT |
---|---|
- 10- 20 Testers
(10 from PI and 10 from public) |
- 30-40 Testers
(15 from PI and 25 from public) |
Functions to be tested for Mid Sem: 1. Login. Registration |
Functions to be tested for Final: 1. All functions |
Actions to be taken after each UAT
- Review the test cases suggested by users and do debugging accordingly using the following template:
UAT 1 (13 Sep- 14 Sep)
For more details, please visit our UAT 1 page.
UAT 2 (20 Sep- 21 Sep)
For more details, please visit our UAT 2 page.
UAT 3 (8 Nov- 9 Nov)
For more details, please visit our UAT 3 page.
Test Plans
After each iterations, testing will be done using test plan prepared at the start of the iterations to to verify and ensure that our system meets its requirements.
Click to view our test plans. Media:PIEs_TestPlan.pdf
PI Portal
After 5 months of work and effort... We present some of the functions available in PI Portal.
Email Notifications
Volunteer's Homepage
Join Event
Add Event - Sales
Create Program Schedule - Operations personnel
Community Sharing - Forum
Please download Media: PIE_FBRegistration&Login.pdf for full view of Facebook Registration & Login.
Please download Media: PIE_HelpersFunctions.pdf for full Helpers functions
Please download Media: PIE_AdminFunctions.pdf for full Administrator functions
Please download Media: PIE_SalesFunctions.pdf for full Sales Personnel functions
Please download Media: PIE_OperationsFunctions.pdf for full Operations Personnel functions
Please download Media: PIE_ClientFunctions.pdf for full Operations Personnel functions
Current Operations VS New Operations
Visit http://portal.pipl.com.sg/ today!
Technology
Technical Diagram
Basic Development Technology
Microsoft SQL Server
NetBeans IDE 7.0
XAMPP
Apache Tomcat 7.0.11
Filezilla FTP
Programming language
PHP
Jquery
Java Script
Ajax
Learning Outcome(s)
Team Learning Outcome
Individual Reflection
Minutes
Media:PIE_Compiled Minutes.pdf
Media Files
Acceptance Presentation Slides : Media:Project_Acceptance_v4.pdf
Mid-Term Presentation Slides: Media:PIE_mid-term.pdf