Post on 05-Jan-2016
KSA by the Numbers
Data extracts represented as charts with references. The slides are organized by source and time.
Last updated 14 April 2013
Kuali Implementation Status
Source/imm/I130411F, 11 April 2013
Kuali Governance and Collaboration
Project Teams
User Groups Total
Kuali Financial System 37 7 44Kuali Student 26 2 28Kuali Research Administration 26 6 32Kuali Rice 19 3 22Kuali Ready 9 0 9Kuali OLE 30 2 32Kuali People Management 9 1 10Kuali IT Support 3 0 3Kuali for Government 1 0 1Kuali Mobility 5 1 6Kuali Foundation 34 34
Count 199 22 221
Kuali Student Accounts Performance
Source/imm/I130413F, 11 April 2013
Response time measures
Screen Response Time Calls, top 3 "lines"
Currency Type 330 milliseconds 847
Transaction Display 17.4 seconds 7.2 million
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.
Currency Type Screen
Transaction Display Screen
Kuali Student Accounts Documentation
Document Pages
Classes 78
Data Model 58
Process Diagrams 217
XML Schema 70
System Settings (Configuration) 20
Total 443
Page count, 12 April 2013
Kuali Student Accounts UseKRAD User Group Forum
Kuali Student Accounts Others
Threads 7 38
Posts 45 133
Posts per thread 6.4 3.5
Threads per day 0.2 0.9
Days per thread 6.3 1.2
Posts per day 1.0 3.0
Data from 1 March through 13 April 2013. KSA use is trending down.
Kuali Student Accounts Performance Expectations and Goals
Various sources, 13 April 2013
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.
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.
Nielsen: College Students and Adults
Jakob Nielsen (2013, February 4) Teenage Usability: Designing Teen-Targeted Websites. Alertbox blog.
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.
Response Time ExpectationClick/Enter to full screen rendered
Harry Shum as quoted in the New York Times, “The Blink of an Eye? Oh Please,” 29 February 2012250 milliseconds is a Microsoft goal.
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.
Performance Goals
• Google – 100 milliseconds• Microsoft – 250 milliseconds• Neilsen-Tilton (in context of KSA)
100 milliseconds for added productivity
200 milliseconds for screens except1 Second for those with complex algorithms10 Second maximum for user attention in every case