Methodology for Architectural Level Reliability Risk Analysis

Slides:



Advertisements
Similar presentations
Seyedehmehrnaz Mireslami, Mohammad Moshirpour, Behrouz H. Far Department of Electrical and Computer Engineering University of Calgary, Canada {smiresla,
Advertisements

Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
SBSE Course 3. EA applications to SE Analysis Design Implementation Testing Reference: Evolutionary Computing in Search-Based Software Engineering Leo.
Metrics Project and Process Metrics. Why do we measure? Assessing project status Allows us to track risks Before they go critical Adjust workflow See.
CSE 322: Software Reliability Engineering Topics covered: Architecture-based reliability analysis.
Software Testing Using Model Program DESIGN BY HONG NGUYEN & SHAH RAZA Dec 05, 2005.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Software Engineering Metrics for Object Oriented Programming Developed by – Shrijit Joshi.
Improving Robustness in Distributed Systems Jeremy Russell Software Engineering Honours Project.
Software Testing and Reliability Testing Real-Time Systems Aditya P. Mathur Purdue University May 19-23, Corporation Minneapolis/St Paul,
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
Software Process and Product Metrics
Chapter 10: Architectural Design
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Software System Integration
Methodology for Architectural Level Reliability Risk Analysis Lalitha Krothapalli CSC 532.
TEST CASE DESIGN Prepared by: Fatih Kızkun. OUTLINE Introduction –Importance of Test –Essential Test Case Development A Variety of Test Methods –Risk.
Software Architecture Risk Assessment (SARA) Tool Khader Basha Shaik Problem Report Defense Master of Science in Computer Science Lane Department of Computer.
1 Refining Reliability Estimation of Mobile Software Systems The International Workshop on Software Architectures and Mobility, ICSE-SAM 2008, Leipzig,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Chapter 10 Architectural Design
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
CLEANROOM SOFTWARE ENGINEERING.
بسم الله الرحمن الرحيم الحمد لله ، والصلاة والسلام على رسول الله
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
Research Heaven, West Virginia 1 FY 2004 Initiative: Risk Assessment of Software Architectures Hany Ammar, Katerina Goseva-Popstojanova, Ajith Guedem,
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Chapter 6 : Software Metrics
Lecture 9: Chapter 9 Architectural Design
Research Heaven, West Virginia 1 FY 2003 Initiative: IV&V of UML Hany Ammar, Katerina Goseva-Popstojanova, V. Cortelessa, Ajith Guedem, Kalaivani Appukutty,
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
June 05 David A. Gaitros Jean Muhammad Introduction to OOD and UML Dr. Jean Muhammad.
IV&V Facility 1 FY 2002 Initiative IV&V of UML Hany Ammar, Katerina Goseva-Popstojanova, V. Cortelessa, Ajith Guedem, Diaa Eldin Nassar, Walid AbdelMoez,
Quality of System requirements 1 Performance The performance of a Web service and therefore Solution 2 involves the speed that a request can be processed.
©Ian Sommerville 2004 Software Engineering. Chapter 21Slide 1 Chapter 21 Software Evolution.
West Virginia University Architectural-Level Risk Analysis for UML Dynamic Specifications Dr. Sherif M. Yacoub Hewlett-Packard Laboratories.
An Automatic Software Quality Measurement System.
Research Heaven, West Virginia 1 FY 2004 Initiative: Risk Assessment of Software Architectures Hany Ammar, Katerina Goseva-Popstojanova, Ajith Guedem,
Research Heaven, West Virginia FY2003 Initiative: Hany Ammar, Mark Shereshevsky, Walid AbdelMoez, Rajesh Gunnalan, and Ahmad Hassan LANE Department of.
Electrical and Computer Engineering University of Cyprus LAB 1: VHDL.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Architecture Analysis Techniques
Using Social Network Analysis Methods for the Prediction of Faulty Components Gholamreza Safi.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
West Virginia University Sherif Yacoub, Hany H. Ammar, and Ali Mili A UML Model for Analyzing Software Quality Sherif Yacoub, Hany H. Ammar, and Ali Mili.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Software reviews Cost impact of software defects Defect amplification model Review metrics and their use – Preparation effort (E p ), assessment effort.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Presented by Lu Xiao Drexel University Quantifying Architectural Debt.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Model-Based Risk Assessment
Prepared by: Fatih Kızkun
Research Heaven, West Virginia
Software Metrics 1.
BA Continuum India Pvt Ltd
Software Engineering B.Tech Ii csE Sem-II
Software Risk Assessment based on UML models
The Extensible Tool-chain for Evaluation of Architectural Models
Software System Integration
Standards.
Software Metrics “How do we measure the software?”
Introduction To software engineering
Software Architecture Risk Assessment (SARA) Tool
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Chapter 9 Architectural Design.
Chapter 8 Software Evolution.
Presentation transcript:

Methodology for Architectural Level Reliability Risk Analysis Lalitha Krothapalli CSC 532

Risk Risk is a combination of two factors. Probability of malfunctioning( failure) Consequence of malfunctioning (severity)

Uses of Risk Assessment Finding out the complex modules. Finding out the potentially troublesome modules. Calculates the effort for testing.

Types of Risks Availability Risk. Acceptance Risk. Performance Risk. Cost Risk. Schedule Risk Reliability Risk.

Components: Like objects, classes or procedures. Architectural level System is divided in to two parts Components: Like objects, classes or procedures. Connectors: Procedural calls , Client- server protocols

Advantage of Architectural Risk Analysis Early detection and correction of errors Cost will be less. Design and coding are also depend on the complexity of the architecture.

Advantages of simulating the Architecture Model Obtain dynamic behavior of components and connectors using dynamic metrics. Study the consequences of failure and severity of that failure.

Background The proposed methodology is based on the previous work of Dynamic Metrics Reliability Modeling and Analysis of Software Architecture

Dynamic Metrics Used to find out the complexity of each component Executive components have lot of state changes Measures the impact on the maintainability, reusability and error proneness Connector complexity can be calculated by using dynamic coupling metrics

Component Dependency Graphs Used to find out the reliability analysis at the architectural level. Represents components, connectors and component, connector reliabilities Can be used to calculate the execution time of the components and the interaction between the components

Risk Assessment Methodology Usage of architectural description language for modeling system architecture. Calculate complexity analysis using simulation of the architecture. Obtain severity analysis using FEMA and simulation runs. Developing heuristic risk factors for components and connectors. Preparing CDGs for calculating risk assessment.

Architectural Modeling Interaction between the components Behavior of individual components Real time object oriented model can be used to simulate the architecture

Complexity Analysis Component Complexity Connector complexity

Severity analysis Identifying failure modes. - failures modes of Individual components. - failure modes of individual connectors. Conducting Effect Analysis. Ranking severity. Catastrophic Critical Marginal Minor.

Develop Reliability Risk Factors for Architecture Elements Heuristic Factor for a component Heuristic factor for a connector.

Developing Component Dependency Graphs Calculate the execution time of each scenario. Calculate the execution time of each component Calculate the transition probability from one component to other for each and every scenario. Predict the complexity factor and severity of the index of the each component.

Reliability Risk Analysis Algorithm The risk factor of a system can be obtained from aggregating the risk factors of all components and connectors Breadth of a graph - All risk factors Depth of a graph - Sequential execution

Conclusion Applicable to architecture level so the errors can identified and detected at the early stages of life cycle. Based on dynamic metrics . Automatable.

References 1. Volume: 28,   Issue: 6,   Year: Jun 2002 A methodology for architecture-level reliability risk analysis Yacoub, S.M.; Ammar, H.H. Page(s): 529-547 2. 1  Architectural-level risk analysis using UML Goseva-Popstojanova, K.; Hassan, A.; Guedem, A.; Abdelmoez, W.; Nassar, D.E.M.; Ammar, H.; Mili, A.; Software Engineering, IEEE Transactions on , Volume: 29 , Issue: 10 , Oct. 2003 Pages:946 – 960 3. 7  Risk analysis-a subjective process Redmill, F.; Engineering Management Journal , Volume: 12 , Issue: 2 , April 2002 Pages:91 – 96