Web services strategy

Thesis (S.M.M.O.T.)--Massachusetts Institute of Technology, Sloan School of Management, Management of Technology Program, 2003.June 2003.Includes bibliographical references (p. 116-123).This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.Everything is connected to everything. El Aleph (1945), by Jorge Luis Borges[1] This thesis addresses the need to simplify and streamline web service network infrastructure and to identify business models that best leverage Web services technology and industry dynamics to generate positive business results. Web services have evolved from the simple page-display protocol of their origin and now reach beyond the links that simply updated web data dynamically from corporate databases, to where systems can automatically transact. These Web services represent a series of network business technology standards and capabilities that irrevocably change the way in which businesses will do business. In fact, every business today is a networked business and has opportunities to grow using Web services. This study focuses on the implementation challenges in the financial services market, specifically the On Line Transaction Processing (OLTP) sector where legacy mainframes interface with multiple tiers of distribution through proprietary EDI links. The OLTP industry operates under stringent regulatory requirements for availability and audit-ability of not only who performed what transaction, but who had access to the information about the information. In this environment organizational demands on network infrastructure including hardware, software and personnel are changing radically, while concurrently Information Technology (IT) budgets are under pressure. The strategic choices for deploying web services in this environment may contain lessons for other industries where cost effective large scale processing, high availability, security, manageability and Intellectual Property Rights (IPR) are paramount concerns. In this paper we use a systems dynamics model to simulate the impact of market changes on the adoption of innovative technologies and their commoditization on the industry value chain, with the aim of identifying business models and network topologies which best support the growth of an Open Systems network business. From the results of the simulation we will derive strategic recommendations for networked business models and web services integration strategies to meet Line Of Business (LOB) objectives.by Stephen B. Miles.S.M.M.O.T

Factors Affecting Success in Migration of Legacy Systems to Service-Oriented Architecture (SOA) - Shared Experiences from Five Case Companies

Background: The term ‘legacy systems’ refers to existing Information Systems that have been deployed in the past and have been running critical business processes within an enterprise in its current IT architecture. Based on their important role, legacy systems are considered the heart of a company’s operating enterprise system and therefore are of significant business value to the company. Therefore IT architects have not neglected the value these existing assets can bring to the adoption of service-oriented architecture and have been studying different methods and factors to migrate the legacy investments into the new architecture and take advantage of their business value. However, not in all cases has the process of migrating legacy systems into SOA been successful. In fact, the level of success in adapting the legacy systems in a company with the new service-oriented architecture is dependant on some factors which vary from one legacy infrastructure and series of business processes to another. There is no quick fix to transforming the existing legacy assets which highlights the fact that considering the right factors to reach legacy system migration success in a specific company is of key value. Therefore, we hereby studied the factors influencing success of migrating these legacy investments into SOA in five different companies which include a Large European Bank, SAS, a Large globally-known Company in Sweden, Sandvik AB and a large UK Bank. Purpose: To identify factors affecting successful migration of legacy systems into SOA in five companies. Method: The main adopted research method in this study has been interviews for different case studies. Through separate interviews, critical success factors of migrating legacy systems into SOA have been collected and identified in each case. Finally collected results are analyzed and presented as the recognized factors affecting successful migration of legacy assets into SOA in five different enterprises with their own Information System infrastructures. Conclusion: The success factors identified include potential of legacy systems for being migrated, strategy of migration, SOA governance, the business process of the company, budgeting and resources, legacy architecture, close monitoring, dependence on commercial products, information architecture, testing and technical skills of the personnel. Out of all these factors, only three factors have been applied and mentioned by all the case companies in this study, which are the potential of legacy systems for being migrated into SOA, strategy of migration and SOA Governance

BUILDING RELIABLE AND ROBUST SERVICE-BASED SYSTEMS FOR AUTOMATED BUSINESS PROCESSES

An exciting trend in enterprise computing lies in the integration of applications across an organisation and even between organisations. This allows the provision of services by automated business processes that coordinate business activity among several collaborating organisations. The best successes in this type of integrated distributed system come through use of Web Services and Service-based Architecture, which allow interoperation between applications through open standards based on XML and SOAP. But still, there are unresolved issues when developers seek to build a reliable and robust system. An important goal for the designers of a loosely coupled distributed system is to maintain consistency for each long running business process in the presence of failures and concurrent activities. Our approach to assist the developers in this domain is to guide the developers with the key principles they must consider, and to provide programming models and protocols, which make it easier to detect and avoid consistency faults in service-based system. We start by defining a realistic e-procurement scenario to illustrate the common problems faced by the developers which prevent them from building a reliable and robust system. These problems make it hard to maintain the consistency of the data and state during the execution of a business process in the occurrence of failures and interference from concurrent activities. Through the analysis of the common problems, we identify key principles the developers must consider to avoid producing the common problems. Then based on the key principles, we provide a framework called GAT in the orchestration infrastructure. GAT allows developers to express all the necessary processing to handle deviations including those due to failures and concurrent activities. We discuss the GAT framework in detail with its structure and key features. Using an example taken from part of the e-procurement case study, we illustrate how developers can use the framework to design their business requirements. We also discuss how key features of the new framework help the developers to avoid producing consistency faults. We illustrate how systems based on our framework can be built using today’s proven technology. Finally, we provide a unified isolation mechanism called Promises that is not only applicable to our GAT framework, but also to any applications that run in the service-based world. We discuss the concept, how it works, and how it defines a protocol. We also provide a list of potential implementation techniques. Using some of the implementation techniques we mention, we provide a proof-of-concept prototype system

