1 / 10

A Survey on Software Architecture Analysis Methods

This paper delves into the methods for analyzing software architecture, discussing findings from a group survey led by Liliana Bobrica and Eila Niemela. It also explores the complexities of software testing as highlighted by James Whittaker, identifying common reasons users encounter bugs such as untested code execution and environmental discrepancies. The study outlines four essential phases for effective testing, including scenario selection and progress measurement, emphasizing the importance of testability and reliability in software development.

prentice
Download Presentation

A Survey on Software Architecture Analysis Methods

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Survey on Software Architecture Analysis Methods Liliana Bobrica and Eila Niemela IEEE TOSE July 02

  2. Group Presentations • Progress? • Has every group found their articles? • Is every group working together? • Example? • Does every group have an example?

  3. Group Presentations Schedule • Thursday, 11/21 • Tuesday, 11/26

  4. What is Software Testing? And Why Is It So Hard? James Whittaker, IEEE Software Jan/Feb2000 Pp70-79

  5. Why users find bugs • The user executed untested code • The order in which statements were executed in actual use differed from that during testing • The user applied a combination of untested input values • The user’s operating environment was never tested

  6. Four phases • Modeling the environment • Input sources, interfaces • Selecting test scenarios • Test data adequacy criteria • Running and evaluating test scenarios • Measuring testing progress

  7. Phase 4: Measuring Testing Progress • Number of tests • Percentage of code covered • Number of failures • Functional testing completeness • Structural testing completeness • Error Rates

  8. Voas’ Testability • From a point in the code, what is the probability that a change (fault) will be visible (cause a failure)? • Fault detection probability

  9. Reliability • Probability that software will not fail in x time • Operational profile

More Related