Team Motiva Final
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflection
Project Progress Summary
The team has learned how to translate business requirements into a IT solution. As the team is using Objective C and wants to submit the application to the app store, we have to adhere to Apple's iOS Human Interface Guidelines (HIG).
When developing the application, our client wanted a checkbox to be implemented. However, this could not be fulfilled in the iOS environment as it's against the HIG. Any attempt to go against HIG would means our application would be rejected when submitting for reviewal.
Another issue our team faced is the accepting credit cards in PayPal. However, B1G1 does not have SSL server and though we could get the PayPal to accept credit cards in sandboxed environment, the actual implementation would be longer than the expected as we need to code on both the SSL server and the application. Given the short timeframe, the app that we submitted only accepts PayPal accounts.
Project Schedule (Plan VS Actual)
Refer to main wiki page for detailed information.
To know more on how we manage our schedule, click here.
Quality of Product
|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 1||UAT 1 guide|
|UAT 2||UAT 2 guide|
We had designed all our database transactions with REST web services. As such, when B1G1 wants change the type of information to be displayed to the users, they just need to alter the web service and does not need to be submitted to App Store for reviewal again.
During the entire phase of development and testings, our team are connected to B1G1's staging database. 6 devices were deployed during internal testings, UAT 1 and UAT 2. As our application can only de deployed to iPhones, we could not provide a direct link for our client. We could only do so when we met with our client during meetings and push the application into their respective phones.
We had a total of 16 test plans and 2 UATs. Each test plans have approx 15 test cases each and should any bugs found during the testing phase, the team would log them with the bug metric. Refer to here on more information of our test plans and test cases
Manage ongoing changes to business requirements
On schedule with our projected timeline
To provide the best alternatives whenever necessary
Interaction with Client on a regular basis
Value add with subtle implementation of HIG Principles
Assuring the quality of work delivered
"It is only just the beginning"
Finally, we have come to an end of our final year project, there are many mistakes we made and lesson learnt. Throughout the entire process, it is certainly an enjoyable one. Our FYP group spent endless hours working together through thick and thin. We celebrated birthdays, did team bonding like going Malaysia, Hong kong, and many places. We really did work hard and play hard. We took on challenges such as scope change, difficulties in the implementation of databases and following the apple iOS HIG. Today, we look back into where we start, how we form the group and how we make use of our individual weakness and strength. Now, FYP is coming to an end, but I realized that we've only complete 1 iteration of our life. With what we learnt from FYP, we will be able to take on further challenges to start our own business or revolutionarize the software industries using our technical expertise.
"End of the story"
End of the story, we became best friends after spending so many hours working together, facing challenges and making things happen! Our strategy is to bid for the same class, so with our common schedule we can utilize it better. So in fact, we spent over 60hours a week being together. This marks the tedious but most memorable experience in SMU.
Hui Juan's Reflection
Having been working on the project for 6 months, I can really feel that at different stage of the project, we've learnt different things. Today, the project is coming to an end very soon. I can feel that we are working towards a different objective. Near the ending stage, we are now looking towards having a quality product. It is also important to be able to be in-line with B1G1's business objectives. We are no longer looking at the functional requirements stage anymore. It has been interesting to see how the project changes at each different stage.
Having gone through the many weeks of FYP, it has been a journey with much obstacles faced. We've had several scope changes. I would say that we are able to cope with them fairly well. The project has been a great one so far. I do hope that we will have more chances of embarking on similar projects like this in future. I'm glad everything went well. This has been a great learning experience that I believe is worth the hard work.