MS101

1. Rating Scales in Quantitative Research

Rating scales are closed-ended questions designed to measure and collect data about various characteristics,
opinions, or attitudes of respondents. They provide a systematic way for individuals to express their opinions or
preferences on a scale, allowing researchers to quantify and analyze responses.
Types of Rating Scales:
1. Likert Scale
 Description: A Likert scale asks respondents to indicate their level of agreement or disagreement with a
series of statements, typically on a scale of 1 to 5 or 1 to 7 (strongly agree to strongly disagree).
 Common Use: Measuring attitudes, opinions, and behaviors. For example, “I enjoy using this software”
with responses like Strongly Agree, Agree, Neutral, Disagree, Strongly Disagree.

2. Semantic Differential Scale

 Description: This scale presents two opposite adjectives (e.g., “easy” vs. “difficult”) with a continuum in
between. Respondents rate a subject by selecting a point between the two adjectives.
 Common Use: Measuring attitudes toward an object, product, or service.
3. Numerical Rating Scale (NRS):
 Description: Respondents are asked to assign a number to indicate the intensity of a characteristic or
feeling.
 Common Use: Rating pain intensity or satisfaction levels on a scale from 1 to 10.

4. Graphic Rating Scale:

 Description: This scale uses a visual continuum, such as a line or bar, with
numbers at the ends and respondents select a point along this line to
indicate their response.
 Common Use: Evaluating customer satisfaction or product performance.

Considerations for Designing Rating Scales:

Scale Length: Shorter scales (5 to 7 points) tend to be more reliable and easier to interpret, but longer scales
(10+ points) provide more detail.
Balanced vs. Unbalanced Scales: A balanced scale has an equal number of positive and negative options, while
an unbalanced scale might have more positive or negative options.
Neutral Option: Whether to include a neutral or undecided option, which can allow respondents who have no
opinion to select that option.
Reversal of Scales: Reversing the order of options (i.e., presenting "Strongly Agree" first in some items and
"Strongly Disagree" first in others) to reduce response bias.

2. ISO 25010 - Software Product Quality

The quality model is the cornerstone of a product quality evaluation system. The quality model determines
which quality characteristics will be taken into account when evaluating the properties of a software product.
The quality of a system is the degree to which the system satisfies the stated and implied needs of its various
stakeholders, and thus provides value. Those stakeholders' needs (functionality, performance, security,
maintainability, etc.) are precisely what is represented in the quality model, which categorizes the product
quality into characteristics and sub-characteristics.

Key Characteristics of ISO 25010:

1. Functional Suitability:
a. The degree to which the software provides the required functions and features.
 b. Sub-characteristics: Functional completeness, Functional correctness, Functional
appropriateness.
2. Performance Efficiency:
a. The software's ability to perform its functions with optimal use of resources.
b. Sub-characteristics: Time behavior, Resource utilization, Capacity.
3. Compatibility:
a. The ability of the software to operate in various environments and with other software.
b. Sub-characteristics: Coexistence, Interoperability.
4. Usability:
a. The ease with which users can learn, operate, prepare inputs for, and interpret outputs from the
software.
b. Sub-characteristics: Appropriateness recognizability, Learnability, Operability, User error
protection, User interface aesthetics, Accessibility.
5. Reliability:
a. The software’s ability to maintain performance under specified conditions and over time.
b. Sub-characteristics: Maturity, Fault tolerance, Recoverability.
6. Security:
a. The protection of software from unauthorized access and modification, ensuring the integrity of
data.
b. Sub-characteristics: Confidentiality, Integrity, Non-repudiation, Accountability, Authenticity.
7. Maintainability:
a. The ease with which the software can be modified to fix defects, improve performance, or adapt
to a changed environment.
b. Sub-characteristics: Modularity, Reusability, Analyzability, Modifiability, Testability.
1. Portability:
a. The ability to move the software from one environment to another.
b. Sub-characteristics: Adaptability, Installbility, Replaceability.

B. Designing a Questionnaire Based on ISO 25010 Criteria Using Likert Scale

Below is a sample questionnaire designed using these criteria, employing a Likert scale (1 to 5), where:
1 = Strongly Disagree
2 = Disagree
3 = Neutral
4 = Agree
5 = Strongly Agree

Questionnaire on Software Quality (ISO 25010)

1. Functional Suitability

Q1.1:The software meets the functional requirements as specified.

Q1.2: The software performs all intended functions correctly.
Q1.3: The features of the software are useful and fulfill the tasks I need.
 2. Performance Efficiency

Q2.1:*The software performs tasks in a timely manner.

Q2.2:The software does not experience significant delays during regular use.
Q2.3: The system can handle large volumes of data without a performance degradation.

3. Compatibility

Q3.1: The software works seamlessly with other systems or applications I use.
Q3.2: The software is compatible with different operating systems (e.g., Windows, macOS, Linux).
Q3.3: The software integrates well with third-party services and APIs.

4. Usability

Q4.1: The software has an intuitive and easy-to-use interface.

Q4.2:I can accomplish tasks without needing extensive training or support.
Q4.3: The software provides helpful guidance (e.g., tooltips, tutorials) when I need it.
5. Reliability

Q5.1: The software functions correctly without errors or crashes.

Q5.2: The software performs consistently over extended periods of use.
Q5.3: I have not experienced data loss or corruption while using the software.
6. Security

Q6.1:The software ensures my personal and sensitive data is protected.

Q6.2:I trust that the software handles security breaches effectively.
Q6.3: The software includes features such as encryption or authentication to safeguard my information.

7. Maintainability

Q7.1: The software allows for easy updates and bug fixes.
Q7.2:The software's code is well-documented, making it easier to maintain.
Q7.3: The software’s architecture supports easy modification and scalability.

8. Portability

Q8.1: The software can be easily installed and used on different devices (e.g., desktop, mobile).
Q8.2: The software can be easily transferred or installed across multiple platforms.
Q8.3: The software works consistently across various environments or configurations.
Scoring and Interpretation:
Each response is scored on a scale of 1-5. To interpret the results, follow these steps:
1. Calculate the average score for each section (Functional Suitability, Performance Efficiency, etc.).
2. Interpret the averages: 1.0 to 2.0: Poor quality in this area. - 2.1 to 3.0: Needs improvement. - 3.1 to 4.0:
Satisfactory. - 4.1 to 5.0: Excellent quality in this area.
Questionnaire Goal: This questionnaire is designed to evaluate the overall software quality from the user
perspective using ISO 25010 criteria.
Target Audience: Users, testers, developers, or any stakeholders familiar with the software.
Customizable: This template can be adapted to the specific software being tested by modifying the questions
based on context and functionality. This structure will give a comprehensive view of the software’s strengths and
weaknesses, highlighting areas needing attention.