16
Software Architecture ATAM Process Presentation

Your Application Name

  • Upload
    hailey

  • View
    42

  • Download
    0

Embed Size (px)

DESCRIPTION

Software Architecture ATAM Process Presentation. Your Application Name. Outline. Introduction to your application ATAM Step 3 - Present Architecture ATAM Step 4 - Identify Architectural Approaches ATAM Step 5 - Generate Quality Attribute Utility Tree - PowerPoint PPT Presentation

Citation preview

Page 1: Your Application Name

Software Architecture ATAM Process Presentation

Page 2: Your Application Name

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

Page 3: Your Application Name

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

Page 4: Your Application Name

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

Page 5: Your Application Name

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

Page 6: Your Application Name

SampleSample

Page 7: Your Application Name

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

Page 8: Your Application Name

Sample

Interceptor

Runner

Script Model

Test scriptMFSM Editor

HFSM Editor

Test case generator

FSM ModelHFSM Model

XML

GTT User

Editor

GTT

OR

Page 9: Your Application Name

Sample

ReliabilityModifiabilityPerformance

Page 10: Your Application Name

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:…

Page 11: Your Application Name

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

Page 12: Your Application Name

Sample

By context diagram, whole GUI Testing architecture just likes layers

Each layer’s output will be as next layer’s input

Page 13: Your Application Name

Quality Attribute

AttributeRefinement

Scenario

Reliability Detect incorrect GUI components

… …

Modifiability

Test Driven …

Support other GUI library

… …

… …

… …

Performance

Do test oracle …

Test Case Generation …

Page 14: Your Application Name

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

Page 15: Your Application Name

Sample

Sensitivity S1: MVC pattern is a sensitivity point to

modifiability. S2: Update the newest hardware is a

sensitivity point to performance.

Page 16: Your Application Name

Sample

Conclusion and Lesson Learn!