Team Motiva Mid Term

From IS480
Jump to navigation Jump to search

back to main

Project Progress Summary

This section only covers the progress of the project. For more detailed information, refer to our main wiki page here.

The following functions are completed.

  • Registration of a new account
  • Login and Logout
  • Creating of new lifestyle and tagging a project to it.
  • Uploading of picture from camera and library
  • Randomizing of projects for users
  • Filtering of projects by category
  • Contribution via PayPal

Project Highlights

  • Total of 2 changes raised while development. For more information, click here.
Iteration 1 Summary
1. Bug Logs:

Our bugs severity points for this iteration is 5. Our targeted bug severity goal per iteration is 10.
All bugs found are small issues and we resolved them within our allocated buffer time.

2. Test Results:
We ran the test cases twice.
The first test cases carried out failed as bugs were found and logged it.
We performed the test cases the 2nd time to ensure all bugs are quashed.
Test cases for Iteration 2 are done and uploaded.

3. Schedule Metric:
We are on time for Iteration 1

Iteration 2 Summary
1. Bug Logs:

Our bugs severity points for this Iteration 2 is 7. Our targeted bug severity goal per iteration is 10.
The bug found was found during the development. It has been fixed.

2. Test Results:
We ran test cases and found no bug.

3. Schedule Metric:
We were half day late (SPI is 0.5) but utilized 1 buffer day.
We had also changed our schedule to start one day earlier as there was 1 unused buffer day.

4. Client feedback:
We had met up with Masami and showcased her the project. Refer to the meeting minutes here.

Iteration 3 Summary
1. Bug Logs:

Our bug severity point for Iteration 3 is 3. Our targeted bug severity goal per iteration is 10.

2. Test Result:
Test cases were ran twice as the few of the test cases failed. All bugs found are small issues and we resolved within the allocated time.

3. Schedule metric:
We were 2 days late for this iteration 3. This is mainly due to a new scope change and that PayPal API did not function correctly days before UAT.

4. Change of scope
Client had raised a change on contribution management. Refer to scope change 02 for more information.

5. UAT
A total of 58 testers attended our first UAT. Our targeted size was 50. Schedule has been changed for more time to make changes based on UAT comments.

Project Management

Project Schedule (Plan VS Actual)

Refer to main wiki

Project Metrics

To know how we manage our schedule, click here
Schedule Metric:

To know how we manage the quality of the product, click here
Bug Metric:

Project Risks

Risk Description Type Impact (Low/Medium/High) Probability (Low/Medium/High) Rating Mitigation Strategy Impact of Strategy
Client requirements may change during the course of project resulting in change of scope External High High A Enforce the scope change process. Ensure that all documentations are up to date and that all members of the team are aware of the scope changes. More time required on ensuring proper documentation for each change.
Conflicting clauses in placing charitable transaction based services in the application for Apple AppStore billing system Business High Medium A Use an external link which brings user out from the application to a web browser for further payment process Reduces user experience.
Submission of application to Paypal for review Business Medium Medium B Submit to Paypal as early as possible. Research on the internet for more information on Paypal application submission. Tighter schedule in developing the application.
Quality issues like application bugs and synchronization with B1G1 database may surface. Technical Medium Medium B Design more test cases and increase testing frequencies each iteration. Engage a higher number of users during User Acceptance Test (UAT) More time incurred for carrying out more tests and design more test cases
Minimal professional training on Cocoa (API) and Objective-C programming language used in Mac application development Technical Low Low C Source for Apple training program and reading up eBooks from library and internet More time spent on research, peer sharing sessions and self-learning for the team.

Technical Complexity

  • Threading in iOS to enhance user experience
  • Credit calculation in PayPal API
  • Navigation Flow
  • Pre-processing of images

Quality of Product

Intermediate Deliverables

Stage Specification Module
Project Management Scope Management Motiva Scope Management
Time Management Motiva Time Management
Quality Management - Bug Metric Motiva Bug Metric
Quality Management - UAT Motiva UAT
Communication Management Client & Supervisor Meeting Minute
Requirements Navigation Flow Navigation Diagram
Story Boarding Story Boarding PDF
Analysis User Interface Prototype User Interface PDF
Use Case Diagram Motiva Use Case
Schema Diagram Motiva Schema Diagram PDF
Sequence Diagram Motiva Sequence PDF
Design ERD Motiva ERD PDF
Archiecture Diagram Motiva Arch. Diagram
Testing Test cases All test cases used through iteration
UAT Guide UAT 1 guide


