Difference between revisions of "Team Motiva Final"
|Line 180:||Line 180:|
Revision as of 21:00, 16 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
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.
Eugene Chong's Reflection
The final league of FYP is coming to an end and I am proud to say I have gained the much-needed technical knowledge in Objective-C to develop an Apple Application. I am able to put the knowledge to good use in future and perhaps start developing my own applications to be listed in the App Store!
Looking back at when we first accepted the project, the team has came a long way till date and the bonding we have is simply irreplaceable! We worked hard to deliver the end product without compromising our schedule. The synergy we have boils down to everyone's determination and hardwork. I am glad to have them as my teammates and I am sure we would all love to see the success of the Giving Life App in time to come!
We have come a long way since this project started in July 2011. New friendship has been forged and I would like to thank everyone for giving me this opportunity to contribute and indeed we have race this journey with pride. It all started with a simple goal of delivering ideas through the mobile platform. With the trend of smartphone adoption rate and technology curve coupled with information that is readily available in public channels, we believe that our project will certainly grow from here.
I was new to the group at the beginning but in fact we share the same passion and objective. Before the start of our work, we had a several gathering and chill out session where we bonded together; and I think that really helps in fostering the team spirit which eventually helps us to weave through these rough roads.
From our project, I have learnt a lot and I’m going to share some major ones that may have impacted me. Talking management is easy then practically managing it. All of us have numerous works to do but we manage to plan things ahead, pinpoint the risk and reschedule if there were potential conflicts. The basis of understanding forms the foundation of our team and I am very thankful towards everyone’s patience. The last point is competency. We knew there were problems as we went along and what turns out is how effective we are in solving them. Once an issue is discovered and notified, we immediately find a solution and rectify it. It is tough but great work and I am very proud to work with such a wonderful team.
I have enjoyed myself in this 6 months long project. I would like to thank our wonderful client who continuingly innovate and pushing us to deliver a better experience and product for the community.
Ong Wee Chian, Roger's Reflection
Just a few more weeks and our FYP will come to a closure. I still remembered the time where we went to NYP to have an induction course on Objective C organized by Code Xtreme.Our team bonded with faith and trust. During development, we ensure that everyone knows the progress of the development and the new changes to requirements.
What i learnt from this FYP is translating business requirements to IT solutions is no easy task. An example that we encountered would be that B1G1 wanted a checkbox in Giving Life. However, iOS does not allow checkbox to be implemented due to its Human Interface Guides and any attempt to create our own checkbox would be rejected immediately. Sometimes, we have to balance between client's requirements and the technical implementation. We also had fun working together! 4 out of 5 team members are having 5 CUs this semester but we are still meeting for more than 60 hours per week! Geez, looking back, I wondered how we achieved that!
Last but not least, I would like to use this opportunity to thank my team members for their hard works and B1G1 for providing us the opportunity to work on a project that could impact the community!
"Motiva team has managed the project with great care. They were able to put a clear plan in place from the beginning and then execute the development accordingly. They've also explained their concerns and managed our expectations throughout. Facing many challenges due to the the complexity of logistics required by B1G1 and Apple, they've done well."
"Working with clients can be challenging and I'm sure that in B1G1 we're more challenging than most. Motiva team has managed things in a very professional way. Sometimes though, that professionalism has unduly impacted on the user experience. So the UAT tests involving REAL people were, I think, quite eye-opening for the team and for us as well. Doing things 'out-of-the-box' and moving beyond what we know, embracing uncertainty and being prepared to fail is crucial to developing an amazing customer experience. Sometimes, the limited time-span of an assigned project means that 'safety' is pursued rather than doing something that's not been done before. Doing that — something that has not been done before — is the real mark of the entrepreneur and not necessarily of the systems approach. But when the two come together — as, for example, in the Apple case — real magic occurs. We've learnt amazing things through this process and through the wonderful diligence and commitment of the Motiva team. "