The Four Primary Design Principles Of Service Oriented Architecture

1009 Words5 Pages
One of the four primary design principles of service oriented architecture is service reusability is one of the design principles that are most commonly incorporated within the service model process. The text defines service reusability as being responsible for defining the inventory blueprint, grouping logic within the contexts of proposed agnostic service candidates and refining functionality (Thomas, 2008). The goals of a traditional system does not differ much from this model, because they both focus on identifying and refining functionality. The next most commonly incorporated design principle is service autonomy. The service autonomy process involves gathering and analyzing information about the system in order to prevent future mishaps.…show more content…
(2008). SOA Principles of Service Design, (1st edition). Boston, MA; Prentice Hall. Upon reviewing all of the service reusability is the stage of service oriented design that most affect the granularity that compose the software solution. I came to this conclusion, because reusability of a service grants it to have endless potential. Not only can a service be reused, it can perform different tasks. Service granularity is based on the granularity of the functionality of the service’s scope. The granularity of a service is reflected by the quantity of potential logic it can encapsulate (Thomas, 2008). Logic solutions that encapsulate a lot of potential can be beneficial in a lot of ways. Increased resources and a decrease in cost are two of the benefits of having logic solutions with a lot of potential. Not only does service reusability relate most to service granularity, it also cut IT cost and increase long-term repeated return on investment. This also allows for service resources to be used in other places that will increase functionality in relation to agnostic service context. Through reuse and performing various functions, services can increase the potential of what they can do.…show more content…
I worked for a company named Fleet Management Expansion, which was responsible for maintaining equipment readiness, data management systems and reporting. One of the issues that we dealt with was linking our host systems to our client systems in real-time. The equipment that we had was separated by different unit ownership. Sometimes the equipment was located in separated areas from the main location. In these instances, we had to set up client data management systems that displayed in real-time with the host systems. Setting this up in a top-down sequence would not be feasible for this operation, because the main focus is not on the subsystem (client), the host has to be set up properly before the focus could lean toward the client. If the client system had to be reverse engineered in order to setup the host system, then the top-down model would be sufficient. In our case we used the bottom-up model to set up our data management systems. We made sure that all the details were covered at the host level first and then moved on to the client. We made sure that the time zone was in sync, oracle was set up properly in order for the systems to interface and the data that was in the systems was input correctly. Afterwards, we made a backup of the host system and loaded it on the client system; allowing changes to be made on both ends in real
Get Access