Post on 16-Jan-2016
description
Software Architecture ATAM Process Presentation
Sample
Introduction to your application ATAM Step 3 - Present Architecture ATAM Step 4 - Identify Architectural
Approaches ATAM Step 5 - Generate Quality Attribute
Utility Tree ATAM Step 6 - Analyze Architectural
Approaches Conclusion
Sample
GUI – Graphical User InterfaceGUI Testing – Test the software with
GUI The most of software are using GUI
to interact with user, and GUI plays very important role in software
Test Driven Design (TDD) is very popular
Sample
Automation Reduce time to operate the software Create test case in easy way Use a great algorithm to generate test
data
Provide a convenient way to edit test-flow
Sample
Determine what to test
Generate test input
Generate expected output
Execute test case and verify output
Determine if the GUI was adequately test
Performing regression testing
SampleSample
Sample
AP User
OS
JVM Jemmy
Interceptor
SwingApplicati
on
Test Case
generation
FSM Model
Tester
Runner
Script Model
Editor
HFSM Model
XML
GTT User
Java Runtime Environment
GTT
OR
Sample
Interceptor
Runner
Script Model
Test scriptMFSM Editor
HFSM Editor
Test case generator
FSM ModelHFSM Model
XML
GTT User
Editor
GTT
OR
Sample
ReliabilityModifiabilityPerformance
Sample
Add supporting other Java GUI library
Add edition of test case ways and views
Source:developer
Stimulus:…
Artifact:…
Environment:…
Response:…
Response Measure:…
Source:developer
Stimulus:…
Artifact:…
Environment:…
Response:…
Response Measure:…
Sample
Because of providing graphic interface, implementation with MVC pattern is required
In order to add new edition way and views
The most important parts of GUI Testing is core algorithm, and we should separate it from view
Sample
By context diagram, whole GUI Testing architecture just likes layers
Each layer’s output will be as next layer’s input
Quality Attribute
AttributeRefinement
Scenario
Reliability Detect incorrect GUI components
…
… …
Modifiability
Test Driven …
Support other GUI library
…
… …
… …
… …
Performance
Do test oracle …
Test Case Generation …
Scenario #: M3 Scenario: Add edition of test case ways and views, and should be done in a week
Attribute(s) Modifiability
Environment Design Time
Stimulus Change tree-view to diagram-view
Response Modification is made without effecting model
Architecture decisions
Sensitivity Tradeoff Risk Nonrisk
MVC Pattern S1
Reasoning If want to generate test case by FSM ways, add diagram-view into editor is quite important.
Architecture Diagram
Editor
Tree view
Diagram view
Sample
Sensitivity S1: MVC pattern is a sensitivity point to
modifiability. S2: Update the newest hardware is a
sensitivity point to performance.
Sample
Conclusion and Lesson Learn!