Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883783
W. Tsai, Xiaoying Bai, R. Paul, G. Devaraj, Vishal Agarwal
The windowing technique has been a popular method to address the Y2K problem. In fact, about 80% of the systems used this technique. Unfortunately, the windowing technique is a temporary solution and windows will expire some time later. This paper proposes several approaches to address the expired window problem including modification and testing techniques. In software modification, ripple effect technique is used to locate all the necessary software elements need to be changed. In testing, both regression techniques and new test case generation techniques are proposed.
{"title":"An approach to modify and test expired window logic","authors":"W. Tsai, Xiaoying Bai, R. Paul, G. Devaraj, Vishal Agarwal","doi":"10.1109/APAQ.2000.883783","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883783","url":null,"abstract":"The windowing technique has been a popular method to address the Y2K problem. In fact, about 80% of the systems used this technique. Unfortunately, the windowing technique is a temporary solution and windows will expire some time later. This paper proposes several approaches to address the expired window problem including modification and testing techniques. In software modification, ripple effect technique is used to locate all the necessary software elements need to be changed. In testing, both regression techniques and new test case generation techniques are proposed.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120995607","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883787
S. Reid
This paper covers both the development of BS 7925-2 and compliance with the finished standard. The process used to produce BS 7925-2 is described by presenting a history of its development, showing how initial chaotic development evolved with experience into a systematic process. This process was found to bear a strong resemblance to the software engineering process, and borrowed techniques from it, drawing particularly from those that support verification and validation. The knowledge gained from this development should be applicable to many areas of standardisation. The most important clauses of BS 7925-2 describe a generic test process and definitions of test case design techniques and test measurement techniques. These are explained in detail and compliance with BS 7925-2 is described in the context of following the test process, which, in turn, requires the user to select techniques from the other two clauses.
{"title":"BS 7925-2: the software component testing standard","authors":"S. Reid","doi":"10.1109/APAQ.2000.883787","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883787","url":null,"abstract":"This paper covers both the development of BS 7925-2 and compliance with the finished standard. The process used to produce BS 7925-2 is described by presenting a history of its development, showing how initial chaotic development evolved with experience into a systematic process. This process was found to bear a strong resemblance to the software engineering process, and borrowed techniques from it, drawing particularly from those that support verification and validation. The knowledge gained from this development should be applicable to many areas of standardisation. The most important clauses of BS 7925-2 describe a generic test process and definitions of test case design techniques and test measurement techniques. These are explained in detail and compliance with BS 7925-2 is described in the context of following the test process, which, in turn, requires the user to select techniques from the other two clauses.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127358238","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883789
D. Flater
In the manufacturing domain, few new distributed systems are built ground-up; most contain wrapped legacy components. While the legacy components themselves are already well-tested, imperfect integration can introduce subtle faults that are outside the prime target area of generic integration and system tests. One might postulate that focused testing for integration faults could improve the yield of detected faults when used as part of a balanced integration and system test effort. We define such a testing strategy and describe a trial application to a prototype control system. The results suggest that focused testing does not add significant value over traditional black-box testing.
{"title":"Testing for imperfect integration of legacy software components","authors":"D. Flater","doi":"10.1109/APAQ.2000.883789","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883789","url":null,"abstract":"In the manufacturing domain, few new distributed systems are built ground-up; most contain wrapped legacy components. While the legacy components themselves are already well-tested, imperfect integration can introduce subtle faults that are outside the prime target area of generic integration and system tests. One might postulate that focused testing for integration faults could improve the yield of detected faults when used as part of a balanced integration and system test effort. We define such a testing strategy and describe a trial application to a prototype control system. The results suggest that focused testing does not add significant value over traditional black-box testing.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"158 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114730660","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883788
T. H. Tse, Xin Feng, T. Chen
Most research on weak mutation testing focuses on predicate statements. Relative little attention has been paid to arithmetic expressions. In this paper we analyse the latter type of expression and prove that, given an atomic arithmetic expression, if it contains no variable or if the operator is the unary "++" or "--", then a single test case is sufficient and necessary to kill any fundamental mutant; otherwise, two test cases are sufficient and necessary.
{"title":"On the completeness of test cases for atomic arithmetic expressions","authors":"T. H. Tse, Xin Feng, T. Chen","doi":"10.1109/APAQ.2000.883788","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883788","url":null,"abstract":"Most research on weak mutation testing focuses on predicate statements. Relative little attention has been paid to arithmetic expressions. In this paper we analyse the latter type of expression and prove that, given an atomic arithmetic expression, if it contains no variable or if the operator is the unary \"++\" or \"--\", then a single test case is sufficient and necessary to kill any fundamental mutant; otherwise, two test cases are sufficient and necessary.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123543371","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883785
D. Ram, S. Raju
Estimating different characteristics viz., size, cost, etc. of software during different phases of software development is required to manage the resources effectively. Function points measure can be used as an input to estimate these characteristics of software. The Traditional Function Point Counting Procedure (TFPCP) can not be used to measure the functionality of an Object Oriented (OO) system. This paper suggests a counting procedure to measure the functionality of an OO system during the design phase from a designers' perspective. It is adapted from the TFPCP. The main aim of this paper is to use all the available information during the OO design phase to estimate Object Oriented Design Function Points (OODFP). The novel feature of this approach is that it considers all the basic concepts of OO systems such as inheritance, aggregation, association and polymorphism.
{"title":"Object oriented design function points","authors":"D. Ram, S. Raju","doi":"10.1109/APAQ.2000.883785","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883785","url":null,"abstract":"Estimating different characteristics viz., size, cost, etc. of software during different phases of software development is required to manage the resources effectively. Function points measure can be used as an input to estimate these characteristics of software. The Traditional Function Point Counting Procedure (TFPCP) can not be used to measure the functionality of an Object Oriented (OO) system. This paper suggests a counting procedure to measure the functionality of an OO system during the design phase from a designers' perspective. It is adapted from the TFPCP. The main aim of this paper is to use all the available information during the OO design phase to estimate Object Oriented Design Function Points (OODFP). The novel feature of this approach is that it considers all the basic concepts of OO systems such as inheritance, aggregation, association and polymorphism.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128902160","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883774
B. M. Subraya, S. Subrahmanya
Performance of many Web sites depends on the load on the site at peak time under varying conditions. Performance testing is normally conducted in reasonably simulated environment with the help of performance testing tools. However, performance of a Web site depends on various parameters and each parameter must be tested under varying stress levels. It is not possible to draw a common denominator for performance parameters to test the Web site due to complexity of Web sites. Different parts of the Web site must be tested with different parameters under varying condition and stress level. In such circumstances, it is necessary to decompose the Web site into many components, which represents the behavior of various business components. These business components are mapped to various objects that truly represent the behavior and structure of the part of the web site. These objects are subjected to performance testing with different parameters and stress levels. This paper addresses the new testing process, which uses the concept of decomposing the behavior of the Web site into testable components, which are mapped onto testable objects. These testable objects are subjected to performance testing under varied performance parameters and stress levels.
{"title":"Object driven performance testing of Web applications","authors":"B. M. Subraya, S. Subrahmanya","doi":"10.1109/APAQ.2000.883774","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883774","url":null,"abstract":"Performance of many Web sites depends on the load on the site at peak time under varying conditions. Performance testing is normally conducted in reasonably simulated environment with the help of performance testing tools. However, performance of a Web site depends on various parameters and each parameter must be tested under varying stress levels. It is not possible to draw a common denominator for performance parameters to test the Web site due to complexity of Web sites. Different parts of the Web site must be tested with different parameters under varying condition and stress level. In such circumstances, it is necessary to decompose the Web site into many components, which represents the behavior of various business components. These business components are mapped to various objects that truly represent the behavior and structure of the part of the web site. These objects are subjected to performance testing with different parameters and stress levels. This paper addresses the new testing process, which uses the concept of decomposing the behavior of the Web site into testable components, which are mapped onto testable objects. These testable objects are subjected to performance testing under varied performance parameters and stress levels.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132018141","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883795
A. Merceron, G. Pinna
The formal verification of properties in reactive real-time systems is crucial, as these systems are often safety-critical ones. Refinement is a relevant operation in synchronous languages. In this paper, we argue that, in the synchronous approach to the design and implementation of reactive real-time systems, modular verification (from the point of view of the refining program) is best achieved with observers.
{"title":"Refinement and modular verification with observers","authors":"A. Merceron, G. Pinna","doi":"10.1109/APAQ.2000.883795","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883795","url":null,"abstract":"The formal verification of properties in reactive real-time systems is crucial, as these systems are often safety-critical ones. Refinement is a relevant operation in synchronous languages. In this paper, we argue that, in the synchronous approach to the design and implementation of reactive real-time systems, modular verification (from the point of view of the refining program) is best achieved with observers.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125284582","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883801
T. Chen, P. Poon, Sau-Fun Tang, Yuen-Tak Yu
Many useful test case construction methods that are based on important aspects of the specification have been proposed in the literature. A comprehensive test suite thus obtained is often very large and yet is non-redundant with respect to the aspects identified from the specification. This paper addresses the problem of selecting a subset of test cases from such a test suite. We propose the use of white box criteria to select test cases from the initial black-box-generated test suite. We illustrate our ideas with examples and demonstrate the viability and benefits of our approach by means of a case study.
{"title":"White on black: a white-box-oriented approach for selecting black box-generated test cases","authors":"T. Chen, P. Poon, Sau-Fun Tang, Yuen-Tak Yu","doi":"10.1109/APAQ.2000.883801","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883801","url":null,"abstract":"Many useful test case construction methods that are based on important aspects of the specification have been proposed in the literature. A comprehensive test suite thus obtained is often very large and yet is non-redundant with respect to the aspects identified from the specification. This paper addresses the problem of selecting a subset of test cases from such a test suite. We propose the use of white box criteria to select test cases from the initial black-box-generated test suite. We illustrate our ideas with examples and demonstrate the viability and benefits of our approach by means of a case study.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133632718","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883799
I. Hampton, B. Quinn
The consensus of opinion of a sample of Mass Transit Railway Corporation (MTRC) management and engineering staff is that projects containing software products have proved difficult to deliver to programme and within budget. This fact is further exasperated when a particular supplier does not subscribe to a "mature" software development process (SDP), thereby failing to either sustain consistency in the application or provide the client with visibility of progress throughout the development and manufacturing process. The introduction of standard SDPs has recently become an integral part of many contract specifications. This development has provided a defined measure of visibility of the SDP to the client. Software is of a nebulous composition, as opposed to being a physical commodity which can be visibly "measured". The quality of the software product is therefore deemed analogous to the processes adopted during production. The result is that the SDP can be ameliorated to formulate a framework for establishing a robust set of measurement criteria. This paper describes the approach adopted by MTRC in measuring the progress of a safety-related software-intensive development project. It should be noted however, that the exercise described in this paper is not constrained to software development, and the methodology can be adapted to measure any phase, element or activity of any project.
{"title":"Software project measurement criteria","authors":"I. Hampton, B. Quinn","doi":"10.1109/APAQ.2000.883799","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883799","url":null,"abstract":"The consensus of opinion of a sample of Mass Transit Railway Corporation (MTRC) management and engineering staff is that projects containing software products have proved difficult to deliver to programme and within budget. This fact is further exasperated when a particular supplier does not subscribe to a \"mature\" software development process (SDP), thereby failing to either sustain consistency in the application or provide the client with visibility of progress throughout the development and manufacturing process. The introduction of standard SDPs has recently become an integral part of many contract specifications. This development has provided a defined measure of visibility of the SDP to the client. Software is of a nebulous composition, as opposed to being a physical commodity which can be visibly \"measured\". The quality of the software product is therefore deemed analogous to the processes adopted during production. The result is that the SDP can be ameliorated to formulate a framework for establishing a robust set of measurement criteria. This paper describes the approach adopted by MTRC in measuring the progress of a safety-related software-intensive development project. It should be noted however, that the exercise described in this paper is not constrained to software development, and the methodology can be adapted to measure any phase, element or activity of any project.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133556707","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883794
Doug Goldson
This paper presents a case study in interface modelling and testing using the Z specification language. The paper models a single feature of a VCR and the use of Z allows the model to be tested from different points of view, including an approach to interface testing in which system dynamics are categorised according to formal attributes that are relevant to user cognition.
{"title":"Formal modelling of interactive systems","authors":"Doug Goldson","doi":"10.1109/APAQ.2000.883794","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883794","url":null,"abstract":"This paper presents a case study in interface modelling and testing using the Z specification language. The paper models a single feature of a VCR and the use of Z allows the model to be tested from different points of view, including an approach to interface testing in which system dynamics are categorised according to formal attributes that are relevant to user cognition.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128405806","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：