Difference between revisions of "IS480 Team wiki: 2013T2 Carpe Diem Final Wiki"
Line 200: | Line 200: | ||
===Testing:=== | ===Testing:=== | ||
− | + | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2013T2_Carpe_Diem_Testing] Functional Testing | |
− | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2013T2_Carpe_Diem_Testing | ||
− | |||
− | |||
<br><br> | <br><br> | ||
User Test:<br> | User Test:<br> |
Revision as of 14:53, 6 April 2014
Project Progress Summary
<Final Presentation Slides Link>
Links to Deployed Application
Application Name | Link to Deployed Application |
---|---|
Customer Booking Application | Customer App |
Sub-Contractor Application | Sub-Contractor App |
Administrator Portal | http://kohbusapp.appspot.com/ |
The following are test accounts for each application:
Account Type | Username | Password |
---|---|---|
Administrator | 91234567 | password |
For the Customer and Sub-Contractor application, accounts have to be created on devices as every account is tagged to a device ID, which renders it invalid if created independently without a specific device.
The following are some suggestions for Customer and Sub-Contractor Accounts (which requires registration):
Account Type | Username | Password |
---|---|---|
Customer | 98765432 | password |
Sub-Contractor | 98989898 | password |
The project started on the 06 September 2013 and by Iteration #7 (Last Iteration), Carpe Diem has completed the following key accomplishments:
- Completed UT 1 on the Customers (Student Users)
- Completed UT 2 on the Administrators
- Completed UT 3 on the Sub-Contractors
- Completed UT 4 on the Administrators and Customers
- Completed UT 5 on the performance of the integrated application
- Project successfully gone live on 24 March 2014
- Efficiently managed the 3 platforms (Customer, Administrator and Sub-Contractor)
Project Highlights:
Project Overview:
We have completed all the modules, as shown in our project completion diagram below. Besides completion of functionalities, we will be exploring on how we can improve the applications based on feedback from our user testings and stakeholders.
<Create a diagram to show module completion here>
Project Scope:
Functionality Changes:
Project Challenges:
Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.
Project Achievements:
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.
Project Management
We have completed all the Core, Secondary, Tertiary and Good-To-Have Functions of our system and it is now fully functional.
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Schedule (Plan Vs Actual):
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
Iterations | Planned | Actual | Comments | ||
1 | Customer CRUD | 1 Sept 2010 | 25 Aug 2010 | Fiona took the Sales CRUD as well. | |
Trend Analytic | 1 Sept 2010 | 15 Sept 2010 | Ben is too busy and pushed iteration 1 back | ||
2 | User tutorial | 1 Oct 2010 | Removed proposed by Ben | ||
Psycho analysis | 1 Oct 2010 | New module proposed by sponsor |
Project Metrics:
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
Technical Complexity:
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
Quality of product
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
Project Deliverables:
Stage | Specification | Modules |
Project Management | Minutes | Meeting Minutes |
Metrics | Metrics Management | |
Requirements | Story cards | Use Case Diagram, Trend Analytic |
Analysis | Use case | overall |
System Sequence Diagram | client, server | |
Business Process Diagram | ||
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | 1, 2, 3 |
Class Diagram | 1, 2, 3 | |
Testing | Test plan | instructions |
Handover | Manuals | Koh Bus User Manual (Administrator), Koh Bus User Manual (Sub-Contractor) |
Code | client server | |
Deployment Diagram | instructions |
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
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:
[1] Functional Testing
User Test:
UT | Summary | Documents | Result Data |
---|---|---|---|
UT1 | Objective: Gauge usability of customer booking mobile app Number of users: 19 |
|
Group 1 (Time Based & Single Trip) Observations
|
UT2 | Objective: Gauge business process fit and usability of admin portal web app Number of users: 2 |
||
UT3 | Objective: Gauge business process fit and usability of subcon mobile app Number of users: 1 subcon, 20 students |
Student Questionnaire |
|
UT4a | Objective: Gauge usability of admin portal web app Number of users: 2 |
||
UT4b | Objective: Gauge usability of customer mobile app Number of users: 2 |
||
UT5 | Objective: Stress test for all 3 systems Number of users: 20 - 2 admin, 5 subcon, 13 customers |
Reflection
Compile common lessons and reflection for the team and for each team member. Be brief.
Team Reflection:
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Individual Reflection:
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.