46

Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

  • Upload
    fitc

  • View
    168

  • Download
    0

Embed Size (px)

DESCRIPTION

Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed with Mike Costanzo Presented on September 18 2014 in Toronto at FITC's Web Unleashed 2014 More info at www.fitc.ca OVERVIEW Designing for the Web has become increasingly complex; the rise of HTML5 web apps, responsive design, adaptive design, etc. has made static mock-ups redundant and the trend toward lean and agile development methodologies can create a hostile environment for designers who are often left feeling rushed, disorganized and overwhelmed. But there is hope. Many new tools are now available to deal with designing in this dynamic landscape. Mike Costanzo will look at some and evaluate the advantages and limitations of each while discussing how they can be integrated into the workflow. These tools not only allow for faster design but also facilitate rapid iteration, concept evaluation and the creation of clear deliverables to distribute to product owners and team members, in turn, leaving more time to design a holistic product. OBJECTIVE Present and demonstrate rapid interactive prototyping applications and workflows TARGET AUDIENCE Designers interested in learning about new applications that quickly build, iterate and distribute interactive application prototypes. ASSUMED AUDIENCE KNOWLEDGE Design application knowledge i.e. Adobe Creative Suite, Sketch, Balsamiq, ect… FIVE THINGS AUDIENCE MEMBERS WILL LEARN 1. Various applications to create rapid interactive prototypes 2. Integrating the workflow into an Agile team (however not exclusive to Agile) 3. How designing for interaction differs from traditional static mock-ups 4. The importance of delivering the right level of prototype fidelity 5. Methods of delivering the prototypes to clients and users for testing

Citation preview

Page 1: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

������

����

Page 2: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 3: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 4: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

���� ���������������

Page 5: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

�����������������

Page 6: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

�����������������

Page 7: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 8: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

����������������������

Page 9: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 10: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 11: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

Page - 2

Confidential and Proprietary

Senior Information Developer

1.1.3 SPECIFICATION DISTRIBUTION RESTRICTIONS

1.2 Project Schedule Summary and Timeline

1.3 Project DeliverablesDeliverable Delivery Method Deliverable Description Delivery Date

Pre-beta

Beta

FCS

Maintenance releases

1.4 Evolution of the Software Development PlanVersion Primary Author(s) Version Description Date Expected

Draft

Revised Draft

Preliminary

Final

1.5 Reference Materials

1.5.1 DOCUMENT ARCHIVE LOCATION(S)

1.5.2 BIBLIOGRAPHY

1.6 Definitions, Acronyms, and Abbreviationsbeta test: The testing of a pre-release (possibly unreliable) software product by selected users ina live setting.

CM: Configuration Management. The process of configuring the pieces of a software system,systematically controlling changes to the configuration, and maintaining the integrity andtraceability of the system throughout the software lifecycle. Also referred to as “revision control” or“version control."

CVS: Concurrent Revision System. A powerful configuration management system which isdistributed free of cost under the terms of the GNU General Public License. CVS is currently usedby Austin APG staff.

Page - 3

Confidential and Proprietary

defect: An unwanted and/or unintended property of a software product that causes it tomalfunction. A defect can be due to any number of causes, including programming error, systemincompatibility, or improper specification.

defect severity: A description of the seriousness of the defect in terms of its consequences tothe user of the product. Defects fall into five severity levels:

� Critical (severity 1): The defect causes the system to crash, or causes irretrievable dataloss, or major portions of the system are unusable. There is no reasonable workaround.[Note: The reasonableness of the workaround should take into account the intended enduser of the system and seriousness of the consequences caused by the bug.]

� High (severity 2): The defect causes a major portion of the system to be unusable orvery difficult to use, but reasonable workarounds exist.

� Medium (severity 3): The defect causes some portion of the system to not work as thedeveloper intended or the user preferred, resulting in some noticeable deficiency ordifficulty, but still allowing system use. Simple workarounds are obvious, and no loss ofdata is possible.

� Low (severity 4): The defect is a minor imperfection that does not impede systemfunctionality in any way, but should be fixed anyway.

� Enhancement (severity 5): The defect is not really a defect in the current system, but isa description of a desired enhancement or new feature.

FCS: First Customer Ship. Refers to the first customer shipment of the product as it will besold/deployed. Pre-releases such as beta test versions do not qualify as FCS.

GUI: Graphical User Interface. That portion of the product which the user uses to interact withthe program, including the keyboard, mouse, buttons, pictures, menus, windows, and dialogs.

POS: Point of Sale.

PT: Problem tracking. Usually refers to problem- or defect-tracking software packages for use bydevelopment and quality assurance staff for reporting and tracking product defects.

QA: Quality Assurance. A planned and systematic process necessary to provide adequateconfidence that the product optimally fulfills customer expectations.

QDM: Qualit Defect Manager, a commercial problem tracking tool from Qualit Software. A freeevaluation copy of QDM is currently being used by Austin APG staff, while a more permanentdefect tracking solution is sought.

regression testing: The retesting of previously tested features and components to ensure thatno new defects have been introduced by the addition of new features and fixes.

Y2K: Year 2000. Refers to the class of defects related to the date rollover of January 1, 2000. Aproduct is considered Y2K-compliant if it contains no defects relating to the year 2000 daterollover.

Page 12: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 13: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 14: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 15: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 16: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

����!���"����#�������$�%�����

Page 17: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 18: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

&���

'��(���"�����

Page 19: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

!��������

Page 20: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 21: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

)��

*��

+��

,��

-��

Page 22: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 23: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 24: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 25: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 26: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 27: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

)��

*��

+��

Page 28: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 29: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 30: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 31: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

)��

*��

+��

Page 32: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 33: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

!� �����.����������/������������/����

.������0����1���#�$�����������#���$�%

Page 34: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 35: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

����������

������������2���

��������������"������������

�%���������/��� ������

�������/��

������������"������

Page 36: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 37: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 38: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

)��

*��

+��

,��

Page 39: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 40: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 41: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 42: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 43: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed
Page 44: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

)��

*��

+��

Page 45: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

!��� �������������$������

$����3�����#�.44

Page 46: Rapid Interactive Prototyping – How Designers can Embrace the Need for Speed

5����������1