DOCSLIB.ORG

Software Testing Overview Software Testing Overview: Dr

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Testing Overview Software Testing Overview: Dr Software Testing Overview Software Testing Overview: Dr. Andrea Arcuri Part I Simu la R esearc h La boratory Oslo,,y Norway [email protected] Based on slides provided by Prof. Lionel Briand 1 2 Lionel Briand 2009 Lionel Briand 2009 Software has become prevalent in all aspects of our lives Qualities of Software Products • Correctness • Repairability • Reliability • Evolvability • Robustness • Reusability • Performance • Portability • User Friendliness • Understandability • Verifiability • Interoperability • Maintainability 3 4 Lionel Briand 2009 Lionel Briand 2009 Pervasive Problems Examples of Software Failures • Communications: Loss or corruption of • Software is commonly delivered late, way over communication media, non delivery of data. budgg,et, and of unsatisfactor yqy quality • Space Applications: Lost lives , launch delays , e .g ., • Software validation and verification are rarely European Ariane 5 shuttle, 1996: systematic and are usually not based on sound, – From the official disaster report: “Due to a well-defined techniques malfunction in the control software, the rocket veered off its flight path 37 seconds after • Software development processes are commonly launch.” unstable an d uncontro lled • Defense and Warfare: Misidentification of friend or • Software quality is poorly measured, monitored, foe. andtlldd controlled. • Transportation: Deaths, delays, sudden acceleration, • Software failure examples: inability to brake. http://www. cs. bc. edu/~gtan/bug/softwarebug. html • Electric Power: Death , injuries , power outages , long-term health hazards (radiation). 5 6 Lionel Briand 2009 Lionel Briand 2009 Examples of Software Failures Ariane 5 – ESA (()cont.) • Money Management: Fraud, violation of privacy, shutdown of stock exchanges and banks, negative interest rates . • Control of Elections: Wrong results (intentional or non- On June 4, 1996, the flight of the intentional). Ariane 5 launcher ended in a • Control of Jails: Technology-aided escape attempts and successes, failure. failures in software-controlled locks. • Law Enforcement: False arrests and imprisonments . Only about 40 seconds after initiation of the flight sequence, at an altitude of about 3,700 m, the launcher veered off its flight path, broke up and exploded . 7 8 Lionel Briand 2009 Lionel Briand 2009 Ariane 5 – Root Cause Ariane 5 – Lessons Learned • Source: ARIANE 5 Fligg,pyqyht 501 Failure, Report by the Inquiry Board • Adequate exception handling and redundancy strategies A program segment for converting a floating point number to a (real function of a backup system, degraded modes?) signe d 16 bit i n teger was execut ed with an i nput d at a val ue out sid e the range representable by a signed 16-bit integer. • Clear, complete, documented specifications (e.g., This run time error (out of range , overflow) , which arose in both preconditions, post-conditions) the active and the backup computers at about the same time, was • But perhaps more importantly: usage-based testing detected and both computers shut themselves down. (based on operational profiles), in this case actual This resulted in the total loss of attitude control. The Ariane 5 Ariane 5 trajectories turned uncontrollably and aerodynamic forces broke the vehicle apart. • Note this was not a complex, computing problem, but a deficiency of the software engineering practices in place This breakup was detected by an on-board monitor which ignited the explosive charges to destroy the vehicle in the air. Ironically, … the result of this format conversion was no longer needed after lift 9 10 off. Lionel Briand 2009 Lionel Briand 2009 F-18 cras h Fatal Therac-25 Radiation • An F-18 crashed because of a missing exception condition: An if ... then ... block without the else clause that was • In 1986, a man in Texas received between 16,500- thought could not possibly arise. 25, 000 radiations in less than 10 sec , over an area of about 1 cm. • In simulation, an F-16 program bug caused the virtual plane to flip over whenever it crossed the equator, as a • He lost his left arm, and died of complications 5 result of a missing minus sign to indicate south latitude. months later. 11 12 Lionel Briand 2009 Lionel Briand 2009 Power Shutdown in 2003 Consequences of Poor Quality 508 generating units and 256 power plants shut down • Standish Group surveyed 350 companies, over 8000 projects, in 1994 Affected 10 million people in Ontario, • 31% cancelled before completed, 9-16% were delivered Canada within cost and budget Affected 40 million • US study (1995): 81 billion US$ spend per year for failing people in 8 US software development projects states • NIST stu dy (2002) : bugs cost $ 59. 5 billion a year. Ear lier Financial losses of detection could save $22 billion. $6 Billion USD The alarm system in the energy management system failed due to a software error and operators were not informed of the power overload in the system 13 14 Lionel Briand 2009 Lionel Briand 2009 Quality Assurance Dealing with SW Faults • Uncover faults in the documents where they are FltHdliFault Handling introduced, in a systematic way, in order to avoid ripple effects. Systematic, structured reviews of software FltTlFault Tolerance dtfdtdocuments are referred to as itiinspections. Fault Avoidance Fault Detection • Derive, in a systematic way, effective test cases to uncover faults Design Atomic Modular Inspections • Automate testing and inspection activities, to the Methodology Transactions Redundancy maximum extent possible Configuration Verification • Monitor and control quality, e.g., reliability, Management maintainability, safety, across all project phases and Testing Debugging activities • All this implies the quality measurement of SW products and processes Component Integration System Correctness Performance Testing Testing Testing Debugging Debugging 15 16 Lionel Briand 2009 Lionel Briand 2009 Testing Definition Basic Testing Definition • Errors: People commit errors • SW Testing: Techniques to execute programs • Fault: A fault is the result of an error in the software with the intent of finding as many defects as docu mentation, code , etc . possible and/or gaining sufficient confidence • Failure: A failure occurs when a fault executes • Many people use the above three terms inter -changeably. It in the software system under test. should be avoided – “Program testing can show the presence of • Incident: Consequences of failures – Failure occurrence bugs, never their absence” (Dijkstra) may or may not be apparent to the user • The fundamental chain of SW dependability threats: propagation causation results in Error Fault Failure Incident ... 17 18 Lionel Briand 2009 Lionel Briand 2009 Why is SW testing important? • According to some estimates: ~50% of development costs Testing • A study by (the American) NIST in 2002: – The annual national cost of inadequate testing is as Definitions & Objectives much as $59 Billion US! – The report i s t it led : “The E conomi c I mpacts of Inadequate Infrastructure for Software Testing” 19 20 Lionel Briand 2009 Lionel Briand 2009 Test Stubs and Drivers Summary of Definitions •Test Stub: Partial implementation of a component on which a unit under test Test suite depends. Test S tub exercises is re vised by Depends * * 1…n Component a Component b Test case Component Correction U nder T es t * * * Test stub finds • Test Driver: Partial implementation of a component that depends on a unit under repairs test. * Test Driver Test driver Depends C om ponent j C om ponent k * * Failure * * Fault ** Error Under Test is caused by is caused by • Test stubs and drivers enable components to be isolated from the rest of the system for testing. 21 22 Lionel Briand 2009 Lionel Briand 2009 Motivations The Testing Dilemma Available • No matter how rigorous we are, software is going testing to be faulty Limited resources resources All Software System • Testing represent a functionality substantial percentage of expertis Time Peopl e software development Money Potentially costs and time to market e • Impossible to test under thousands all operating conditions – bdbased on incomp ltlete of items testing, we must gain confidence that the system to test has the des ired be hav ior o • Testing large systems is complex – it requires strategy and technology- and is often done inefficiently in practice 23 Faulty functionality 24 Lionel Briand 2009 Lionel Briand 2009 TtiPTesting Process Overvi ew Qualities of Testing SW Representation (e.g., models, requirements) • Effective at uncovering faults DiDerive TtTest cases Estimate •Help locate faults for debugging Expected SW Code • Repeatable so that a precise understanding Results Execute Test cases of the fault can be gained Get Test Results • Automated so as to lower the cost and Test Oracle Compare timescale [Test Result==Oracle] [Test Result!=Oracle] • SiSystematic so as to bdiblibe predictable in terms of its effect on dependability 25 26 Lionel Briand 2009 Lionel Briand 2009 Subtleties of Software Continuity Property • Problem: Test a bridge ability to sustain a Dependability certain weight • Continuity Property: If a bridge can sustain a • Dependability: Correctness, reliability, safety, weight equal to W1, then it will sustain any robustness weight W2 <= W1 • A program is correct if it obeys its specification. • EtilltiittEssentially, continuity property= small differences in operating conditions should not • Reliability is a way of statistically approximating result in dramatically different behavior correctness. • Safety
Load more

