Scribd
Upload
24 views14 pages

SARC Topic 2 - Quality

Software design quality testing 1

Uploaded by

Alwi Albeity
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
24 views14 pages

SARC Topic 2 - Quality

Software design quality testing 1

Uploaded by

Alwi Albeity
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Software Architecture

Topic 2
Software Quality

By: Esther Baguma (Msc)

Bachelor of Science in Software Engineering -BSSE


Quality Attributes
2

 Quality is a measure of excellence or the state of being free


from deficiencies or defects.
 Quality attributes are system properties that are separate
from the functionality of the system.
 Implementing quality attributes makes it easier to
differentiate a good system from a bad one.
 Attributes are overall factors that affect runtime behavior,
system design, and user experience. They can be classified
as follows:

© IUEA – 2020. 07/19/2024


Quality Attributes
3

Static Quality Attributes


 Reflect the structure of the system and organization,

directly related to architecture, design, source code.


 They are invisible to end-user, but affect the development

and maintenance cost, e.g.: modularity, testability,


maintainability, etc.

© IUEA – 2020. 07/19/2024


Quality Attributes
4

Dynamic Quality Attributes


 Reflect the behavior of the system during its execution.

They are directly related to the system’s architecture,


design, source code and also configuration, deployment
parameters, environment, and platform.
 They are visible to the end-user and exist at runtime, e.g.:

throughput, robustness, scalability, etc.

© IUEA – 2020. 07/19/2024


Quality Scenarios
5

Quality scenarios specify how to prevent a fault from


becoming a failure. They can be divided into six parts based
on their attribute specifications:
 Source: An internal or external entity such as people,

hardware, software, or physical infrastructure that


generates the stimulus.
 Stimulus: A condition that needs to be considered when it

arrives on a system.
 Environment: The stimulus occurs within certain conditions.

 Artifact: A whole system or some part of it such as

processors, communication channel, persistent storage,


processes etc.
© IUEA – 2020. 07/19/2024
Quality Scenarios
6

 Response: An activity undertaken after the arrival of


stimulus such as detect faults, recover from fault, disable
event source etc.
 Response measure: Should measure the occurred
responses so that the requirements can be tested.

© IUEA – 2020. 07/19/2024


Common Quality Attributes
7

1. Design Qualities:
 Conceptual Integrity - Defines the consistency and
coherence of the overall design. This includes the way
components or modules are designed
 Maintainability - Ability of the system to undergo changes

with a degree of ease.


 Reusability - Defines the capability for components and

subsystems to be suitable for use in other applications

© IUEA – 2020. 07/19/2024


Common Quality Attributes
8

2. Run-time Qualities
 Interoperability - Ability of a system or different systems to

operate successfully by communicating and exchanging


information with other external systems written and run by
external parties.
 Manageability - Defines how easy it is for system

administrators to manage the application


 Reliability - Ability of a system to remain operational over

time
 Scalability - Ability of a system to either handle increases in

load without impact on the performance of the system, or


the ability to be readily enlarged.
© IUEA – 2020. 07/19/2024
Common Quality Attributes
9

2. Run-time Qualities
 Security - Capability of a system to prevent malicious or

accidental actions outside of the designed usages


 Performance - Indication of the responsiveness of a system

to execute any action within a given time interval.


 Availability - Defines the proportion of time that the system

is functional and working. It can be measured as a


percentage of the total system downtime over a predefined
period.

© IUEA – 2020. 07/19/2024


Common Quality Attributes
10

3. System Qualities
 Supportability – Ability of the system to provide
information helpful for identifying and resolving issues
when it fails to work correctly.
 Testability - Measure of how easy it is to create test criteria

for the system and its components

© IUEA – 2020. 07/19/2024


Common Quality Attributes
11

4. User Qualities
 Userability – Defines how well the application meets the

requirements of the user and consumer by being intuitive


5. Architecture Qualities
 Correctness – Accountability for satisfying all the
requirements of the system.

© IUEA – 2020. 07/19/2024


Common Quality Attributes
12

6. Non-runtime Qualities
 Portability – Ability of the system to run under different

computing environment.
 Integrality – Ability to make separately developed
components of the system work correctly together.
 Modifiability - Ease with which each software system can

accommodate changes to its software.

© IUEA – 2020. 07/19/2024


Common Quality Attributes
13

7. Business quality attributes


 Cost and schedule – Cost of the system with respect to

time to market, expected project lifetime & utilization of


legacy
 Marketability - Use of system with respect to market

competition.

© IUEA – 2020. 07/19/2024


14

Thank you
© IUEA – 2020. 07/19/2024

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy