Pub Date : 1994-12-21DOI: 10.1109/STRQA.1994.526377
P. Jalote, Y.R. Muralidhara
There is an increasing interest in estimating and predicting the reliability of software systems. Many models exist for reliability estimation. Most of these models consider a software system as a black box and predict the reliability based on the failure data observed during testing. The application of these models require a fair amount of data collection, computation, and expertise and computation for interpreting the results. We propose a model that is based on the coverage history of the program. A software is modeled as a graph, and the reliability of a node is assumed to be a function of the number of times it gets executed during testing-the larger the number of times a node gets executed, the higher its reliability. The reliability of the software system is then computed through simulation by using the reliabilities of the individual nodes. With such a model, coverage analysis tools can easily be extended to compute the reliability also, thereby fully automating reliability estimation.
{"title":"A coverage based model for software reliability estimation","authors":"P. Jalote, Y.R. Muralidhara","doi":"10.1109/STRQA.1994.526377","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526377","url":null,"abstract":"There is an increasing interest in estimating and predicting the reliability of software systems. Many models exist for reliability estimation. Most of these models consider a software system as a black box and predict the reliability based on the failure data observed during testing. The application of these models require a fair amount of data collection, computation, and expertise and computation for interpreting the results. We propose a model that is based on the coverage history of the program. A software is modeled as a graph, and the reliability of a node is assumed to be a function of the number of times it gets executed during testing-the larger the number of times a node gets executed, the higher its reliability. The reliability of the software system is then computed through simulation by using the reliabilities of the individual nodes. With such a model, coverage analysis tools can easily be extended to compute the reliability also, thereby fully automating reliability estimation.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131526102","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526384
Y.R. Muralidhara, P. Jalote
Estimating the reliability of software is becoming increasingly important. There are a large number of models available for estimating reliability. Most of these models are computationally complex and require statistical inferencing to estimate the parameters. In addition, techniques for evaluating the results obtained from a given model themselves are computationally expensive. We describe a software that can apply a model of the choice of the tester (from a set of models) for estimating the reliability of a given software, and also provide data for evaluating the predictions of the model.
{"title":"A software to aid reliability estimation","authors":"Y.R. Muralidhara, P. Jalote","doi":"10.1109/STRQA.1994.526384","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526384","url":null,"abstract":"Estimating the reliability of software is becoming increasingly important. There are a large number of models available for estimating reliability. Most of these models are computationally complex and require statistical inferencing to estimate the parameters. In addition, techniques for evaluating the results obtained from a given model themselves are computationally expensive. We describe a software that can apply a model of the choice of the tester (from a set of models) for estimating the reliability of a given software, and also provide data for evaluating the predictions of the model.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"94 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132784767","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526397
A. Bhattacharjee, A. Seby, G. Sen, S. Dhodapkar
CLAS (C Language Program Analysis System) is a reverse engineering tool intended for use in the verification and validation (V&V) of software programs developed in the ANSI 'C' language. By analysing the source code, CLAS generates data according to two conceptual models of software programs viz, the entity-relationship (ER) model and control flow graph (CFG) model. The tools within CLAS, make use of this data, to provide different graphical views of the programs. We discuss the features provided by CLAS and show how these can aid in automating some aspects of V&V and quality assessment activities.
{"title":"CLAS: a reverse engineering tool","authors":"A. Bhattacharjee, A. Seby, G. Sen, S. Dhodapkar","doi":"10.1109/STRQA.1994.526397","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526397","url":null,"abstract":"CLAS (C Language Program Analysis System) is a reverse engineering tool intended for use in the verification and validation (V&V) of software programs developed in the ANSI 'C' language. By analysing the source code, CLAS generates data according to two conceptual models of software programs viz, the entity-relationship (ER) model and control flow graph (CFG) model. The tools within CLAS, make use of this data, to provide different graphical views of the programs. We discuss the features provided by CLAS and show how these can aid in automating some aspects of V&V and quality assessment activities.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127058179","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526394
S. Murugesan
Increasing emphasis placed on high quality and customer (user) satisfaction of software calls for rethinking on the objectives and management of testing. Test and evaluation methods and tools, in themselves, do not guarantee effective testing and ensure high quality of software. The key to improving the effectiveness of testing is to improve the attitude of software developers towards testing and the nature and culture of the organisation. Also, testing has to be seen in a broader perspective of maximising 'customer satisfaction' and providing feedback for process refinement, rather than just detecting and correcting errors in the software. The paper addresses software testing from these perspectives. It highlights human factor and management issues in current software testing practices and offers suggestions for improvement.
{"title":"Attitude towards testing: a key contributor to software quality","authors":"S. Murugesan","doi":"10.1109/STRQA.1994.526394","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526394","url":null,"abstract":"Increasing emphasis placed on high quality and customer (user) satisfaction of software calls for rethinking on the objectives and management of testing. Test and evaluation methods and tools, in themselves, do not guarantee effective testing and ensure high quality of software. The key to improving the effectiveness of testing is to improve the attitude of software developers towards testing and the nature and culture of the organisation. Also, testing has to be seen in a broader perspective of maximising 'customer satisfaction' and providing feedback for process refinement, rather than just detecting and correcting errors in the software. The paper addresses software testing from these perspectives. It highlights human factor and management issues in current software testing practices and offers suggestions for improvement.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114956259","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526387
S. Ramakrishnan
The paper presents the quality factors that were addressed in designing an object-oriented framework for a class of resource allocation problems. The paper discusses the interplay between domain analysis and object-oriented software engineering in the context of defining external and internal qualities for that software system and describes the process of system development.
{"title":"Quality factors for resource allocation problems-linking domain analysis and object-oriented software engineering","authors":"S. Ramakrishnan","doi":"10.1109/STRQA.1994.526387","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526387","url":null,"abstract":"The paper presents the quality factors that were addressed in designing an object-oriented framework for a class of resource allocation problems. The paper discusses the interplay between domain analysis and object-oriented software engineering in the context of defining external and internal qualities for that software system and describes the process of system development.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115663047","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526392
T. Moores, R. Champion
The paper argues that quality assurance must begin with quality software requirements specification (SRS) and that by preserving the link between a customer's requirements definition and the SRS, the quality of a software system can be assured beyond first release. Without such a link, it would be difficult to properly analyse the effect of related or inconsistent requirements because the reason for their existence in the final SRS document has been lost, an example of forward and backward tracing requirements through the business and system models developed during analysis and design is given. Areas of further research are then identified.
{"title":"Software quality through the traceability of requirements specifications","authors":"T. Moores, R. Champion","doi":"10.1109/STRQA.1994.526392","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526392","url":null,"abstract":"The paper argues that quality assurance must begin with quality software requirements specification (SRS) and that by preserving the link between a customer's requirements definition and the SRS, the quality of a software system can be assured beyond first release. Without such a link, it would be difficult to properly analyse the effect of related or inconsistent requirements because the reason for their existence in the final SRS document has been lost, an example of forward and backward tracing requirements through the business and system models developed during analysis and design is given. Areas of further research are then identified.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124803302","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526386
R. N. Rattihalli, B. Zachariah
The paper presents a software reliability model based on group rectification of faults. In doing so we compare the advantages and disadvantages of obtaining the optimal group size.
提出了一种基于故障分组纠错的软件可靠性模型。在此过程中,我们比较了获得最佳群体规模的优点和缺点。
{"title":"A software reliability model based on group rectification policy","authors":"R. N. Rattihalli, B. Zachariah","doi":"10.1109/STRQA.1994.526386","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526386","url":null,"abstract":"The paper presents a software reliability model based on group rectification of faults. In doing so we compare the advantages and disadvantages of obtaining the optimal group size.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131322323","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526391
G. Sen, J. Brummer
The paper describes a specialized graphical language for formally specifying real time safety systems. The language architecture is designed as a transparent high-level language with a dual approach representation: to describe the functionality and for realising the timing and synchronization aspects of real time systems; a relationship is then defined between the two representations for complete system specification in a composite way. A special form of time Petri net is used to represent the time behavior. This also provides a good foundation for system analysis, especially analysis for temporal requirements of real time systems.
{"title":"An approach to graphical specification of real-time safety systems","authors":"G. Sen, J. Brummer","doi":"10.1109/STRQA.1994.526391","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526391","url":null,"abstract":"The paper describes a specialized graphical language for formally specifying real time safety systems. The language architecture is designed as a transparent high-level language with a dual approach representation: to describe the functionality and for realising the timing and synchronization aspects of real time systems; a relationship is then defined between the two representations for complete system specification in a composite way. A special form of time Petri net is used to represent the time behavior. This also provides a good foundation for system analysis, especially analysis for temporal requirements of real time systems.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133498468","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526393
S. Gupta, M. K. Sinha
The testability of software has been defined as provisions that can be made in the software during the design and coding phases, so that test-plans can be executed easily and systematically. Software testability measures are defined in terms of controllability and observability measures. Observability measures are incorporated in the software to facilitate observation of internal states. Controllability measures are incorporated to allow the software to attain states required for execution of various tests, which are normally difficult to achieve through user interface commands. Specificity of testability measures to be incorporated in software depends upon the test-plan. Hence, the test-plan, for each pre-testing phase of software development, is an essential input for the next phase to make the software testable. The design verification test-plan also has to be checked for testability, and, if required, the design has to be revised to incorporate necessary testability measures. A similar process has to be repeated with a detail design verification test-plan as well as a code verification test-plan. The impact of software testability considerations has resulted in the 'Testable-Software Development Model'.
{"title":"Impact of software testability considerations on software development life cycle","authors":"S. Gupta, M. K. Sinha","doi":"10.1109/STRQA.1994.526393","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526393","url":null,"abstract":"The testability of software has been defined as provisions that can be made in the software during the design and coding phases, so that test-plans can be executed easily and systematically. Software testability measures are defined in terms of controllability and observability measures. Observability measures are incorporated in the software to facilitate observation of internal states. Controllability measures are incorporated to allow the software to attain states required for execution of various tests, which are normally difficult to achieve through user interface commands. Specificity of testability measures to be incorporated in software depends upon the test-plan. Hence, the test-plan, for each pre-testing phase of software development, is an essential input for the next phase to make the software testable. The design verification test-plan also has to be checked for testability, and, if required, the design has to be revised to incorporate necessary testability measures. A similar process has to be repeated with a detail design verification test-plan as well as a code verification test-plan. The impact of software testability considerations has resulted in the 'Testable-Software Development Model'.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129786921","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 : 1994-12-21DOI: 10.1109/STRQA.1994.526385
Kapsu Kim, Chisu Wu
We propose a software reliability model for estimating, measuring, and controlling software reliability of embedded systems, and a software test stopping equation for determining software testing time. It is not easy to correct errors occurring in embedded systems on site.
{"title":"A software reliability model in the embedded system","authors":"Kapsu Kim, Chisu Wu","doi":"10.1109/STRQA.1994.526385","DOIUrl":"https://doi.org/10.1109/STRQA.1994.526385","url":null,"abstract":"We propose a software reliability model for estimating, measuring, and controlling software reliability of embedded systems, and a software test stopping equation for determining software testing time. It is not easy to correct errors occurring in embedded systems on site.","PeriodicalId":125322,"journal":{"name":"Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94)","volume":"89 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-12-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123832010","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}