Recommended publications
  • Balancing Dependability Quality Attributes Relationships for Increased Embedded Systems Dependability
    Master Thesis Software Engineering Thesis no: MSE-2009:17 September 2009 Balancing Dependability Quality Attributes Relationships for Increased Embedded Systems Dependability Saleh Al-Daajeh Supervisor: Professor Mikael Svahnberg School of Engineering Blekinge Institute of Technology Box 520 SE – 372 25 Ronneby Sweden This thesis is submitted to the School of Engineering at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Software Engineering. The thesis is equivalent to 2 x 20 weeks of full time studies. Contact Information: Author: Saleh Al-Daajeh E-mail: [email protected] University advisor: Prof. Miakel Svahnberg School of Engineering Internet : www.bth.se/tek Blekinge Institute of Technology Phone : +46 457 385 000 Box 520 Fax : +46 457 271 25 SE – 372 25 Ronneby Sweden II Abstract Embedded systems are used in many critical applications of our daily life. The increased complexity of embedded systems and the tightened safety regulations posed on them and the scope of the environment in which they operate are driving the need for more dependable embedded systems. Therefore, achieving a high level of dependability to embedded systems is an ultimate goal. In order to achieve this goal we are in need of understanding the interrelationships between the different dependability quality attributes and other embedded systems’ quality attributes. This research study provides indicators of the relationship between the dependability quality attributes and other quality attributes for embedded systems by identify- ing the impact of architectural tactics as the candidate solutions to construct dependable embedded systems. III Acknowledgment I would like to express my gratitude to all those who gave me the possibility to complete this thesis.
    [Show full text]
  • A Reasoning Framework for Dependability in Software Architectures Tacksoo Im Clemson University, [email protected]
    Clemson University TigerPrints All Dissertations Dissertations 12-2010 A Reasoning Framework for Dependability in Software Architectures Tacksoo Im Clemson University, [email protected] Follow this and additional works at: https://tigerprints.clemson.edu/all_dissertations Part of the Computer Sciences Commons Recommended Citation Im, Tacksoo, "A Reasoning Framework for Dependability in Software Architectures" (2010). All Dissertations. 618. https://tigerprints.clemson.edu/all_dissertations/618 This Dissertation is brought to you for free and open access by the Dissertations at TigerPrints. It has been accepted for inclusion in All Dissertations by an authorized administrator of TigerPrints. For more information, please contact [email protected]. A Reasoning Framework for Dependability in Software Architectures A Dissertation Presented to the Graduate School of Clemson University In Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy Computer Science by Tacksoo Im August 2010 Accepted by: Dr. John D. McGregor, Committee Chair Dr. Harold C. Grossman Dr. Jason O. Hallstrom Dr. Pradip K. Srimani Abstract The degree to which a software system possesses specified levels of software quality at- tributes, such as performance and modifiability, often have more influence on the success and failure of those systems than the functional requirements. One method of improving the level of a software quality that a product possesses is to reason about the structure of the software architecture in terms of how well the structure supports the quality. This is accomplished by reasoning through software quality attribute scenarios while designing the software architecture of the system. As society relies more heavily on software systems, the dependability of those systems be- comes critical.
    [Show full text]
  • Fundamental Concepts of Dependability
    Fundamental Concepts of Dependability Algirdas Avizˇ ienis Jean-Claude Laprie Brian Randell UCLA Computer Science Dept. LAAS-CNRS Dept. of Computing Science Univ. of California, Los Angeles Toulouse Univ. of Newcastle upon Tyne USA France U.K. UCLA CSD Report no. 010028 LAAS Report no. 01-145 Newcastle University Report no. CS-TR-739 LIMITED DISTRIBUTION NOTICE This report has been submitted for publication. It has been issued as a research report for early peer distribution. Abstract Dependability is the system property that integrates such attributes as reliability, availability, safety, security, survivability, maintainability. The aim of the presentation is to summarize the fundamental concepts of dependability. After a historical perspective, definitions of dependability are given. A structured view of dependability follows, according to a) the threats, i.e., faults, errors and failures, b) the attributes, and c) the means for dependability, that are fault prevention, fault tolerance, fault removal and fault forecasting. he protection and survival of complex information systems that are embedded in the infrastructure supporting advanced society has become a national and world-wide concern of the 1 Thighest priority . Increasingly, individuals and organizations are developing or procuring sophisticated computing systems on whose services they need to place great reliance — whether to service a set of cash dispensers, control a satellite constellation, an airplane, a nuclear plant, or a radiation therapy device, or to maintain the confidentiality of a sensitive data base. In differing circumstances, the focus will be on differing properties of such services — e.g., on the average real-time response achieved, the likelihood of producing the required results, the ability to avoid failures that could be catastrophic to the system's environment, or the degree to which deliberate intrusions can be prevented.
    [Show full text]
  • Dependability Assessment of Software- Based Systems: State of the Art
    Dependability Assessment of Software- based Systems: State of the Art Bev Littlewood Centre for Software Reliability, City University, London [email protected] You can pick up a copy of my presentation here, if you have a lap-top ICSE2005, St Louis, May 2005 - slide 1 Do you remember 10-9 and all that? • Twenty years ago: much controversy about need for 10-9 probability of failure per hour for flight control software – could you achieve it? could you measure it? – have things changed since then? ICSE2005, St Louis, May 2005 - slide 2 Issues I want to address in this talk • Why is dependability assessment still an important problem? (why haven’t we cracked it by now?) • What is the present position? (what can we do now?) • Where do we go from here? ICSE2005, St Louis, May 2005 - slide 3 Why do we need to assess reliability? Because all software needs to be sufficiently reliable • This is obvious for some applications - e.g. safety-critical ones where failures can result in loss of life • But it’s also true for more ‘ordinary’ applications – e.g. commercial applications such as banking - the new Basel II accords impose risk assessment obligations on banks, and these include IT risks – e.g. what is the cost of failures, world-wide, in MS products such as Office? • Gloomy personal view: where it’s obvious we should do it (e.g. safety) it’s (sometimes) too difficult; where we can do it, we don’t… ICSE2005, St Louis, May 2005 - slide 4 What reliability levels are required? • Most quantitative requirements are from safety-critical systems.
    [Show full text]
  • Software Reliability and Dependability: a Roadmap Bev Littlewood & Lorenzo Strigini
    Software Reliability and Dependability: a Roadmap Bev Littlewood & Lorenzo Strigini Key Research Pointers Shifting the focus from software reliability to user-centred measures of dependability in complete software-based systems. Influencing design practice to facilitate dependability assessment. Propagating awareness of dependability issues and the use of existing, useful methods. Injecting some rigour in the use of process-related evidence for dependability assessment. Better understanding issues of diversity and variation as drivers of dependability. The Authors Bev Littlewood is founder-Director of the Centre for Software Reliability, and Professor of Software Engineering at City University, London. Prof Littlewood has worked for many years on problems associated with the modelling and evaluation of the dependability of software-based systems; he has published many papers in international journals and conference proceedings and has edited several books. Much of this work has been carried out in collaborative projects, including the successful EC-funded projects SHIP, PDCS, PDCS2, DeVa. He has been employed as a consultant to industrial companies in France, Germany, Italy, the USA and the UK. He is a member of the UK Nuclear Safety Advisory Committee, of IFIPWorking Group 10.4 on Dependable Computing and Fault Tolerance, and of the BCS Safety-Critical Systems Task Force. He is on the editorial boards of several international scientific journals. 175 Lorenzo Strigini is Professor of Systems Engineering in the Centre for Software Reliability at City University, London, which he joined in 1995. In 1985-1995 he was a researcher with the Institute for Information Processing of the National Research Council of Italy (IEI-CNR), Pisa, Italy, and spent several periods as a research visitor with the Computer Science Department at the University of California, Los Angeles, and the Bell Communication Research laboratories in Morristown, New Jersey.
    [Show full text]
  • Critical Systems
    Critical Systems ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 1 Objectives ● To explain what is meant by a critical system where system failure can have severe human or economic consequence. ● To explain four dimensions of dependability - availability, reliability, safety and security. ● To explain that, to achieve dependability, you need to avoid mistakes, detect and remove errors and limit damage caused by failure. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 2 Topics covered ● A simple safety-critical system ● System dependability ● Availability and reliability ● Safety ● Security ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 3 Critical Systems ● Safety-critical systems • Failure results in loss of life, injury or damage to the environment; • Chemical plant protection system; ● Mission-critical systems • Failure results in failure of some goal-directed activity; • Spacecraft navigation system; ● Business-critical systems • Failure results in high economic losses; • Customer accounting system in a bank; ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 4 System dependability ● For critical systems, it is usually the case that the most important system property is the dependability of the system. ● The dependability of a system reflects the user’s degree of trust in that system. It reflects the extent of the user’s confidence that it will operate as users expect and that it will not ‘fail’ in normal use. ● Usefulness and trustworthiness are not the same thing. A system does not have to be trusted to be useful. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 3 Slide 5 Importance of dependability ● Systems that are not dependable and are unreliable, unsafe or insecure may be rejected by their users.
    [Show full text]
  • A Practical Framework for Eliciting and Modeling System Dependability Requirements: Experience from the NASA High Dependability Computing Project
    The Journal of Systems and Software 79 (2006) 107–119 www.elsevier.com/locate/jss A practical framework for eliciting and modeling system dependability requirements: Experience from the NASA high dependability computing project Paolo Donzelli a,*, Victor Basili a,b a Department of Computer Science, University of Maryland, College Park, MD 20742, USA b Fraunhofer Center for Experimental Software Engineering, College Park, MD 20742, USA Received 9 December 2004; received in revised form 21 March 2005; accepted 21 March 2005 Available online 29 April 2005 Abstract The dependability of a system is contextually subjective and reflects the particular stakeholderÕs needs. In different circumstances, the focus will be on different system properties, e.g., availability, real-time response, ability to avoid catastrophic failures, and pre- vention of deliberate intrusions, as well as different levels of adherence to such properties. Close involvement from stakeholders is thus crucial during the elicitation and definition of dependability requirements. In this paper, we suggest a practical framework for eliciting and modeling dependability requirements devised to support and improve stakeholdersÕ participation. The framework is designed around a basic modeling language that analysts and stakeholders can adopt as a common tool for discussing dependability, and adapt for precise (possibly measurable) requirements. An air traffic control system, adopted as testbed within the NASA High Dependability Computing Project, is used as a case study. Ó 2005 Elsevier Inc. All rights reserved. Keywords: System dependability; Requirements elicitation; Non-functional requirements 1. Introduction absence of failures (with higher costs, longer time to market and slower innovations) (Knight, 2002; Little- Individuals and organizations increasingly use wood and Stringini, 2000), everyday software (mobile sophisticated software systems from which they demand phones, PDAs, etc.) must provide cost effective service great reliance.
    [Show full text]
  • A Brief Essay on Software Testing
    1 A Brief Essay on Software Testing Antonia Bertolino, Eda Marchetti Abstract— Testing is an important and critical part of the software development process, on which the quality and reliability of the delivered product strictly depend. Testing is not limited to the detection of “bugs” in the software, but also increases confidence in its proper functioning and assists with the evaluation of functional and nonfunctional properties. Testing related activities encompass the entire development process and may consume a large part of the effort required for producing software. In this chapter we provide a comprehensive overview of software testing, from its definition to its organization, from test levels to test techniques, from test execution to the analysis of test cases effectiveness. Emphasis is more on breadth than depth: due to the vastness of the topic, in the attempt to be all-embracing, for each covered subject we can only provide a brief description and references useful for further reading. Index Terms — D.2.4 Software/Program Verification, D.2.5 Testing and Debugging. —————————— u —————————— 1. INTRODUCTION esting is a crucial part of the software life cycle, and related issues, we can only briefly expand on each argu- T recent trends in software engineering evidence the ment, however plenty of references are also provided importance of this activity all along the development throughout for further reading. The remainder of the chap- process. Testing activities have to start already at the re- ter is organized as follows: we present some basic concepts quirements specification stage, with ahead planning of test in Section 2, and the different types of test (static and dy- strategies and procedures, and propagate down, with deri- namic) with the objectives characterizing the testing activity vation and refinement of test cases, all along the various in Section 3.
    [Show full text]
  • Dependability Analysis of a Safety Critical System: the LHC Beam Dumping System at CERN
    In Supremae Dignitatis Universita` di Pisa · FACOLTA` DI INGEGNERIA Dipartimento Di Sistemi Elettrici ed Automazione Dependability Analysis of a Safety Critical System: The LHC Beam Dumping System at CERN Tesi di Dottorato di Ricerca in Automatica, Robotica e Bioingegneria CERN-THESIS-2006-054 21/04/2006 Relatore: Candidato: Prof. Ing. Ing. ALDO BALESTRINO ROBERTO FILIPPINI Co-relatore: Dr. Ir. JAN UYTHOVEN Anno Accademico 2005-2006 Abstract This thesis presents the dependability study of the Beam Dumping System of the Large Hadron Collider (LHC), the high energy particle accelerator to be commissioned at CERN in summer 2007. There are two identical, independent LHC Beam Dumping Systems (LBDS), one per LHC beam, each consisting of a series of magnets that extract the particle beam from the LHC ring into the extraction line leading to the absorbing block. The consequences of a failure within the LBDS can be very severe. This risk is reduced by applying redundancy to the design of the most critical components and on-line surveillance that, in case of a detected failure, issues a safe operation abort, called false beam dump. The system has been studied applying Failure Modes Effects and Criticality Analysis (FMECA) and reliability prediction. The system failure processes have been represented with a state transition diagram, governed by a Markov regener- ative stochastic process, and analysed for different operational scenarios for one year of operation. The analysis of the system results in a safety level ranked SIL4 in the IEC 61508 standard and 4 ( 2) expected false beam dumps generated ± per LBDS. These results will be validated through a three months reliability run.
    [Show full text]
  • Empirical Evaluation of the Effectiveness and Reliability of Software Testing Adequacy Criteria and Reference Test Systems
    Empirical Evaluation of the Effectiveness and Reliability of Software Testing Adequacy Criteria and Reference Test Systems Mark Jason Hadley PhD University of York Department of Computer Science September 2013 2 Abstract This PhD Thesis reports the results of experiments conducted to investigate the effectiveness and reliability of ‘adequacy criteria’ - criteria used by testers to determine when to stop testing. The research reported here is concerned with the empirical determination of the effectiveness and reliability of both tests sets that satisfy major general structural code coverage criteria and test sets crafted by experts for testing specific applications. We use automated test data generation and subset extraction techniques to generate multiple tests sets satisfying widely used coverage criteria (statement, branch and MC/DC coverage). The results show that confidence in the reliability of such criteria is misplaced. We also consider the fault-finding capabilities of three test suites created by the international community to serve to assure implementations of the Data Encryption Standard (a block cipher). We do this by means of mutation analysis. The results show that not all sets are mutation adequate but the test suites are generally highly effective. The block cipher implementations are also seen to be highly ‘testable’ (i.e. they do not mask faults). 3 Contents Abstract ............................................................................................................................ 3 Table of Tables ...............................................................................................................
    [Show full text]
  • Dependability in Cloud Computing
    FACOLTA` DI SCIENZE MATEMATICHE,FISICHE E NATURALI DIPARTIMENTO DI INFORMATICA DOTTORATO DI RICERCA IN INFORMATICA SCUOLA DI DOTTORATO IN INFORMATICA, XXVI CICLO Dependability in Cloud Computing TESI DI DOTTORATO DI RICERCA DI Ravi Jhawar RELATORE Prof. Vincenzo Piuri CORRELATORE Prof. Pierangela Samarati DIRETTORE DELLA SCUOLA DI DOTTORATO Prof. Ernesto Damiani Anno Accademico 2012/13 ii Abstract The technological advances and success of Service-Oriented Architectures and the Cloud computing paradigm have produced a revolution in the Information and Communications Technology (ICT). Today, a wide range of services are provisioned to the users in a flexible and cost-effective manner, thanks to the encapsulation of several technologies with modern business models. These services not only offer high-level software functionalities such as social networks or e-commerce but also middleware tools that simplify application development and low-level data storage, processing, and networking resources. Hence, with the advent of the Cloud computing paradigm, today's ICT allows users to completely outsource their IT infrastructure and benefit significantly from the economies of scale. At the same time, with the widespread use of ICT, the amount of data being generated, stored and processed by private companies, public organizations and individuals is rapidly increasing. The in-house management of data and applications is proving to be highly cost intensive and Cloud computing is becoming the destination of choice for increasing number of users. As a consequence, Cloud computing services are being used to realize a wide range of applications, each having unique dependability and Quality-of-Service (Qos) requirements. For example, a small enterprise may use a Cloud storage service as a simple backup solution, requiring high data availability, while a large government organization may execute a real-time mission-critical application using the Cloud compute service, requiring high levels of dependability (e.g., reliability, availability, security) and performance.
    [Show full text]
  • Model-Driven Tools for Dependability Management in Component-Based Distributed Systems
    Model-driven Tools for Dependability Management in Component-based Distributed Systems Sumant Tambe†, Akshay Dabholkar†, Jaiganesh Balasubramanian†, Aniruddha Gokhale†, Douglas C. Schmidt† †Department of EECS, Vanderbilt University, Nashville, TN, USA I. INTRODUCTION Emerging trends and challenges. Component-based software engineering supported by middleware technologies, such as CORBA Component Model (CCM) and Enterprise Java Beans (EJB), has emerged as a preferred way of developing enterprise distributed real-time and embedded (DRE) systems, such as smart buildings, modern office enterprises, and inflight entertainment systems. These systems consist of applications whose dependability requirements, such as availability and security, must be satisfied simultaneously to ensure dependable operation [1], [2]. For correct dependable operation of enterprise DRE systems, however, multiple dependability attributes must often be simultaneously satisfied. There are inherent challenges in satisfying multiple dependability attributes together due to tradeoffs and conflicts between them. For example, deploying replicas of a service on hosts that are unauthorized to access by clients may result in unavailability of the service to its clients on failure of another replica of the same service. It is hard to detect and analyze these errors at runtime, which motivates the need to catch as many errors at design-time as possible. Hence, there is a need for design-time tools to reason about the inherent tradeoffs and conflicts between multiple dependability attributes and alleviate complexities in developing dependable enterprise DRE systems. Figure 1 depicts desirable properties of a design-time tool that considers multiple dependability attributes (such as availability and security) to reason about system dependability e.g., protecting it from various hazards (such as faults and unauthorized access).
    [Show full text]