Quality Attribute Scenario : is a format for defining a testable scenario for a system

Reliability

Source of stimulus Human system System database server

Stimulus Trigger of the scenario database crashes
Environment What are the conditions when the stimulus occurs runtime with average load
Artifact what elements of the system are stimulated database
Response the activity undertaken after the occurrence of the stimulus detect the failure, inform the sys-adm, use redundant database server
Response measure When the response occurs it should be measurable so that the requirements can be tested seconds until recovery is at most 120

Capability Maturity Model Integration (CMMI)

Software Quality Assurance Chapter 1 Software Quality Assurance Chapter 3 Laying out a generic path to process improvement for a software organization
Management &
Level 1 : initial Level 2 : Repeatable Level 3 : Defined Engineering processes documented
Standardized, Integrated, and actually used
Code error ad hoc basic management processes
Procedure error
Incorrect code as a result of
Documentation error Software Errors grammatical or logical mistake by the developer Measured and monitored and controlled
Software data error Level 5 : Optimizing Level 4 : Managed
using measurements
SQA Environment Software faults
Software errors that cause the Continues process improvement is enabled
Software incorrect functioning of the software by quantitative feedback from the process
products Other Products During specific application and from piloting innovative ideas and technologies
1. Contractual Conditions 2. Subjection to customer-supplier relationship The nine causes for it Software faults that are activated
Software failures that is when a user tries to apply
Fundamental Difference
List of functional requirements 1. Faulty requirement definition the specific faulty software section should be
Change requests -> Feedback -> Approval 2. Client-developer communication failures Quality Attributes : is a measurable or testable property of a system that is used to indicate - Objective
caused by Project budget
The only phase 3. deliberate deviations from sofware requirements how well the system satisfies the needs of its stakeholders - In sufficient detail
can be measured by The root of any software failure is a software error
where defects can Project Timetable 4. Logical design error Functional Suitability
the number of operational can
be detected 5. Coding errors Quality Requirements : is a specification of the acceptable values of a quality attribute be
Higher Complexity modes the product evalu
6. Non-compliance with documentation and coding instructions that must be present in the system ated
permits Example
7. Shortcomings of the testing process Reliability by change scenarios for assessing maintainability
Invisibility of Software Scenario-based evaluation
8. Procedure errors
Defects in software 3. Required Teamwork 4. Interfaces with other software systems Example
Nature of The product development 9. Documentation error Attributes of software that bear on its ability Prototyping is a form of simulation
are invisible Performance Efficiency Simulation
Nature of production process 1. Functionality : Security to prevent unauthorized access, whether accidental where a part of the architecture
TimeTable requirements Input Interface
or deliberate, to programs and data. is implemented and executed in
Need For Specializations There are basic quality models and tailored quality models Level 0 : no security at all the actual system context
Output interface
Comparison software product quality Operability Level 1 : firewalls number of successful intrusions
Benefit From Professional Mutual Support
Measurement is L
Level 2 : encryption sc
total number of intrusion attempts Example
Basic Quality Models Tailored Quality Models Mathematical modeling Checking for potential deadlocks, performance, reliability
Level 3 : authentication (digital ID verification)
Security 0.1 ~ 0.001 level 1
characteristics Software products Other Products Example this is based on subjective factors like intuition and
Level 4 : intrusion protection 10-7 ~ 10-9 level 4 Experience based assessment
5. The need to continue carrying out a project despite team member changes Mc Call Boehm FURPS Dromey ISO 9126 Bertoa Geogiadou CapGemini expertise of software engineers
Usually very complex Lower degree of complexity Compatibility Level 5 : combination of level 1-4
Complexity allowing very large Functionality
number of operational
allowing at most few 6. The need to continue carrying out software maintenance for an extended period Rawashdek OpenBRR Andreu ISO 25010
options thousands operations Usability
Alvaro Maintainability The set of attributes that bear on the effort needed for use
Reliability SQO - OSS QualOSS Upadhyay
11 factors Performance 3. Usability and on the individual assessment of such use, by a stated
visible product Transferability
Summary
Invisible product Al-Badareen Quamoco Midas or implied set of users
supportability
Visibility impossible to detect allowing effective detection
defects by sight of defects by sight Defined as the number of available functions / (divided) the number of system required functions
Product Transition Factors Product revision factors
Portability Maintainability UA = (Naf / Nrf) * 100%
Nature of Chances to detect defects Chances to detect defects
arise only in one phase 1. Being contracted Reusability Flexibility
Development arise in all phases of development one of it's features was to standardize the terminology regarding quality of software
development & production Interoperability Testability
& 1. development 2. subjection to customer-supplier relationship Product operation Factors
Production 2. Planning Functionality
3. Manufacturing 3. Requirements for team work Correctness
Reliability Portability Reliability
4. Need for cooperation and coordination with other development teams Efficiency Maintainability Usability
5. Need for interfaces with other software systems Integrity
Usability Efficiency
6. Need to continue carrying out a project while the team changes

7. Need to continue maintaining the software system for years

Internal Metrics do not rely on software execution

Applied to running software External Metric Quality Lifecycle

Quality in use Metrics

Software Quality Assurance Chapter 2 Applied when the final product is used in real conditions
Functionality : is the set of attributes that bear on the existence
of a set of functions and their specified properties. The functions are those
that satisfy stated or implied needs
Reliability : is the set of attributes that bear on the capability of software to maintain
What is software? Components of Software? its level of performance under stated conditions for a stated period of time
They activate the computer to perform applications Quality in use
Computer programs, procedures, and possibly Computer programs Usability : is the set of attributes that bear on the effort needed for use
associated documentation and data pertaining procedures Effectiveness : the capability of the software product to enable users to achieve and on the individual assessment of such use, by a stated or implied set of users
to the operation of a computer system documentation specified goals with accuracy and completeness in a specified context of use Efficiency : is the set of attributes that bear on the relationship between
Parameters, codes and name lists
data necessary for operating the software system the level of performance of the software and the amount of resources
Standard test data Productivity : the capability of the software product to enable users to expend Views used, under stated conditions
software quality assurance always appropriate amounts of resources in relation to the effectiveness achieved in a
includes in addition to code quality, They define : specified context of use Maintainability : is the set of attributes that bear on the effort needed
Users
the quality of the procedures, the 1. The order and schedule in which the programs are performed to make specified modifications
documentation and the necessary Safety : the capability of the software product to achieve acceptable levels
2. The method employed of risk of harm to people, business, software, property, or the environment Portability : is the set of attributes that bear on the ability of software
software data 3. The person responsible for performing the activites in specified context of use to be transferred from one environment
Managers Developers
People's quality expectations rely upon are two folds Satisfaction : The capability of the software product to satisfy users
Developers => Development documentation in a specified context of use
1. software must do what they are supposed User => User's documentation
to do Maintenance Personnel => Maintenance documentation
2. They must perform these specific tasks correctly Alternative frameworks and focus on correctness

Many companies and communities

associated
with different application domains IBM used for their software products
Example
Have adapted and customized Quality attribute list CUPRIMDS
existing quality frameworks
capability
to define quality for themselves,
usability CUPRIMDS is often used together with overall
taking into consideration their
performance customer satisfaction to characterize and
specific business and market
reliability measure software quality for IBM's software products
environment
installation
maintenance
documentation
service