D. Thurman, Justin Almquist, I. Gorton, A. Wynne, J. Chatterton
Architectures and technologies for enterprise application integration are relatively mature, resulting in a range of standards-based and proprietary COTS middleware technologies. However, in the domain of complex analytical applications, integration architectures are not so well understood. Analytical applications such as those used in scientific discovery and financial and intelligence analysis exert unique demands on their underlying architectures. These demands make existing COTS integration middleware less suitable for use in enterprise analytics environments. In this paper we describe SIFT (Scalable Information Fusion and Triage), an application architecture designed for integrating the various components that comprise enterprise analytics applications. SIFT exploits a common pattern for composing analytical components, and extends an existing messaging platform with dynamic configuration mechanisms and scaling capabilities. We demonstrate the use of SIFT to create a decision support platform for quality control based on large volumes of incoming delivery data. The strengths and weaknesses of the SIFT solution are discussed, and we conclude by describing where further work is required to create a complete solution applicable to a wide range of analytical application domains
{"title":"SIFT - A Component-Based Integration Architecture for Enterprise Analytics","authors":"D. Thurman, Justin Almquist, I. Gorton, A. Wynne, J. Chatterton","doi":"10.1109/ICCBSS.2007.35","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.35","url":null,"abstract":"Architectures and technologies for enterprise application integration are relatively mature, resulting in a range of standards-based and proprietary COTS middleware technologies. However, in the domain of complex analytical applications, integration architectures are not so well understood. Analytical applications such as those used in scientific discovery and financial and intelligence analysis exert unique demands on their underlying architectures. These demands make existing COTS integration middleware less suitable for use in enterprise analytics environments. In this paper we describe SIFT (Scalable Information Fusion and Triage), an application architecture designed for integrating the various components that comprise enterprise analytics applications. SIFT exploits a common pattern for composing analytical components, and extends an existing messaging platform with dynamic configuration mechanisms and scaling capabilities. We demonstrate the use of SIFT to create a decision support platform for quality control based on large volumes of incoming delivery data. The strengths and weaknesses of the SIFT solution are discussed, and we conclude by describing where further work is required to create a complete solution applicable to a wide range of analytical application domains","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125356171","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. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages
只提供摘要形式。这张海报展示了一个经验，关于在适应业务专家语言的业务模型中收集业务需求，并以系统的方式将这些需求转换为面向服务的体系结构(SOA)。海报介绍了目前的情况，突出了三个互操作性问题:(1)组织没有使用标准、统一和广泛采用的业务流程定义语言。组织希望对从不同角度参与的过程有一个共同的理解;(2)信息系统的实现是为了满足特定的需求，而忽略了未来的集成需求，使用专有格式和自组织通信策略和协议;(3)信息系统显然不能支持业务流程。业务流程模型和它们的信息系统实现之间存在差距。这张海报中展示的方法是基于从模型驱动的角度对SOA范例的使用:模型驱动的面向服务的体系结构(MDSOA)框架。基于MDA规范，我们已经为三个抽象级别中的每一个定义了一个元模型:(1)选择POP*(过程、组织、产品)作为表示和交换业务过程的元模型。POP*是统一企业建模语言(UEML)的继承者。POP*元模型表示起点;(2) PIM4SOA(面向服务架构的平台独立模型)(Benguria et al.， 2006)是表示服务、流程、信息和服务元素质量的元模型;(3) WSDL (Web服务描述语言)和BPEL(业务流程执行语言)是平台特定的语言
{"title":"MDSOA for Achieving Interoperability","authors":"X. Larrucea, Gorka Benguria, Stefan Schuster","doi":"10.1109/ICCBSS.2007.21","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.21","url":null,"abstract":"Summary form only given. This poster presents an experience, on gathering business needs in business models adapted to the business expert language and translating these needs into a service oriented architecture (SOA) in a systematic way. The poster introduces the current situation highlighting three interoperability problems: (1) Organisations do not use a standard, unified and widely adopted business process definition language. Organisations want a common understanding of the process where they are involved from different perspectives; (2) Information systems are implemented to address specific requirements, ignoring future integration needs by using proprietary formats, and ad-hoc communication strategies and protocols; and (3) Information systems do not, clearly, support the business processes. There is a gap between business process models and their information systems implementations. The approach shown in this poster is based on the usage of the SOA paradigm from a model driven point of view: a model driven service oriented architecture (MDSOA) framework. Based on the MDA specification we have identified a metamodel for each of the three abstraction levels: (1) POP* (process, organisation, product) is selected as the metamodel to represent and exchange business processes. POP* is the unified enterprise modelling language (UEML) successor. POP* metamodel represents the starting point; (2) PIM4SOA (platform independent model for service oriented architecture) (Benguria et al., 2006) is a metamodel to represent service, process, information and quality of service elements; and (3) WSDL (Web service description language) and BPEL (business process execution language) are platform specific languages","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116795681","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}
In the process of selecting commercial off-the-shelf (COTS) products, it is inevitable to encounter mismatches between COTS products and system requirements. Mismatches occur when COTS attributes do not exactly match our requirements. Many of these mismatches are resolved after selecting a COTS product in order to improve its fitness with the requirements. This paper proposes a decision support approach that aims at addressing COTS mismatches during and after the selection process. Our approach can be integrated with existing COTS selection methods at two stages: (I) When evaluating COTS candidates: our approach is used to estimate the anticipated fitness of the candidates if their mismatches are resolved. This helps to base our COTS selection decisions on the fitness that the COTS candidates will eventually have if selected. (2) After selecting a COTS product: the approach suggests alternative plans for resolving the most appropriate mismatches using suitable actions, such that the most important risk, technical, and resource constraints are met. A case study from the e-services domain is used to illustrate the method and to discuss its added value
{"title":"Decision Support for Handling Mismatches between COTS Products and System Requirements","authors":"Abdallah Mohamed, G. Ruhe, A. Eberlein","doi":"10.1109/ICCBSS.2007.13","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.13","url":null,"abstract":"In the process of selecting commercial off-the-shelf (COTS) products, it is inevitable to encounter mismatches between COTS products and system requirements. Mismatches occur when COTS attributes do not exactly match our requirements. Many of these mismatches are resolved after selecting a COTS product in order to improve its fitness with the requirements. This paper proposes a decision support approach that aims at addressing COTS mismatches during and after the selection process. Our approach can be integrated with existing COTS selection methods at two stages: (I) When evaluating COTS candidates: our approach is used to estimate the anticipated fitness of the candidates if their mismatches are resolved. This helps to base our COTS selection decisions on the fitness that the COTS candidates will eventually have if selected. (2) After selecting a COTS product: the approach suggests alternative plans for resolving the most appropriate mismatches using suitable actions, such that the most important risk, technical, and resource constraints are met. A case study from the e-services domain is used to illustrate the method and to discuss its added value","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127669763","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}
Workflow reconfiguration traditionally involves modifying workflow specifications to adapt to changing architectural conditions. Causes include the introduction of new services or the alteration of goals. Dynamic reconfiguration is currently achieved in workflow specifications employing Web services using techniques that modify endpoint bindings and control structures. Abstract specification of service endpoints delay the point at which the endpoint for a Web service is bound, and modifications to control structures can allow for a variety of complex workflows to be specified. These approaches work with limited changes. This paper defines an improved process of dynamically reconfiguring Web service workflows. Our double loop approach utilizes companion meta-data specifications and reconfiguration plans that are associated with workflow specifications. The approach maps external change requests to workflow actions to determine an appropriate reconfiguration plan without changing the workflow language. Dynamic reconfiguration concepts are reused from architecture reconfiguration research to offer a wider range of potential changes
{"title":"Reconfiguring Workflows of Web Services","authors":"R. Baird, M. Hepner, R. Gamble, M. T. Gamble","doi":"10.1109/ICCBSS.2007.30","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.30","url":null,"abstract":"Workflow reconfiguration traditionally involves modifying workflow specifications to adapt to changing architectural conditions. Causes include the introduction of new services or the alteration of goals. Dynamic reconfiguration is currently achieved in workflow specifications employing Web services using techniques that modify endpoint bindings and control structures. Abstract specification of service endpoints delay the point at which the endpoint for a Web service is bound, and modifications to control structures can allow for a variety of complex workflows to be specified. These approaches work with limited changes. This paper defines an improved process of dynamically reconfiguring Web service workflows. Our double loop approach utilizes companion meta-data specifications and reconfiguration plans that are associated with workflow specifications. The approach maps external change requests to workflow actions to determine an appropriate reconfiguration plan without changing the workflow language. Dynamic reconfiguration concepts are reused from architecture reconfiguration research to offer a wider range of potential changes","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130509391","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}
One of the main barriers for interoperability today, is the proliferation of different standards and proprietary formats for the exchange of information among the organizations willing to interoperate. But how can the different standards and formats be reconciled? Traditionally, code based mapping techniques have been performed to reconcile standards and formats, but recently a new approach has appeared for dealing with this situation; it is known as model transformation. Model transformation techniques support the engineer in the definition of formal translation rules which allow communication between incompatible components. This paper presents two of these techniques, MTF (model transformation framework) and ATL (Atlas transformation language) and compares them with the traditional approach
{"title":"Data Model Transformation for Supporting Interoperability","authors":"Gorka Benguria, X. Larrucea","doi":"10.1109/ICCBSS.2007.12","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.12","url":null,"abstract":"One of the main barriers for interoperability today, is the proliferation of different standards and proprietary formats for the exchange of information among the organizations willing to interoperate. But how can the different standards and formats be reconciled? Traditionally, code based mapping techniques have been performed to reconcile standards and formats, but recently a new approach has appeared for dealing with this situation; it is known as model transformation. Model transformation techniques support the engineer in the definition of formal translation rules which allow communication between incompatible components. This paper presents two of these techniques, MTF (model transformation framework) and ATL (Atlas transformation language) and compares them with the traditional approach","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115031208","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}
Several activities of the COTS-based systems lifecycle are supported not only by the analysis of their technical quality but also (and sometimes mostly) by considering how they fulfill some non-technical quality features considered relevant (licensing, reputation, costs and similar issues). Whilst many catalogues of technical quality features exist, it is not the case for non-technical ones, which are often managed in an ad-hoc form. In a recent work, we proposed a catalogue of non-technical quality features, designed to integrate smoothly into the ISO/IEC 9126-1 standard. In this paper, we detail the process used for the composition of the catalogue, which embraces the inclusion of several non-technical quality features already identified in the literature as well as others which have emerged form our own experience in industrial COTS components selection processes. We also outline some potential applications of the resulting catalogue, intended to support several activities of the COTS-based systems lifecycle. Finally, we describe a COTS selection process carried out in a telecommunications company
{"title":"Towards a Unified Catalogue of Non-Technical Quality Attributes to Support COTS-Based Systems Lifecycle Activities","authors":"J. Carvallo, Xavier Franch, C. Quer","doi":"10.1109/ICCBSS.2007.43","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.43","url":null,"abstract":"Several activities of the COTS-based systems lifecycle are supported not only by the analysis of their technical quality but also (and sometimes mostly) by considering how they fulfill some non-technical quality features considered relevant (licensing, reputation, costs and similar issues). Whilst many catalogues of technical quality features exist, it is not the case for non-technical ones, which are often managed in an ad-hoc form. In a recent work, we proposed a catalogue of non-technical quality features, designed to integrate smoothly into the ISO/IEC 9126-1 standard. In this paper, we detail the process used for the composition of the catalogue, which embraces the inclusion of several non-technical quality features already identified in the literature as well as others which have emerged form our own experience in industrial COTS components selection processes. We also outline some potential applications of the resulting catalogue, intended to support several activities of the COTS-based systems lifecycle. Finally, we describe a COTS selection process carried out in a telecommunications company","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132860223","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}
While COTS products can be made secure and reliable within a individual domains, they may introduce security vulnerabilities when integrated with other components due to different security expectations. These problematic interactions within an integrated system can be hidden among the multiple, contributing policy types. Furthermore, security certification criteria governing the integrated system can introduce conflicts with local component policies. Security policies and certification criteria lack a common representation. Security policies use various formats and levels of granularity without comparable attributes. Certification criteria are often text-based checklists. We outline a policy configuration model to represent security policies in a format which can manifest conflicting properties across policy specifications. The model defines security policies according to fundamental attributes of property assertions, observable behaviors, mechanisms, constraints, communication and interaction expectations, dependencies on other policies, system configuration, and component state. We extend model expression concepts to incorporate requirements based on common certification criteria
{"title":"The Impact of Certification Criteria on Integrated COTS-Based Systems","authors":"M. Kelkar, R. Perry, R. Gamble, A. Walvekar","doi":"10.1109/ICCBSS.2007.42","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.42","url":null,"abstract":"While COTS products can be made secure and reliable within a individual domains, they may introduce security vulnerabilities when integrated with other components due to different security expectations. These problematic interactions within an integrated system can be hidden among the multiple, contributing policy types. Furthermore, security certification criteria governing the integrated system can introduce conflicts with local component policies. Security policies and certification criteria lack a common representation. Security policies use various formats and levels of granularity without comparable attributes. Certification criteria are often text-based checklists. We outline a policy configuration model to represent security policies in a format which can manifest conflicting properties across policy specifications. The model defines security policies according to fundamental attributes of property assertions, observable behaviors, mechanisms, constraints, communication and interaction expectations, dependencies on other policies, system configuration, and component state. We extend model expression concepts to incorporate requirements based on common certification criteria","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114940314","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}
A. Pasala, Srinivasa Rao, Arnab Dutta Gupta, Srinivas Gunturu
Various regression test selection strategies have been developed to establish the correctness of software systems upon deployment of COTS upgrades. These strategies recommend a smaller regression test suite to be re-executed. We present a process that identifies the patch impact on the system and localizes the source of potential errors without executing the system test suite. The impact is analyzed based on verifying the behavior of affected COTS API execution-sequences. An API execution-sequence is called affected when one or more of the altered functions of the COTS upgrade are part of COTS API execution-sequence that interfaces with application components. A wrapper-based passive test oracle has been developed to check the correctness of the behavior of these execution-sequences. The changed behavior of these execution-sequences reflects the patch impact. A case study has been conducted and the results are encouraging
{"title":"On the validation of API execution-sequence to assess the correctness of application upon COTS upgrades deployment","authors":"A. Pasala, Srinivasa Rao, Arnab Dutta Gupta, Srinivas Gunturu","doi":"10.1109/ICCBSS.2007.23","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.23","url":null,"abstract":"Various regression test selection strategies have been developed to establish the correctness of software systems upon deployment of COTS upgrades. These strategies recommend a smaller regression test suite to be re-executed. We present a process that identifies the patch impact on the system and localizes the source of potential errors without executing the system test suite. The impact is analyzed based on verifying the behavior of affected COTS API execution-sequences. An API execution-sequence is called affected when one or more of the altered functions of the COTS upgrade are part of COTS API execution-sequence that interfaces with application components. A wrapper-based passive test oracle has been developed to check the correctness of the behavior of these execution-sequences. The changed behavior of these execution-sequences reflects the patch impact. A case study has been conducted and the results are encouraging","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115177303","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}
With the goal of reducing time to market and project costs, the current trend of real time business and mission critical systems is evolving from the development of custom made applications to the use of commercial off the shelf (COTS) products. Obviously, the same confidence and quality of the custom made software components is expected from the commercial applications. In most cases, such products (COTS) are not designed with stringent timing and/or safety requirements as priorities. Thus, to decrease the gap between the use of custom made components and COTS components, this paper presents a methodology for evaluating COTS products in the scope of dependable, real time systems, through the application of fault injection techniques at key points of the software engineering process. By combining the use of robustness testing (fault injection at interface level) with software fault injection (using educated fault injection operators), a COTS component can be assessed in the context of the system it will belong to, with special emphasis given to timing and safety constraints that are usually imposed by the target real time dependable environment. In the course of this work, three case studies have been performed to assess the methodology using realistic scenarios that used common COTS products. Results for one case study are presented
{"title":"Verification and Validation of (Real Time) COTS Products using Fault Injection Techniques","authors":"R. Barbosa, N. Silva, J. Durães, H. Madeira","doi":"10.1109/ICCBSS.2007.45","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.45","url":null,"abstract":"With the goal of reducing time to market and project costs, the current trend of real time business and mission critical systems is evolving from the development of custom made applications to the use of commercial off the shelf (COTS) products. Obviously, the same confidence and quality of the custom made software components is expected from the commercial applications. In most cases, such products (COTS) are not designed with stringent timing and/or safety requirements as priorities. Thus, to decrease the gap between the use of custom made components and COTS components, this paper presents a methodology for evaluating COTS products in the scope of dependable, real time systems, through the application of fault injection techniques at key points of the software engineering process. By combining the use of robustness testing (fault injection at interface level) with software fault injection (using educated fault injection operators), a COTS component can be assessed in the context of the system it will belong to, with special emphasis given to timing and safety constraints that are usually imposed by the target real time dependable environment. In the course of this work, three case studies have been performed to assess the methodology using realistic scenarios that used common COTS products. Results for one case study are presented","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121726898","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}
Currently, information systems are mainly built by integrating or customizing commercial off-the-shelf (COTS) components acquired or licensed from the marketplace. The processes necessary to steer a suitable acquisition are different from traditional software development processes. Among them, we are interested in the process of selection of COTS components. COTS selection requires discipline to coordinate the selection team and the set of new activities that are necessary to support a successful selection. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifies "what" we must have into account to achieve the disciplined processes (among others things). On the other hand, agile methods are playing nowadays an important role in software engineering practices, because they are specifying "how" the software practices must be addressed to attain agility and improvement in the software processes. The contribution of this work is to propose a framework to reconcile agile and discipline-based approaches in the COTS selection domain, by including agile practices into the 5 levels of CMMI for COTS acquisition
{"title":"Reconciling Agility and Discipline in COTS Selection Processes","authors":"F. Navarrete, P. Botella, Xavier Franch","doi":"10.1109/ICCBSS.2007.29","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.29","url":null,"abstract":"Currently, information systems are mainly built by integrating or customizing commercial off-the-shelf (COTS) components acquired or licensed from the marketplace. The processes necessary to steer a suitable acquisition are different from traditional software development processes. Among them, we are interested in the process of selection of COTS components. COTS selection requires discipline to coordinate the selection team and the set of new activities that are necessary to support a successful selection. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifies \"what\" we must have into account to achieve the disciplined processes (among others things). On the other hand, agile methods are playing nowadays an important role in software engineering practices, because they are specifying \"how\" the software practices must be addressed to attain agility and improvement in the software processes. The contribution of this work is to propose a framework to reconcile agile and discipline-based approaches in the COTS selection domain, by including agile practices into the 5 levels of CMMI for COTS acquisition","PeriodicalId":326403,"journal":{"name":"2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2007-02-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130083511","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
扫码关注我们
求助内容：
应助结果提醒方式：