Distribute Service Components into Multi-level Architecture from Legacy Applications

Enterprise IT Architecture Greenfield Design Combining IEC 62264 and TOGAF by Example of Battery Manufacturing

With the advancements in technology, information systems are continually increasing in size and complexity. More and more businesses are looking to these systems to provide them with greater business efficiencies and services through consolidation and integration. Businesses are also using information systems to provide governance and directions by enabling quality decision support through system information analysis and related capabilities. The ability to successfully deliver these complex information systems is creating greater challenges for businesses and system developers. As a result, businesses are turning to a variety of enterprise architectures for policies and technical choices to achieve business standardization and integration requirements of the firm’s operating model. It is particularly important for asset management, since the operational technologies utilised in asset lifecycle management can also be classed as information systems. Technology management for asset management, thus, calls for an all encompassing architecture that caters for the individual needs of operational and information technologies, as well as that of their integration. There are a number of recognised architecture frameworks available today, many of which providing similar principles and strategies. However, all of these frameworks are unique in regards to how their frameworks are used and implemented. This paper develops the case for enterprise IT architectures in asset management and provides a comparison of architecture frameworks in relation to the strengths, weaknesses, opportunities and threats. The paper focuses on three recognised architecture frameworks and provides recommendations for additional considerations of each with reference to operational and information technologies for asset lifecycle management.

This research aims to create an information technology architecture that will automate the company's business processes that focus on customer relationship management systems using a case study from PT Indorama. Enterprise IT Architecture must complement the vision and organizational goals and match the needs of business processes. As a result, creating IT blueprints is critical for businesses to make the future development of information systems easier. TOGAF ADM was used to create the IT architecture for this investigation. To integrate current system applications, Customer Relationship Management (CRM) based applications are used to complete various business tasks that are not currently enabled by the current application system. This research results in the design of an IT architecture to support the company's strategic plans through business process automation and answer predetermined challenges. Keywords” Enterprise Architecture, Customer Relationship Management, TOGAF ADM

Simulation modeling can be a key enabler and method for mitigating risk within the Department of Defense?s Enterprise Transformation, especially in the area of the IT systems that enable transformation. This paper provides a brief overview of the Air Force?s approach to enterprise architecture development and demonstrates how modeling and simulation (M&S) can be used to optimize Enterprise IT architecture design to meet the needs of operational end users.

The current approach to the design, maintenance, and governance of service-oriented architecture (SOA) solutions has focused primarily on flow-driven assembly and orchestration of reusable service components. The practical application of this approach in creating industry solutions has been limited, because flow-driven assembly and orchestration models are too rigid and static to accommodate complex, real-world business processes. Furthermore, the approach assumes a rich, easily configured library of reusable service components when in fact the development, maintenance, and governance of these libraries is difficult. An alternative approach pioneered by the IBM Research Division, model-driven business transformation (MDBT), uses a model-driven software synthesis technology to automatically generate production-quality business service components from high-level business process models. In this paper, we present the business entity life cycle analysis (BELA) technique for MDBT-based SOA solution realization and its integration into service-oriented modeling and architecture (SOMA), the end-to-end method from IBM for SOA application and solution development. BELA shifts the process-modeling paradigm from one that is centered on activities to one that is centered on entities. BELA teams process subject-matter experts with IT and data architects to identify and specify business entities and decompose business processes. Supporting synthesis tools then automatically generate the interacting business entity service components and their associated data stores and service interface definitions. We use a large-scale project as an example demonstrating the benefits of this innovation, which include an estimated 40 percent project cost reduction and an estimated 20 percent reduction in cycle time when compared with conventional SOA approaches.

Understanding Service-Oriented Architecture (SOA): A systematic literature review and directions for further investigation

Answers to your most pressing SOA development questions How do we start with service modeling? How do we analyze services for better reusability? Who should be involved? How do we create the best architecture model for our organization? must-read for all enterprise leaders gives you all the answers and tools needed to develop a sound service-oriented architecture in your organization. Praise for Service-Oriented Modeling Service Analysis, Design, and Architecture Bell has done it again with a book that will be remembered as a key facilitator of the global shift to Service-Oriented Architecture. . . . With this book, Michael Bell provides that foundation and more-an essential bible for the next generation of enterprise IT. -Eric Pulier, Executive Chairman, SOA Software Bell's insightful book provides common language and techniques for business and technology organizations to take advantage of the SOA paradigm. By focusing modeling techniques on the business problem, Bell provides a way for professionals to work throughout the life cycle to create reusable and enduring services. -Mike Zbranak, CIO, Chase Card Services This book will become an imperative business and technology service-oriented modeling recipe for any manager, architect, modeler, analyst, and developer in today's software development -Jeff Schneider, CEO, MomentumSI 'Innovative' and 'groundbreaking' are words that best describe Michael Bell's Service-Oriented Modeling. It depicts a true service modeling approach that elegantly closes a clear and critical service modeling gap in the SOA industry. holistic book ties these concepts together using real-world examples across a service life cycle that transitions services from ideas and concepts into production assets that deliver business value. A must-read for business and technical SOA practitioners. -Eric A. Marks, CEO, AgilePath Corporation As hot as SOA is today, many business and technology professionals still find it challenging to mind the gap between their disparate methodologies and objectives. Herein Michael Bell speaks clearly to both camps in straightforward language, outlining disciplines each can use to communicate effectively and advance the realization of corporate aims. book is a bible for all who seek to drive business/technology into the future. -Mark Edward Goodrich, Director, Investing Product Management, Reuters Media This book takes senior IT architects and systems designers into the depths of modeling for SOA, with a fresh new perspective on tools, terminology, and how to turn the theory into practice. His full life-cycle approach balances process, control, and accountability to align all the participants in the delivery pipeline-clearing the road for successful SOA business solutions. -Phil Gilligan, Chief Technology Officer, EBS