As our project is iPhone application, provision IDs need to be assigned to devices before it can be used for deployments.
The deployment is done at every end of the iteration and will be connected only to our client's B1G1 staging database.
Architecture Diagram is shown here.


The plan for our 1st UAT
While we aimed for 50 testers, a total of 58 testers attended our UAT.
The UAT was carried out over 2 days, 21st and 22nd Sept and 6 devices were deployed.
5 bugs were found during UAT and we had logged it here.

At the end of the testing, testers rated the ease of using our application and the overall user experience.

The results are shown as below:
Ease of using.png

  • 0% for Very Difficult, hence not shown in pie chart.

Overall exp.png

  • 0% for Very Bad, hence not shown in pie chart.


Team Reflection

Daniel Reflection

I had encounter many problems during the development and it was not so much from the core functionalities but rather the foundation in navigation and hierarchical structure of iOS App design. At the start, I am over-enthusiastic on looking through the client requirements and developing solutions for it. Through several attempts of building additional features to satisfy and improve user in-app experience, the project sway off course in not complying with certain Apple design; but not much.

Communication during project development is so much more important that I think it should be. It's not so much about efficiency but effectiveness. I found situation where I need to email our client for database and design clarifications several times. I feel that in the upcoming timeline, I need to constantly update our client with the project expectation, design, workflow and any requirements that risk for potential changes.

In my perspective, I feel passionate and will continue to push forward this concept and application design into the apps store. Imagine a world full of giving and I'm pretty sure that such connectivity and relationship can be found in all lifestyle.

Eugene Reflection

Since acceptance till date, I am definitely becoming more adapted to the native Objective-C programming language. But being programmatically inclined in Objective-C is not enough for developing iOS applications, I would need to understand the many underlying design and Human Interface Guidelines (HIG) principles to incorporate, alongside the native programming language.

Thus, given a chance to develop an iOS application has since allowed me to learn these skills that are otherwise not taught during school curriculum, and I look forward to complete the development soon!

Hui Juan Reflection

I believe that our development would run more smoothly now that we've gone through at least 6 weeks of coding in Objective C and using Xcode. I do look forward to completing the project as the application grows. As more interesting functions are to be added and more changes to be made, I'm sure that we are going to overcome these obstacles.

The journey thus far hasn't been well with the scope changes and schedules. The tight schedule with FYP and last minutes changes has been quite a pain. Different situations call for different measures and it really tests us on how we're going to manage our project and the approach we take in different situations. Nevertheless, I know we'll pull it through!

Roger Reflection

Working on this project, I had gained much invaluable experiences.
Different technologies that need to be incorporated into our application such as Facebook connect, PayPal API & Google Map. It provided an insight to me on what the industry is doing to develop mobile applications to be socially connected. Of course, I learnt more on the Objective C and Cococa.

Secondly, the soft skills that were acquired when communicating with the client and interactions between testers during UAT. It serves as an opportunity for me to translate project requirements and functionalities into business needs and user needs.

I'm looking forward to completing the project and publishing it to the App Store.

Vyane Reflection

'"Development Insights" overcoming the storm of technical complexities

Having been involved in the project for almost 6months (including the preparation phase), i've gained several insights on the development, the project management and with my expectations. Through these experiences, I realized that developing an iPhone application is not as easy as you thought.

We encountered many difficulties while coming up with the logics, the UI, IOS standards and meeting the client's requirement. Learning is limitless, and there’s no shortcut to it. we gone through countless number of testing, user acceptance testing and even regression testing to prefect the system. In terms of GUI, it is very subjective as different people will have different opinion on it. Some would like the font to be smaller and some like it to be larger. As the UI person, i faced the dilemma of adopting user feedback or how to translate and formulate that feedback into a plus point. It is not only on how to redesign it, it is how we re-egineer it. I use the term "engineer" because it contains not only design complexities but technical complexities. At most time, I've to turn to my groupmates asking for help and their opinion. This is how we started estasblishing good communication and common understanding in a common goal.

Every milestone is just like another chapter of learning in our lives. We gained from what we've went through. 58 users tested our application and we called that an UAT, but our SIS Dean, Steven Miller asked us have we done our "WAT?" oh, by the way WAT means "world acceptance test".

I would want to see how the application can change the world. I would give my best to see that a team of 5 SIS students can make a difference in beautifying the culture of giving. My passion in FYP continues..