HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 Carpe Diem Final Wiki"

From IS480
Jump to navigation Jump to search
Line 169: Line 169:
 
|| Testing
 
|| Testing
 
|| Test plan
 
|| Test plan
|| [[IS480_Midterm_Wiki#Testing: | instructions]]
+
|| [[IS480 Team wiki: 2013T2 Carpe Diem Final Wiki#Testing: | Test plan]]
 
|-
 
|-
  

Revision as of 15:06, 7 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:

  1. Completed UT 1 on the Customers (Student Users)
  2. Completed UT 2 on the Administrators
  3. Completed UT 3 on the Sub-Contractors
  4. Completed UT 4 on the Administrators and Customers
  5. Completed UT 5 on the performance of the integrated application
  6. Project successfully gone live on 24 March 2014
  7. 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:

1. Schedule metrics never went over 120%
2. Completed 5 different user tests, and met with all real users (customers, admins, subcon) to gather feedback
3. Project is fully deployed by end of schedule

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):

Carpediem PlannedVSactual v1.png

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
Analysis Use case Use Case Diagrams
System Sequence Diagram Sequence Diagrams and System Sequence Diagrams
Business Process Diagram Business Workflow
Design ER Diagram ER Diagrams
Class Diagram Class Diagram
Testing Test plan Test plan
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.
Design pattern: MVC for web portal
Fault tolerance: in customer application, cannot view buses when there is no internet connection, so they cannot make a booking. Admin and subcon application are assured to always run with internet connection.
Reliability and performance: Admin portal can handle up to 50 bookings in a 30 minute time interval.

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:

Functional Testing

User Test:

UT Summary Documents Result Data
UT1 Objective: Gauge usability of customer booking mobile app

Number of users: 19
User profile: students
Date: 18, 19 December 2013


Informed Consent Form
Questionnaire
Study Script
User Testing Instructions

Group 1 (Time Based & Single Trip) Observations
Group 2 (Time Based & Return Trip) Observations
Questionnaire Responses
UT1 Compiled Bugs


UT2 Objective: Gauge business process fit and usability of admin portal web app

Number of users: 2
User profile: Actual users - KohBus admins
Date: 13 February

Questionnaire
Study Script
User Testing Instructions

Observations & Questionnaire Responses
Compiled Bugs

UT3 Objective: Gauge business process fit and usability of subcon mobile app

Number of users: 1 subcon, 20 students
User profile: Actual subcon, and university students
Date: 20 March

Student Questionnaire
Subcon Questionnaire
Study Script
User Testing Instructions

Observations & Questionnaire Responses

UT4a Objective: Gauge usability of admin portal web app

Number of users: 2
User profile: Actual users - KohBus admins
Date: 27 March

Questionnaire
Study Script
User Testing Instructions

Observations & Questionnaire Responses
Compiled Bugs

UT4b Objective: Gauge usability of customer mobile app

Number of users: 2
User profile: Actual customers
Date:

UT5 Objective: Stress test for all 3 systems

Number of users: 20 - 2 admin, 5 subcon, 13 customers
User profile: Actual users - KohBus admins
Date: 13 February

Slides for students

Reflection

Team Reflection:

1. Change management has taken up an unexpectedly large amount of time and effort on our part. We understand how important it is to have face to face communicate with our client, in order to fully gather details of his requirements. We also learnt how to manage the changes that need to be implemented, and how we have to modify our schedule to roll them out.
2. Meeting up with the actual stakeholders for user testing has helped us gain important feedback on whether our idea of user-system interaction is accurate or not. Speaking to them has also allowed us to learn more about what we can do to improve the user experience.
3. Internal communication is very important so that we can have the same understanding of what tasks need to be completed.

Individual Reflection:

Hui Qi: I learnt the importance of communication with our supervisor, client as well as internally. Change management has been the focus post-midterms and I now understand how much iterative work is required in order to bring the system from a prototype to deployment.

Qilin: Through my research and comparing of various methods to implement the system's functionalities, I have learnt a lot about system design principles. This has made me more efficient at carrying out research.

Zhongyun: On top of the integration of front and back end codes, I have also enhanced my knowledge of usability in both web and Android applications. As such, communication internally in order to make the development and usage of the system cohesive has become extremely important.

Nicholas: I have learnt a considerable amount about researching of new methods, and how to implement changes into the applications. Iteratively making changes to the system from the change management has also enhanced my knowledge of system design.

Xin Lin: Applying user test results for usability and functionality has taught me a great deal about the importance of data collection. I am now able to better plan user tests in order to get the data we require. I have also learnt more about the various types of tests.

Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.