V. Garcia, Liana Barachisio Lisboa, S. Meira, E. Almeida, D. Lucrédio, Renata Pontin de Mattos Fortes
The growing interest of software reuse by software organizations makes adoption and evaluation of reuse an essential activity. Many organizations struggle in their attempts to select appropriate reuse practices (methods, techniques and tools support) in their processes. In this way, we propose a reuse assessment method to evaluate the organization's capability of software reuse in an efficient way.
{"title":"Towards an Assessment Method for Software Reuse Capability (Short Paper)","authors":"V. Garcia, Liana Barachisio Lisboa, S. Meira, E. Almeida, D. Lucrédio, Renata Pontin de Mattos Fortes","doi":"10.1109/QSIC.2008.58","DOIUrl":"https://doi.org/10.1109/QSIC.2008.58","url":null,"abstract":"The growing interest of software reuse by software organizations makes adoption and evaluation of reuse an essential activity. Many organizations struggle in their attempts to select appropriate reuse practices (methods, techniques and tools support) in their processes. In this way, we propose a reuse assessment method to evaluate the organization's capability of software reuse in an efficient way.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"171 2-3 1","pages":"294-299"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"78008317","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}
Software inspection is the most powerful static quality assurance method. However, the inspection process needs to be monitored continuously and refined when it is not producing expected results. We suggest using prescriptive metrics for following the effectiveness of the inspection process and process pattern approach for introducing improvement actions that steer the process into right direction. We have analyzed the inspection process data from two year time period in a large software development organization. The data is compared to organization-specific prescriptive metrics. The measurements show that limits set by metrics are exceeded in some cases and the process needs improvement. Prescriptive metrics set helps in identifying the weak points in the process. Patterns provide a lightweight and practicable approach for defining the targets of improvement. In the case organization, prescriptive metrics and patterns worked well in instantiating the inspection process improvement.
{"title":"Steering the inspection process with prescriptive metrics and process patterns","authors":"L. Harjumaa, I. Tervonen, Sirpa Salmela","doi":"10.1109/QSIC.2008.27","DOIUrl":"https://doi.org/10.1109/QSIC.2008.27","url":null,"abstract":"Software inspection is the most powerful static quality assurance method. However, the inspection process needs to be monitored continuously and refined when it is not producing expected results. We suggest using prescriptive metrics for following the effectiveness of the inspection process and process pattern approach for introducing improvement actions that steer the process into right direction. We have analyzed the inspection process data from two year time period in a large software development organization. The data is compared to organization-specific prescriptive metrics. The measurements show that limits set by metrics are exceeded in some cases and the process needs improvement. Prescriptive metrics set helps in identifying the weak points in the process. Patterns provide a lightweight and practicable approach for defining the targets of improvement. In the case organization, prescriptive metrics and patterns worked well in instantiating the inspection process improvement.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"640 1","pages":"285-293"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"74729262","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}
The system-level size measures are particularly important in software project management as tasks such as planning and estimating the cost and schedule of software development can be performed more effectively when a size estimate of the entire system is available. However, due to the black-box nature of components, traditional software measures are not adequate as system-level measures for component-based systems (CBS). Thus, if a system-level size is required, alternate measures should be used for sizing CBS. In this paper, we present a function point like approach, named component point to measure the system-level size of a CBS using the CBS specification written in UML. The component point approach integrates two software measures and extends an existing size measure from the more matured object-oriented paradigm to the related and relatively young CBS discipline. We also suggest a customized set of general system characteristics so as to make our measure more relevant to CBS.
{"title":"A Method for Measuring the Size of a Component-Based System Specification","authors":"T. Wijayasiriwardhane, R. Lai","doi":"10.1109/QSIC.2008.17","DOIUrl":"https://doi.org/10.1109/QSIC.2008.17","url":null,"abstract":"The system-level size measures are particularly important in software project management as tasks such as planning and estimating the cost and schedule of software development can be performed more effectively when a size estimate of the entire system is available. However, due to the black-box nature of components, traditional software measures are not adequate as system-level measures for component-based systems (CBS). Thus, if a system-level size is required, alternate measures should be used for sizing CBS. In this paper, we present a function point like approach, named component point to measure the system-level size of a CBS using the CBS specification written in UML. The component point approach integrates two software measures and extends an existing size measure from the more matured object-oriented paradigm to the related and relatively young CBS discipline. We also suggest a customized set of general system characteristics so as to make our measure more relevant to CBS.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"66 1","pages":"329-337"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"87161420","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}
W. Grieskamp, N. Kicillof, Dave MacDonald, A. Nandan, Keith Stobie, F. L. Wurden, Danpo Zhang
Microsoft is producing technical documentation for Windows client-server and server-server protocols to enable licensees to produce interoperable server products. This paper describes certain aspects of a new quality assurance process for technical documents as it is in place at Microsoft. We are applying various test methods including, when appropriate, a model-based approach. The paper uses the Server Message Block Protocol Version 2 (SMB2) as a running example to illustrate the process.
{"title":"Model-Based Quality Assurance of the SMB2 Protocol Documentation","authors":"W. Grieskamp, N. Kicillof, Dave MacDonald, A. Nandan, Keith Stobie, F. L. Wurden, Danpo Zhang","doi":"10.1109/QSIC.2008.34","DOIUrl":"https://doi.org/10.1109/QSIC.2008.34","url":null,"abstract":"Microsoft is producing technical documentation for Windows client-server and server-server protocols to enable licensees to produce interoperable server products. This paper describes certain aspects of a new quality assurance process for technical documents as it is in place at Microsoft. We are applying various test methods including, when appropriate, a model-based approach. The paper uses the Server Message Block Protocol Version 2 (SMB2) as a running example to illustrate the process.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"149 1","pages":"235-240"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"82845000","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}
Wei Huang, Ru Li, C. Maple, Hongji Yang, D. Foskett, Vince Cleaver
Software engineering has proven to be very important for standard software development. But, can Web applications be engineered as well? Currently, J2EE, Apache/Perl/PDP/MySQL and .NET have been universally accepted as Web application development technology, but there is no universal accepted methodology for Web application development process. Web application needs to be engineered by moving focus from technology to process. In this paper, a novel lifecycle model for Web application development in SMEs has been proposed. It includes two iterative process phases with a pre-iterative sequential process phase. This model has been applied to a real-world project and the result has proved its potential to shape the way on how web applications can be engineered in SMEs.
{"title":"Web Application Development Lifecycle for Small Medium-Sized Enterprises (SMEs) (Short Paper)","authors":"Wei Huang, Ru Li, C. Maple, Hongji Yang, D. Foskett, Vince Cleaver","doi":"10.1109/QSIC.2008.43","DOIUrl":"https://doi.org/10.1109/QSIC.2008.43","url":null,"abstract":"Software engineering has proven to be very important for standard software development. But, can Web applications be engineered as well? Currently, J2EE, Apache/Perl/PDP/MySQL and .NET have been universally accepted as Web application development technology, but there is no universal accepted methodology for Web application development process. Web application needs to be engineered by moving focus from technology to process. In this paper, a novel lifecycle model for Web application development in SMEs has been proposed. It includes two iterative process phases with a pre-iterative sequential process phase. This model has been applied to a real-world project and the result has proved its potential to shape the way on how web applications can be engineered in SMEs.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"40 1","pages":"247-252"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89357898","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}
Agent-oriented software engineering (AOSE) has the potential to revolutionize critical software systems by employing autonomy, adaptability, and robustness mechanisms advantageous to essential infrastructure. Yet, requisite with critical software is the need for dependability techniques to provide high assurance that the multi-agent system (MAS) will function as intended. In this paper we investigate how dynamic event/fault trees (DEFT) can be utilized for AOSE as a mechanism to analyze and reason about agent behavior and failures. Specifically, we: (1) adapt DEFT for MAS to identify and analyze necessary safety responsibilities; (2) show how the use of Galileo, the tool for DEFT probabilistic risk assessment, assists in developing a more robust MAS; and, (3) identify necessary AOSE-specific enhancements for DEFT needed to better support the dependability analysis of MAS. We illustrate this work through an application to a proposed NASA agent-based satellite swarm.
{"title":"Dynamic Event/Fault Tree Analysis of Multi-agent Systems Using Galileo","authors":"J. Dehlinger, J. Dugan","doi":"10.1109/QSIC.2008.14","DOIUrl":"https://doi.org/10.1109/QSIC.2008.14","url":null,"abstract":"Agent-oriented software engineering (AOSE) has the potential to revolutionize critical software systems by employing autonomy, adaptability, and robustness mechanisms advantageous to essential infrastructure. Yet, requisite with critical software is the need for dependability techniques to provide high assurance that the multi-agent system (MAS) will function as intended. In this paper we investigate how dynamic event/fault trees (DEFT) can be utilized for AOSE as a mechanism to analyze and reason about agent behavior and failures. Specifically, we: (1) adapt DEFT for MAS to identify and analyze necessary safety responsibilities; (2) show how the use of Galileo, the tool for DEFT probabilistic risk assessment, assists in developing a more robust MAS; and, (3) identify necessary AOSE-specific enhancements for DEFT needed to better support the dependability analysis of MAS. We illustrate this work through an application to a proposed NASA agent-based satellite swarm.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"7 1","pages":"429-434"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"80356587","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}
Test purposes have been presented as a solution to avoid the state space explosion when selecting test cases from formal models. Although such techniques work very well with regard to the speed of the test derivation, they leave the tester with one important task that influences the quality of the overall testing process: Test purposes have to be formulated manually. In this paper, we present an approach that assists a test engineer with test purpose design in two ways: It allows automatic generation of coverage based test suites and can be used to automatically exercise those aspects of the system that manually test purposes missed. We consider coverage of LOTOS specifications, and show how labeled transition systems derived from such specifications have to be extended in order to allow the application of logical coverage criteria to LOTOS specifications. We then show how existing tools can be used to efficiently derive test cases and suggest how to use the coverage information to minimize test suites while generating them.
{"title":"Coverage Based Testing with Test Purposes","authors":"G. Fraser, Martin Weiglhofer, F. Wotawa","doi":"10.1109/QSIC.2008.41","DOIUrl":"https://doi.org/10.1109/QSIC.2008.41","url":null,"abstract":"Test purposes have been presented as a solution to avoid the state space explosion when selecting test cases from formal models. Although such techniques work very well with regard to the speed of the test derivation, they leave the tester with one important task that influences the quality of the overall testing process: Test purposes have to be formulated manually. In this paper, we present an approach that assists a test engineer with test purpose design in two ways: It allows automatic generation of coverage based test suites and can be used to automatically exercise those aspects of the system that manually test purposes missed. We consider coverage of LOTOS specifications, and show how labeled transition systems derived from such specifications have to be extended in order to allow the application of logical coverage criteria to LOTOS specifications. We then show how existing tools can be used to efficiently derive test cases and suggest how to use the coverage information to minimize test suites while generating them.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"86 1","pages":"199-208"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"83500276","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}
Importance measures of a system provide a sense of the relative priorities of the components from a system reliability perspective. These measures can thus be used to identify critical components and to guide the allocation of resources so that the system reliability can be improved in a cost effective manner. Importance measures are widely used in many engineered hardware and electro-mechanical systems. Their use in the engineering of software systems, however, is lacking. In this paper we develop an analytical methodology to compute the importance measures of a software system. The analytical treatment facilitates an assessment of the sensitivity of the importance measures of a software system to the uncertainties in its architectural parameters, component reliabilities, and operational profiles. The capability of enabling sensitivity analysis, which is a key strength of our approach, is crucial to the adaptation of importance measures in software because the parameters characterizing a software system are inherently expected to be uncertain, especially in the design phase. We illustrate the potential of our approach to provide valuable information towards resource allocation decisions using an example application from the European Space Agency.
{"title":"Importance Measures for a Modular Software System (Short Paper)","authors":"L. Fiondella, S. Gokhale","doi":"10.1109/QSIC.2008.42","DOIUrl":"https://doi.org/10.1109/QSIC.2008.42","url":null,"abstract":"Importance measures of a system provide a sense of the relative priorities of the components from a system reliability perspective. These measures can thus be used to identify critical components and to guide the allocation of resources so that the system reliability can be improved in a cost effective manner. Importance measures are widely used in many engineered hardware and electro-mechanical systems. Their use in the engineering of software systems, however, is lacking. In this paper we develop an analytical methodology to compute the importance measures of a software system. The analytical treatment facilitates an assessment of the sensitivity of the importance measures of a software system to the uncertainties in its architectural parameters, component reliabilities, and operational profiles. The capability of enabling sensitivity analysis, which is a key strength of our approach, is crucial to the adaptation of importance measures in software because the parameters characterizing a software system are inherently expected to be uncertain, especially in the design phase. We illustrate the potential of our approach to provide valuable information towards resource allocation decisions using an example application from the European Space Agency.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"95 1","pages":"338-343"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"75737895","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}
Xiaofang Zhang, Baowen Xu, Zhenyu Chen, Changhai Nie, Leifang Li
As the cost of executing and maintaining a large test suite is always expensive, many test suite reduction techniques have been proposed and some empirical studies of test suite reduction techniques have already been reported. The aim of this paper is to provide a guideline for choosing the appropriate test suite reduction techniques for Boolean specification-based testing. Four typical heuristic reduction strategies: G, GE, GRE, and H are introduced to be compared empirically. Furthermore, testing requirement optimization is combined to enhance these four reduction strategies. This paper presents the empirical evaluation of these reduction strategies based on a set of Boolean specifications from TCAS II.
{"title":"An Empirical Evaluation of Test Suite Reduction for Boolean Specification-Based Testing (Short Paper)","authors":"Xiaofang Zhang, Baowen Xu, Zhenyu Chen, Changhai Nie, Leifang Li","doi":"10.1109/QSIC.2008.25","DOIUrl":"https://doi.org/10.1109/QSIC.2008.25","url":null,"abstract":"As the cost of executing and maintaining a large test suite is always expensive, many test suite reduction techniques have been proposed and some empirical studies of test suite reduction techniques have already been reported. The aim of this paper is to provide a guideline for choosing the appropriate test suite reduction techniques for Boolean specification-based testing. Four typical heuristic reduction strategies: G, GE, GRE, and H are introduced to be compared empirically. Furthermore, testing requirement optimization is combined to enhance these four reduction strategies. This paper presents the empirical evaluation of these reduction strategies based on a set of Boolean specifications from TCAS II.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"56 1","pages":"270-275"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"90999291","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}
Defects have been compromising quality of software and costing a lot to find and fix. Thus a number of effective tools have been built to automatically find defects by analyzing code statically. These tools apply various techniques and detect a wide range of defects, with a little overlap among defect libraries. Unfortunately, the advantages of tools' defect detection capacity are stubborn to combine, due to the unique style each tool follows when generating analysis reports. In this paper, we propose an approach to merge results from different tools and report them in a universal manner. Besides, two prioritizing policies are introduced to rank results so as to raise users' efficiency. Finally, the approach and prioritizing policies are implemented in an integrated tool by merging results from three independent analyzing tools. In this way, end users may comfortably benefit from more than one static analysis tool and thus improve software's quality.
{"title":"An Approach to Merge Results of Multiple Static Analysis Tools (Short Paper)","authors":"Na Meng, Qianxiang Wang, Qian Wu, Hong Mei","doi":"10.1109/QSIC.2008.30","DOIUrl":"https://doi.org/10.1109/QSIC.2008.30","url":null,"abstract":"Defects have been compromising quality of software and costing a lot to find and fix. Thus a number of effective tools have been built to automatically find defects by analyzing code statically. These tools apply various techniques and detect a wide range of defects, with a little overlap among defect libraries. Unfortunately, the advantages of tools' defect detection capacity are stubborn to combine, due to the unique style each tool follows when generating analysis reports. In this paper, we propose an approach to merge results from different tools and report them in a universal manner. Besides, two prioritizing policies are introduced to rank results so as to raise users' efficiency. Finally, the approach and prioritizing policies are implemented in an integrated tool by merging results from three independent analyzing tools. In this way, end users may comfortably benefit from more than one static analysis tool and thus improve software's quality.","PeriodicalId":6446,"journal":{"name":"2008 The Eighth International Conference on Quality Software","volume":"7 1","pages":"169-174"},"PeriodicalIF":0.0,"publicationDate":"2008-08-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89961079","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
扫码关注我们
求助内容：
应助结果提醒方式：