Your SlideShare is downloading. ×
  • Like
Coding Gateway - Exam Stefan
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Coding Gateway - Exam Stefan

  • 102 views
Published

 

Published in Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
102
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Hi, present yourselfPresent background, as programmerSoftware one of the most important parts of the projectDifference between good UX and a bad one, secondsPresent the process
  • DDS Requirement, most importantExplain each bullet point
  • Or, to rephrase it …..
  • I will be taking about …
  • AggregationModularity
  • MMT are as innovative as they getThey liked the ideaAlmost unique explained
  • Good reason why is not largely usedMake it shortStill “experimental” technology
  • Say about cameraWhy we used Kinect nowWhy not in the future
  • Paul details
  • Android and Apple related excluded from startOther are less popular, less supportOS to power it
  • Eather go that way, or the order wayPros and Cons
  • We used a nifty toolTppicaly, web is used is a fullscreen windows(with flash)Against convention = coloring outside the lines
  • easy title, contains also technologically challenged Analytical approach(q)/actor approach(interview) New field, not so many informationWhat is now usedExtrapolate gestures from smartphones/XboxFuture survey: observe people’s reaction
  • Planning - Analytical approach(q)/actor approach(interview) MRS = observation & research for othersObserving tech, Extrapolate gestures from smartphones/XboxObsprague airportTech path = info from tech related sources => tech exists, features possibleUser path = we not doing Idea, concept, design, just test if it workingNew field, not so many informationFuture survey: observe people’s reaction
  • Best info sourceHuman interface guidelines from MicrosoftTake position to start as bad exampleMoves to be used: Wave,Take and move, Dismiss, Swipe, Circles, Underline
  • Seen at the beginningFocus prototype – only a few featuresSince Kinect is not going to be used, it works will suffice
  • Overlap milestone with Scrum iteration end
  • Seen at the beginningRelate to first project model of working
  • Great team effort, I am cracftsmanFirst time focusing on process not goalWished to do it moreStakeholder gave the green light for forward developmentSoftware put on backburner, just basic

Transcript

  • 1. STEFAN FODOR24TH OF JANUARY 2013
  • 2. Overview Introduction Problems Faced Quick round-up Go into each problem Critical Reflection Questions
  • 3. Introduction “Create an innovating interactive display” Unique content New way of interacting Appropriate Input device Appropriate hardware Appropriate Operating Systems Appropriate base software Handle people’s fear of technology/technically challenged people Create a prototype
  • 4. Innovating andInteractive DisplayContent InteractionInput DeviceOSFearPrototypeSW HW
  • 5. Innovating andInteractive DisplayContent InteractionInput DeviceOSFearPrototypeSW HW
  • 6. Innovating andInteractive DisplayContent InteractionInput DeviceOSFearPrototypeSW HW
  • 7. Interaction Interaction Voice Touch Keys (Markerless) Motion Trackers Markerless Motion Tracking pitched to DDS Almost unique featureInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 8. History Project Natal – November 2010 Adafruit Industries bounty – December 2010 Microsoft Strategy Change – June 2011 Commercial SDK - May 2012 Today – January 2013Innovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 9. Innovating andInteractive DisplayContent InteractionInput DeviceOSFearPrototypeSW HW
  • 10. Innovating andInteractive DisplayContent InteractionInput DeviceOSFearPrototypeSW HW
  • 11. Operating System Linux based distro Ubuntu, Debian Red Hat Light Linux based distro LFS Gentoo Windows Embedded Full size Windows (7 or 8)Innovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 12. Web vs StandAlone Application 1/2 Power of HTML(5) and CSS vs The week WPF Power of C# and native APIs vs The week PHP Tie-breaker Modularity ScalabilityInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 13. Web vs StandAlone Application 2/2UseStandAloneinstead ofWebappHarder Design Creation(1)Against Convention (2)Portability (3)Content Maintenance(3)(4) Easy integration of APIs(3) Easy Extension of Radio(5) Modularity(5) Scalability(3) SW MaintenanceForces against change: 9Forces for change: 20
  • 14. Fear of technology Good UX User friendly Fell Natural Be intuitiveInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 15. Fear of technology – Information collection Information collection and analysis Market related sources Technology related sources Information paths Technical dominance path User Acceptance pathInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 16. Natural User Interaction (“Biomimicry”)Innovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 17. Software Prototype Focused, work-like Prototype Confirm that gesture recognition is doable Prototyping Plan Purpose – Rear camera, gesture recognition Level of Approximation – It works Experimental plan – recognize proximity/swipe gesture Schedule – 29th of November - 15th JanuaryInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 18. Software Prototype The 4 Purposes Learning the feasibility of Markerless Motion Trackers Communication our progress to DDS Integration with Gateway design prototypeInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 19. Software Prototype Demonstration to the stakeholdersInnovating andInteractive DisplayContent InteractionInputDeviceOSFearPrototypeSW HW
  • 20. Conclusion and Critical Reflection
  • 21. Thank you! 