Legacy systems are valuable assets for organisations. They continuously evolve with new emerged technologies in rapidly changing business environment. Web services, together with service-oriented architectures, facilitate legacy system webification and evolution in service-oriented computing environment. Traditional approaches to integrate legacy systems with Web service technology are wrapping a legacy system as a black-box without adequate system understanding. In this paper, we proposed a reengineering approach which applies an improved agglomerative hierarchical clustering algorithm to restructure legacy code and to facilitate legacy code extraction for Web service construction. It supports service identification and service packaging and archives legacy system migration into service-oriented architectures by providing functional legacy code as Web services.

The service-oriented architecture (SOA) enables organizations to cooperate in expanding their businesses and creating new opportunities by connecting multiple participant’s resources. However, some organizations are not yet ready to integrate with this inter-enterprise SOA environment due to their internal traditional IT-based systems. So, to face the challenge of market and system expansion, they first have to enable their systems for collaboration. This paper explores and analyses SOA implementation aspects in the small and medium enterprise (SME) communities by using systematic literature review method. This work presents facts regarding the state of SME community, i.e. the attributes, existing IT architectures, and the adopted collaboration frameworks. Virtual organization (VO) with its variants is a prominent model to establish in the ICT-based SME community. The centralized system is the dominant architectural structure types proposed due to the natural characteristics of SOA and SMEs.

We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.

Recent research suggests that a strong link exists between business innovation and service oriented IT architectures: modern IT architecture enables business to quickly create new services. However, the relationship between IT capabilities and business performance is not always straightforward. How does SOA support fast innovation in practice, and under which conditions is it effective? In this paper, the authors investigate these issues and ask: How can a SOA architecture like the Enterprise Service Bus support business innovation? This paper investigates this question through a case study at an airline company. Analyzing the relationship between innovation and IT architecture in the company over time, the authors offer the following conclusion: ESB gives strong support to business innovation, under two conditions. First, the implementation of ESB has to be comprehensive, that is, it should include the core processes of the business. Second, the top management (and partners) need to understand the principles of ESB.

Service Oriented Architecture (SOA) is a framework for integrating business processes and supporting IT infrastructure as secure, standardized components-services-that can be reused and combined to address changing business priorities. Services are the building blocks of SOA and new applications can be constructed through consuming these services and orchestrating services within a business process. In SOA, services map to the business functions that are identified during business process analysis. Upon a successful implementation of SOA, the enterprise gain benefit by reducing development time, utilizing flexible and responsive application structure, and following dynamic connectivity of application logics between business partners. This paper presents SOA reference architecture blueprint as the building blocks of SOA which is services, service components and flows that together support enterprise business processes and the business goals.Keywords: Service Oriented Architecture, SOA Reference Architecture

Cloud computing has been envisioned as next-generation architecture of IT enterprise.Cloud computing is the internet based model which delivers computing services on demand.Cloud storage moves the users data to large data centers, which are remotely located and on which user does not have any control.Apart having more benefits, this unique feature of the cloud also poses many new security challenges which need to be clearly understood and resolved.The important concerns that need to be addressed in cloud computing is to assure the integrity of data i.e. correctness of his data in the cloud.In this paper we provide a scheme which gives a proof of data integrity in the cloud which the customer can employ to check the correctness of his data in the cloud.This proof can be done by both the cloud and the customer and can be incorporated in the Service level agreement (SLA).Here we are encrypting the hash values and providing the more security.This scheme ensures that the storage at the client side is minimal which will be beneficial for thin clients.Here the computational time is minimized by using integrity and encryption methodology on the data in cloud .It should be noted that this scheme applies only to archive storage data.

Cloud computing has been envisioned as the next-generation architecture of IT enterprise. However the security problem of Cloud computing hinder itself from large-scale application. One major challenge is to verify the integrity of data at untrusted server under the condition of supporting public auditability and dynamic data operation. This paper analyzed the problems of existing schemes, introduced commutative hash into Merkle hash tree, aggregated basic block into subblock and block, constructed a kind of hierarchical Merkle hash tree by using the concept of hierarchical structure in granular computing and proposed an improved scheme to offer effective, multi-granular dynamic operation. We analyzed the efficiency and security of the protocol. The analysis result showed that the protocol is efficient and security.

It seems that the mention of SOA (service-oriented architecture) alone is enough to release the funds needed for IT departments to modernise mainframes. But should departments use SOA to drive traditional legacy mainframe upgrades under the guise of making systems SOA compliant? The IT industry has been at a loss when it comes to legacy mainframe systems. 'To modernise, or not to modernise?' has been the unanswered question of recent years. Legacy mainframe managed systems and associated maintenance costs are a considerable drain on IT department budgets. The costs are high because of interactions between the obsolete platforms and non-mainstream languages on which these legacy systems are built. Adoption of SOA has allowed IT departments to sneak in funding for modernisation programs. The underlying question to this trend is whether SOA should be used as a tool for driving forwards traditional legacy mainframe modernisation programmes under the guise of making systems SOA compliant? It appears the SOA name alone can release the funds required for IT departments to modernise their mainframes. What problem is a little white lie if it gets the job done?