Pub Date : 2007-05-20DOI: 10.1109/ICSECOMPANION.2007.35
D. Firesmith
Summary form only given. Many software-intensive systems have significant safety ramifications and need to have their associated safety-related requirements properly engineered. It has been observed by several consultants, researchers, and authors that inadequate requirements are a major cause of accidents involving software-intensive systems. Yet in practice, there is very little interaction between the requirements and safety disciplines and little collaboration between their respective communities. Most requirements engineers know little about safety engineering, and most safety engineers know little about requirements engineering. Also, safety engineering typically concentrates on architectures and designs rather than requirements because hazard analysis typically depends on the identification of hardware and software components, the failure of which can cause accidents. This leads to safety-related requirements that are often ambiguous, incomplete, and even missing. The tutorial begins with a single common realistic example of a safety critical system that will be used throughout to provide good examples of safety-related requirements. The tutorial then provides an introduction to requirements engineering for safety engineers and an introduction to safety engineering for requirements engineers. The tutorial then provides clear definitions and descriptions of the different kinds of safety-related requirements and finishes with a practical process for producing them
{"title":"Engineering Safety - and Security-Related Requirements for Software-Intensive Systems","authors":"D. Firesmith","doi":"10.1109/ICSECOMPANION.2007.35","DOIUrl":"https://doi.org/10.1109/ICSECOMPANION.2007.35","url":null,"abstract":"Summary form only given. Many software-intensive systems have significant safety ramifications and need to have their associated safety-related requirements properly engineered. It has been observed by several consultants, researchers, and authors that inadequate requirements are a major cause of accidents involving software-intensive systems. Yet in practice, there is very little interaction between the requirements and safety disciplines and little collaboration between their respective communities. Most requirements engineers know little about safety engineering, and most safety engineers know little about requirements engineering. Also, safety engineering typically concentrates on architectures and designs rather than requirements because hazard analysis typically depends on the identification of hardware and software components, the failure of which can cause accidents. This leads to safety-related requirements that are often ambiguous, incomplete, and even missing. The tutorial begins with a single common realistic example of a safety critical system that will be used throughout to provide good examples of safety-related requirements. The tutorial then provides an introduction to requirements engineering for safety engineers and an introduction to safety engineering for requirements engineers. The tutorial then provides clear definitions and descriptions of the different kinds of safety-related requirements and finishes with a practical process for producing them","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-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121108143","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}
Many organizations are increasingly looking for techniques that can lead to large-scale (and often dynamic) integration and inter operation of new and existing components, services, or systems. Service-oriented architecture (SOA) holds great promise as an approach that can facilitate these desires. Over the past decades, organizations have tried various development software reuse approaches, such as commercial off-the-shelf (COTS) based systems, product line engineering, and frames. As we move into this new world of highly interoperable systems, we should take advantage of the lessons taught by the development of these approaches. This paper identifies key lessons from COTS and software reuse that can be applied to SOA
{"title":"What COTS and Software Reuse Teach Us about SOA","authors":"W. Anderson","doi":"10.1109/ICCBSS.2007.46","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.46","url":null,"abstract":"Many organizations are increasingly looking for techniques that can lead to large-scale (and often dynamic) integration and inter operation of new and existing components, services, or systems. Service-oriented architecture (SOA) holds great promise as an approach that can facilitate these desires. Over the past decades, organizations have tried various development software reuse approaches, such as commercial off-the-shelf (COTS) based systems, product line engineering, and frames. As we move into this new world of highly interoperable systems, we should take advantage of the lessons taught by the development of these approaches. This paper identifies key lessons from COTS and software reuse that can be applied to SOA","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":"115628097","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. As evidenced by the success of the ICCBSS Conferences, the OTS (off-the-shelf)-based development community is constantly growing. Unfortunately, different development projects and organizations have adopted different terminology and reference models for the OTS-based tasks to be performed, work products to be produced, and roles to be played. Due to the current lack of standardization, these unnecessary differences have produced a growing confusion that has limited effective communication and have slowed the improvement and spread of OTS-based development methods. We believe it is feasible and the time is ripe to start reaching a consensus on a single common framework of reusable OTS-related method components
{"title":"Second International OTS-Based Development Methods Workshop","authors":"D. Firesmith","doi":"10.1109/ICCBSS.2007.33","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.33","url":null,"abstract":"Summary form only given. As evidenced by the success of the ICCBSS Conferences, the OTS (off-the-shelf)-based development community is constantly growing. Unfortunately, different development projects and organizations have adopted different terminology and reference models for the OTS-based tasks to be performed, work products to be produced, and roles to be played. Due to the current lack of standardization, these unnecessary differences have produced a growing confusion that has limited effective communication and have slowed the improvement and spread of OTS-based development methods. We believe it is feasible and the time is ripe to start reaching a consensus on a single common framework of reusable OTS-related method components","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":"117064196","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}
Civilization has slipped into the twenty-first century with electronics touching nearly every part of our lives. Since inception, integrated circuit technology and software have advanced exponentially. Complex systems such as cars, satellites and aircraft can have subsystems with lifespans that wildly differ. Many such products are truly a systems of systems where subsystem change-out is required to keep the unit up-to-date. Products that run mostly on electronics are often smaller like telephones and computers. When obsolete they are usually replaced rather than refurbished. But in larger systems like an aircraft or a submarine, subsystem change-out should be considering during planning. In the Department of Defense as well as other organizations, managing such a process is complex. This paper examines such complexity, provides a visual framework for a system of systems and the relevance and importance of change-out in general
{"title":"Change-out: A System of Systems Approach to COTS Management","authors":"S. J. Baron","doi":"10.1109/ICCBSS.2007.8","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.8","url":null,"abstract":"Civilization has slipped into the twenty-first century with electronics touching nearly every part of our lives. Since inception, integrated circuit technology and software have advanced exponentially. Complex systems such as cars, satellites and aircraft can have subsystems with lifespans that wildly differ. Many such products are truly a systems of systems where subsystem change-out is required to keep the unit up-to-date. Products that run mostly on electronics are often smaller like telephones and computers. When obsolete they are usually replaced rather than refurbished. But in larger systems like an aircraft or a submarine, subsystem change-out should be considering during planning. In the Department of Defense as well as other organizations, managing such a process is complex. This paper examines such complexity, provides a visual framework for a system of systems and the relevance and importance of change-out in general","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":"123584582","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. Several COTS evaluation processes such as those in (Comella-Dorda et al., 2002) and (Yang and Boehm, 2004) utilize a weighted aggregation (or a similar) method to evaluate COTS products' functional and nonfunctional capabilities. The weighted aggregation method uses O (COTS score * weight of the criteria) to score COTS products relative to each other. However, so far there is little literature that guides users in weighting the evaluation criteria and scoring COTS products on these criteria. In (Boehm and Gruenbacher, 2000) and (Briggs and Grunbacher, 2002) authors have presented a stakeholder-driven process that is used to elicit stakeholder Win conditions, which can then transformed into prioritized requirements (Boehm et al., 1994 and Kitapci et al., 2003). In this poster we present a tailored version of such a stakeholder-driven process that can be applied in the COTS context to define a weighted COTS evaluation criteria as well as a scale for scoring COTS products
只提供摘要形式。一些COTS评估过程，如(Comella-Dorda et al.， 2002)和(Yang and Boehm, 2004)中使用加权聚合(或类似的)方法来评估COTS产品的功能和非功能能力。加权聚合法使用0 (COTS评分*标准权重)对COTS产品进行相对评分。然而，到目前为止，很少有文献指导用户对评估标准进行加权，并根据这些标准对COTS产品进行评分。在(Boehm and Gruenbacher, 2000)和(Briggs and Grunbacher, 2002)中，作者提出了一个利益相关者驱动的过程，该过程用于引出利益相关者获胜条件，然后可以将其转化为优先需求(Boehm et al.， 1994和Kitapci et al.， 2003)。在这张海报中，我们展示了这样一个利益相关者驱动过程的定制版本，它可以应用于COTS上下文中，以定义一个加权的COTS评估标准，以及一个为COTS产品评分的尺度
{"title":"A Stakeholder Negotiation Process for Deriving COTS Evaluation Criteria","authors":"Jesal Bhuta, Hasan Kitapci","doi":"10.1109/ICCBSS.2007.5","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.5","url":null,"abstract":"Summary form only given. Several COTS evaluation processes such as those in (Comella-Dorda et al., 2002) and (Yang and Boehm, 2004) utilize a weighted aggregation (or a similar) method to evaluate COTS products' functional and nonfunctional capabilities. The weighted aggregation method uses O (COTS score * weight of the criteria) to score COTS products relative to each other. However, so far there is little literature that guides users in weighting the evaluation criteria and scoring COTS products on these criteria. In (Boehm and Gruenbacher, 2000) and (Briggs and Grunbacher, 2002) authors have presented a stakeholder-driven process that is used to elicit stakeholder Win conditions, which can then transformed into prioritized requirements (Boehm et al., 1994 and Kitapci et al., 2003). In this poster we present a tailored version of such a stakeholder-driven process that can be applied in the COTS context to define a weighted COTS evaluation criteria as well as a scale for scoring COTS products","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":"134164377","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}
By investigating the failure of Software IC in object-oriented technology and studying the characteristics of component-based or COTS-based software technologies, this paper revises software IC and develops a software-slot-oriented strategy for the design of component-based software systems. This new strategy introduces requirements directly into the design of component-based systems, and allows architects to focus on system frameworks without too much concern about components. This work provides a mechanism to deal with the increasingly complex interface logics of COTS systems, and suggests a possible guidance for component standardization. Effectiveness and availability of the proposed approach are illustrated with a case study that applies the software-slot-oriented design on a practical component-based software system
{"title":"Software IC Revised: A New Approach of Component-Based Software Design with Software Slots","authors":"Shangwei Duan, Xiaobu Yuan","doi":"10.1109/ICCBSS.2007.41","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.41","url":null,"abstract":"By investigating the failure of Software IC in object-oriented technology and studying the characteristics of component-based or COTS-based software technologies, this paper revises software IC and develops a software-slot-oriented strategy for the design of component-based software systems. This new strategy introduces requirements directly into the design of component-based systems, and allows architects to focus on system frameworks without too much concern about components. This work provides a mechanism to deal with the increasingly complex interface logics of COTS systems, and suggests a possible guidance for component standardization. Effectiveness and availability of the proposed approach are illustrated with a case study that applies the software-slot-oriented design on a practical component-based software system","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":"133842874","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}
N. Chandrashekar, S. M. Gautam, K. S. Srinivas, J. Vijayananda
Ever since medical images were digitized in the late 1970fs, there has been an explosion of diagnostic digital imaging techniques and procedures. Medical information systems have embraced the advances in technology to provide better health care for the patients and significant workflow improvements for the hospitals. This has led to a noteworthy evolution of medical information systems over the last few decades. From what used to be single stand alone modalities, the evolution has passed through cluster of modalities; multi modality clusters in a single hospital and has now reached a stage where in we have an enterprise network connecting many such hospitals thereby creating a system of systems. Medical image repositories form a critical subsystem in the medical systems of systems. They have a diverse role to play in any hospital starting from storing of electronic patient records and scanned medical images generated by individual modalities like X-Ray and MR to storing of data in an enterprise hospital network. This paper discusses the challenges faced by a medical image repository used in the context of a system of systems and how we have realized the image repository to handle these challenges
{"title":"Realizing a Generic Medical Image Repository for System of Systems","authors":"N. Chandrashekar, S. M. Gautam, K. S. Srinivas, J. Vijayananda","doi":"10.1109/ICCBSS.2007.28","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.28","url":null,"abstract":"Ever since medical images were digitized in the late 1970fs, there has been an explosion of diagnostic digital imaging techniques and procedures. Medical information systems have embraced the advances in technology to provide better health care for the patients and significant workflow improvements for the hospitals. This has led to a noteworthy evolution of medical information systems over the last few decades. From what used to be single stand alone modalities, the evolution has passed through cluster of modalities; multi modality clusters in a single hospital and has now reached a stage where in we have an enterprise network connecting many such hospitals thereby creating a system of systems. Medical image repositories form a critical subsystem in the medical systems of systems. They have a diverse role to play in any hospital starting from storing of electronic patient records and scanned medical images generated by individual modalities like X-Ray and MR to storing of data in an enterprise hospital network. This paper discusses the challenges faced by a medical image repository used in the context of a system of systems and how we have realized the image repository to handle these challenges","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":"123033047","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}
Software systems today are frequently composed from prefabricated commercial components that provide complex functionality and engage in complex interactions. Such projects that utilize multiple commercial-off-the-shelf (COTS) products often confront interoperability conflicts resulting in budget and schedule overruns. These conflicts occur because of the incompatible assumptions made by developers of these products. Identification of such conflicts and planning strategies to resolve them is critical for developing such systems under budget and schedule constraints. Unfortunately, acquiring information to perform interoperability analysis is a time-intensive process. Moreover, increase in the number of COTS products available to fulfill similar functionality leads to hundreds of COTS product combinations, further complicating the COTS interoperability assessment landscape. In this paper we present a set of attributes that can be used to define COTS interoperability-specific characteristics. COTS product definitions based on these attributes can be used to perform high-level and automated interoperability assessment to filter out COTS product combinations whose integration will not be feasible within project constraints. In addition to above stated attributes, we present a tool that can be used to assess COTS-based architectures for interoperability conflicts, reducing the overall effort spent in performing interoperability analysis. Our preliminary experience in using the framework indicates an increase in interoperability assessment productivity by 50% and accuracy by 20%
{"title":"Attribute-Based COTS Product Interoperability Assessment","authors":"Jesal Bhuta, B. Boehm","doi":"10.1109/ICCBSS.2007.6","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.6","url":null,"abstract":"Software systems today are frequently composed from prefabricated commercial components that provide complex functionality and engage in complex interactions. Such projects that utilize multiple commercial-off-the-shelf (COTS) products often confront interoperability conflicts resulting in budget and schedule overruns. These conflicts occur because of the incompatible assumptions made by developers of these products. Identification of such conflicts and planning strategies to resolve them is critical for developing such systems under budget and schedule constraints. Unfortunately, acquiring information to perform interoperability analysis is a time-intensive process. Moreover, increase in the number of COTS products available to fulfill similar functionality leads to hundreds of COTS product combinations, further complicating the COTS interoperability assessment landscape. In this paper we present a set of attributes that can be used to define COTS interoperability-specific characteristics. COTS product definitions based on these attributes can be used to perform high-level and automated interoperability assessment to filter out COTS product combinations whose integration will not be feasible within project constraints. In addition to above stated attributes, we present a tool that can be used to assess COTS-based architectures for interoperability conflicts, reducing the overall effort spent in performing interoperability analysis. Our preliminary experience in using the framework indicates an increase in interoperability assessment productivity by 50% and accuracy by 20%","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":"133744080","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 principal challenge in requirements engineering for component-based software systems is to develop models that allow us to make the best use of the available component technology by balancing aspects of requirements, business concerns, and architectural considerations with capabilities embodied in software components. Unfortunately, the critical steps of requirements elicitation and modelling are often ignored in requirements methods for component-based systems. Requirements elicitation not only allows the developer to establish the actors and stakeholders associated with the system, it also provides a means for identifying and structuring their needs. Requirement modelling in component-based development, is an important vehicle for contextualizing, scoping and mapping user requirements to possible blackbox component solutions. This paper proposes an approach to requirements definition that uses the nation of viewpoints and services. Viewpoints provide us with a framework for eliciting and structuring user requirements; services provide us with a mechanism for mapping the requirements to components and component architectures. Together, they provide traceable progression from initial system formulation through to system design and composition
{"title":"A Service-Oriented Approach for Specifying Component-Based Systems","authors":"G. Kotonya, J. Hutchinson","doi":"10.1109/ICCBSS.2007.4","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.4","url":null,"abstract":"The principal challenge in requirements engineering for component-based software systems is to develop models that allow us to make the best use of the available component technology by balancing aspects of requirements, business concerns, and architectural considerations with capabilities embodied in software components. Unfortunately, the critical steps of requirements elicitation and modelling are often ignored in requirements methods for component-based systems. Requirements elicitation not only allows the developer to establish the actors and stakeholders associated with the system, it also provides a means for identifying and structuring their needs. Requirement modelling in component-based development, is an important vehicle for contextualizing, scoping and mapping user requirements to possible blackbox component solutions. This paper proposes an approach to requirements definition that uses the nation of viewpoints and services. Viewpoints provide us with a framework for eliciting and structuring user requirements; services provide us with a mechanism for mapping the requirements to components and component architectures. Together, they provide traceable progression from initial system formulation through to system design and composition","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":"114617830","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. Architects are faced with the problem of building enterprise scale information systems, with streamlined, automated internal business processes and Web-enabled business functions, all across multiple legacy applications. The underlying architectures such systems are embodied in a range of diverse products known as 'enterprise integration' technologies. In this tutorial, we highlight some of the major problems, approaches and issues in designing enterprise integration architectures and selecting appropriate supporting technology. An architect's perspective on designing large-scale integrated applications is taken, and we discuss requirements elicitation, architecture patterns, enterprise integration technology features and risk mitigation. Specific technology platforms covered include messaging, message brokers, application servers, business process management and Web services and service-oriented architecture technologies
{"title":"Evaluating Enterprise Integration Middleware Technologies","authors":"I. Gordon","doi":"10.1109/ICCBSS.2007.16","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.16","url":null,"abstract":"Summary form only given. Architects are faced with the problem of building enterprise scale information systems, with streamlined, automated internal business processes and Web-enabled business functions, all across multiple legacy applications. The underlying architectures such systems are embodied in a range of diverse products known as 'enterprise integration' technologies. In this tutorial, we highlight some of the major problems, approaches and issues in designing enterprise integration architectures and selecting appropriate supporting technology. An architect's perspective on designing large-scale integrated applications is taken, and we discuss requirements elicitation, architecture patterns, enterprise integration technology features and risk mitigation. Specific technology platforms covered include messaging, message brokers, application servers, business process management and Web services and service-oriented architecture technologies","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":"125886403","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
扫码关注我们
求助内容：
应助结果提醒方式：