The author describes a component bused checkpointing code generation tool. Scientific applications that require long computation runtimes experience the risk of hardware or software failures. Failure during a long computation requires that the application restarts the calculations from the beginning. Checkpointing important data at set intervals and using that data during a restart of the application minimizes the recalculation of data during failures.
{"title":"Dynamic reconfiguration: checkpointing code generation","authors":"A. Chowdhury","doi":"10.1109/AST.1997.599911","DOIUrl":"https://doi.org/10.1109/AST.1997.599911","url":null,"abstract":"The author describes a component bused checkpointing code generation tool. Scientific applications that require long computation runtimes experience the risk of hardware or software failures. Failure during a long computation requires that the application restarts the calculations from the beginning. Checkpointing important data at set intervals and using that data during a restart of the application minimizes the recalculation of data during failures.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"365 5","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114011036","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}
Modern software developers are guided by a variety of formal and informal processes that organize and control development activities across large groups of developers or multiple organizations and supply the discipline and order that was lacking in many early development efforts. The available inventory of documented process methods is limited: most process methods assume the system being built will be coded largely from scratch. The processes do not address many of the challenges associated with building systems that contain large amounts of commercial off-the-shelf (COTS) software. The infrastructure incremental development approach (IIDA) is a combination of the classical development model and the spiral process model to accommodate the needs of COTS-based technical infrastructure development.
{"title":"A software development process for COTS-based information system infrastructure","authors":"Gregory Fox, K. W. Lantner, S. Marcom","doi":"10.1109/AST.1997.599923","DOIUrl":"https://doi.org/10.1109/AST.1997.599923","url":null,"abstract":"Modern software developers are guided by a variety of formal and informal processes that organize and control development activities across large groups of developers or multiple organizations and supply the discipline and order that was lacking in many early development efforts. The available inventory of documented process methods is limited: most process methods assume the system being built will be coded largely from scratch. The processes do not address many of the challenges associated with building systems that contain large amounts of commercial off-the-shelf (COTS) software. The infrastructure incremental development approach (IIDA) is a combination of the classical development model and the spiral process model to accommodate the needs of COTS-based technical infrastructure development.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"262 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115826860","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}
CHAIMS supports an innovative paradigm in software engineering: composition. The CHAIMS programming language focuses solely on integrating so-called megamodules into new applications. In doing this, CHAIMS exploits existing or emerging standards for interoperation like CORBA, ActiveX, JavaBeans or DCE. The approach reduces software development and maintenance costs by actively supporting autonomy and reuse of megamodules.
{"title":"A compiler for composition: CHAIMS","authors":"L. Perrochon, G. Wiederhold, R. Burback","doi":"10.1109/AST.1997.599910","DOIUrl":"https://doi.org/10.1109/AST.1997.599910","url":null,"abstract":"CHAIMS supports an innovative paradigm in software engineering: composition. The CHAIMS programming language focuses solely on integrating so-called megamodules into new applications. In doing this, CHAIMS exploits existing or emerging standards for interoperation like CORBA, ActiveX, JavaBeans or DCE. The approach reduces software development and maintenance costs by actively supporting autonomy and reuse of megamodules.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115729705","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}
Component-based software engineering (CBSE) offers a new approach to the development of large software-intensive systems. To fully exploit CBSE technology, organisations will need to consider how this technology is best transferred, institutionalised and evolved within the organisation. The author outlines five CBSE technology risk areas and discusses the manner in which metrics could be used to help control the risks and to count the cost of the transfer.
{"title":"CBSE: can we count the cost?","authors":"A. Vickers","doi":"10.1109/AST.1997.599917","DOIUrl":"https://doi.org/10.1109/AST.1997.599917","url":null,"abstract":"Component-based software engineering (CBSE) offers a new approach to the development of large software-intensive systems. To fully exploit CBSE technology, organisations will need to consider how this technology is best transferred, institutionalised and evolved within the organisation. The author outlines five CBSE technology risk areas and discusses the manner in which metrics could be used to help control the risks and to count the cost of the transfer.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129914910","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}
Integration of software components is a major issue in the development of software systems. Integration can be approached from different perspectives including infrastructures (middleware) and the characteristics of individual components which might support integration. The paper concentrates on integration mechanisms which a given component might enjoy. A major portion of the paper looks at application programming interfaces (APIs) which provide the most complete range of integration possibilities. The various dimensions of APIs are analyzed in this portion. Also discussed are internal programming languages, filters, modification of internal component files and shared repositories. Component enhancement techniques are mentioned in places because they are so intertwined with integration. It is necessary to understand a wide range of component integration properties in detail in order to make intelligent evaluation of components.
{"title":"Mechanisms for integration and enhancement of software components","authors":"J. Rader","doi":"10.1109/AST.1997.599908","DOIUrl":"https://doi.org/10.1109/AST.1997.599908","url":null,"abstract":"Integration of software components is a major issue in the development of software systems. Integration can be approached from different perspectives including infrastructures (middleware) and the characteristics of individual components which might support integration. The paper concentrates on integration mechanisms which a given component might enjoy. A major portion of the paper looks at application programming interfaces (APIs) which provide the most complete range of integration possibilities. The various dimensions of APIs are analyzed in this portion. Also discussed are internal programming languages, filters, modification of internal component files and shared repositories. Component enhancement techniques are mentioned in places because they are so intertwined with integration. It is necessary to understand a wide range of component integration properties in detail in order to make intelligent evaluation of components.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129734780","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}
Describes the management of software development component characteristics, such as quality and/or complexity. We define a key problem in software development change: the software development complexity and the methods to reduce this. In component-based software engineering, "component-based" metrics are also necessary in our new object-oriented measurement framework. Tools for the support of the software measurement process are classified as computer-assisted measurement and evaluation (CAME) tools. Some aspects of Java software development measurement and evaluation are discussed.
{"title":"Managing the component-based software engineering with metrics","authors":"R. Dumke, A. S. Winkler","doi":"10.1109/AST.1997.599920","DOIUrl":"https://doi.org/10.1109/AST.1997.599920","url":null,"abstract":"Describes the management of software development component characteristics, such as quality and/or complexity. We define a key problem in software development change: the software development complexity and the methods to reduce this. In component-based software engineering, \"component-based\" metrics are also necessary in our new object-oriented measurement framework. Tools for the support of the software measurement process are classified as computer-assisted measurement and evaluation (CAME) tools. Some aspects of Java software development measurement and evaluation are discussed.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127748000","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 move to component-based development (CBD) is driven by a number of important requirements with respect to the agile assembly of application systems from pre-developed parts. However, to make CBD a reality requires a deeper understanding of the fundamental concepts of CBD and how those concepts can be embodied in tools and techniques. The most basic questions are in respect to what constitutes a component, how appropriate components can be found, and how to assemble components when building an application system. This paper addresses these questions and makes the case for more rigorous descriptions of component behaviors through the use of domain and specification models which allow interfaces and implementations of components to be more easily understood, analyzed and combined.
{"title":"On components and objects: the foundations of component-based development","authors":"A. Brown, K. Short","doi":"10.1109/AST.1997.599921","DOIUrl":"https://doi.org/10.1109/AST.1997.599921","url":null,"abstract":"The move to component-based development (CBD) is driven by a number of important requirements with respect to the agile assembly of application systems from pre-developed parts. However, to make CBD a reality requires a deeper understanding of the fundamental concepts of CBD and how those concepts can be embodied in tools and techniques. The most basic questions are in respect to what constitutes a component, how appropriate components can be found, and how to assemble components when building an application system. This paper addresses these questions and makes the case for more rigorous descriptions of component behaviors through the use of domain and specification models which allow interfaces and implementations of components to be more easily understood, analyzed and combined.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125288560","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}
This article overviews the Next-Generation Software Engineering program of the Software CALS (Continuous Acquisition and Lifecycle Support) project (SCALS) in Japan and discusses the component-based software process model and its economic model, based on the early study of the project. With this model, it is estimated that component-based software development could reduce the cost by between 50 and 70%.
{"title":"Process and economic model of component-based software development: a study from Software CALS Next Generation Software Engineering program","authors":"M. Aoyama","doi":"10.1109/AST.1997.599919","DOIUrl":"https://doi.org/10.1109/AST.1997.599919","url":null,"abstract":"This article overviews the Next-Generation Software Engineering program of the Software CALS (Continuous Acquisition and Lifecycle Support) project (SCALS) in Japan and discusses the component-based software process model and its economic model, based on the early study of the project. With this model, it is estimated that component-based software development could reduce the cost by between 50 and 70%.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"135 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115189759","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}
Component-based software engineering (CBSE) offers a new approach to the development of large software-intensive systems. To fully exploit CBSE technology, organisations will need to consider how this technology is best transferred, institutionalised and evolved within the organisation. This paper discusses the risks associated with the adoption of CBSE technology. A model of the risk analysis and management (RAM) process for CBSE technology is proposed as a means of controlling risks. Five CBSE technology risk areas are identified-domain inadequacies, shortfalls in reuse components, shortfalls in the architecture, deficiencies in the CBSE infrastructure and educational issues-and examined. A number of risk management techniques are proposed. Different kinds of risk knowledge are highlighted, and the role of the risk repository explained. The paper closes with a set of RAM guidelines for the risk manager.
{"title":"Managing the risks of component-based software engineering","authors":"W. Lam, A. Vickers","doi":"10.1109/AST.1997.599922","DOIUrl":"https://doi.org/10.1109/AST.1997.599922","url":null,"abstract":"Component-based software engineering (CBSE) offers a new approach to the development of large software-intensive systems. To fully exploit CBSE technology, organisations will need to consider how this technology is best transferred, institutionalised and evolved within the organisation. This paper discusses the risks associated with the adoption of CBSE technology. A model of the risk analysis and management (RAM) process for CBSE technology is proposed as a means of controlling risks. Five CBSE technology risk areas are identified-domain inadequacies, shortfalls in reuse components, shortfalls in the architecture, deficiencies in the CBSE infrastructure and educational issues-and examined. A number of risk management techniques are proposed. Different kinds of risk knowledge are highlighted, and the role of the risk repository explained. The paper closes with a set of RAM guidelines for the risk manager.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132397387","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}
Summary form only given, substantially as follows. Articulates the risks and metrics associated with CBSE (component-based software engineering) technology. The goal is to share useful hints and recommendations with a view to standardizing relevant metrics and mitigating attendant risks. An important step in reaching such a goal will be to achieve community consensus on the basic features of what we believe to be the CBSE process; only with such a tool can we intelligently collect and make sense of the risks and metrics that are observed or that come to mind. This paper describes such a model for CBSE and points out examples of how it can assist in the effort to usefully articulate CBSE risks and metrics.
{"title":"A framework for understanding CBSE risks and metrics","authors":"P. Oberndorf","doi":"10.1109/AST.1997.599916","DOIUrl":"https://doi.org/10.1109/AST.1997.599916","url":null,"abstract":"Summary form only given, substantially as follows. Articulates the risks and metrics associated with CBSE (component-based software engineering) technology. The goal is to share useful hints and recommendations with a view to standardizing relevant metrics and mitigating attendant risks. An important step in reaching such a goal will be to achieve community consensus on the basic features of what we believe to be the CBSE process; only with such a tool can we intelligently collect and make sense of the risks and metrics that are observed or that come to mind. This paper describes such a model for CBSE and points out examples of how it can assist in the effort to usefully articulate CBSE risks and metrics.","PeriodicalId":345632,"journal":{"name":"Proceedings Fifth International Symposium on Assessment of Software Tools and Technologies","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-06-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121843044","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
扫码关注我们
求助内容：
应助结果提醒方式：