The long sale: future-setting strategies for enterprise technologies

Markets for enterprise technologies are complex socio-technical arrangements where the nature of the goods or services available for exchange is frequently uncertain. Early offerings may appear obfuscated, in part ontologically due to contested boundary definitions, and in part through the intentional and unintentional work of sales actors. While it is difficult for actors to know what they are transacting with certainty before an exchange occurs, expectations are partly shaped in practice during a protracted and multipartite sales process. In the early stages, such technologies may be nothing more than ‘slideware’ or ‘vapourware’, with the promise of the offering yet to be realised. Suppliers are therefore faced with the challenge of how to bring an immature product to the serious attention of users. One such example which has dominated the ICT landscape in recent times is ‘cloud computing’, a vision for on-demand utility computing which on the one hand promised computing resources accessible like an infrastructure commodity such as electricity, but on the other declared by some as simply everything we already do in computing today. This thesis offers a longitudinal case study of the way in which a major ICT supplier, IBM, attempted to galvanise the market for its cloud-enabled products amongst user organisations. In doing so the supplier had the challenge of selling a model of outsourced services to organisations with deeply embedded ICT systems around which the sales processes had to be made to fit. The research centers on four empirical chapters which bring together contextual narratives of cloud computing, findings related to the sales work users do, the sales challenges encountered during crisis management, and the shadow activity that occurs during professional user groups and conferences. The discussion explains how actors work together to construct an imagined community of technology artefacts and practices that extends our understanding of how technology constituencies hold together without overt forms of control. The study draws together a number of years of fieldwork investigating user group events in the corporate ICT arena and a major UK customer implementation. These are explored through a mobile ethnography under the banner of a Biography of Artefacts and Practices (Pollock & Williams, 2008) making use of participant observation, and selective interviewing, with a particular focus on naturally occurring data

A Reference Architecture for Service Lifecycle Management – Construction and Application to Designing and Analyzing IT Support

Service-orientation and the underlying concept of service-oriented architectures are a means to successfully address the need for flexibility and interoperability of software applications, which in turn leads to improved IT support of business processes. With a growing level of diffusion, sophistication and maturity, the number of services and interdependencies is gradually rising. This increasingly requires companies to implement a systematic management of services along their entire lifecycle. Service lifecycle management (SLM), i.e., the management of services from the initiating idea to their disposal, is becoming a crucial success factor. Not surprisingly, the academic and practice communities increasingly postulate comprehensive IT support for SLM to counteract the inherent complexity. The topic is still in its infancy, with no comprehensive models available that help evaluating and designing IT support in SLM. This thesis presents a reference architecture for SLM and applies it to the evaluation and designing of SLM IT support in companies. The artifact, which largely resulted from consortium research efforts, draws from an extensive analysis of existing SLM applications, case studies, focus group discussions, bilateral interviews and existing literature. Formal procedure models and a configuration terminology allow adapting and applying the reference architecture to a company’s individual setting. Corresponding usage examples prove its applicability and demonstrate the arising benefits within various SLM IT support design and evaluation tasks. A statistical analysis of the knowledge embodied within the reference data leads to novel, highly significant findings. For example, contemporary standard applications do not yet emphasize the lifecycle concept but rather tend to focus on small parts of the lifecycle, especially on service operation. This forces user companies either into a best-of-breed or a custom-development strategy if they are to implement integrated IT support for their SLM activities. SLM software vendors and internal software development units need to undergo a paradigm shift in order to better reflect the numerous interdependencies and increasing intertwining within services’ lifecycles. The SLM architecture is a first step towards achieving this goal.:Content Overview List of Figures....................................................................................... xi List of Tables ...................................................................................... xiv List of Abbreviations.......................................................................xviii 1 Introduction .................................................................................... 1 2 Foundations ................................................................................... 13 3 Architecture Structure and Strategy Layer .............................. 57 4 Process Layer ................................................................................ 75 5 Information Systems Layer ....................................................... 103 6 Architecture Application and Extension ................................. 137 7 Results, Evaluation and Outlook .............................................. 195 Appendix ..........................................................................................203 References .......................................................................................... 463 Curriculum Vitae.............................................................................. 498 Bibliographic Data............................................................................ 49

Air Traffic Management Abbreviation Compendium

As in all fields of work, an unmanageable number of abbreviations are used today in aviation for terms, definitions, commands, standards and technical descriptions. This applies in general to the areas of aeronautical communication, navigation and surveillance, cockpit and air traffic control working positions, passenger and cargo transport, and all other areas of flight planning, organization and guidance. In addition, many abbreviations are used more than once or have different meanings in different languages. In order to obtain an overview of the most common abbreviations used in air traffic management, organizations like EUROCONTROL, FAA, DWD and DLR have published lists of abbreviations in the past, which have also been enclosed in this document. In addition, abbreviations from some larger international projects related to aviation have been included to provide users with a directory as complete as possible. This means that the second edition of the Air Traffic Management Abbreviation Compendium includes now around 16,500 abbreviations and acronyms from the field of aviation

Software test and evaluation study phase I and II : survey and analysis

Issued as Final report, Project no. G-36-661 (continues G-36-636; includes A-2568