Pub Date : 2000-10-30DOI: 10.1109/APAQ.2000.883792
Ravi Prakash Nandivada, Arunava Chandra, Saswata Dutta, Gargi Keeni
Discusses a decision-making model which can be used to determine the efficiency of a code review process. This model is based on statistical techniques such as control charts. The model has nine quadrants, each of which depicts a range of values of the cost and yield of a code review. The efficiency of the code review in detecting defects is determined by taking inputs from past data, in terms of the costs and yields of those code reviews. This estimate also provides an in-process decision-making tool. Other tools can be used effectively, in conjunction with this model, to plan for code reviews and to forecast the number of defects that could be expected in the reviews. This model can be successfully used to decide what the next step of the operational process should be. The decisions taken using this model help to reduce the number of defects present in the software delivered to the customer.
{"title":"The 9 quadrant model for code reviews","authors":"Ravi Prakash Nandivada, Arunava Chandra, Saswata Dutta, Gargi Keeni","doi":"10.1109/APAQ.2000.883792","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883792","url":null,"abstract":"Discusses a decision-making model which can be used to determine the efficiency of a code review process. This model is based on statistical techniques such as control charts. The model has nine quadrants, each of which depicts a range of values of the cost and yield of a code review. The efficiency of the code review in detecting defects is determined by taking inputs from past data, in terms of the costs and yields of those code reviews. This estimate also provides an in-process decision-making tool. Other tools can be used effectively, in conjunction with this model, to plan for code reviews and to forecast the number of defects that could be expected in the reviews. This model can be successfully used to decide what the next step of the operational process should be. The decisions taken using this model help to reduce the number of defects present in the software delivered to the customer.","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":"129608321","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.883778
C. Pons, M. Prieto, L. Olsina
Although quality is not easy to evaluate since it is a complex concept compound by different aspects, several properties that make a good object-oriented design have been recognized and widely accepted by the software engineering community. We agree that both the traditional and the new object-oriented properties should be analyzed in assessing the quality of object-oriented design. However, we believe that it is necessary to pay special attention to the polymorphism concept and metric, since they should be considered one of the key concerns in determining the quality of an object-oriented system. In this paper, we have given a rigorous definition of polymorphism. On top of this formalization we propose a metric that provides an objective and precise mechanism to detect and quantify dynamic polymorphism. The metric takes information coming from the first stages of the development process giving developers the opportunity to early evaluate and improve the quality of the software product. Finally, a first approach to the theoretical validation of the metric is presented.
{"title":"A formal mechanism for assessing polymorphism in object-oriented systems","authors":"C. Pons, M. Prieto, L. Olsina","doi":"10.1109/APAQ.2000.883778","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883778","url":null,"abstract":"Although quality is not easy to evaluate since it is a complex concept compound by different aspects, several properties that make a good object-oriented design have been recognized and widely accepted by the software engineering community. We agree that both the traditional and the new object-oriented properties should be analyzed in assessing the quality of object-oriented design. However, we believe that it is necessary to pay special attention to the polymorphism concept and metric, since they should be considered one of the key concerns in determining the quality of an object-oriented system. In this paper, we have given a rigorous definition of polymorphism. On top of this formalization we propose a metric that provides an objective and precise mechanism to detect and quantify dynamic polymorphism. The metric takes information coming from the first stages of the development process giving developers the opportunity to early evaluate and improve the quality of the software product. Finally, a first approach to the theoretical validation of the metric is presented.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"3 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":"116537576","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.883773
Chien-Hung Liu, D. Kung, P. Hsia, Chih-Tung Hsu
Recently, the extraordinary growth in the World Wide Web has been sweeping through business and industry. Many companies have developed or integrated their mission-critical applications using Web technologies. As Web applications become complex, testing Web applications becomes crucial. This paper extends traditional data flow testing techniques to Web applications. Several data flow issues for analyzing HTML documents in Web applications are discussed. A test model that captures data flow test artifacts of Web applications is presented. In the test model, each component of a Web application is modeled as an object. The data flow information of the Web application is captured using flow graphs. From the test model, data flow test cases for the Web application then can be derived based on the intra-object, inter-object, and inter-client perspectives.
{"title":"Object-based data flow testing of web applications","authors":"Chien-Hung Liu, D. Kung, P. Hsia, Chih-Tung Hsu","doi":"10.1109/APAQ.2000.883773","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883773","url":null,"abstract":"Recently, the extraordinary growth in the World Wide Web has been sweeping through business and industry. Many companies have developed or integrated their mission-critical applications using Web technologies. As Web applications become complex, testing Web applications becomes crucial. This paper extends traditional data flow testing techniques to Web applications. Several data flow issues for analyzing HTML documents in Web applications are discussed. A test model that captures data flow test artifacts of Web applications is presented. In the test model, each component of a Web application is modeled as an object. The data flow information of the Web application is captured using flow graphs. From the test model, data flow test cases for the Web application then can be derived based on the intra-object, inter-object, and inter-client perspectives.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"54 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":"134506571","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.883781
N. Malevris, E. Petrova
Software testing is widely used as a means of increasing software reliability. The prohibitive nature of exhaustive testing has given rise to the problem of determining when a system has reached an acceptable reliability slate and can be released. This has probably become the hardest problem facing a project manager. In this paper, a stopping rule that indicates the appropriate time at which to stop testing is presented. The rule automatically adapts to modifications in the assumptions, since it can be applied under any software error-counting model. An investigation of the properties of the rule is described and the results obtained after applying it to a set of real data in conjunction with two statistical models are presented.
{"title":"On the determination of an appropriate time for ending the software testing process","authors":"N. Malevris, E. Petrova","doi":"10.1109/APAQ.2000.883781","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883781","url":null,"abstract":"Software testing is widely used as a means of increasing software reliability. The prohibitive nature of exhaustive testing has given rise to the problem of determining when a system has reached an acceptable reliability slate and can be released. This has probably become the hardest problem facing a project manager. In this paper, a stopping rule that indicates the appropriate time at which to stop testing is presented. The rule automatically adapts to modifications in the assumptions, since it can be applied under any software error-counting model. An investigation of the properties of the rule is described and the results obtained after applying it to a set of real data in conjunction with two statistical models are presented.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"36 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":"132423280","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.883779
R. Sitte
This paper proposes a framework for assessing quantitatively the error-proneness of computer program modules. The model uses an information theory approach to derive an error proneness index, that can be used in a practical way. Debugging and testing rake at least 40% of a software project's effort, but do not uncover all defects. While current research looks at identifying problem-modules in a program, no attempt is made for a quantitative error-proneness evaluation. By quantitatively assessing a module's susceptibility to error, we are able to identify error prone paths in a program and enhance testing efficiency. The goal is to identify error prone paths in a program using genetic algorithms. This increases software reliability, aids in testing design, and reduces software development cost.
{"title":"A framework for quantifying error proneness in software","authors":"R. Sitte","doi":"10.1109/APAQ.2000.883779","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883779","url":null,"abstract":"This paper proposes a framework for assessing quantitatively the error-proneness of computer program modules. The model uses an information theory approach to derive an error proneness index, that can be used in a practical way. Debugging and testing rake at least 40% of a software project's effort, but do not uncover all defects. While current research looks at identifying problem-modules in a program, no attempt is made for a quantitative error-proneness evaluation. By quantitatively assessing a module's susceptibility to error, we are able to identify error prone paths in a program and enhance testing efficiency. The goal is to identify error prone paths in a program using genetic algorithms. This increases software reliability, aids in testing design, and reduces software development cost.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"25 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":"115996183","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.883786
Kecheng Liu, S. Zhou, Hongji Yang
The quality of software has an important bearing on the financial and safety aspects in our daily life. Assessing quality of software at the design level will provide ease and higher accuracy for users. However, there is a great gap between the rapid adoption of Object Oriented (OO) techniques and the slow speed of developing corresponding object oriented metric measures, especially object oriented design measures. To tackle this issue, we look into measuring the quality of Object Oriented designs during both software development and re-development processes. A set of OO design metrics has been derived from the existing work found in literature and been further extended. The paper also presents software tools for assisting software re-engineering using the metric measures developed; this has been illustrated with an example of the experiments conducted during our research, finally concluded with the lessons learned and intended further work.
{"title":"Quality metrics of object oriented design for software development and re-development","authors":"Kecheng Liu, S. Zhou, Hongji Yang","doi":"10.1109/APAQ.2000.883786","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883786","url":null,"abstract":"The quality of software has an important bearing on the financial and safety aspects in our daily life. Assessing quality of software at the design level will provide ease and higher accuracy for users. However, there is a great gap between the rapid adoption of Object Oriented (OO) techniques and the slow speed of developing corresponding object oriented metric measures, especially object oriented design measures. To tackle this issue, we look into measuring the quality of Object Oriented designs during both software development and re-development processes. A set of OO design metrics has been derived from the existing work found in literature and been further extended. The paper also presents software tools for assisting software re-engineering using the metric measures developed; this has been illustrated with an example of the experiments conducted during our research, finally concluded with the lessons learned and intended further work.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"58 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":"126657639","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.883798
M. Murugappan, Gargi Keeni
Six Sigma provides an effective mechanism to focus on customer requirements, through the improvement of process quality. In the Global Engineering Development Center of Tata Consultancy Services (TCS-GEDC) at Chennai, India, Six Sigma projects are being carried out with the objective of improving on-time delivery, product quality and in-process quality. This paper describes the application of the Six Sigma methodology, comprising the five phases Define, Measure, Analyze, Improve and Control, by taking the example of a project, and demonstrates the benefits attained.
{"title":"Quality improvement-the Six Sigma way","authors":"M. Murugappan, Gargi Keeni","doi":"10.1109/APAQ.2000.883798","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883798","url":null,"abstract":"Six Sigma provides an effective mechanism to focus on customer requirements, through the improvement of process quality. In the Global Engineering Development Center of Tata Consultancy Services (TCS-GEDC) at Chennai, India, Six Sigma projects are being carried out with the objective of improving on-time delivery, product quality and in-process quality. This paper describes the application of the Six Sigma methodology, comprising the five phases Define, Measure, Analyze, Improve and Control, by taking the example of a project, and demonstrates the benefits attained.","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":"125408384","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.883775
X. Cai, J. Chen
Distributed and multithreaded systems are usually much more complex to analyze statically or test dynamically due to the nondeterminism involved. Forcing the system to take a particular execution path manually may be fairly difficult sometimes. In this paper, we present our work in test control methods for distributed concurrent systems, and introduce the framework of our automated test control toolkit that can help users to realize some particular execution paths desired. The testing is specification-based: a test scenario is given as a pair of a test case and a control constraint expressing the partial order among certain events we are interested in. The test control is however based on a derived constraint only on shared objects. This allows us to develop more efficient test tools based on some unique code extension for different test scenarios. In our experiment, systems under testing consist of a set of processes, each in Java possibly with multiple threads, and communications among the processes are through CORBA.
{"title":"Control of nondeterminism in testing distributed multithreaded programs","authors":"X. Cai, J. Chen","doi":"10.1109/APAQ.2000.883775","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883775","url":null,"abstract":"Distributed and multithreaded systems are usually much more complex to analyze statically or test dynamically due to the nondeterminism involved. Forcing the system to take a particular execution path manually may be fairly difficult sometimes. In this paper, we present our work in test control methods for distributed concurrent systems, and introduce the framework of our automated test control toolkit that can help users to realize some particular execution paths desired. The testing is specification-based: a test scenario is given as a pair of a test case and a control constraint expressing the partial order among certain events we are interested in. The test control is however based on a derived constraint only on shared objects. This allows us to develop more efficient test tools based on some unique code extension for different test scenarios. In our experiment, systems under testing consist of a set of processes, each in Java possibly with multiple threads, and communications among the processes are through CORBA.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"9 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":"117197609","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.883793
S. Biffl, M. Halling, M. Köhle
The goal of software inspection is to identify defects and to measure the product and inspection process quality. Software development products that are suspected to contain a substantial number of defects after inspection may be subject to a second inspection cycle (re-inspection). So far, very few empirical results can be found on re-inspections. This paper reports on a controlled experiment that compares the effect of two inspection cycles. A software requirements document was re-inspected by 31 teams, after defects found during the initial inspection had been removed. We present data on the effectiveness, efficiency, net gain and return-on-investment from a second inspection cycle, and compare these results with data from the initial inspection. Models in the literature suggest decision criteria with regard to when to re-inspect, based on assumptions on the relationships of variables between the two inspection cycles. With experimental data, we evaluate these assumptions and the correctness of their decision criteria. The results of the experiment strongly support considering re-inspection as an option to improve product quality.
{"title":"Investigating the effect of a second software inspection cycle. Cost-benefit data from a large-scale experiment on reinspection of a software requirements document","authors":"S. Biffl, M. Halling, M. Köhle","doi":"10.1109/APAQ.2000.883793","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883793","url":null,"abstract":"The goal of software inspection is to identify defects and to measure the product and inspection process quality. Software development products that are suspected to contain a substantial number of defects after inspection may be subject to a second inspection cycle (re-inspection). So far, very few empirical results can be found on re-inspections. This paper reports on a controlled experiment that compares the effect of two inspection cycles. A software requirements document was re-inspected by 31 teams, after defects found during the initial inspection had been removed. We present data on the effectiveness, efficiency, net gain and return-on-investment from a second inspection cycle, and compare these results with data from the initial inspection. Models in the literature suggest decision criteria with regard to when to re-inspect, based on assumptions on the relationships of variables between the two inspection cycles. With experimental data, we evaluate these assumptions and the correctness of their decision criteria. The results of the experiment strongly support considering re-inspection as an option to improve product quality.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"100 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":"124125803","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.883803
A. A. Keshlaf, K. Hashim
Software industry is facing many types of risks that make software development projects miss their planned schedule, time and quality. Hence, the urge to manage such risks if one wants to avoid the above problems. However, available software risk management tools present many weaknesses and above all, they are few. This paper is a contribution to increase the number of tools in the library of software risk management tools. The main features of a prototype tool called SoftRisk, which is developed to manage software risks, is presented. SoftRisk is designed based on a software risk management model that has been conceived in this research. This model can be thought of as a reference to any software risk management tool. Among others, contributions like risk estimation assistance, risk documentation, concentrating on top risks and graphic representation are discussed.
{"title":"A model and prototype tool to manage software risks","authors":"A. A. Keshlaf, K. Hashim","doi":"10.1109/APAQ.2000.883803","DOIUrl":"https://doi.org/10.1109/APAQ.2000.883803","url":null,"abstract":"Software industry is facing many types of risks that make software development projects miss their planned schedule, time and quality. Hence, the urge to manage such risks if one wants to avoid the above problems. However, available software risk management tools present many weaknesses and above all, they are few. This paper is a contribution to increase the number of tools in the library of software risk management tools. The main features of a prototype tool called SoftRisk, which is developed to manage software risks, is presented. SoftRisk is designed based on a software risk management model that has been conceived in this research. This model can be thought of as a reference to any software risk management tool. Among others, contributions like risk estimation assistance, risk documentation, concentrating on top risks and graphic representation are discussed.","PeriodicalId":432680,"journal":{"name":"Proceedings First Asia-Pacific Conference on Quality Software","volume":"32 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":"124130592","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
扫码关注我们
求助内容：
应助结果提醒方式：