This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established. Scope: This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types; libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools. Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.
|Published (Last):||3 June 2008|
|PDF File Size:||7.13 Mb|
|ePub File Size:||15.31 Mb|
|Price:||Free* [*Free Regsitration Required]|
The growing importance and stringent quality requirements of software systems are in-creasing demand for efficient software testing. Hiring more test engineers or lengthening the testing time are not viable long-term solutions, rather there is a need to decrease the amount of resources needed.
One a One attractive solution to this problem is test automation, i. There are countless approaches to test automation, and they work differently in different contexts. The thesis opens its discussion of test automation frameworks by defining their high-level requirements.
The most important requirements are identified as ease-of-use, maintain-ability and, of course, the ability to automatically execute tests and report results. More detailed requirements are derived from these high-level requirements: data-driven and keyword-driven testing techniques, for example, are essential prerequisites for both ease-of-use and maintainability. Cohen, Xiao Qu " System testing of configurable software is an expensive and resource constrained process. Insufficient testing often leads to escaped faults in the field where failures impact customers and are costly to repair.
Prior work has shown that it is possible to efficiently sample configurations for testin Prior work has shown that it is possible to efficiently sample configurations for testing using combinatorial interaction testing, and to prioritize these configurations to increase the rate of early fault detection. The underlying assumption to date has been that there is no added complexity to configuring a system level environment over a user configurable one; i.
In this paper we examine prioritization of system configurable software driven not only by fault detection but also by the cost of configuration and setup time that moving between different configurations incurs.
We present a case study on two releases of an enterprise software system using failures reported in the field. We examine the most effective prioritization technique and conclude that 1 using failure history of configurations can improve the early fault detection rate, but that 2 we must consider fault detection rate over time, not by the number of configurations tested.
It is better to test related configurations which incur minimal setup time than to test fewer, more diverse configurations. Show Context Citation Context There is a growing trend to move desktop applications towards the web.
In this paper, Show Context Citation Context Regression testing of web applications  in general and Ajax-based applications in particular is far from trivial due to the high degree of dynamism in such applications. This dynamism is usually Yuen, Henry C. Abstract—This paper proposes a fuzzy Analytic Hierarchy Process model for evaluating the software quality of vendors. To meet the standard of software quality, software quality assurance plays an essential role in software development.
Lau " Abstract—This paper proposes a fuzzy Analytic Hierarchy Process model for software vendors selection. The prioritization method of the fuzzy AHP model applies IEEE " Abstract-Software reliability growth modeling helps in deciding project release time and managing project resources. A large number of such models have been presented in the past.
This paper presents empirical results of using genetic programming GP for modeling software reliability growth based on weekly fault count data of three different industrial projects.
The goodness of fit adaptability and predictive accuracy of the evolved model is measured using five different measures in an attempt to present a fair evaluation.
The results show that the GP evolved model has statistically significant goodness of fit and predictive accuracy. If the software frequently fails to perform according to user-specified behavior, other software quality factors matters less .
Software reliability growth models SRGMs , which are based on the Software products often need to vary in terms of functionality, but also in terms of quality attributes. We describe KumbangSec, which in an approach for modelling functional and security variability applying different architectural viewpoints.
KumbangSec builds on an existing variability modelling KumbangSec builds on an existing variability modelling method, Kumbang, by extending it with security engineering concepts. KumbangSec consists of a conceptualisation and a language implementing the conceptualisation. The semantics for the conceptualisation has been described using natural language; the syntax for the language has been defined in a grammar.
KumbangSec can be supported with a configurator, which is an intelligent tool supporting derivation of products that each satisfy specific and different functional and security requirements. Such a tool, KumbangSec configurator, is currently being developed. Many quality attributes are architectural, meaning that the architecture of the software is critical to their realisation, and these qualities should be designed in and evaluated at the architectura Effort estimations within software development projects and the ability to work within these estimations are perhaps the single most important, and at the same time inadequately mastered, discipline for overall project success.
This study examines some characteristics of accuracies in software devel This study examines some characteristics of accuracies in software development efforts and identifies patterns that can be used to increase the understanding of the effort estimation discipline as well as to improve the accuracy of effort estimations. The study complements current research by taking a more simplistic approach than usually found within mainstream research concerning effort estimations. It shows that there are useful patterns to be found as well as interesting causalities, usable to increase the understanding and effort estimation capability.
Review, process audit, and testing are three main Quality Assurance activities during the software development life cycle. They complement each other to examine work products for defects and improvement opportunities to the largest extent. Understanding the effort distribution and inter-co Understanding the effort distribution and inter-correlation among them will facilitate software organization project planning, improve the software quality within the budget and schedule and make continuous process improvement.
This paper reports some empirical findings of effort distribution pattern of the three types of QA activities from a series of incremental projects in China. The result of the study gives us some implications on how to identify which type of QA activity is insufficient while others might be overdone, how to balance the effort allocation and planning for future projects, how to improve the weak part of each QA activity and finally improve the Return On Investment ROI of QA activities and the whole process effectiveness under the specific organization context.
Review, process audit and testing are three popular quality assurance activities during the software life cycle. Review, often referred to requirements review, formal design reviews, peer reviews i Published online in Wiley InterScience www. DOI: A major benefit of Model Driven Engineering MDE relies on the automatic generation of artefacts from high-level models through intermediary levels using model transformations. In such a process, the input must be well-designed and the model transformations should be trustworthy.
Due to the specifi Due to the specificities of models and transformations, classical software test techniques have to be adapted. Among these techniques, mutation analysis has been ported and a set of mutation operators has been defined. However, mutation analysis currently requires a considerable manual work and suffers from the test data set improvement activity.
This activity is seen by testers as a difficult and time-consuming job, and reduces the benefits of the mutation analysis. This paper addresses the test data set improvement activity. Model transformation traceability in conjunction with a model of mutation operators, and a dedicated algorithm allow to automatically or semi-automatically produce test models that detect new faults.
The proposed approach is validated and illustrated in a case study written in Kermeta. It is presented in Figure 4. The four main activities are the following. Preliminary step activity a : this activity is divided into two parts: the c Powered by:.
Hear about relevant training courses in your area. To insert individual citation into a bibliography in a word-processor, select your preferred citation style below and drag-and-drop it into the document. If you are a client of PPI or subsidiary company CTI and wish to obtain a username and password, please use the email contact form. Standard definitions for those terms are established. Search all the public and authenticated articles in CiteULike. Groups Connections Recommendations Neighbours Watchlist.
IEEE 610.12 PDF