You don't have to look far to become aware of the effect that service-oriented architecture (SOA) is having on software systems. Vendors are aggressively marketing hardware, software, tools, and services that support SOA implementation within organizations as diverse as the Department of Defense, banks, federal agencies, manufacturing companies, and health care providers. Even more significantly, customers are embracing SOA as a way to successfully achieve business agility and interoperability among systems. However, our experience from working with current and potential adopters of SOA is that they often have a variety of misconceptions that lead them to oversimplify the effort required to implement SOA. Chief among these misconceptions is the belief that simply by adopting an SOA strategy for the enterprise, an organization has established a well-crafted architecture that will help the organization achieve its many IT goals. In reality, SOA is not an architecture, but an architectural pattern from which an infinite number of architectures can be derived - both good and bad. In this experience report, we discuss at a high level this and several other misconceptions about SOA derived from our experiences
{"title":"Common Misconceptions about Service-Oriented Architecture","authors":"G. Lewis, E. Morris, Soumya Simanta, L. Wrage","doi":"10.1109/ICCBSS.2007.9","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.9","url":null,"abstract":"You don't have to look far to become aware of the effect that service-oriented architecture (SOA) is having on software systems. Vendors are aggressively marketing hardware, software, tools, and services that support SOA implementation within organizations as diverse as the Department of Defense, banks, federal agencies, manufacturing companies, and health care providers. Even more significantly, customers are embracing SOA as a way to successfully achieve business agility and interoperability among systems. However, our experience from working with current and potential adopters of SOA is that they often have a variety of misconceptions that lead them to oversimplify the effort required to implement SOA. Chief among these misconceptions is the belief that simply by adopting an SOA strategy for the enterprise, an organization has established a well-crafted architecture that will help the organization achieve its many IT goals. In reality, SOA is not an architecture, but an architectural pattern from which an infinite number of architectures can be derived - both good and bad. In this experience report, we discuss at a high level this and several other misconceptions about SOA derived from our experiences","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":"123409102","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 tutorial outlines the basic principles of SOA based systems and discusses their potentials and challenges. The basic operations of service discovery, service composition and service invocation are outlined. The OASIS SOA-based systems development reference model is also presented. The tutorial also identifies common misconceptions that users have experienced in migrating to SOAs. SOA systems are analyzed from three perspectives: the application developer, the infrastructure developer, and the service provider. The needs and concerns of each of these participants, as well as the types of cross organizational communication patterns required for success are outlined. While there is often an emphasis on technical SOA issues, organizations need to address a far broader set of issues. These are outlined as the four pillars of SOA-based systems development. The four pillars include: alignment with overall business strategy; development of realistic SOA governance policies and procedures; Understanding of realistic contextual-based technology capabilities limitations; and recognition of the paradigm shift that SOA-based development entails. The issues of migrating legacy assets to an SOA environment are outlined. The service migration and reuse technique (SMART) is discussed. SMART is a method for making decisions on whether and how to convert legacy components to services within a specific SOA infrastructure. A case study using the method provides a real world context for its applicability. Open issues and current research topics are outlined
{"title":"Developing Realistic Approaches for Migration of Legacy Assets to SOA Environments","authors":"Dennis B. Smith, G. Lewis","doi":"10.1109/ICCBSS.2007.14","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.14","url":null,"abstract":"Summary form only given. This tutorial outlines the basic principles of SOA based systems and discusses their potentials and challenges. The basic operations of service discovery, service composition and service invocation are outlined. The OASIS SOA-based systems development reference model is also presented. The tutorial also identifies common misconceptions that users have experienced in migrating to SOAs. SOA systems are analyzed from three perspectives: the application developer, the infrastructure developer, and the service provider. The needs and concerns of each of these participants, as well as the types of cross organizational communication patterns required for success are outlined. While there is often an emphasis on technical SOA issues, organizations need to address a far broader set of issues. These are outlined as the four pillars of SOA-based systems development. The four pillars include: alignment with overall business strategy; development of realistic SOA governance policies and procedures; Understanding of realistic contextual-based technology capabilities limitations; and recognition of the paradigm shift that SOA-based development entails. The issues of migrating legacy assets to an SOA environment are outlined. The service migration and reuse technique (SMART) is discussed. SMART is a method for making decisions on whether and how to convert legacy components to services within a specific SOA infrastructure. A case study using the method provides a real world context for its applicability. Open issues and current research topics are outlined","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":"121602725","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 workshop is a key part of the ICCBSS transition and will determine the future focus for the conference. The necessity for the transition is a reflection of community's recognition that the complexity of the systems and their sizes have grown tremendously, and that, while COTS-based systems are vital in today's business, the hardest part of successful COTS-based development often has little to do with the "C" $"commercial" - in "COTS". The workshop will generate a robust discussion about the challenges - whether technological, organizational, or cultural $for constructing, acquiring, deploying, and sustaining software-intensive systems of systems that require interoperation among a wide variety of components or constituent systems. The objective of the workshop is to develop and organize the challenges into areas that are in need of further research and to provide some indications of the directions such research might take. Workshop contributions and results will be published as an SEI-NRC Technical Report
{"title":"Research Agenda for System of Systems Interoperability","authors":"P. Oberndorf, Anatol W. Kark","doi":"10.1109/ICCBSS.2007.31","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.31","url":null,"abstract":"Summary form only given. This workshop is a key part of the ICCBSS transition and will determine the future focus for the conference. The necessity for the transition is a reflection of community's recognition that the complexity of the systems and their sizes have grown tremendously, and that, while COTS-based systems are vital in today's business, the hardest part of successful COTS-based development often has little to do with the \"C\" $\"commercial\" - in \"COTS\". The workshop will generate a robust discussion about the challenges - whether technological, organizational, or cultural $for constructing, acquiring, deploying, and sustaining software-intensive systems of systems that require interoperation among a wide variety of components or constituent systems. The objective of the workshop is to develop and organize the challenges into areas that are in need of further research and to provide some indications of the directions such research might take. Workshop contributions and results will be published as an SEI-NRC Technical Report","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":"122565429","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 potential benefits of evolving legacy systems to COTS-based component architectures are well documented. These include rapid, non-intrusive modernization through the use of COTS software components, and significantly reduced post maintenance costs. However, the hype has not translated to a corresponding increase in the migration of legacy systems to COTS-based architectures. There are two main reasons for this. First, many legacy systems provide adequate core functionality. For this type of legacy system, replacement may not be the most cost-effective solution. Secondly, there is a general lack of scalable methods and tools that support COTS-based evolution of legacy systems. This paper describes our experience in using a component-based method to evolve a legacy system
{"title":"A COTS-Based Approach for Evolving legacy Systems","authors":"G. Kotonya, J. Hutchinson","doi":"10.1109/ICCBSS.2007.1","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.1","url":null,"abstract":"The potential benefits of evolving legacy systems to COTS-based component architectures are well documented. These include rapid, non-intrusive modernization through the use of COTS software components, and significantly reduced post maintenance costs. However, the hype has not translated to a corresponding increase in the migration of legacy systems to COTS-based architectures. There are two main reasons for this. First, many legacy systems provide adequate core functionality. For this type of legacy system, replacement may not be the most cost-effective solution. Secondly, there is a general lack of scalable methods and tools that support COTS-based evolution of legacy systems. This paper describes our experience in using a component-based method to evolve a legacy 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":"125890799","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. The last few years has seen a great acceleration in the convergence of two communities - the open standards community that is setting a foundation for how global, interoperable software intensive systems can be specified and the open source community which is implementing many of these standards. As the pace of software complexity continues to accelerate -we are assembling and integrating software that is produced by a global community - new challenges are driving architectural innovation. How can we design these systems with composability in mind while at the same time improving the productivity & consumability (by architects as well as users) of the systems we deliver? The move towards model driven architecture (MDA) service oriented architecture (SOA) - the `architecture word is respectable now! - and many of the open source projects at eclipse.org and apache.org that implement these specifications clearly illustrate this trend. What is missing? - A focus on `consumability': How can we use motivating scenarios from end users that drive the implementation of these standards as we continue our thirst for simplifying and managing software complexity? The talk will conclude with some late breaking information on how some of the key emerging MDA and SOA standards are converging and building a foundation for the next wave of standards & innovation in business process management
{"title":"Improving Architectural Composability and Consumability using Communities: Lessons learned from Eclipse, SOA and MDA","authors":"S. Iyengar","doi":"10.1109/ICCBSS.2007.18","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.18","url":null,"abstract":"Summary form only given. The last few years has seen a great acceleration in the convergence of two communities - the open standards community that is setting a foundation for how global, interoperable software intensive systems can be specified and the open source community which is implementing many of these standards. As the pace of software complexity continues to accelerate -we are assembling and integrating software that is produced by a global community - new challenges are driving architectural innovation. How can we design these systems with composability in mind while at the same time improving the productivity & consumability (by architects as well as users) of the systems we deliver? The move towards model driven architecture (MDA) service oriented architecture (SOA) - the `architecture word is respectable now! - and many of the open source projects at eclipse.org and apache.org that implement these specifications clearly illustrate this trend. What is missing? - A focus on `consumability': How can we use motivating scenarios from end users that drive the implementation of these standards as we continue our thirst for simplifying and managing software complexity? The talk will conclude with some late breaking information on how some of the key emerging MDA and SOA standards are converging and building a foundation for the next wave of standards & innovation in business process management","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":"131345746","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}
{"title":"Interoperability \"Pain Points\" in SMEs","authors":"H. Müller","doi":"10.1109/ICCBSS.2007.19","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.19","url":null,"abstract":"No abstract provided.","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":"128739502","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}
Commercial and government organizations are increasingly dependent on multiple systems that will operate seamlessly together both within their own enterprise as well as across organizational boundaries. Defining, building, fielding, and evolving these "systems of systems" is sufficiently different from traditional single system development that changes to engineering, management, and organizational practices is necessary. This tutorial explores the differences of systems of systems and leverage applicable lessons from acquiring, fielding, evolving COTS-based systems
{"title":"Promises, Expectations, and Realities of Interoperability: from COTS to Systems of Systems","authors":"Lisa Brownsword, James Smith","doi":"10.1109/ICCBSS.2007.27","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.27","url":null,"abstract":"Commercial and government organizations are increasingly dependent on multiple systems that will operate seamlessly together both within their own enterprise as well as across organizational boundaries. Defining, building, fielding, and evolving these \"systems of systems\" is sufficiently different from traditional single system development that changes to engineering, management, and organizational practices is necessary. This tutorial explores the differences of systems of systems and leverage applicable lessons from acquiring, fielding, evolving COTS-based systems","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":"127201407","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 this paper we propose a taxonomy to characterize component-based systems. The criteria of our taxonomy have been selected as a result of constructing a number of component-based software engineering tools within the Adoption-Centric Software Engineering project at the University of Victoria. We have applied the taxonomy in our work to characterize the resulting tools and to define the design space of our project's proposed tool-building methodology. Our taxonomy strives to capture the most important properties of component-based systems, resulting in a taxonomy that is both course-grained and lightweight. We believe that it is useful for other researchers in a number of ways, for instance, for component selection and to reason about certain quality attributes of components
{"title":"A Lightweight Taxonomy to Characterize Component-Based Systems","authors":"H. Kienle, H. Müller","doi":"10.1109/ICCBSS.2007.2","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.2","url":null,"abstract":"In this paper we propose a taxonomy to characterize component-based systems. The criteria of our taxonomy have been selected as a result of constructing a number of component-based software engineering tools within the Adoption-Centric Software Engineering project at the University of Victoria. We have applied the taxonomy in our work to characterize the resulting tools and to define the design space of our project's proposed tool-building methodology. Our taxonomy strives to capture the most important properties of component-based systems, resulting in a taxonomy that is both course-grained and lightweight. We believe that it is useful for other researchers in a number of ways, for instance, for component selection and to reason about certain quality attributes of 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":"132336525","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}
Service-Oriented Architecture (SOA) is having a significant impact on the way software systems are developed. Organizations as diverse as banks, health care providers, and government organizations are focusing on SOA as a way to reach a previously unachievable level of interoperability among systems and agility within business practices.
{"title":"A Research Agenda for Service-Oriented Architecture","authors":"K. Kontogiannis","doi":"10.1145/1370916.1370917","DOIUrl":"https://doi.org/10.1145/1370916.1370917","url":null,"abstract":"Service-Oriented Architecture (SOA) is having a significant impact on the way software systems are developed. Organizations as diverse as banks, health care providers, and government organizations are focusing on SOA as a way to reach a previously unachievable level of interoperability among systems and agility within business practices.","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":"133832519","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 team at the SEI has developed a framework that has shown promise in assessing the survivability of a business process in a system of systems environment. Assessment outputs in pilot use included survivability requirements and gaps among interoperable systems. It is anticipated that the framework can be of use in the evaluation of other quality attributes. Researchers and practitioners in software design, architecture, quality assurance, and requirements validation are asked to participate in this workshop to review the work done for survivability and assist in the determination of its broader applicability
{"title":"Workshop: Assessing the Quality of a Business Process Implemented across Systems of Systems","authors":"R. Ellison, Carol Woody","doi":"10.1109/ICCBSS.2007.47","DOIUrl":"https://doi.org/10.1109/ICCBSS.2007.47","url":null,"abstract":"A team at the SEI has developed a framework that has shown promise in assessing the survivability of a business process in a system of systems environment. Assessment outputs in pilot use included survivability requirements and gaps among interoperable systems. It is anticipated that the framework can be of use in the evaluation of other quality attributes. Researchers and practitioners in software design, architecture, quality assurance, and requirements validation are asked to participate in this workshop to review the work done for survivability and assist in the determination of its broader applicability","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":"133535877","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
扫码关注我们
求助内容：
应助结果提醒方式：