Pub Date : 2002-12-05DOI: 10.1109/SEW.2002.1199451
O. Mondragon, Ann Q. Gates, Steve Roach
Formal specification and analysis of software properties can be useful in reducing the number of errors in production software. More intuitive methods of specifying constraints and system properties are needed so that developers and other stakeholders can participate in validation of formal software requirements. This work introduces composite propositions, a set of abstractions that define the relations between sets of conditions or events, and it is directed at making the specification of common temporal properties accessible to practitioners and clients. Composite propositions can be used with response formulas to describe concurrent behavior such as concurrency, synchronization, and nondeterminism. Composite propositions assist in the elicitation and validation of properties facilitating the integration of formal approaches into the software development lifecycle.
{"title":"Composite propositions: toward support for formal specification of system properties","authors":"O. Mondragon, Ann Q. Gates, Steve Roach","doi":"10.1109/SEW.2002.1199451","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199451","url":null,"abstract":"Formal specification and analysis of software properties can be useful in reducing the number of errors in production software. More intuitive methods of specifying constraints and system properties are needed so that developers and other stakeholders can participate in validation of formal software requirements. This work introduces composite propositions, a set of abstractions that define the relations between sets of conditions or events, and it is directed at making the specification of common temporal properties accessible to practitioners and clients. Composite propositions can be used with response formulas to describe concurrent behavior such as concurrency, synchronization, and nondeterminism. Composite propositions assist in the elicitation and validation of properties facilitating the integration of formal approaches into the software development lifecycle.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115321214","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199444
N. Schneidewind
This is report #1 in a series of reports on the NASA IV&V Facility Project "investigation of the risk to software reliability and maintainability of requirements changes". This report covers the discriminate analysis experiment. In order to continue to make progress in software measurement, as it pertains to reliability and maintainability, we must shift the emphasis from design and code metrics to metrics that characterize the risk of making requirements changes. Although these software attributes can be difficult to deal with due to the fuzzy requirements from which they are derived, the advantage of having early indicators of future software problems outweighs this inconvenience. Our case example consists of twenty-four Space Shuttle change requests, nineteen risk factors, and the associated failures and software metrics. The approach can be generalized to other NASA domains with numerical results that would vary according to the application.
{"title":"Report on results of discriminant analysis experiment","authors":"N. Schneidewind","doi":"10.1109/SEW.2002.1199444","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199444","url":null,"abstract":"This is report #1 in a series of reports on the NASA IV&V Facility Project \"investigation of the risk to software reliability and maintainability of requirements changes\". This report covers the discriminate analysis experiment. In order to continue to make progress in software measurement, as it pertains to reliability and maintainability, we must shift the emphasis from design and code metrics to metrics that characterize the risk of making requirements changes. Although these software attributes can be difficult to deal with due to the fuzzy requirements from which they are derived, the advantage of having early indicators of future software problems outweighs this inconvenience. Our case example consists of twenty-four Space Shuttle change requests, nineteen risk factors, and the associated failures and software metrics. The approach can be generalized to other NASA domains with numerical results that would vary according to the application.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"180 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122758528","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199482
A. D. de Beer, C. Fidge
The dynamic behaviour of multitasking systems is complex and hard to understand. We explain how a simple multitasking simulator was constructed by implementing scheduling theory's computational model in a commercial simulation toolkit. The resulting simulator displays multitasking behaviours graphically.
{"title":"A simple multi-tasking simulator","authors":"A. D. de Beer, C. Fidge","doi":"10.1109/SEW.2002.1199482","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199482","url":null,"abstract":"The dynamic behaviour of multitasking systems is complex and hard to understand. We explain how a simple multitasking simulator was constructed by implementing scheduling theory's computational model in a commercial simulation toolkit. The resulting simulator displays multitasking behaviours graphically.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128580378","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199468
S. Bohner
As software components and middleware occupy more and more of the software engineering landscape, interoperability relationships point to increasingly relevant software change impacts. Packaged software now represents over thirty-two percent of the software in most organizations. While traceability and dependency analysis frameworks have effectively supported software impact analysis in the past, they do not adequately addressed this trend. As software systems grow in size and complexity, their dependency webs of information also extend beyond most software engineers ability to comprehend them. We examine research for extending current software change impact analysis to incorporate interoperability dependency relationships for addressing distributed applications and explores three dimensional (3D) visualization techniques for more effective navigation of software changes.
{"title":"Extending software change impact analysis into COTS components","authors":"S. Bohner","doi":"10.1109/SEW.2002.1199468","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199468","url":null,"abstract":"As software components and middleware occupy more and more of the software engineering landscape, interoperability relationships point to increasingly relevant software change impacts. Packaged software now represents over thirty-two percent of the software in most organizations. While traceability and dependency analysis frameworks have effectively supported software impact analysis in the past, they do not adequately addressed this trend. As software systems grow in size and complexity, their dependency webs of information also extend beyond most software engineers ability to comprehend them. We examine research for extending current software change impact analysis to incorporate interoperability dependency relationships for addressing distributed applications and explores three dimensional (3D) visualization techniques for more effective navigation of software changes.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116509213","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199460
W. Harrison
Most software organizations possess a large, but informal, corporate memory. This corporate memory is comprised of the experiences of every software engineer and manager, yet it is informal because there is seldom an institutionalized mechanism for disseminating the wisdom. In order to exploit this informal corporate memory, the key points of each experience can be placed into a repository for later dissemination. We describe a lessons learned repository (LLR) that facilitates such dissemination.
{"title":"A software engineering lessons learned repository","authors":"W. Harrison","doi":"10.1109/SEW.2002.1199460","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199460","url":null,"abstract":"Most software organizations possess a large, but informal, corporate memory. This corporate memory is comprised of the experiences of every software engineer and manager, yet it is informal because there is seldom an institutionalized mechanism for disseminating the wisdom. In order to exploit this informal corporate memory, the key points of each experience can be placed into a repository for later dissemination. We describe a lessons learned repository (LLR) that facilitates such dissemination.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"110 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132624130","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199450
N.S. Eickelmann, Francesca Ruffolo, J. Baik, A. Anant
We present findings from a six sigma black belt project. Every black belt project has a charter that defines the customer focus and the goals of the project. This project is designed to identify the key factors that impact effectiveness for software inspections and to compare Fagan inspections and modified Fagan inspections used at Motorola. Empirical data is collected and simulation models of the generic processes are created. The models that are created abstract away unnecessary details of the process and provide a test-bed to evaluate the methodologies relative to their effectiveness, cost in effort, time required (duration), and complexity of the activity.
{"title":"An empirical study of modifying the Fagan inspection process and the resulting main effects and interaction effects among defects found, effort required, rate of preparation and inspection, number of team members and product 1st pass quality","authors":"N.S. Eickelmann, Francesca Ruffolo, J. Baik, A. Anant","doi":"10.1109/SEW.2002.1199450","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199450","url":null,"abstract":"We present findings from a six sigma black belt project. Every black belt project has a charter that defines the customer focus and the goals of the project. This project is designed to identify the key factors that impact effectiveness for software inspections and to compare Fagan inspections and modified Fagan inspections used at Motorola. Empirical data is collected and simulation models of the generic processes are created. The models that are created abstract away unnecessary details of the process and provide a test-bed to evaluate the methodologies relative to their effectiveness, cost in effort, time required (duration), and complexity of the activity.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"83 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125908595","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199454
D. Kuhn, michael. reilly, michael. reilly
Approaches to software testing based on methods from the field of design of experiments have been advocated as a means of providing high coverage at relatively low cost. Tools to generate all pairs, or higher n-degree combinations, of input values have been developed and demonstrated in a few applications, but little empirical evidence is available to aid developers in evaluating the effectiveness of these tools for particular problems. We investigate error reports from two large open-source software projects, a browser and Web server, to provide preliminary answers to three questions: Is there a point of diminishing returns at which generating all n-degree combinations is nearly as effective as all n+1-degree combinations? What is the appropriate value of n for particular classes of software? Does this value differ for different types of software, and by how much? Our findings suggest that more than 95% of errors in the software studied would be detected by test cases that cover all 4-way combinations of values, and that the browser and server software were similar in the percentage of errors detectable by combinations of degree 2 through 6.
{"title":"An investigation of the applicability of design of experiments to software testing","authors":"D. Kuhn, michael. reilly, michael. reilly","doi":"10.1109/SEW.2002.1199454","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199454","url":null,"abstract":"Approaches to software testing based on methods from the field of design of experiments have been advocated as a means of providing high coverage at relatively low cost. Tools to generate all pairs, or higher n-degree combinations, of input values have been developed and demonstrated in a few applications, but little empirical evidence is available to aid developers in evaluating the effectiveness of these tools for particular problems. We investigate error reports from two large open-source software projects, a browser and Web server, to provide preliminary answers to three questions: Is there a point of diminishing returns at which generating all n-degree combinations is nearly as effective as all n+1-degree combinations? What is the appropriate value of n for particular classes of software? Does this value differ for different types of software, and by how much? Our findings suggest that more than 95% of errors in the software studied would be detected by test cases that cover all 4-way combinations of values, and that the browser and server software were similar in the percentage of errors detectable by combinations of degree 2 through 6.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"127 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129720853","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199448
Roy Sterritt
Autonomic computing is emerging as a significant new approach for the design of computing systems. Its goal is the production of systems that are self-managing, self-healing, self-protecting and self-optimizing. Achieving this goal involve techniques from both software engineering and artificial intelligence. We discuss one particular aspect of autonomic computing: event management. It considers the range of event handling techniques in use, particularly in relation to distributed systems. Intelligent approaches are illustrated using the example of event handling in telecommunication systems. In particular, the telecom survivable network architecture is analyzed to identify lessons and potential pitfalls for autonomic computing.
{"title":"Towards autonomic computing: effective event management","authors":"Roy Sterritt","doi":"10.1109/SEW.2002.1199448","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199448","url":null,"abstract":"Autonomic computing is emerging as a significant new approach for the design of computing systems. Its goal is the production of systems that are self-managing, self-healing, self-protecting and self-optimizing. Achieving this goal involve techniques from both software engineering and artificial intelligence. We discuss one particular aspect of autonomic computing: event management. It considers the range of event handling techniques in use, particularly in relation to distributed systems. Intelligent approaches are illustrated using the example of event handling in telecommunication systems. In particular, the telecom survivable network architecture is analyzed to identify lessons and potential pitfalls for autonomic computing.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116604935","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199478
A. Cerone
We present an environment for the verification of complex concurrent software and hardware systems. The tool is targeted at users who are not necessarily expert in formal methods. The underlying mathematical specification language and verification methodologies are hidden to the user by encapsulating them within a high-level environment that supports graphical design, intuitive specification of properties, high-level data representation, customised interfaces and predefined verification strategies. The semantic base of the tool is given by the Circal process algebra, which allows the internal representation of both the system model and its properties within the same language.
{"title":"Towards a user-friendly design and verification environment","authors":"A. Cerone","doi":"10.1109/SEW.2002.1199478","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199478","url":null,"abstract":"We present an environment for the verification of complex concurrent software and hardware systems. The tool is targeted at users who are not necessarily expert in formal methods. The underlying mathematical specification language and verification methodologies are hidden to the user by encapsulating them within a high-level environment that supports graphical design, intuitive specification of properties, high-level data representation, customised interfaces and predefined verification strategies. The semantic base of the tool is given by the Circal process algebra, which allows the internal representation of both the system model and its properties within the same language.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132919950","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 : 2002-12-05DOI: 10.1109/SEW.2002.1199472
J. McC Smith, D. Stotts
Design patterns are an important concept in the field of software engineering, providing a language and application independent method for expressing and conveying lessons learned by experienced designers. There is a large gap, however, between the aesthetic and elegance of the patterns as intended and the reality of working with an ultimately mathematically expressible system such as code. We describe a step towards meaningful formal analysis of code within the language of patterns, and discuss potential uses. The major contributions include: a compendium of elemental design patterns (EDPs), a layer of seemingly simplistic relationships between objects that, on closer inspection, provide a critical link between the world of formal analysis and the realm of pattern design and implementation without reducing the patterns to merely syntactic constructs; an extension to the /spl sigmav/-calculus, termed /spl rho/-calculus, a formal notation for expressing relationships between the elements of object oriented languages, and its use in expressing the EDPs directly. We discuss their use in composition and decomposition of existing patterns, identification of pattern use in existing code to aid comprehension, and future research directions, such as support for refactoring of designs, interaction with traditional code analysis systems, and the education of students of software architecture.
{"title":"Elemental design patterns: a formal semantics for composition of OO software architecture","authors":"J. McC Smith, D. Stotts","doi":"10.1109/SEW.2002.1199472","DOIUrl":"https://doi.org/10.1109/SEW.2002.1199472","url":null,"abstract":"Design patterns are an important concept in the field of software engineering, providing a language and application independent method for expressing and conveying lessons learned by experienced designers. There is a large gap, however, between the aesthetic and elegance of the patterns as intended and the reality of working with an ultimately mathematically expressible system such as code. We describe a step towards meaningful formal analysis of code within the language of patterns, and discuss potential uses. The major contributions include: a compendium of elemental design patterns (EDPs), a layer of seemingly simplistic relationships between objects that, on closer inspection, provide a critical link between the world of formal analysis and the realm of pattern design and implementation without reducing the patterns to merely syntactic constructs; an extension to the /spl sigmav/-calculus, termed /spl rho/-calculus, a formal notation for expressing relationships between the elements of object oriented languages, and its use in expressing the EDPs directly. We discuss their use in composition and decomposition of existing patterns, identification of pattern use in existing code to aid comprehension, and future research directions, such as support for refactoring of designs, interaction with traditional code analysis systems, and the education of students of software architecture.","PeriodicalId":146269,"journal":{"name":"27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings.","volume":"62 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-12-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126206837","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
扫码关注我们
求助内容：
应助结果提醒方式：