Filtyp
This paper presents a methodology for developing software systems denoted Cleanroom Software Engineering. The methodology has been developed at IBM and Software Engineering Technology (SET) in the USA, and is currently being adapted and applied to the field of telecommunications by E-P Telecom Q-Labs. The paper gives a brief introduction to Cleanroom. The main objective of Cleanroom is to introdu
Presents a method proposal for estimation of software reliability before the implementation phase. The method is based upon a formal description technique and that it is possible to develop a tool for performing dynamic analysis, i.e. locating semantic faults in the design. The analysis is performed by applying a usage profile as input as well as doing a full analysis, i.e. locating all faults tha
The testing method proposed in the Cleanroom methodology is Statistical Usage Testing. This testing technique is based on that the test cases represent theoperational profile. The failure data from testing is then used in a software reliability model to certify the reliability of the software. This paper introduces a new model for modelling the usage of the system, i.e. the operational profile. It
Software reliability is a frequently used term, but very seldom the reliability is under control during a software development project. This paper presents a method, Statistical Usage Testing (SUT), which gives the possibility to estimate and predict, and hence control the software reliability. SUT is the reliability certification method described as a part of Cleanroom software engineering. The m
In order to improve the efficiency of inspections, quantitative data on defect content have to be the basis for decisions in the inspection process. An experience-based capture-recapture method is proposed, which overcomes some problems with the basic pre-requisites of the original method. A C-code inspection experiment is conducted to evaluate the enhanced method and its applicability to software
Software quality engineering is concerned with building software products with required quality and assessing the level of quality. Software processes are important assets in achieving and assessing the software quality. Furthermore the adherence to defined processes is a key issue to having the software engineering under control and to enable process improvement. The software quality assurance (S
Requirements engineering and software reliability engineering both involve model building related to the usage of the intended system; requirements models and test case models respectively are built. Use case modelling for requirements engineering and operational profile testing for software reliability engineering are techniques which are evolving into software engineering practice. Approaches to
Reviews are essential for defect detection and they provide an opportunity to control the software development process. This paper focuses upon methods for estimating the defect content after a review and hence to provide support for process control. Two new estimation methods are introduced as the assumptions of the existing statistical methods are not fulfilled. The new methods are compared with
This paper presents a method proposal for estimation of software reliability before the implementation phase. The method is based upon that a formal specification technique is used and that it is possible to develop a tool performing dynamic analysis, i.e., locating semantic faults in the design. The analysis is performed with both applying a usage profile as input as well as doing a full analysis
It is of paramount importance that software reliability requirements not only can be formulated, but also enforced and evaluated before accepting a software product for release. This requires sound acceptance criteria for software, which implies that methods for evaluating the software reliability are needed during the testing phase. Thus, theoretical models which are practically applicable are ne
Software reliability is a frequently used term, but very seldom the reliability is under control, at least not in quantitative terms, during a software development project. This paper outlines a method, Statistical Usage Testing (SUT), which provides the opportunity to estimate and predict, and hence control software reliability. SUT is the reliability certification method described as a part of C
Software reliability is a frequently used term, but very seldom the reliability is under control during a software development project. This paper presents a method, Statistical Usage Testing (SUT), which gives the possibility to estimate and predict, and hence control software reliability. SUT is the reliability certihcation method described as a part of Cleanroom software engineering. The main o
he use of capture‐recapture to estimate the residual faults in a software artifact has evolved as a promising method. However, the assumptions needed to make the estimates are not completely fulfilled in software development, leading to an underestimation of the residual fault content. Therefore, a method employing a filtering technique with an experience factor to improve the estimate of the resi
Reuse is becoming one of the key areas in dealing with the cost and quality of software systems. An important issue is the reliability of the components, hence making certification of software components a critical area. The objective of this article is to try to describe methods that can be used to certify and measure the ability of software components to fulfil the reliability requirements place
A methodology for developing software intensive systems denoted Cleanroom Software Engineering is presented. The methodology has been developed at IBM and Software Engineering Technology (SET) in the USA, and is currently being adapted and applied to the field of telecommunications by Q-Labs.The main objective of Cleanroom is to introduce a set of management and engineering techniques which shall
Understandability of the current system is a key issue in most reengineering processes. An architecture description of the system may increase its understandability. This paper presents experiences from architectural design recovery in a product family of large distributed, embedded systems. Automated recovery tools were hard to apply due to the nature of the source code. A qualitative evaluation
There are several suggestions regarding the definition of the term software architecture. Yet discussions concerning the subject are ambiguous. This leads to unclear discussions and slow scientific progress. This paper suggests a coherent set of properties a Taxonomy of Orthogonal Properties of Software Architecture (TOPSA) that enables more precise communication within the software architecture d
The popularization of parallelism is arguably the most fundamental computing challenge for years to come. We present an approach where parallel programming takes place in a restricted (sub-Turing-complete), logic-based declarative language, embedded in Java. Our logic-based language, PQL, can express the parallel elements of a computing task, while regular Java code captures sequential elements. T
Metabolic Syndrome (MetS) is multivariate disease, clustered with socioeconomic and behavioral risk factors. Investigations about epidemiology estimative could be a prevention strategy. Aim: to investigate the prevalence of metabolic syndrome and its associated factors in adult population in Fernando de Noronha Archipelago (PE-Brazil). Methods: A cross-sectional study was performed on a representa
