{"title":"Message from the Vice President of Strategy and Technology, IBM Software Group","authors":"Kristof Kloeckner","doi":"10.1147/sj.472.0194","DOIUrl":"https://doi.org/10.1147/sj.472.0194","url":null,"abstract":"","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 2","pages":"194-194"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.472.0194","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68013571","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 paper relates our experiences at the University of California, Berkeley (UC Berkeley), designing a service science discipline. We wanted to design a discipline of service science in a principled and theoretically motivated way. We began our work by asking, “What questions would a service science have to answer?” and from that we developed a new framework for understanding service science. This framework can be visualized as a matrix whose rows are stages in a service life cycle and whose columns are disciplines that can provide answers to the questions that span the life cycle. This matrix systematically organizes the issues and challenges of service science and enables us to compare our model of a service science discipline with other definitions and curricula. This analysis identified gaps, overlaps, and opportunities that shaped the design of our curriculum and in particular a new survey course that serves as the cornerstone of service science education at UC Berkeley.
{"title":"Designing a service science discipline with discipline","authors":"R. J. Glushko","doi":"10.1147/sj.471.0015","DOIUrl":"https://doi.org/10.1147/sj.471.0015","url":null,"abstract":"This paper relates our experiences at the University of California, Berkeley (UC Berkeley), designing a service science discipline. We wanted to design a discipline of service science in a principled and theoretically motivated way. We began our work by asking, “What questions would a service science have to answer?” and from that we developed a new framework for understanding service science. This framework can be visualized as a matrix whose rows are stages in a service life cycle and whose columns are disciplines that can provide answers to the questions that span the life cycle. This matrix systematically organizes the issues and challenges of service science and enables us to compare our model of a service science discipline with other definitions and curricula. This analysis identified gaps, overlaps, and opportunities that shaped the design of our curriculum and in particular a new survey course that serves as the cornerstone of service science education at UC Berkeley.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 1","pages":"15-27"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.471.0015","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"67994363","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}
M. Astley;S. Bhola;M. J. Ward;K. Shagin;H. Paz;G. Gershinsky
The complexity of real-time systems is growing extremely rapidly, as they move from isolated devices to multilevel networked systems. Traditional methodologies for developing and managing these systems are not scaling to meet the requirements of a new generation of distributed applications. While developers of complex real-time applications are looking to service-oriented architecture to address their needs for ease of development and flexibility of integration, current software infrastructures for service-oriented applications do not address the issue of predictable latency for the applications they host. In this paper, we present Pulsar, a resource-control architecture for managing the end-to-end latency of a set of distributed, time-critical applications. The primary entity of Pulsar is called a controller, which regulates an aspect of resource allocation or scheduling policy. Controllers utilize policy configurations, which may include latency targets to be achieved or resource allocations to be honored, and interact with resource allocators and schedulers (e.g., thread schedulers, memory allocators, or bandwidth reservation mechanisms) to effect local policy. Controllers also provide feedback on how well they are executing a policy. Pulsar includes an application model which captures resource-sensitive behavior and requirements and is independent of high-level programming models and application programming interfaces.
{"title":"Pulsar: A resource-control architecture for time-critical service-oriented applications","authors":"M. Astley;S. Bhola;M. J. Ward;K. Shagin;H. Paz;G. Gershinsky","doi":"10.1147/sj.472.0265","DOIUrl":"https://doi.org/10.1147/sj.472.0265","url":null,"abstract":"The complexity of real-time systems is growing extremely rapidly, as they move from isolated devices to multilevel networked systems. Traditional methodologies for developing and managing these systems are not scaling to meet the requirements of a new generation of distributed applications. While developers of complex real-time applications are looking to service-oriented architecture to address their needs for ease of development and flexibility of integration, current software infrastructures for service-oriented applications do not address the issue of predictable latency for the applications they host. In this paper, we present Pulsar, a resource-control architecture for managing the end-to-end latency of a set of distributed, time-critical applications. The primary entity of Pulsar is called a controller, which regulates an aspect of resource allocation or scheduling policy. Controllers utilize policy configurations, which may include latency targets to be achieved or resource allocations to be honored, and interact with resource allocators and schedulers (e.g., thread schedulers, memory allocators, or bandwidth reservation mechanisms) to effect local policy. Controllers also provide feedback on how well they are executing a policy. Pulsar includes an application model which captures resource-sensitive behavior and requirements and is independent of high-level programming models and application programming interfaces.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 2","pages":"265-280"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.472.0265","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68013562","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":"Message from the Vice President, Solutions & Global Technical Sales, IBM Global Sales & Distribution","authors":"Holly D. Unland","doi":"10.1147/SJ.2008.5386518","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386518","url":null,"abstract":"","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"1-1"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386518","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68033284","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}
IBM Parallel Sysplex® is a clustering technology that was designed to address specific client business objectives for IBM mainframe System z® servers. The nondisruptive addition of scalable processing capacity and improved application availability with respect to unplanned and planned outages were two key design objectives. This paper focuses on the evolving technology options that support the business objective of continuous availability. Key technology options are discussed relative to their importance to achieving continuous availability. Best practices for effectively using these technology options to improve availability, based on extensive client experiences, are recommended.
IBM Parallel Sysplex®是一种集群技术，旨在解决IBM大型机System z®服务器的特定客户业务目标。针对计划外和计划内停机，无中断地增加可扩展的处理能力和提高应用程序可用性是两个关键的设计目标。本文重点介绍了支持持续可用性业务目标的不断发展的技术选项。讨论了关键技术选项对实现持续可用性的重要性。建议根据广泛的客户体验，有效使用这些技术选项来提高可用性的最佳做法。
{"title":"IBM Parallel Sysplex clustering: Technology options for continuous availability","authors":"C. Jews;R. Ahmad;D. H. Surman","doi":"10.1147/SJ.2008.5386514","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386514","url":null,"abstract":"IBM Parallel Sysplex® is a clustering technology that was designed to address specific client business objectives for IBM mainframe System z® servers. The nondisruptive addition of scalable processing capacity and improved application availability with respect to unplanned and planned outages were two key design objectives. This paper focuses on the evolving technology options that support the business objective of continuous availability. Key technology options are discussed relative to their importance to achieving continuous availability. Best practices for effectively using these technology options to improve availability, based on extensive client experiences, are recommended.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"505-517"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386514","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68033289","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 successful development and marketing of commercial high-availability systems requires the ability to evaluate the availability of systems. Specifically, one should be able to demonstrate that projected customer requirements are met, to identify availability bottlenecks, to evaluate and compare different configurations, and to evaluate and compare different designs. For evaluation approaches based on analytic modeling, these systems are often sufficiently complex so that state-space methodsare not effective due to the large number of states, whereas combinatorial methods are inadequate for capturing all significant dependencies. The two-level hierarchical decomposition proposed here is suitable for the availability modeling of blade server systems such as IBM BladeCenter®, a commercial, high-availability multicomponent system comprising up to 14 separate blade servers and contained within a chassis that provides shared subsystems such as power and cooling. This approach is based on an availability model that combines a high-level fault tree model with a number of lowerlevel Markov models. It is used to determine component level contributions to downtime as well as steady-state availability for both standalone and clustered blade servers. Sensitivity of the results to input parameters is examined, extensions to the models are described, and availability bottlenecks and possible solutions are identified.
{"title":"Availability analysis of blade server systems","authors":"W. E. Smith;K. S. Trivedi;L. A. Tomek;J. Ackaret","doi":"10.1147/SJ.2008.5386524","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386524","url":null,"abstract":"The successful development and marketing of commercial high-availability systems requires the ability to evaluate the availability of systems. Specifically, one should be able to demonstrate that projected customer requirements are met, to identify availability bottlenecks, to evaluate and compare different configurations, and to evaluate and compare different designs. For evaluation approaches based on analytic modeling, these systems are often sufficiently complex so that state-space methodsare not effective due to the large number of states, whereas combinatorial methods are inadequate for capturing all significant dependencies. The two-level hierarchical decomposition proposed here is suitable for the availability modeling of blade server systems such as IBM BladeCenter®, a commercial, high-availability multicomponent system comprising up to 14 separate blade servers and contained within a chassis that provides shared subsystems such as power and cooling. This approach is based on an availability model that combines a high-level fault tree model with a number of lowerlevel Markov models. It is used to determine component level contributions to downtime as well as steady-state availability for both standalone and clustered blade servers. Sensitivity of the results to input parameters is examined, extensions to the models are described, and availability bottlenecks and possible solutions are identified.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"621-640"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386524","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68034520","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 diversity of service activities means that service innovations and innovation processes take various forms. In this paper, we use input/output and other data to depict how service industries vary in such areas as products, markets, work organization, and technological characteristics—most being very distinctive from primary industries (i.e., extractive industries such as agriculture, fisheries, forestry, mining, petroleum, quarrying, and the like) and secondary industries (i.e., manufacturing, construction, and utilities). Innovation survey data indicates that some service organizations behave very much like high-technology manufacturing. This is especially true of technology-based, knowledge-intensive business services (T-KIBS). Distinctive innovation patterns are displayed by KIBS based more on professional knowledge and by large network-based service firms, while many smaller service firms conform to a supplier-driven pattern. Only a small segment of service innovation conforms to the typical manufacturing-based model, in which innovation is largely organized and led by formal research and development (R&D) departments and production engineering. Project management and on-the-job innovation are common ways of organizing service innovation. Innovation policy and management have to be much more than R&D policy and R&D management: This is recognized by some national governments and in some business schools, but the full implications of a service-dominant logic are still rarely found.
{"title":"Patterns of innovation in service industries","authors":"I. Miles","doi":"10.1147/sj.471.0115","DOIUrl":"https://doi.org/10.1147/sj.471.0115","url":null,"abstract":"The diversity of service activities means that service innovations and innovation processes take various forms. In this paper, we use input/output and other data to depict how service industries vary in such areas as products, markets, work organization, and technological characteristics—most being very distinctive from primary industries (i.e., extractive industries such as agriculture, fisheries, forestry, mining, petroleum, quarrying, and the like) and secondary industries (i.e., manufacturing, construction, and utilities). Innovation survey data indicates that some service organizations behave very much like high-technology manufacturing. This is especially true of technology-based, knowledge-intensive business services (T-KIBS). Distinctive innovation patterns are displayed by KIBS based more on professional knowledge and by large network-based service firms, while many smaller service firms conform to a supplier-driven pattern. Only a small segment of service innovation conforms to the typical manufacturing-based model, in which innovation is largely organized and led by formal research and development (R&D) departments and production engineering. Project management and on-the-job innovation are common ways of organizing service innovation. Innovation policy and management have to be much more than R&D policy and R&D management: This is recognized by some national governments and in some business schools, but the full implications of a service-dominant logic are still rarely found.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 1","pages":"115-128"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.471.0115","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"67993181","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}
We apply pattern language methodology to describe design and integration patterns for real-world-aware and real-time solutions, i.e., software solutions that integrate business information processing with sensor and actuator manipulations of the external world. Efficient engineering of such solutions depends on the definition and reuse of components whose real-time characteristics can be specified. Other nonfunctional characteristics, such as throughput and reliability, may also be constrained and critical for correct behavior of a design element. We present a pattern language comprising a basic catalog of design patterns for component-based real-time solutions.
{"title":"Patterns for real-world-aware and real-time solutions","authors":"F. N. Parr;L. Yusuf","doi":"10.1147/sj.472.0335","DOIUrl":"https://doi.org/10.1147/sj.472.0335","url":null,"abstract":"We apply pattern language methodology to describe design and integration patterns for real-world-aware and real-time solutions, i.e., software solutions that integrate business information processing with sensor and actuator manipulations of the external world. Efficient engineering of such solutions depends on the definition and reuse of components whose real-time characteristics can be specified. Other nonfunctional characteristics, such as throughput and reliability, may also be constrained and critical for correct behavior of a design element. We present a pattern language comprising a basic catalog of design patterns for component-based real-time solutions.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 2","pages":"335-350"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.472.0335","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68013566","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}
All too often, software designers ignore the fact that a running computer system is a combination of software and hardware. In this combination, hardware may play a crucial role, particularly in time-sensitive systems. In this paper, we first explore the nature and impact that platforms may have on application software and its design. Based on this analysis, a canonical model of software platforms is proposed to assist in more accurately factoring in the effects of platforms on the design of real-time and embedded software applications. Finally, we show how this model can be realized using modern model-driven design standards and methods.
{"title":"Accounting for platform effects in the design of real-time software using model-based methods","authors":"B. Selic","doi":"10.1147/sj.472.0309","DOIUrl":"https://doi.org/10.1147/sj.472.0309","url":null,"abstract":"All too often, software designers ignore the fact that a running computer system is a combination of software and hardware. In this combination, hardware may play a crucial role, particularly in time-sensitive systems. In this paper, we first explore the nature and impact that platforms may have on application software and its design. Based on this analysis, a canonical model of software platforms is proposed to assist in more accurately factoring in the effects of platforms on the design of real-time and embedded software applications. Finally, we show how this model can be realized using modern model-driven design standards and methods.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 2","pages":"309-320"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.472.0309","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68013567","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}
R. Varadan;K. Channabasavaiah;S. Simpson;K. Holley;A. Allam
Most organizations understand the need to address service-oriented architecture (SOA) governance during SOA adoption. An abundance of information is available defining SOA governance: what it is and what it is not, why it is important, and why organizational change must be addressed. Increasingly business and information technology (IT) stakeholders, executive and technical, acknowledge that SOA governance is essential for realizing the benefits of SOA adoption: building more-flexible IT architectures, improving the fusion between business and IT models, and making business processes more flexible and reusable. However, what is not clear is how an organization gets started. What works and what does not work? More importantly, what is required in SOA governance for organizations to see sustained and realized benefits? This paper describes a framework, the SOA governance model, that can be used to scope and identify what is required for effective SOA governance. Based on client experiences, we describe four approaches to getting started with SOA governance, and we describe how to use these four approaches to make shared services (services used by two or more consumers), reuse, and flexibility a reality. We also discuss lessons learned in using these four approaches.
{"title":"Increasing business flexibility and SOA adoption through effective SOA governance","authors":"R. Varadan;K. Channabasavaiah;S. Simpson;K. Holley;A. Allam","doi":"10.1147/sj.473.0473","DOIUrl":"https://doi.org/10.1147/sj.473.0473","url":null,"abstract":"Most organizations understand the need to address service-oriented architecture (SOA) governance during SOA adoption. An abundance of information is available defining SOA governance: what it is and what it is not, why it is important, and why organizational change must be addressed. Increasingly business and information technology (IT) stakeholders, executive and technical, acknowledge that SOA governance is essential for realizing the benefits of SOA adoption: building more-flexible IT architectures, improving the fusion between business and IT models, and making business processes more flexible and reusable. However, what is not clear is how an organization gets started. What works and what does not work? More importantly, what is required in SOA governance for organizations to see sustained and realized benefits? This paper describes a framework, the SOA governance model, that can be used to scope and identify what is required for effective SOA governance. Based on client experiences, we describe four approaches to getting started with SOA governance, and we describe how to use these four approaches to make shared services (services used by two or more consumers), reuse, and flexibility a reality. We also discuss lessons learned in using these four approaches.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 3","pages":"473-488"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.473.0473","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68016258","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
扫码关注我们
求助内容：
应助结果提醒方式：