1. KSA by the Numbers Data extracts represented as charts with references. The slides are organized by source and time. Last updated 14 April 2013

2. Kuali Implementation Status Source/imm/I130411F, 11 April 2013

5. Kuali Governance and Collaboration Project TeamsUser GroupsTotal Kuali Financial System37744 Kuali Student26228 Kuali Research Administration26632 Kuali Rice19322 Kuali Ready909 Kuali OLE30232 Kuali People Management9110 Kuali IT Support303 Kuali for Government101 Kuali Mobility516 Kuali Foundation34 Count19922221

6. Kuali Student Accounts Performance Source/imm/I130413F, 11 April 2013

12. Response time measures Response time measured from “Enter” to the browser completely rendering the screen. These two screens were selected to represent extremes in performance. Other and older devices may show increased response time.

13. Currency Type Screen

14. Transaction Display Screen

16. Kuali Student Accounts Documentation DocumentPages Classes78 Data Model58 Process Diagrams217 XML Schema70 System Settings (Configuration)20 Total443 Page count, 12 April 2013

17. Kuali Student Accounts Use KRAD User Group Forum Kuali Student AccountsOthers Threads738 Posts45133 Posts per thread6.43.5 Threads per day0.20.9 Days per thread6.31.2 Posts per day1.03.0 Data from 1 March through 13 April 2013. KSA use is trending down.

19. Kuali Student Accounts Performance Expectations and Goals Various sources, 13 April 2013

20. Nielsen on Performance 1.0.1 second (100 milliseconds) is about the limit for having the user feel that the system is reacting instantaneously. 2.1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. 3.10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays,users will want to perform other tasks while waiting. Jakob Nielsen (1993: September 23) Usability Engineering. Boston: Academic Press as excerpted in his Alert Box blog, January 1, 1993.

21. Nielsen on Performance: Principles Eradicate the term "web-based application“ because it distracts from the real issue, which is one of application UI design. The fundamental usability recommendations [are broadly applied] … since we are discussing user experience, not coding. In cases where the computer cannot provide fairly immediate response, continuous feedback should be provided to the user in form of a percent-done indicator [Myers 1985 ]. As a rule of thumb, percent-done progress indicators should [only] be used for operations taking more than about 10 seconds. Jakob Nielsen from his Alert Box blog, January 1, 1993.

22. Nielsen: College Students and Adults Jakob Nielsen (2013, February 4) Teenage Usability: Designing Teen-Targeted Websites. Alertbox blog.

23. Neilson on Teens Teens perform worse than adults (71% compared to 83%) for three reasons: Insufficient reading skills Less sophisticated research strategies Dramatically lower levels of patience Jakob Nielsen (2013, February 4) Teenage Usability: Designing Teen-Targeted Websites. Alertbox blog.

24. Response Time Expectation Click/Enter to full screen rendered Harry Shum as quoted in the New York Times, “The Blink of an Eye? Oh Please,” 29 February 2012 250 milliseconds is a Microsoft goal.

25. Google’s Response Time Goal “We want you to be able to flick from one page to another as quickly as you can flick a page on a book. So we’re really aiming very, very high here… at something like 100 milliseconds.” ~Urs Hölzle, Senior VP Operations, Google Quoted by Joshua Bixby, Web Performance Today, 23 September 2010 based on video from Urs’ presentation at Velocity in June.

26. Performance Goals Google – 100 milliseconds Microsoft – 250 milliseconds Neilsen-Tilton (in context of KSA) 100 milliseconds for added productivity 200 milliseconds for screens except 1 Second for those with complex algorithms 10 Second maximum for user attention in every case