Standards Based Approach to User Interface Development


Published on

Standards Based Approach to User Interface Development presentation at ACM SIGCHI conference Bangalore

Published in: Design, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Standards Based Approach to User Interface Development

  1. 1. Standards Based Approach to User Interface Development Easy6 ACM CHI-SI Conference Bangalore Jan 2006 Sameer Chavan Applications User Experience Oracle
  2. 2. Standards <ul><li>Standards are in Architecture, Mechanical, Electrical, Medical, Social fields </li></ul><ul><li>Standards in software industry are evolving </li></ul><ul><ul><li>Company specific standards </li></ul></ul><ul><ul><li>International standards – ISO, IEEE, CMM, W3C </li></ul></ul><ul><li>Software User Interface Standards </li></ul><ul><ul><li>Macintosh Human Interface Guidelines (Apple) </li></ul></ul><ul><ul><li>Comman User Access (IBM) </li></ul></ul><ul><ul><li>OS/Motif Style Guide (opern software) </li></ul></ul><ul><ul><li>Windows Interface Guidelines (Microsoft) </li></ul></ul><ul><ul><li>BLAF (Oracle) </li></ul></ul>
  3. 3. Definitions <ul><li>UI Standards </li></ul><ul><li>UI Guidelines </li></ul><ul><li>UI Patterns </li></ul>Component Level When to use which standard Standard ways of interactions. Eg checkout Branding Specifications Button behavior Text Graphics Table OR
  4. 4. Before applying Standards <ul><li>Applications had their own look and feel </li></ul><ul><li>No cohesion . </li></ul><ul><li>Inconsistent interactions for common UI needs </li></ul><ul><li>Many duplicated efforts in design and implementation </li></ul><ul><li>Poor user experience </li></ul>
  5. 5. Need for UI Standards <ul><li>Standardize the commonly used actions, labels & dialogue boxes across the applications. </li></ul><ul><li>Incorporate Human factors research and best practices, which is empirically proven. </li></ul><ul><li>Reduce the number of UI decisions made during design process. </li></ul><ul><li>Reuse the user experience. Avoid reinventing same designs. </li></ul><ul><li>To help Product Managers. Reduced the dependency on UI designers . </li></ul>After
  6. 6. Limitations of Standards <ul><li>Standards are very generic so they don’t know exact requirements for a particular task. </li></ul><ul><li>Standards are often compromised solution across all products. So it cannot guarantee best interaction for that task. </li></ul><ul><li>Having just consistent UI will not insure usability. </li></ul><ul><li>All the designs cannot be documented and have UI standard. </li></ul><ul><li>Standards cannot give design solution </li></ul>
  7. 7. Challenges for Standards Development <ul><li>Wide range of applications ranging from Financials, HRMS, SCM, CRM, etc </li></ul><ul><li>Very broad range of user profiles </li></ul><ul><li>Technological limitation to make the designs accessible, cross browser compatible and localized </li></ul>
  8. 8. Solution : BLAF standards <ul><li>Flexible enough to use across the variety of applications but specific enough of meet each team’s requirement </li></ul><ul><li>Interactivity was reduced and was limited to plain html </li></ul><ul><li>Standards were defined at Component level, Page level, Flows, Patterns. </li></ul><ul><li>Structure of Guidelines </li></ul>
  9. 9. Standards were result of.. <ul><li>Functional requirements from many product teams. (tasks & flows) </li></ul><ul><li>Technical constraints after discussing with development. (Browsers & bandwidth) </li></ul><ul><li>Legal constraints (Accessibility) </li></ul><ul><li>Competitive pressure (e.g. “Save for later” feature ) </li></ul><ul><li>Cost constraints </li></ul><ul><li>Human cognitive limitations (e.g. reduce memory load) </li></ul>
  10. 10. Benefits of Standards <ul><li>The Standards are Comprehensive, Robust and scalable designs. </li></ul><ul><li>Empirically proven and continuously enhanced designs. </li></ul><ul><li>Avoid duplication of efforts, divert PM & DM to higher level tasks. </li></ul><ul><li>Easily upgradeable. </li></ul><ul><li>The products are consistence in look & feel and interactions. </li></ul><ul><li>User Experience is reused so learning curve is reduced. </li></ul><ul><li>Does not have to worry about the working of the component or interaction because it is already tested </li></ul><ul><li>Prototypes can be done in Visio or html prototyping tool. </li></ul>
  11. 11. Standards Development process <ul><li>Requirement gathering </li></ul><ul><li>Concept and Draft proposal </li></ul><ul><li>Reviews with different teams </li></ul><ul><li>Usability testing </li></ul><ul><li>Redesigns and updates </li></ul><ul><li>Visual Design </li></ul><ul><li>Release process – translation, legal, performance,.. </li></ul><ul><li>Publishing </li></ul>Usability Testing
  12. 12. Ongoing Activities <ul><li>Enhancement bug against Standards </li></ul><ul><li>Replying to questions from Development, Designers & PM </li></ul><ul><li>Training on Standards </li></ul><ul><li>Research on new interaction widgets </li></ul><ul><li>Usability testing of new components </li></ul><ul><li>Updating standards for new technology </li></ul>Enhancement UI Helpdesk Training Research Usability Test Updating Standards
  13. 13. Reviews- Standards compliance <ul><li>Reviews are done at </li></ul><ul><ul><li>Concept </li></ul></ul><ul><ul><li>Prototype </li></ul></ul><ul><ul><li>Code </li></ul></ul><ul><li>Attended by Development, Designer, Reviewer, PM </li></ul><ul><li>Bugs are filled </li></ul><ul><li>Score cards are issued </li></ul>
  14. 14. Challenges due to Standards based Design <ul><li>Dose not insure best design. </li></ul><ul><li>The designer needs to apply right standards for given task flow. </li></ul><ul><li>A designer needs to know each standard before designing. </li></ul><ul><li>You cannot design freely. </li></ul><ul><li>Interpreting the meaning of standards become difficult. </li></ul><ul><li>Standards constrains the flexibility and innovation in design. </li></ul><ul><li>Lengthy process of standards. </li></ul><ul><li>Standards become absolute after certain time. </li></ul>
  15. 15. Future perspective on Standards <ul><li>Can we have a wizard based design </li></ul><ul><li>Can a designer becomes redundant using patterns. </li></ul><ul><li>Common standards across the platform (windows, Unix, mac) </li></ul><ul><li>Can different companies have same flow for same task(eg. Shopping cart) </li></ul>
  16. 16. Questions and Answers Q A & [email_address]