Difference between revisions of "Team Motiva Final"
|Line 91:||Line 91:|
the , .
Revision as of 14:58, 15 November 2011
- 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