Auflistung P058 - Testing of Component-Based Systems and Software Quality 2004 nach Erscheinungsdatum
1 - 10 von 18
Treffer pro Seite
- KonferenzbeitragGeneric environment for full automation of benchmarking(Testing of component-based systems and software quality, 2004) Kalibera, Tomáš; Bulej, Lubomír; Tůma, PetrRegression testing is an important part of software quality assurance. We work to extend regression testing to include regression benchmarking, which applies benchmarking to detect regressions in performance. Given the specific requirements of regression benchmarking, many contemporary benchmarks are not directly usable in regression benchmarking. To overcome this, we present a case for designing a generic benchmarking environment that will facilitate the use of contemporary benchmarks in regression benchmarking, analyze the requirements and propose architecture of such an environment.
- KonferenzbeitragAssessing and interpreting object-oriented software complexity with structured and independent metrics(Testing of component-based systems and software quality, 2004) Neumann, Roland; Klemann, DennisObject-oriented software complexity is difficult to assess due to its manifold influences from cognition science or algorithmic complexity theory. A practical process for a structured complexity assessment is presented in this paper. It starts with considerations for measurement and data preparation. Using mathematical transformation techniques, independent complexity metrics are gained. With these results, complexity aspects of a software system can be defined. This makes a complexity comparison through system classes possible, which helps getting an overview on large systems. These process steps are then illustrated with an industrial example.
- KonferenzbeitragTesting in the component age(Testing of component-based systems and software quality, 2004) Winter, MarioAt the end of the last century, quality and especially reusability problems of object-oriented software cropped out. As a remedy, nowadays component based software development resounds throughout the developer communities. Nevertheless the special aspects of testing component based systems often remain overlooked. After characterizing the main differences between object-oriented and componentbased software, this paper firstly surveys some basic concepts of component development and software testing. Then applicable techniques for specification and black-box testing of components are depicted, and particularly contract-based test case specification for component interfaces is emphasized. On this groundwork, some new testing levels and testing roles which have to be played in component based software development are proposed. The paper ends with some prospects on appropriate testing tools.
- KonferenzbeitragCate: A system for analysis and test of Java card applications(Testing of component-based systems and software quality, 2004) Pfahler, Peter; Günther, JürgenCate is a domain-specific testing environment. It integrates both static and dynamic analyzes that are designed for Java Card application software. Cate supports the test process by analyzing the command/response behavior of the software, by performing test coverage analysis and by providing tools to visualize the analysis results. This paper gives a concise overview over the system which is successfully employed in the area of smart card development for mobile phones.
- KonferenzbeitragTowards a practical approach to test aspect-oriented software(Testing of component-based systems and software quality, 2004) Zhou, Yuewei; Ziv, Hadar; Richardson, DebraAspect-Oriented Programming (AOP) provides new constructs and tools to handle cross-cutting concerns in programs. Fully realizing the potentials of Aspect-Oriented Software Development requires new abstractions and techniques for testing. This paper proposes a first step towards a practical approach to test aspect-oriented software. The proposed approach is accompanied by a selection algorithm that can select test cases that are relevant to aspects under test. A new testing coverage definition is proposed to specify the sufficiency of test cases on the aspect being tested. A tool is developed to support the approach, automating test case selection and coverage calculation. A detailed case study of banking account processing illustrates this initial approach.
- KonferenzbeitragAn optimum, system-based component testing approach for evaluating software reliability(Testing of component-based systems and software quality, 2004) Rajgopal, Jayant; Mazumdar, MainakIn a component testing approach for evaluating system reliability, one tests units of the components or subsystems that make up a larger system in order to draw conclusions about the reliability of the latter. An optimum, system-based component test plan explicitly account for the relationship between component and system reliabilities and also minimizes total testing effort. This paper reviews the main features of such plans and describes an application to reliability testing of a software system that is made up of several different components/modules.
- KonferenzbeitragA strategy to improve component testability without source code(Testing of component-based systems and software quality, 2004) Ribeiro Rocha, Camila; Martins, ElianeA software component must be tested every time it is reused, to guarantee the quality of both the component itself and the system in which it is to be integrated. To reduce testing costs, we propose a model to build highly testable components by embedding testing and monitoring mechanisms inside them. The approach is useful to component developers, who can use these built-in test capabilities in the testing phase, as well as to component users, who can verify whether the component fulfills its contract. Our approach proposes the insertion of built-in mechanisms directly into intermediate code, allowing its use even in COTS components.
- KonferenzbeitragImproving software quality through refactoring by means of didactical augmented experience(Testing of component-based systems and software quality, 2004) Rech, Jörg; Ras, Eric; Jedlitschka, AndreasIn agile software development refactoring is an important phase for the continuous improvement of software quality. Unfortunately, the application of refactorings is very subjective and heavily based on the expertise of the developers resulting in an unstable quality assurance. In this paper, we present an experiencebased approach for the semi-automatic and goal-oriented refactoring of software systems based on didactical augmented experiences, following the experience factory paradigm. This approach promises the accelerated acquisition, (re-) use, and learning of knowledge in the refactoring process.
- KonferenzbeitragInspections in small projects(Testing of component-based systems and software quality, 2004) Iisakka, JuhaPractically all inspection and review methods focus on projects for developing new software that involve numerous people, but software companies also have small projects on which only a few people are working, e.g. maintenance-oriented changes to existing software systems. Unfortunately, these small projects do not necessarily have the power to implement inspections efficiently. This paper raises certain problems that small projects have with inspections and discusses how different forms of inspection are suitable for small projects.
- KonferenzbeitragProperty-oriented testing: An approach to focusing testing efforts on behaviours of interest(Testing of component-based systems and software quality, 2004) Li, Shuhao; Qi, ZhichangThe behaviours of reactive systems are characterized by events, conditions, actions, and information flows. Complex reactive systems further exhibit hierarchy and concurrency. Since there usually exist numerous behaviours in such systems, they can hardly receive both comprehensive and in-depth testing. This paper presents a property-oriented testing method for reactive systems. UML state machine is employed to model the system under test (SUT) and temporal logic is used to specify the property to be tested. Targeted test sequences are derived from the model according to the given property. Based on this method, a property-oriented testing tool is implemented. Experiment results indicate that testing efforts can be focused on behaviours of interest of the SUT and thus usually only a small portion of the total behaviours needs to be tested. This method suits well the occasions when the testers have to focus on only critical properties of the SUT in case limited project budget is available. After appropriate extensions, this method can also be applied to real-time systems and systems with parameterized events.