Upload
griffin-reeves
View
216
Download
1
Embed Size (px)
Citation preview
IT QM BratislavaIT QM Bratislava
IT QM Part2 Lecture 5IT QM Part2 Lecture 5
Dr. Withalm Apr 19, 2023
IT QM Bratislava19.04.23 Dr.Withalm3
Lectures at the University of Bratislava/Spring 2014
27.02.2014 Lecture 1 Impact of Quality-From Quality Control to Quality Assurance
06.03.2014 Lecture 2 Organization Theories-Customer satisfaction-Quality Costs
13.03.2014 Lecture 3 Leadership-Quality Awards
20.03.2014 Lecture 4 Creativity-The long Way to CMMI level 4
27.03.2014 Lecture 5 System Engineering Method-Quality Related Procedures
03.04.2014 Lecture 6 Quality of SW products
10.04.2014 Lecture 7 Quality of SW organization
IT QM Bratislava19.04.23 Dr.Withalm6
Today’s Agenda
• Testing• Definition• Structuring• V-Model• Testlevels• Types of Tests (Black Box- White Box)
• White Box (C0, C1, C2)• Testcases• End of Test Criteria• Conducting Tests• Test Evaluation
• SW Quality Evaluation• Motivation• Quality Characteristics (Subcharacteristics, List of Criteria, Evaluation Procedures)• Conclusions
• Technology Management Process
IT QM Bratislava19.04.23 Dr.Withalm7
Problem
Bill Gates: “50 % of development effort
goes into software testing“
Without professional testing• “old” errors are repeated• hardly any methods & tools are used
What we need:“Best practices” for test planning and test management(methods, tools, etc.)
IT QM Bratislava19.04.23 Dr.Withalm8
10 FAQs about testing
1. What is the purpose of testing?
2. What is being tested?
3. How does testing fit into the development
process?
4. How do you test?
5. How are test cases prepared?
6. How much testing do you need?
7. How are tests conducted?
8. How are tests evaluated?
9. Prerequisites for successful testing?
10. What tools does the SC Test offer?
IT QM Bratislava19.04.23 Dr.Withalm9
Definition of the term “test”
Two points of view:
Systematic verification of design and implementation for compliance with specified requirements.
The purpose of testing is to find bugs
The key motive for testing is to provide verifiableevidence of quality to the customer.
IT QM Bratislava19.04.23 Dr.Withalm10
Structuring of testing
Testing of functional and non-functional requirements
• Functionality, user interface behavior, input field syntax, installation, etc.
• Performance, reliability and availability,
usability etc.
It is necessary to break down the test budgetaccordingly.
IT QM Bratislava19.04.23 Dr.Withalm11
Testing in SEM
Draw up test plan
Design test cases
Set up test infrastructure
Conduct test
Evaluate test
Fault management
Prepare test reports
Initiation
Prototyping
Definition Design Implementation Operations
Termin-ation
Themes relating to multiple phases
IT QM Bratislava19.04.23 Dr.Withalm12
“V” model
Black boxTestSW Req. Spec.
Design
Detailed Design
System Test
Black boxand
White box Test
Integration &Integration Test
Component Test
DevelopmentDocuments
Test LevelsCoding
IT QM Bratislava19.04.23 Dr.Withalm13
General process model
SW req. spec.
Arch. design
Detailed design
System test
Integration test
Unit test(stand-alone test)
VerificationValidation
Implementation
User req. spec. Acceptance test
IT QM Bratislava19.04.23 Dr.Withalm14
Test levels (1)
Stand-alone test (component test): Test of a single component or of groups of components
Integration test: Test to verify interfaces and how components
interact via such interfaces
System test: Test of the finished system against the functional and non functional
requirements as i.e. performance defined in the requirements specification.
IT QM Bratislava19.04.23 Dr.Withalm15
Breaking the tests down into different levels
helps to bring complexity under control.
Test levels (2)
Acceptance test:Test cases are a subset of System Test
Should be established by customer
Usually performed on customer site
IT QM Bratislava19.04.23 Dr.Withalm16
Types of tests
White box (structure oriented test):• Control flow oriented
– Instruction coverage (C0)– Branch coverage (C1)– Path coverage and other types of coverage
• Data flow oriented
Black box (function oriented test):• Functions as laid down in SW requirements specification• Syntax• States, state transitions
Non-functional requirements e.g. performance, stability, usability
IT QM Bratislava19.04.23 Dr.Withalm17
White box(structure oriented) test
Detailed design
Code structure
Test data
Test results
Flow of control
Flow of data
IT QM Bratislava19.04.23 Dr.Withalm18
Possible goals:
• Go through as large parts of code as possible (coverage test)
• Identify memory leaks
• Identify conflicts between different threads and processes
• Analyze performance behavior
• Check robustness
White box test/1What is dynamic code analysis ?What is dynamic code analysis ?
In contrast to static analysis, the code is executed and tested with a set of test data
IT QM Bratislava19.04.23 Dr.Withalm19
Test Planning
Define goals, scope, methods, resources,time schedule, responsibilities
Test Design
• Define how the goals in the test plan can be reached
• e.g. what goal will be reached by which test method
• Elaborate details of test methods
• Define test objects, environment and test end criteria
White box test/2Test planning / Test designTest planning / Test design
IT QM Bratislava19.04.23 Dr.Withalm20
White box test/3Types of coverage/1Types of coverage/1
C0 coverageEach statement is executed once
void CoverMe (int a, int b){ printf("A"); if (a < 1) printf("B"); printf("C"); if (b < 2) printf("D"); printf("E");}
In this example, 1 test case will be sufficient(a=0, b=1 => ABCDE)
A
C
B
E
D
IT QM Bratislava19.04.23 Dr.Withalm21
C1 coverageEach branch is executed once (‘if’ or ‘case’ statements)
void CoverMe (int a, int b){ printf("A"); if (a < 1) printf("B"); printf("C"); if (b < 2) printf("D"); printf("E");}
For C1 coverage, you need at least 2 test cases in this example (a=0, b=1 => ABCDE, a=1, b=2 => ACE)
White box test/4Types of coverage/2Types of coverage/2
A
C
B
E
D
IT QM Bratislava19.04.23 Dr.Withalm22
White box test/5Types of coverage/3Types of coverage/3
C2 coverageEvery possible path is executed once
void CoverMe (int a, int b){ printf("A"); if (a < 1) printf("B"); printf("C"); if (b < 2) printf("D"); printf("E");}
For C2 coverage, you need 4 test cases(a=0, b=1 => ABCDE, a=1, b=2 => ACE, a=0, b=2 =>
ABCE, a=1, b=1 => ACDE)
A
C
B
E
D
IT QM Bratislava19.04.23 Dr.Withalm23
White box test/6Types of coverage/4Types of coverage/4
Sub-condition coverageEach sub-condition must be at least once true and once false.
if ((a < 1) && (b < 2)) requires 2 test cases
Sub-condition combination coverageEvery possible true/false combination of sub-conditions is verified once
if ((a < 1) && (b < 2)) requires 4 test cases
IT QM Bratislava19.04.23 Dr.Withalm24
White box test/7Defining the required coverageDefining the required coverage
For each code part, you have to decide which type ofcoverage is required and what percentage has to becovered.
Key criteria in this context:
• How complex is the code ? (e.g. McCabe complexity)
• Is the code new or reused ?
• How security-critical is the module ?
• How often is the module executed ?
• How experienced are the developers ?
Code for handling situations that occur only very rarely can be tested by including additional control variables in the code.
IT QM Bratislava19.04.23 Dr.Withalm25
Black box (function oriented) test
Requirements spec.
Preliminary/detailed design
Test data
Test results
IT QM Bratislava19.04.23 Dr.Withalm26
Preparing test cases
• Define end-of-test criteria (in the test plan)
• Create a test structure
• Define the different types of test
• Implement test cases for each type of test
• Never forget: Test cases should be entered in CM
Test structure for system test:
• generated through import of SW requirements
specification (chapter structure) or manually
• contains test packages (for each test type)
as well as test cases
IT QM Bratislava19.04.23 Dr.Withalm27
Test package, test case
Test package:• Unambiguous name• Test type
Test case:• Unambiguous name• Goal/purpose of test case• OK/Not OK• Manual/automated• Hardware / software configuration• Initial state of test object• All input data• Test sequence, individual test steps• Expected result for each test step• To which Requirement it belongs
IT QM Bratislava19.04.23 Dr.Withalm28
End-of-test criteria (examples)
Test type End-of-test criterion
Instruction coverage (C0): 100% and function fulfillment
Branch coverage (C1): 50%-95% (module type)
and function fulfillment
Functions as specified: 100% of test cases “OK“
Syntax: 100% of test cases “OK“
State-based: All states and transitions covered
Performance: Response time under load conditions (< x sec)
IT QM Bratislava19.04.23 Dr.Withalm29
Conducting tests
Execute the manual and automated test
cases
Prepare a test suite by selecting suitable test cases
Record test results in a test management tool to beable to report on test progress at the simple push ofa button. Integration with CM?
IT QM Bratislava19.04.23 Dr.Withalm30
Test evaluation (ongoing)
Draw up test reports
Analyze unsuccessful test cases
Collect diagnostic data for fault identification
Record the faults you found in a fault management system (Important: link between test run, test case, and fault number)
Update regression tests (CM!?)
Enter the faults found in each phase in PROWEB
IT QM Bratislava19.04.23 Dr.Withalm31
Success factors
Project team strives for quality
Sufficient budget (recommendations)
20 to 30% of total effort
During maintenance: up to 50 %
Testability has been taken into account of in
design
Use standards and checklists !
Regard testing as a major part of the project
Milestones have been defined
Test infrastructure is available
IT QM Bratislava19.04.23 Dr.Withalm36
TestSummary
Testing is supposed to verify functional and non-functional requirements find the most important bugs
Testing is an integral part of the development process
Testing needs defined quality requirements defined end-of-test criteria suitable tools
IT QM Bratislava19.04.23 Dr.Withalm37
•Software Quality Evaluation up to now •predominantly focused on errors
•Residual error probability
but
•Quality is more than freedom from error
Software Quality Evaluation/1
Motivation
IT QM Bratislava19.04.23 Dr.Withalm38
Software Quality Evaluation/2Quality Characteristics
reliability
functional performance
user friendliness
time behavior
consume behavior
maintainability
portability
IT QM Bratislava19.04.23 Dr.Withalm39
Software Quality Evaluation/3 Actions in SEM phases
Application of SEMQuality Evaluation
Definition of qualityobjectives
Direction for technicaland quality assuranceactivities
Examination if qualityobjectives are reached
SEM Phases
InitiationStudy
System DesignDetailed DesignImplementationIntegration
System TestAcceptance
IT QM Bratislava19.04.23 Dr.Withalm40
Software Quality Evaluation/4Proceeding
Definition Quality characteristics Subcharacteristics
List of criteria / checklists
Evaluation procedures
IT QM Bratislava19.04.23 Dr.Withalm41
Software Quality Evaluation/5Subcharacteristics / 1
Quality characteristicsin terms of SN 77 350
reliability
functional performance
user friendliness
time behavior
Subcharacteristics
availabilitysafety
completenessCorrectness
learnabilityease of handling
response timestart-up timethroughput rateholding timeCPU-requirementCPU-load
back up
IT QM Bratislava19.04.23 Dr.Withalm42
Software Quality Evaluation/6Subcharacteristics / 2
Quality characteristicsin terms of SN 77 350
consume behaviour
maintainability
portability
Subcharacteristics
primary storage requirementperipheral storage requirementperipheral device requirementoutput volume
-
technical portabilityadaptability
back up
IT QM Bratislava19.04.23 Dr.Withalm43
Software Quality Evaluation/7Evaluation Procedures
measuring point scaling system evaluation tree
functional performance project specific procedures
back up
IT QM Bratislava19.04.23 Dr.Withalm44
Software Quality Evaluation/8Point scaling system/1
• Criteria have been defined and may be summarized in criteria groups
• To each criteria points are allocated
0 Not satisfied at all1 Rarely satisfied2 Partly satisfied3 Satisfied to a large degree4 Completely satisfied
IT QM Bratislava19.04.23 Dr.Withalm45
Software Quality Evaluation/13Ease of Handling/2 Accessibility
1) Conformity2) Transparency 3) Consistent behavior4) Consistent terminology5) Clarity6) Uniformity7) Easy access to functions8) Easy start9) Self-explanatory features
IT QM Bratislava19.04.23 Dr.Withalm46
Software Quality Evaluation/9Point scaling system/2
• Not relevant criteria will be omitted
• The points are added up for every criteria group and standardized•Sum total of the points is divided by the maximum number of points•value range of 0 to 1
• The quality index of a subcharacteristic is determined by forming the mean of all the criteria groups involved.
• The specification of the quality index must always be accompanied by the evaluations of the individual criteria
IT QM Bratislava19.04.23 Dr.Withalm47
Software Quality Evaluation/10Important Quality Characteristics/1
•User friendliness•Learnability•Ease of handling
•Reliability•Availability•Safety
•Functional performance•Completeness•Correctness
IT QM Bratislava19.04.23 Dr.Withalm48
Software Quality Evaluation/11User friendliness/1
Definition (SN 77 350):
Ability of the unit under examination to require a minimum operating effort from its prospective users and to give the users a positive impression of its handling.
Note 1:Operation in this contexts extends also to the preparation of the
application and the utilization of its results.
Note 2:Operation efforts are also incurred by the users when learning how
to operate the unit under examination.
Subcharacteristics: LearnabilityEase of handling
IT QM Bratislava19.04.23 Dr.Withalm49
Software Quality Evaluation/12User friendliness/2 Ease of Handling/1
Definition:
Ease of handling is the extent to which the unit under examination is able to enable an experienced user to use the provided functions with a minimum handling effort.
Criteria groups:
AccessibilityRobustnessConvenience
IT QM Bratislava19.04.23 Dr.Withalm50
Software Quality Evaluation/14Ease of Handling/3 Robustness
1) Tolerance with respect to unexpected operator interventions
2) Tolerance with respect to environment failures
3) Damage minimization
4) Reset ability
IT QM Bratislava19.04.23 Dr.Withalm51
Software Quality Evaluation/15Ease of Handling/4 Convenience
1) Ergonomic output (SN 77 351: Screen form design) 2) Attractive Design 3) Graphic symbols 4) Small number of input characters 5) Early plausibility checks 6) Flexibility 7) Convenient operator control elements 8) Expert mode 9) Response time10) Capability of controlled abortion11) Small number of parameters12) Programming language specific interfaces
IT QM Bratislava19.04.23 Dr.Withalm52
Software Quality Evaluation/16Important Quality Characteristics/2
•User friendliness•Learnability•Ease of handling
•Reliability•Availability•Safety
•Functional performance•Completeness•Correctness
IT QM Bratislava19.04.23 Dr.Withalm53
Software Quality Evaluation/17Functional Performance Assessment Tree
FV= 0,8218
p= 100
F 1
V 1= 0,847p 1 = 40
F 2 V2= 0,805
p 2= 60
F 11
V11= 0,83p 11= 90
F 12
V12= 1p 12= 10
F 21
V21= 0,9p 21= 50
F 22
V22= 0,75p 22= 10
F 23
V23= 0,7 p 23= 40
F 211
V211= 1p 211= 30
F 212
V212= 0p 212= 10
F 213
V213= 1p 213= 60
v J=
(p, x V,)j
100
v 21=30 x 1 + 10 x 0 + 60 x 1
100= 0,9
Fi…function identifier
Pi….function weight
Vi….completeness index
IT QM Bratislava19.04.23 Dr.Withalm54
Software Quality Evaluation/18Cost/Benefits
Exact definition of requirements savesCongestionWrong assignment of development capacityUnexpected requests during acceptance
Early counter measures through better reviews savings
Practical experience for developers
Better products
IT QM Bratislava19.04.23 Dr.Withalm55
Software Quality Evaluation/19Conclusion/1
are indicators
exact evaluation by means of single criteria
Indicators support in
Steering of the development processComparing of different versions of a product
IT QM Bratislava19.04.23 Dr.Withalm56
Software Quality Evaluation/20Conclusion/2
Definition of Quality characteristics in requirements specificationProject accompanying forecast about the anticipatory qualityObjective criteria during acceptance
IT QM Bratislava19.04.23 Dr.Withalm57
Technology Management-Process/1
Technology management ensures: the detecting of new technology trends, the selecting of appropriate technologies, the expanding of the know-how required with regard to
the selected technologies, the profitable applying of those technologies.
The phases result from the definition consists of: detecting selecting expanding applying
IT QM Bratislava19.04.23 Dr.Withalm58
Technology Management-Process/2
Networking involves four steps: Call for Network One ore more persons show their interest in a certain subject for
which no network exists yet by posting a Call for Network. Interest Net A group of people that is interested in a certain subject. The focus is on
getting to know each other and everybody’s particular strengths. The network finances
itself. At least 3 people (typically 5 - 50) are required from at least 2 different
subdivisions. Expert Net A networking group of experts in a certain subject field offering coaching
and consulting within PSE and professional handling of inquiries. At least 3 people
(typically 5 - 20) are required from at least 2 different subdivisions. Support Centers A core team and a PSE-wide competence network for long-term and
strategically important subjects. They offer 3 hours of support for projects without
charge; if more time is required, this will be charged to the respective project account.
IT QM Bratislava19. April 2023 Dr.Withalm59
1990: Study "performance Measurement in enterprises of the future" (e.g. General Electric, Hewlett-Packard, Shell, Canada, Apple computer, Bell South)
History of the Balanced Scorecard
1992: "Balanced Scorecard" by Kaplan and Norton in Harvard developed and in the mean time introduced by many considerable enterprises world-wide very successfully
IT QM Bratislava19. April 2023 Dr.Withalm60
Balanced scorecard (BSC)
Kaplan and Norton, Harvard BusinessSchool, 1992:
Managing based on balance sheets (i.e. outcomes, post facto) is too inertIt is necessary to address the factors that lead tooutcomes:
- Identify impacting factors (drivers) - Strategically define objectives- Monitor achievement (metrics)
Not just keep an eye on finances, but also on- Customers/market- People / innovation- Internal processes
The focus is on business strategy
IT QM Bratislava19. April 2023 Dr.Withalm61
Balanced Scorecard (BSC) at PSE
Joint definition of strategic goals, relatedobjectives and their interrelations(strategy map) by the management
- Overall BSC at the PSE level- Business-specific BSCs in the subdivisions and business
units
Ongoing monitoring of a limited number ofquantities at all levels
- "BSC cockpit" with traffic light representation, early warning
indicators, need for action
IT QM Bratislava19. April 2023 Dr.Withalm62
What is Balanced Scorecard (BSC)?
• Comprehensive strategic control instrument
• Holistic, interlaced view on the enterprise
• Integrates modern management beginnings
•Customer orientation
•Process orientation
•Coworker orientation
•Innovation and learning
• Common systematic development of
•Business drivers
•Goals and measures
Basis is a clear, well prepared strategy!
IT QM Bratislava19. April 2023 Dr.Withalm63
Late indicatorsMonetary characteristic numbersExternal perspective Results (= effect)
Early indicatorsNot-monetary characteristic numbersInternal perspective Causes
Why "balanced"?
IT QM Bratislava19. April 2023 Dr.Withalm64
Elements of the Balanced Scorecard
Visionand
Strategy
Customer Market
Coworker Innovation
Finances
Internal Processes
4 Quadrants
IT QM Bratislava19. April 2023 Dr.Withalm65
Proceeding for the development of a BSC
• Determine the substantial success factors for the successful conversion of the strategy
•business drivers• Development of the effect connections
•driver tree
• Formulation of goals
•quantifiable, scheduling
• Determination of metrics
• Resolution of measures
IT QM Bratislava19. April 2023 Dr.Withalm66
Domaincompetence
DomainKnow How
Care & increaseOf market
TechnicalCompetence
(ICT)
Customersatisfaction
Motivation ofemployees
Training of employeesFocused on new
products
Customersatisfaction
Identifikation ofemployees
Allround- and broad Know-How
Adherence ofaccomplishment
Adherence ofexpenditures
Adherence ofdelivery
Fast reaction to inquiries
Acquisition ofprojects
Many mainpillars
Newacquisitions
Increase ofmarket
Acquisition
Motivation of employeese.g.. by setting-up
of new main pillars
Motivation ofemployees
Knowledge of newSW-technologies
technical authority in technology,
products and industry
Know-how with the integration
of adjacent systems
Training of newtechnologies
Success factors - example
IT QM Bratislava19. April 2023 Dr.Withalm67
Success factors<>Business driver
Portfolioanalysis of the success factors
passive
ac
tiv
e
Access to market
Successfull cooperations
Competitiveness
Asset Management
Motivated employees/managers
Position on Market
Suitable new orders
Appropriate employees/managers
Customer relationship
Knowledge of market
Fullfillment of project plans
Know How
Improvement of costs
reactive
active
inactive
critical
IT QM Bratislava19. April 2023 Dr.Withalm68
Employees /Knowledge/Innovation
Finances
Customer / Market
Processes
value of the business contribution
Customer loyalty
OntimeSupply
ProcessQuality
ProcessCycle time
Knowledge ofemployees
Bring your statements in cause effect connection: The more largely..., the...
Cause-and-Effect chain Example
IT QM Bratislava19. April 2023 Dr.Withalm69
PSE's strategy map
Learning / growth
Customer/market Finances
Internal processes
Expand and improve customer
relations
Focus growthon corebusiness
Expand external
partnerships
Achieve competitive
prices
Safeguard long-term business
success
Improve cost management
Increase innovative strength
Optimizestaff
competence
Increasestaff
motivation
Expand cooperation
in international PSE group
Expand knowledge networking
Optimizing the quality of services
Expand entire PSE marketing activities
"Live"leadership
PSE quality goal
IT QM Bratislava19. April 2023 Dr.Withalm70
FinancesCustomer/Market
EVA
Domaincompetence
TechnicalCompetence
(ICT)
Innovation-oriented
Internalcooperation
Leadershipskills
Close to theEnd customer
Motivation ofemployees
(International) Care & Increase
Of Market
Internationality
Process optimizationIn regard of market
Strat. CooperationsBuilding of partnerships
Employee / Innovation Internal Processes
Driver Tree - Example
IT QM Bratislava19. April 2023 Dr.Withalm71
Driver Measurement/entity
% turnover of new
Products(< 5 years))
% Status green„To Plan“
Barometer:% Commitment . % rate of return
Old/new products
Mio. €
% from turnover
Mio. DEM #Turns
EVA(Economic Value
Added)
Account balance
EBIT(Earnings before interest
And taxes)
EBIT-Assets EBIT Asset turn
Mio. € cumulative
% gap to CMMI level 3
closed
Benchmarking
Savings from BIP
Market/CustomerMarket/Customer FinancesFinances
ProcessesProcessesEmployeer / InnovationsEmployeer / Innovations
Actual
05/06
Target
05/06
Actual05/06
Target
05/06
Driver Measurement/entity
Driver Measurement/entity
DriverMeasurement/entity
% gap of cost closed
Turnover in Mio €
% in USA % in China
Upgrading systems/servicesMarket share in new focus markets
Keep #1 Position/RWS
% deliveries „on time“% building of team proces
finalized
Mio. €
A-Projects acc. R&D Plan
Skills & Competences
Corporate Identity/Culture
-30.5
-13.5
1.3
4662.4
% internal RG/BG % external customer
Customer satisfaction
30.2
28.0
1.7
4082,7
374
-
78.8
75
0
43
6650
30 -
CC
CC
CC
CC
21.3 6.2
BD
BD
BD
GZ374
23 -
150RWS
80
0
GZ-MS
6229
0
86
43
CC
HR
BD
00
62
0
60.9
LO
BMT
CC
Aherence of delivery
(2 days tolerance)
SW Process Improvement BD
Responsibility
Respo
nsibility
Target
05/06Actual05/06
Responsibility
Responsibility
Target
05/06
Actual05/06
Balanced Scorecard - Example
- -
IT QM Bratislava19. April 2023 Dr.Withalm73
Benefit of Balanced Scorecard?
• Broad consent and common understanding of the strategy
• Clear adjustment on the substantial common goals
• Balance of the relevant success factors of the business
•business driver
• Clarify the effect connections of the business
• Strategy well communicatable
• Simple position-fixing
Important: Take time !
IT QM Bratislava19.04.23 Dr.Withalm75
Farbpalette mit Farbcodes
Primäre Flächenfarbe:
R 215G 225B 225
R 130G 160B 165
R 170G 190B 195
R 220G 225B 230
R 145G 155B 165
R 185G 195B 205
R 255G 210B 078
R 229G 025B 055
R 245G 128B 039
R 000G 133B 062
R 000G 000B 000
R 000G 084B 159
R 255G 255B 255
Sekundäre Flächenfarben:
Akzentfarben:
R 255G 221B 122
R 236G 083B 105
R 248G 160B 093
R 064G 164B 110
R 064G 064B 064
R 064G 127B 183
R 255G 232B 166
R 242G 140B 155
R 250G 191B 147
R 127G 194B 158
R 127G 127B 127
R 127G 169B 207
R 255G 244B 211
R 248G 197B 205
R 252G 223B 201
R 191G 224B 207
R 191G 191B 191
R 191G 212B 231
R 255G 250B 237
R 252G 232B 235
R 254G 242B 233
R 229G 243B 235
R 229G 229B 229
R 229G 238B 245