Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Slides:



Advertisements
Similar presentations
B121 Chapter 7 Investigative Methods. Quantitative data & Qualitative data Quantitative data It describes measurable or countable features of whatever.
Advertisements

Individualized Rating Scales (IRS)
Software Process and Product Metrics
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Business Law Chapter 3: The Legal Concept of Acceptance.
Chapter 6: Thinking about requirements and describing them.
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
Requirements / Specifications. 01/18/10CS-499G2 Requirements Determine what the customer needs (wants) the software to do  What are requirements?  An.
Sample Educational Applications Key Educational Advantages User
Capital Community College 2014 Graduate Survey
Technical Communication: Concepts and Features
Pepper modifying Sommerville's Book slides
Lecture 7 After competition of this lecture students will have knowledge of the following: Design Interface Objects Micro Level Processes Macro Level.
Software Metrics and Reliability
Outcome Logic Model Guide
Cheryl Ng Ling Hui Hee Jee Mei, Ph.D Universiti Teknologi Malaysia
Exam 0 review CS 360 Lecture 8.
G&W Chapter 5: Starting Points Software Specification Lecture 12
Chapter 5 – Requirements Engineering
Prototyping Lecture # 08.
G&W Chapter 22: Test Cases Software Specification Lecture 29
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Handout 2: Providing customer service
Presentation on Measuring Service Quality
Project Points Software Specification Lecture 8
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
RELEVANCE OF QUESTIONNAIRE METHOD OF DATA COLLECTION IN SOCIAL SCIENCERESEARCH BY : POOJAR BASAVARAJ HEAD, DEPT OF POLITICAL SCIENCE KARNATAK ARTS.
Imran Hussain University of Management and Technology (UMT)
Evaluation of a hybrid peer-teaching method for undergraduate
Software Quality Engineering CS- 449
Calling all Techies & Non-Techies
Software Quality Engineering
G&W Chapter 12: The Project’s Name Software Specification Lecture 19
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Software Requirements analysis & specifications
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
CS 790M Project preparation (I)
Money Management Chapter Two Notes Planning Your Career
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 24: Making Agreements Software Specification Lecture 31
G&W Chapter 17: Preferences Software Specification Lecture 24
Thebaut’s Guaranteed Method Software Specification Lecture 5
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
G&W Chapter 19: Ambiguity Metrics Software Specification Lecture 26
G&W Chapter 25: Ending Software Specification Lecture 32
G&W Chapter 16: Constraints Software Specification Lecture 23
G&W Chapter 20: Technical Reviews Software Specification Lecture 27
Collecting and Interpreting Quantitative Data – Introduction (Part 1)
Semester 1 Reflection Directions:
Student Satisfaction Results
Delia L. Lang, PhD, MPH Elizabeth Reisinger Walker, PhD, MPH, MAT
Improvement 101 Learning Series
Axiomatic Verification I
Measuring Success How to use simple bug database queries and reports
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Select Findings from the Fall 2018 Enrolled Student Survey
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Development and Deployment of a Web-Based Course Evaluation System
COMP444 Human Computer Interaction Usability Engineering
SOFTWARE REQUIREMENT SPECIFICATION
G&W Preface Software Specification Lecture 4
G&W Chapter 14: Functions Software Specification Lecture 21
OBJECTIVE QUALITY ASSURANCE TESTS TESTING STRATEGIES
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
2000 Research Study Law Society of England & Wales
Welcome to the First-Year Experience!
G&W Chapter 15: Attributes Software Specification Lecture 22
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
Welcome to the First-Year Experience!
Presentation transcript:

Prepared by Stephen M. Thebaut, Ph.D. University of Florida G&W Chapter 21: Measuring Satisfaction Software Specification Lecture 28 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

Part V: Greatly Improving the Odds of Success Ambiguity Metrics Technical Reviews Measuring Satisfaction Test Cases Studying Existing Products Making Agreements Ending

Rationale Perhaps 90% of product development efforts fail. About 30% fail to produce anything at all, but most failures produce a product that people simply don’t like. The easiest way to avoid this problem is to measure user satisfaction as the design takes form.

Addressed to a group of students at UF: Case Study: Development of a Satisfaction Test for Graduate Students at UF Addressed to a group of students at UF: We need half-a-dozen or so attributes by which, in the final analysis, your experience as a graduate student will be evaluated. Using a round-robin approach, please identify an attribute that is important to you.

DRAFT How do you rate your graduate student experience at this time? useless useful not fun fun not satisfied with performance satisfied with performance poor interaction with faculty good interaction with faculty poor job preparation good job preparation poor course selections good course selections Students: If you fill this out each semester, will it enable you to express what you like and don’t like about your graduate student experience?

How do you rate your graduate student experience at this time? Comments? Name ___________________

Using the Satisfaction Test Each completed test has “face validity” and is therefore a useful communication vehicle. Changes in average response can reflect major shifts in satisfaction. Follow-up with an interview. 1 2 3 4 Semester

Interpreting Comments When people take the time to write something free-hand, it’s probably important. Puzzling or strongly worded comments must be tracked down. (Hypothetical) Examples: “This program stinks! I can’t even take the courses I really want to.” “I think the faculty could do much more to help students!”

Attributes of G&W’s Test Allows frequent measurement so that changes in satisfaction can be detected quickly. Provides a periodic indication of divergence of opinion. (Can warn of unrecognized ambiguity or political problems.)

Attributes of G&W’s Test (cont’d) Allows designer to pinpoint specific areas of dissatisfaction, and to identify dissatisfaction within specific user constituencies. Usually yields a high response rate. Allows designers to determine statistical reliability of the sample.

Attributes of G&W’s Test (cont'd) Provides insight into how the completed design will be evaluated. (I.e., the relative importance of attributes.) Useful to those who take it (keeps users involved) and create it. Cheap, easy to use, non-intrusive, and educational to all.

Other Tests The existence of a regular survey should never be used as an excuse for not supplementing it with other, commonsense methods. Try the occasional “How do you feel about the system right now?” You can also observe how people use, avoid, or modify a product increment or prototype to gauge satisfaction.

Prepared by Stephen M. Thebaut, Ph.D. University of Florida G&W Chapter 21: Measuring Satisfaction Software Specification Lecture 28 Prepared by Stephen M. Thebaut, Ph.D. University of Florida