Virtual Mechanics

Virtual MechanicsGroup – 12, CMPT 275, Simon Fraser UniversityFall Semester 2009

Marc Lynch Tyler Shao

Jeffrey Limao Greg Steffensen Chien-Chi Chen

AGENDA

• Introduction to Virtual Mechanics• Architectural diagram and summary• QA steps and integration testing• Bugs in the software• Feedback from real users• Post-mortem analysis

INTRODUCTION• Users can utilize the Virtual Mechanic

application to dismantle and learn about complex machines and organisms in a graphical user environment; all without having to get their hands dirty.• They can drag and drop pictures of

various systems, post comments and photos and take part in discussions about each component and the system overall.

ARCHITECTURAL DIAGRAM

QA STEPS

• Step 1 - Verify menu controls and help function

• Step 2 - Opening new machines • Step 3 - Manipulating the machine • Step 4 - Posting new comments and

photos • Step 5 - Downloading new machines

INTEGRATION TESTING• After designing each version of the program,

we held user tests with people that we knew in SFU or at home. Using test cases, we instructed users to perform a task without helping them. We recorded their actions and documented their success rates. Since many functions were not included in early versions of the program, many actions could not be performed and success rate was low. However, now with our first distributable version, we are proud to announce that all test cases succeeded without any major problems!

POTENTIAL BUGS

• Font that iPhone cannot display the code of the font and shown as confused symbols that cannot be read

• Network errors may occur, causing data that are not received properly.

• Offensive and dangerous comments need to be filtered and deleted

• If the users cannot connect to the server, then their comments and photos are not uploaded.

• Zooming.• Photo taking and uploadingDrawback:• posting comment function is not efficient

because it have to read file, save file, upload file.

• Security issue: user information is not stored in the server but the user iphone.So every one can make any account even duplicated account is valid. .....It is not professional...

UNIMPLEMENTED FEATURES

FEEDBACK

• Very clear and understandable user interface, very easy to use.

• Implement some more features to represent more details of each machines.

• Build more machines in this application.• Machines can be more detailed, more

deeper.

POST-MORTEMWorked well:• Giving out specific positions to members (i.e.

Minutes manager, Lead Coder, etc.)• Weekly meetings• working together in groups, frequent meetings,

updates using text-messaging, keeping record of everyone’s schedules

Didn’t work well:• Google wiki made it confusing keeping track of

changes to documentation.• Conflicting schedules; needed better time

management.• No permanent project manager.

POST-MORTEM

Technical Problems:• No set formatting techniques for documents• Personal computer didn’t support

programming environment• No SDK or old SDK in libraries at one point,

no personal Mac computers for everyone, some unfamiliar with iPhone technology

Human Problems• Conflicting schedules• Poor communication with members• Members not showing up for meetings

POST-MORTEM

What would I do differently?• At least two meetings a week• Set up a better method for

communicationWhat would I do the same?• Meeting with team members• Setting out agendas and deadlines for

each assignment

POST-MORTEM

Advice!• Learn Objective-C early and thoroughly!• Communicate with each other VERY

often!• Always have a backup plan• Have at least two members working

together on any given task, in case one has to drop out or step back.

QUESTION

THANKS

That is the end of the presentation. Thanks for your time and your consideration.