Pub Date : 2002-10-06DOI: 10.1109/STEP.2002.1267609
H. Muller, S. Tilley, L. O'Brien, K. Wong
As the software engineering profession matures, questions related to adoption of best practices by the community at large become increasingly important. The aim of the Adoption-Centric Software Engineering (ACSE) series of workshops is to bring together researchers and practitioners who are concerned with all aspects of software engineering adoption issues. This includes topics such as software process selection criteria and implementation guidelines, construction of software development and maintenance tools, and transitioning current state-of-the-art techniques to widespread practical use.
{"title":"2nd International Workshop on Adoption-Centric Software Engineering Theme: from prototype to product","authors":"H. Muller, S. Tilley, L. O'Brien, K. Wong","doi":"10.1109/STEP.2002.1267609","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267609","url":null,"abstract":"As the software engineering profession matures, questions related to adoption of best practices by the community at large become increasingly important. The aim of the Adoption-Centric Software Engineering (ACSE) series of workshops is to bring together researchers and practitioners who are concerned with all aspects of software engineering adoption issues. This includes topics such as software process selection criteria and implementation guidelines, construction of software development and maintenance tools, and transitioning current state-of-the-art techniques to widespread practical use.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126432116","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-10-06DOI: 10.1109/STEP.2002.1267625
W. Suryn, P. Bourque, Alain Abran, Claude Y. Laporte
This paper presents a combined, high-level quality view of TL9000 handbook and ISO/IEC 9126 in the process of defining, measuring, evaluating and finally achieving appropriate quality of user-centered software products. In its practices-related part this paper discusses the benefits, which the use of TL9000 product operational (in-the-field) quality measures can bring to setting up, measuring and evaluating the quality of the software product being developed, through its entire life cycle.
{"title":"Software product quality practices - quality measurement and evaluation using TL9000 and ISO/IEC 9126","authors":"W. Suryn, P. Bourque, Alain Abran, Claude Y. Laporte","doi":"10.1109/STEP.2002.1267625","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267625","url":null,"abstract":"This paper presents a combined, high-level quality view of TL9000 handbook and ISO/IEC 9126 in the process of defining, measuring, evaluating and finally achieving appropriate quality of user-centered software products. In its practices-related part this paper discusses the benefits, which the use of TL9000 product operational (in-the-field) quality measures can bring to setting up, measuring and evaluating the quality of the software product being developed, through its entire life cycle.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121492803","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-10-06DOI: 10.1109/STEP.2002.1267622
J. Jacobs, J. Trienekens
Verification and validation (V&V) is only marginally addressed in software process improvement models like CMM and CMMI. A roadmap for the establishment of a sound verification and validation process in software development organizations is badly needed. This paper presents a basis for a roadmap; it describes a framework for improvement of the V&V process, based on the Testing Maturity Model (TMM), but with considerable enhancements. The model, tentatively named MB-V/sup 2/M/sup 2/ (Metrics Based Verification and Validation Maturity Model), has been initiated by a consortium of industrial companies, consultancy & service agencies and an academic institute, operating and residing in the Netherlands. MB-V/sup 2/M/sup 2/ is designed to be universally applicable, to unite the strengths of known (verification and validation) improvement models and to reflect proven work practices. It recommends a metrics base to select process improvements and to track and control implementation of improvement actions. This paper outlines the model and addresses the current status.
{"title":"Towards a metrics based verification and validation maturity model","authors":"J. Jacobs, J. Trienekens","doi":"10.1109/STEP.2002.1267622","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267622","url":null,"abstract":"Verification and validation (V&V) is only marginally addressed in software process improvement models like CMM and CMMI. A roadmap for the establishment of a sound verification and validation process in software development organizations is badly needed. This paper presents a basis for a roadmap; it describes a framework for improvement of the V&V process, based on the Testing Maturity Model (TMM), but with considerable enhancements. The model, tentatively named MB-V/sup 2/M/sup 2/ (Metrics Based Verification and Validation Maturity Model), has been initiated by a consortium of industrial companies, consultancy & service agencies and an academic institute, operating and residing in the Netherlands. MB-V/sup 2/M/sup 2/ is designed to be universally applicable, to unite the strengths of known (verification and validation) improvement models and to reflect proven work practices. It recommends a metrics base to select process improvements and to track and control implementation of improvement actions. This paper outlines the model and addresses the current status.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122216396","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-10-06DOI: 10.1109/STEP.2002.1267619
K. Kontogiannis, D. Smith, L. O'Brien
Recent advances in Web and middleware technologies offer a promising solution for a number of enterprise integration problems. The convergence of the Internet and distributed-object technologies, which has been referred to as the Internet's third wave, extends this "information-based" Internet to a worldwide "services-based" Web. In this paper we present a model for Enterprise Application Integration (EAI) and we discuss the role of emerging technologies, as they relate to the specification of services, registration of services, data integration, and control integration.
{"title":"On the role of services in enterprise application integration","authors":"K. Kontogiannis, D. Smith, L. O'Brien","doi":"10.1109/STEP.2002.1267619","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267619","url":null,"abstract":"Recent advances in Web and middleware technologies offer a promising solution for a number of enterprise integration problems. The convergence of the Internet and distributed-object technologies, which has been referred to as the Internet's third wave, extends this \"information-based\" Internet to a worldwide \"services-based\" Web. In this paper we present a model for Enterprise Application Integration (EAI) and we discuss the role of emerging technologies, as they relate to the specification of services, registration of services, data integration, and control integration.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114314407","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-10-06DOI: 10.1109/STEP.2002.1267627
R. Bunting, G. Lewis, F. Long, R. Seacord, L. Wrage
In any component-based software engineering effort, the issues of locating, evaluating and determining compatibility between components are highly important. Also, the knowledge gained during integration is not easily managed or shared. The goal of the STEP2002 Workshop on COTS integration and evaluation was to continue the effort to define a reference architecture for a system to codify component integration knowledge. The system can then evaluate ensembles of components against a manifest of desired components and interactions, and rank these ensembles based upon ease of integration.
{"title":"Workshop on COTS integration and evaluation","authors":"R. Bunting, G. Lewis, F. Long, R. Seacord, L. Wrage","doi":"10.1109/STEP.2002.1267627","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267627","url":null,"abstract":"In any component-based software engineering effort, the issues of locating, evaluating and determining compatibility between components are highly important. Also, the knowledge gained during integration is not easily managed or shared. The goal of the STEP2002 Workshop on COTS integration and evaluation was to continue the effort to define a reference architecture for a system to codify component integration knowledge. The system can then evaluate ensembles of components against a manifest of desired components and interactions, and rank these ensembles based upon ease of integration.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"75 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115855563","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-10-06DOI: 10.1109/STEP.2002.1267624
J. Moll, J. Jacobs, B. Freimut, J. Trienekens, F. Coallier, P. Hoffnagle, P. Layzell, Liam O'Brien, D. Poo
In many low mature organizations dynamic testing is often the only defect detection method applied. Thus, defects are detected rather late in the development process. High rework and testing effort, typically under time pressure, lead to unpredictable delivery dates and uncertain product quality. This paper presents several methods for early defect detection and prevention that have been in existence for quite some time, although not all of them are common practice. However, to use these methods operationally and scale them to a particular project or environment, they have to be positioned appropriately in the life cycle, especially in complex projects. Modeling the development life cycle, that is the construction of a project-specific life cycle, is an indispensable first step to recognize possible defect injection points throughout the development project and to optimize the application of the available methods for defect detection and prevention. This paper discusses the importance of life cycle modeling for defect detection and prevention and presents a set of concrete, proven methods that can be used to optimize defect detection and prevention. In particular, software inspections, static code analysis, defect measurement and defect causal analysis are discussed. These methods allow early, low cost detection of defects, preventing them from propagating to later development stages and preventing the occurrence of similar defects in future projects.
{"title":"The importance of life cycle modeling to defect detection and prevention","authors":"J. Moll, J. Jacobs, B. Freimut, J. Trienekens, F. Coallier, P. Hoffnagle, P. Layzell, Liam O'Brien, D. Poo","doi":"10.1109/STEP.2002.1267624","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267624","url":null,"abstract":"In many low mature organizations dynamic testing is often the only defect detection method applied. Thus, defects are detected rather late in the development process. High rework and testing effort, typically under time pressure, lead to unpredictable delivery dates and uncertain product quality. This paper presents several methods for early defect detection and prevention that have been in existence for quite some time, although not all of them are common practice. However, to use these methods operationally and scale them to a particular project or environment, they have to be positioned appropriately in the life cycle, especially in complex projects. Modeling the development life cycle, that is the construction of a project-specific life cycle, is an indispensable first step to recognize possible defect injection points throughout the development project and to optimize the application of the available methods for defect detection and prevention. This paper discusses the importance of life cycle modeling for defect detection and prevention and presents a set of concrete, proven methods that can be used to optimize defect detection and prevention. In particular, software inspections, static code analysis, defect measurement and defect causal analysis are discussed. These methods allow early, low cost detection of defects, preventing them from propagating to later development stages and preventing the occurrence of similar defects in future projects.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131242979","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-10-06DOI: 10.1109/STEP.2002.1267594
P. Bourque, T. Lethbridge
This workshop focused on the differences and similarities between two bodies of knowledge: the Guide to the Software Engineering Body of Knowledge (SWEBOK) (www.swebok.org) and the Software Engineering Education Body of Knowledge (SEEK) (http://sites.computer.org/ccse/). . It also considered what we can learn from those differences, and what changes the differences suggest for either body of knowledge.
{"title":"Improvements to the Guide to the Software Engineering Body of Knowledge (SWEBOK) and to the Software Engineering Education Body of Knowledge (SEEK)","authors":"P. Bourque, T. Lethbridge","doi":"10.1109/STEP.2002.1267594","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267594","url":null,"abstract":"This workshop focused on the differences and similarities between two bodies of knowledge: the Guide to the Software Engineering Body of Knowledge (SWEBOK) (www.swebok.org) and the Software Engineering Education Body of Knowledge (SEEK) (http://sites.computer.org/ccse/). . It also considered what we can learn from those differences, and what changes the differences suggest for either body of knowledge.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124210535","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-10-06DOI: 10.1109/STEP.2002.1267623
Paul Krause, B. Freimut, W. Suryn
Assessing and controlling software quality is still an immature discipline. One of the reasons for this is that many of the concepts and terms that are used in discussing and describing quality are overloaded with a history from manufacturing quality. We argue in this paper that a quite distinct approach is needed to software quality control as compared with manufacturing quality control. In particular, the emphasis in software quality control is in design to fulfill business needs, rather than replication to agreed standards. We will describe how quality goals can be derived from business needs. Following that, we will introduce an approach to quality control that uses rich causal models, which can take into account human as well as technological influences. A significant concern of developing such models is the limited sample sizes that are available for eliciting model parameters. In the final section of the paper we will show how expert judgment can be reliably used to elicit parameters in the absence of statistical data. In total this provides an agenda for developing a framework for quality control in software engineering that is freed from the shackles of an inappropriate legacy.
{"title":"New directions in measurement for software quality control","authors":"Paul Krause, B. Freimut, W. Suryn","doi":"10.1109/STEP.2002.1267623","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267623","url":null,"abstract":"Assessing and controlling software quality is still an immature discipline. One of the reasons for this is that many of the concepts and terms that are used in discussing and describing quality are overloaded with a history from manufacturing quality. We argue in this paper that a quite distinct approach is needed to software quality control as compared with manufacturing quality control. In particular, the emphasis in software quality control is in design to fulfill business needs, rather than replication to agreed standards. We will describe how quality goals can be derived from business needs. Following that, we will introduce an approach to quality control that uses rich causal models, which can take into account human as well as technological influences. A significant concern of developing such models is the limited sample sizes that are available for eliciting model parameters. In the final section of the paper we will show how expert judgment can be reliably used to elicit parameters in the absence of statistical data. In total this provides an agenda for developing a framework for quality control in software engineering that is freed from the shackles of an inappropriate legacy.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"56 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127051049","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-10-06DOI: 10.1109/STEP.2002.1267614
L. O'Brien, F. Hansen, R. Seacord, D. Smith
Mining and managing software assets are important for strategic reuse of assets in new systems. This report outlines the SEI's Options Analysis for Reengineering (OAR) method, which is an approach for mining components and discusses component repositories and in particular the SEI's Knowledge-Based Automated Component Ensemble Evaluation (K-BACEE). OAR is a systematic, architecture-centric method for mining existing components for a product line or new software architecture. The method incorporates a set of scalable techniques and activities to collaboratively analyze existing components, determine viable mining options, and evaluate the most promising options. Once mined, software assets need to be managed to be useful. Compatibility with other legacy assets, commercial-off-the-shelf software products, and other software components needs to be understood and codified in such a way that it can be easily shared with other development projects within the organization. Towards this end, the SEI has developed K-BACEE which is a component repository that uses codified integration knowledge to assist system integrators in selecting ensembles of highly compatible components.
{"title":"Mining and managing software assets","authors":"L. O'Brien, F. Hansen, R. Seacord, D. Smith","doi":"10.1109/STEP.2002.1267614","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267614","url":null,"abstract":"Mining and managing software assets are important for strategic reuse of assets in new systems. This report outlines the SEI's Options Analysis for Reengineering (OAR) method, which is an approach for mining components and discusses component repositories and in particular the SEI's Knowledge-Based Automated Component Ensemble Evaluation (K-BACEE). OAR is a systematic, architecture-centric method for mining existing components for a product line or new software architecture. The method incorporates a set of scalable techniques and activities to collaboratively analyze existing components, determine viable mining options, and evaluate the most promising options. Once mined, software assets need to be managed to be useful. Compatibility with other legacy assets, commercial-off-the-shelf software products, and other software components needs to be understood and codified in such a way that it can be easily shared with other development projects within the organization. Towards this end, the SEI has developed K-BACEE which is a component repository that uses codified integration knowledge to assist system integrators in selecting ensembles of highly compatible components.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129558560","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-10-06DOI: 10.1109/STEP.2002.1267629
D. Budgen, S. Tilley
An important influence in the evolution of any form of craft into an engineering discipline is the use that is made of evidence, and the adoption of systematic practices for its collection, analysis and propagation. The availability of evidence makes it possible to use analysis as the basis for making the key transition from knowing how to achieve an effect to understanding why the effect occurs, and any limitations associated with it.
{"title":"STEP 2002 - a roadmap for empirical software engineering","authors":"D. Budgen, S. Tilley","doi":"10.1109/STEP.2002.1267629","DOIUrl":"https://doi.org/10.1109/STEP.2002.1267629","url":null,"abstract":"An important influence in the evolution of any form of craft into an engineering discipline is the use that is made of evidence, and the adoption of systematic practices for its collection, analysis and propagation. The availability of evidence makes it possible to use analysis as the basis for making the key transition from knowing how to achieve an effect to understanding why the effect occurs, and any limitations associated with it.","PeriodicalId":271935,"journal":{"name":"10th International Workshop on Software Technology and Engineering Practice","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2002-10-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133806640","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
扫码关注我们
求助内容：
应助结果提醒方式：