Usability in ABAP Programs - SITSP2011

1,048 views
955 views

Published on

Usability in ABAP presentation presented at SAP Inside Track São Paulo 2011

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,048
On SlideShare
0
From Embeds
0
Number of Embeds
20
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Usability in ABAP Programs - SITSP2011

  1. 1. Usability in ABAP Programs<br />
  2. 2. Usability in ABAP Programs<br />Mauricio Roberto Cruz<br />ABAP Consultant since 2006<br />PI Consultant since 2008<br />JAVA/Android/UX Enthusiast<br />Editor for “ABAP Zombie”<br />http://abapzombie.blog.br/<br />
  3. 3. Agenda<br />Concepts<br />Whyshouldwecareabout Usability?<br />Real case analysis<br />Creatinguser-oriented ABAP programs<br />Tools andTechniques<br />ReferencesandGuidelines<br />
  4. 4. Concepts<br />Usability – The ease of use and learnability of a human-made object<br />Interaction Design(IxD) – Tells how a system/product must behave based on user experience with it<br />User Experience (UX) – how someone feels and react when using a product<br />
  5. 5. Why should we think in Usability?<br />Simpler and easier-to-use interfaces<br />Less “misunderstanding errors”<br />Program will last longer on your client’s system<br />And your job will look even more Professional!<br />
  6. 6. A new requirement has arrived!<br />SITBRAZIL 2011<br />FS001<br />Sales Order File<br />
  7. 7. SAP Project – Who’s who?<br />User – He wants something!<br />SD Consultant – He knows what the user wants<br />ABAP Developer – He will create what the SD Consultant tells him the user wants<br />
  8. 8. SAP Project – Classical Structure<br />
  9. 9. Let’s build something… “classical”<br />FS001 - Sales Order File<br />Program must do the following:<br />Extract all sales order data based on date/s.o. number/s.o. type into a text (.txt) file<br />Create file at server or user’s machine <br />
  10. 10. Hand’s on!<br />SD Consultant<br />Defined all rules needed and gathered all transactions/tables from where data will be extracted<br />Also defined an Layout with the end-user<br />ABAP Developer<br />Created the whole program 100% according to the Specification <br />
  11. 11. Results – Is it complete?<br />Program’s Selection Screen:<br />Success Message:<br />
  12. 12. Test Results<br />ABAP Unit Test<br />Done, everything is fine!<br />SD Unit Test<br />Done, everything if fine and according to what I specified<br />User Acceptance Test<br />Program is wrong!<br />
  13. 13. What went wrong?<br />Data modeling was correctly made<br />Business requirements were covered by the program<br />There were no issues with File Layout<br />However…<br />
  14. 14. What went wrong?<br />Nobody thought about how that software will be used.<br />We work for the end-user, yet we often ignore what are his thoughts and what he trully needs<br />
  15. 15. Question<br />Have you ever faced this kind of situation, where the user seems to have no “computer skills” at all, and can’t understand how a “simple and correct” program works?<br />
  16. 16. Question<br />Is it really his fault?<br />
  17. 17. Software Development Process<br />Data Modeling <br />goes first…<br />or<br />User Interaction<br />goes first?<br />
  18. 18. User-Oriented Development<br />Why the software is being created?<br />How the user will use that software?<br />What can be created based on his needs?<br />
  19. 19. SAP Project – User-Oriented Structure<br />Senior<br />
  20. 20. Developer and User Relation<br />User interaction design is one of tasks from ABAP developers<br />An ABAP developer knows technically what can and can’t be built<br />Based on previous developments experiences he can suggest many improvements to the software overall design<br />
  21. 21. In case you are curious…<br />This is what user wanted<br />
  22. 22. Defining a user interface<br />Scenarios and Use Cases<br />User Interaction Scenarios<br />Use cases in those scenarios<br />Prototypes <br />Wireframes<br />Navigation Prototypes<br />
  23. 23. User-Oriented Projects!<br />User-Oriented activities should be applied in any project: smaller and larger ones<br />Senior ABAP Developer engaged in Blueprints and Requirements Gathering phases<br />Agile methodologies can have a Sprint 0, dedicated only for interaction design<br />There are no additional costs, and more quality will be delivered to customers<br />
  24. 24. Guidelines and Techniques <br />ABAP UX Guideline<br />SAP Design Guild – ABAP Development Guideline<br />http://www.sapdesignguild.org/<br />Techniques<br />Researches with users<br />Personas<br />Usability Tests<br />
  25. 25.
  26. 26. Thankyou!<br />Mauricio Roberto Cruz<br />mauriciorcruz@gmail.com<br />@mrc_cruz<br />http://abapzombie.blog.br/<br />http://sapcastbrasil.wordpress.com/<br />

×