Service-Oriented Design of Badger Brick - Case Study Example

Service-Oriented Design of Badger Brick Abstract Badger Bricks are the providing the best quality of bricks to its customers. As compared to its competitors in the market, this company is providing some typical features to its products. As result the bricks are long lasting and are far better in quality that its competitors. These bricks are made under special formulations and as such the packages of Badger Brick Boxes are especially made with proper protection of the bricks. However in order to give the business a better boost there is the adaptation of a service-oriented design, so that Badger Bricks can formulate its functionalities more efficiently and towards a better progressive path. The service oriented section is going to imply the supply chain under the proceedings of BPMN, BPEL4WS and WSDL. The target is to computerize the whole system in order to avoid maximum errors and for the application of fast delivery of services by the company. The process is inclusive of the evaluation proceedings for the betterment of the services as adopted by Badger Bricks. There is the analysis of the BPMN scopes that are basically highlighting on the organizational structures, functional breakdowns and data models. BPEL4WS is the category for the processes in WS-BPEL export and import functionality by using Web Service interfaces under exclusive mannerism. By the application of WSDL, a report is defined by associating a network address with a reusable binding, and a collection of ports define a service. All these are taken into consideration for the selection of a better SOA for Badger Bricks services. Contents Abstract 2 I. Introduction 4 II. Requirements Specification 5 III. Design Discussion 9 IV. Evaluation 11 V. Conclusions 14 Appendix A 16 References 17 I. Introduction The rules as followed by the SOA1 are the most appropriate ways to imply in the functioning of Service-Oriented Development of Badger Brick. These rules are reusable, has got granularity, modularity and the capacitance of composability. These are also the spaces for componentization, and interoperability. In addition to all these, there has to be the compliance to standards in both the cases of common and industry-specific categories. Thus to choose this process by Badger Bricks comes closer to the appropriateness of services as delivered. The identification of services and categorization, provisioning and delivery, and monitoring and tracking are the added beneficiary factors. This paper concentrates on the following of the specific architectural principles for design and service definition focus on specific themes that influence the intrinsic behaviour of a system and the style of its design; Service encapsulation, Service loose coupling, Service contract, Service abstraction, Service abstraction, Service reusability, Service composability, Service autonomy, Service optimization and Service discoverability. The route cause of discussion of this paper is the modelling as adopted by BPMN. The modeling in BPMN is of a small set of graphical elements. The purpose of it is to make the flow and the process of understanding for business users and developers much easier and comprehensible. There are four basic categories of elements, applicable in the process of understanding. These are flow objects that comprises of events, activities and gateways. The next is of connecting objects, by means of sequence flow, message flow and association. Swimlanes are the next in preference which works through pool and lane. Lastly there is the need of artifacts that has got data objects, group and annotation. II. Requirements Specification Badger Bricks is planning to have SOA in its functionalities. As such there are certain basic things that it has to meet to have proper assessments. There is the need of interoperability between different systems and programming languages. OASIS2 defines SOA as, A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. SOA Meta Model, The Linthicum Group, 2007 Sources - http://en.wikipedia.org/wiki/Service-oriented_architecture This provides the basis for integration between applications on different platforms through the communication protocol. The concept of messages is one such for instance. The use of messages across defined message channels decreases the complexity of the end application. It is here that it allows the developer of the application that is Badger Bricks will have the focus on the true application of functionality instead of the intricate needs a communication protocol. The second most important requirement is the desire to create a federation of resources. It needs the establishment and maintenance of data flow to a federated data warehouse. This is the way that allows new functionality developed to reference a common business format for each data element. Badger Bricks must have prolific command over both the requirements to access through SOA that is the Service –Oriented Architecture. SOA Modeling Framework, by Michael Bell. Service-Oriented Modeling. Wiley & Sons, 2008 Sources - http://en.wikipedia.org/wiki/Service-oriented_architecture The decision to adapt with the SOA has its own explanations. According to enterprise architects, SOA can help businesses respond more quickly and cost-effectively to changing market condition3. They say that this style of architecture promotes reuse at the macro-service level rather than micro-classes level. The use of it is very strong in the field of interconnection between the usages of existing IT (legacy) assets. SOA can use truly static bindings to talk to other equipment in the network. The recommendation of SOA approach on formal grounds by Badger Bricks is an intelligent step towards it business development issues. SOA are better positioned to stress the importance of well-defined, highly inter-operable interfaces4. Application of SOA can make the services run on various distributed platforms and can be accessed across networks. This can also maximize reuse of services as delivered by Badger Bricks. By means of SOA design discipline Badger Bricks can conceive to achieve the goals of increased interoperability that will give the growths in the fields of information exchange, reusability, and composability. There will be an increased federation that will gain the uniting resources & apps while maintaining their individual autonomy & self-governance within the company. There is no doubt for an increased business and technology domain alignment to Badger Bricks. Through the application of Service Oriented Architecture (SOA) for constructing complex software-intensive systems from a set of universally interconnected and interdependent building blocks, called services, Badger Bricks can have it own niche in the business. SOA makes it realise its business and IT benefits through the utilisation of an analysis and design methodology. It will create services that will ensure that it is a consistent service provider with the architectural vision & roadmap and adhere to principles of service-orientation. Badger Bricks has got the provision of a working design through SOA for an enterprise-wide implementation with detailed architecture diagrams, component descriptions, detailed requirements, design patterns, opinions about standards, patterns on regulation compliance, standards templates etc5. By means of SOA, Badger Bricks can allow larger chunks of functionality to strung together to form ad hoc applications which are built almost entirely from existing software services. This will lead to fewer requirements of the interface points for the implementation of any given set of functionality. However, larger chunks of functionality are not always granular enough to be easily reused. Thus there is severe need of choosing a proper granularity of services. With the help of the application of SOA, Badger Bricks can have the marginal cost of creating the n-th application; which is zero. It is thus all of the software required already exists to satisfy the requirements of other applications. There are the requirements of three sub-models for the implementation of the BPMN model in SOA. These are the requirements that Badger Bricks must lay emphasis. The categories are; private or the internal business processes, the abstract or the public processes collaboration or the global processes. With the application of SOA services, Badger Brick can attain beneficiary grounds for running in "safe" wrappers such as Java or .NET, which will equally manage memory allocation and reclamation. It will also allow ad hoc and late binding, and provide some degree of indeterminate data typing. With the handling of third-party software companies there is the provision for a fee. SOA as gets created in-house acquires the potential to spread costs over many customers and customer uses. It is also very active in the promotion of standardization both in and across the specific industries. III. Design Discussion In the basic scenario of SOA application there are many upcoming arguments supporting the business and management aspects. Many opt for the SOA getting outlined in various publications6. It is a kind of service with a stand-alone unit of functionality which is available only via a formally defined interface. Services also can be with the interpretations of some kind of "nano-enterprises" which are easy to produce and improve. Apart from this the services can be "mega-corporations" which are constructed as coordinated work of sub-ordinate services. BPMN, has got four basic categories of elements. In general the whole modeling in BPMN is created by the means of simple diagrams with a small set of graphical elements. It generates the business users to comprehend the flow and the process of its service deliveries. These are; Flow Objects, Connecting Objects, Swimlanes and Artifacts. The uses of BPMN, has got the private or the internal business processes that are specified to a specific organization and are the type of processes that have been generally called workflow or BPM processes. By the means of using the swimlanes a private business process can be got hold over within a single Pool. As a result, the sequence flow of the internal business process cannot cross the boundaries of the Pool. Message Flow, on the other hand can cross the Pool boundary to show the interactions between the various peripheries of the private business processes. The abstract or the public process represents the interactions between a private business process and another process or participant. The purpose of the abstract process is to show the outside world the sequence of messages as needed for the interaction with the particular business process. It is always within a Pool. Collaboration or the global processes are used in terms of broader aspects. It is chiefly for the depictions of the interactions between two or more business entities, which are in sequence of activities that represent the message exchange patterns between the entities involved. It exists within a Pool and also varies in reference to the different participant business interactions as gets shown as Lanes within the Pool. Here, each Lane represents two participants and a direction of travel between them. They might have the possession of two or more Abstract Processes interacting through Message Flow. IBM and Microsoft combined BPML and BPMS languages to have a new language called BPEL4WS. It was during the spring of 2003, that BEA Systems, IBM, Microsoft, SAP and Siebel Systems submitted BPEL4WS 1.1 to OASIS for standardization via the Web Services BPEL Technical Committee. BPEL4WS came into being as both a 1.0 and 1.1 version, however the OASIS WS-BPEL technical committee voted on 14 September 2004 to name their spec WS-BPEL 2.0 in align to BPEL with other Web Service standard naming conventions which start with WS- and accounts for the significant enhancements between BPEL4WS 1.1 and WS-BPEL 2.0. The business processes are of executable business model and the abstract model. The use of WS-BPEL is prolific as a model due to the behavior of both Executable and Abstract Processes. It is efficient in providing a language for the specification of Executable and Abstract business processes. It is thus an extended version of the Web Services interaction model. Not only that, it also enabled it to support business transactions. BPEL4WS is a language for the formal specification of business processes and business interaction protocols. The process expands the periphery of the Web Services interaction model. It leads to the circumference of business transactions. WS-BPEL thus stands for an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces. WSDL, is an XML-based language. Its target is to provide a model for describing Web services. The current version is the 2.0; which is a W3C recommendation. WSDL 1.2 was renamed WSDL 2.0 as to have a clear difference with WSDL 1.1. WSDL 2.0 specification offers a better support for web services7. There is still very less support for this particular designing method and thus is not of much popularity. It defines services as a kind of collections of network endpoints, or ports, providing an XML format for documents for this purpose. WSDL describes the public interface to the web service.WSDL is usually applied in combination with SOAP and XML Schema to provide web services over the Internet. In order to determine the functions on the server, the client can program connecting to a web service and can read the WSDL. Datatypes whichever gets used are embedded in the WSDL file in the form of XML Schema. The client can then use SOAP to actually call one of the functions listed in the WSDL. On the contrary, XLang is an extension of the WSDL. IV. Evaluation SOA implementation strictly needs a very efficient use of system resources. Along with that, there has to be the need of service maturity and performance. Enterprise Application Integration, that is EAI, is also an integral part of it. There are many web-services that are consolidated to be used under the SOA Architecture. However further investigations shows that such services are often the service encapsulation which are not properly planned to be under SOA. Services need to maintain a relationship that minimizes dependencies. The process of service loose coupling has the severe requirement of maintaining an awareness of each other. Service contract, on the other hand are the services that adhere to a communications agreement. Most of the time, these services are defined collectively by one or more service description documents. All these criteria are more relevant to BPMN. However, it is very much constrained to support only the concepts of modeling that are applicable to business processes. Organizational structures, functional breakdowns and data models are not a part of BPMN. Service abstraction is described beyond the service contract, services. It is the processing device that hides logic from the outside world. In the functionality of service reusability, logic is divided into services with the intention of promoting reuse. Service composability, on the contrary ha got the services that can be coordinated and assembled to form composite services. Service autonomy is to obtain a whole control over the logic they encapsulate. There has to be equal, high-quality services. Service discoverability is designed to be outwardly descriptive so that they can be found and assessed via available discovery mechanisms8. With an evaluating insight, Badger Bricks has to offer some specific solution to meet the market and to sustain at the same time. The offering must encompass assessment, planning, architecture design, development, implementation and governance. There is the compulsive need of SOA Strategy and Roadmap, SOA assessment and strategy formulation, SOA enabled Enterprise-wide Architecture Roadmap definition and SOA Reference Architecture development. The value proposition must be a dedicated architecture with an SOA center of excellence. This will keep track of developments in SOA, along with the skills on relevant standards and platforms. The scope has to be there for the development of best practices, methodologies, frameworks and reference models. Domain expertise is one of the basic needs for the same. As for the domain in Finance, Insurance, Manufacturing, Telecom, Retail, Energy & Utilities, Hospitality industries and e-Commerce, there is a compulsive need of excellent expertise. Badger Bricks must get definite roles and track for technical and solution with the relevant architects. Information Security & Business Intelligence expertise through dedicated practice groups is another peripheral need. There will be a regular demand for the participation in standards organizations such as OASIS. Constant evaluation and suggestion of technologies and the related platforms for implementation are of specific needs. There has to be SOA Implementation Planning, SOA program management and governance setup, architecture design. The service enabled enterprise architecture has got the task to design the process, applications, data and technology architecture along with the products and solution architecture. Badger and Bricks has also need to show its evaluative skills in architecture modernization and reverse architecting. For the prototype development, the Development has to be for early validation of approach, architecture for non-functional requirements, identification and evaluation technology choices and implementation strategy. The evaluation also gets rated on the basis of the implementation based on J2EE, .Net, Web services technology ESB, MOM, EAI, Application server products and SOA tools. At the same time the inherent complexity in Service Oriented implementations gets tested. It demands a detailed testing process. The process comprised of code and design reviews apart from unit and regression testing for processes and services with the help of integrated testing framework. These tests are done through development proceedings, from service provider and consumer views. There are also different functional units. These units are; components, services, metadata, web services, business process and composite applications. These also include automated, iterative and continuous testing of each functional unit at periodic intervals, and automated scenario based testing for business processes. V. Conclusions The SOA is a new paradigm in the distributed computing and e-business processing. The evolution s from object-oriented and component-based computing to enable building agile networks of collaborating business applications distributed within and across organizational boundaries. Opting to the same paradigm shift, Badger Bricks autonomously builds its platform. It is independent with all the computational elements that can be described, published, discovered and accessed over the Internet using standard protocols. The functionality gets elaborated as the fundamental elements for developing applications and the related solutions; services get customers’ attention and importance. It hardly depends on the specific software or hardware component that is used to implement the services. Services are the next to abstraction in the process of creating systems that would enable automation of e-businesses. This paradigm shift is changing the way the computer software use to get designed, architected, delivered, consumed, and analysed in the past. It is a way to reorganise software applications and infrastructure into a set of interacting services is usually referred to as Service-oriented Architectures (SOA). Eventually Badger Bricks needs to get formatted as per the forms of service-oriented architectures have appeared. The Web services, Grid services, Semantic Web Services, and e-Services are the most important field for the exploration. Standard protocols are the basic principle of SOA, however there is no mature methodology or prolific technique to support and elaborately analysis service-oriented architectures. Badger Bricks need to take care of the fact that all these forms of service-oriented architectures have developed different conceptual models, resulting in different methodologies for modelling and designing service-oriented architectures. Appendix A Documented Design (Full BPMN, BPEL4WS and WSDL) BPMN - The Business Process Modeling Notation (BPMN) is a standardized graphical notation for drawing business processes in a workflow. BPMN was developed by Business Process Management Initiative (BPMI), and is now being maintained by the Object Management Group since the two organizations merged in 2005. BPEL- 4Ws - BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces. EAI - Enterprise Application Integration SOA – It is a design for linking business and computational resources (principally organizations, applications and data) on demand to achieve the desired results for service consumers (which can be end users or other services). WSDL - The Web Services Description Language (WSDL, pronounced 'wiz-d?l' or spelled out, 'W-S-D-L') is an XML-based language that provides a model for describing Web services. The current version of the specification is the 2.0; version 1.1 has not been endorsed by the W3C but version 2.0 is a W3C recommendation. References 1. Bell, Michael (2008). "Introduction to Service-Oriented Modeling", Service-Oriented Modeling: Service Analysis, Design, and Architecture. Wiley & Sons, 3. 2. Bieberstein et al, Executing SOA: A Practical Guide for the Service-Oriented Architect; IBM Press books. 3. Bieberstein et al., Service-Oriented Architecture (SOA) Compass: Business Value, Planning, and Enterprise Roadmap; IBM Press books. 2005 4. Cardoso, Jorge; Sheth, Amit P. (2006). "Foreword", Semantic Web Services, Processes and Applications, SEMANTIC WEB AND BEYOND: Computing for Human Experience, Springer, xxi. 5. Channabasavaiah, Holley and Tuggle, Migrating to a service-oriented architecture, IBM DeveloperWorks, 2003 6. Christopher Koch ‘A New Blueprint for the Enterprise’, CIO Magazine, Mar 1 2005 7. Erl, Thomas (2005). Service-oriented Architecture: Concepts, Technology, and Design. Upper Saddle River: Prentice Hall PTR. 8. Martin van den berg et al. SOA for Profit, A Manager's Guide to Success with Service Oriented Architecture 9. Janner, Till ; Cañas Vaz, Miguel Angel ; Hierro, Juan J. ; Lizcano, David ; Reyes , Marcos ; Volker: Enterprise Mashup: Putting a face on next generation global SOA. WISE 2007; Nancy, France, 2007.- URL http://www.alexandria.unisg.ch/Publikationen/41338 [accessed on 2008-04-25] 10. Joe McKendrick ‘Anti-SOA 2.0 petition nears 400’, ZDNet.com, June, 2006 11. Spewak, Steven; Hill, Steven C. Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology. Read More