Once the business IT systems are rough under the Service-Oriented Architecture umbrella, any one component can be modified, to repair a software defect in a calculation, for example, and the other systems would still be able to interact with the modified component. The largest advantage of Service-oriented Architecture is the cost savings. In the case of this company, different software vendors developed the stovepipe inventory systems and accounting systems.
The company has an inefficient method of connecting the two systems, which breaks down at least monthly, causing a loss of revenue. The inventory system and accounting system could be interconnected, allowing bi-directional data flow with minimal disruptions by way of instituting a Service-Oriented Architecture. There would be no reason to replace software that continues to provide an effective service to the business; instead, a Service-Oriented Architecture can effectively prolong the system’s effective life until the company desires to replace the system.
Show how the architecture has positive (or negative) impact to the business objectives Service- Oriented Architecture positive impacts include reduction of costs. According to Sweeney, most businesses do not realize how much they send on duplication of effort and complexity of their IT systems (Sweeney, 2010, p. 20). The overall impact of committing to a Service-Oriented Architecture is a reduction in complexity and duplication of IT systems; additionally, it allows reuse of existing software systems, possibly extending the software’s life cycle (Sweeney, 2010, up. 1-22). Service-Oriented Architecture negative impacts include performance and improper Service-Oriented Architecture compliance. Performance could be impacted when using web services; redesigning some services may be desired (Masticate, 2007). Regarding the security aspect of Service-Oriented Architecture, the desire to have an interface with the business supplier company requires some element of security.
To simplify and maintain good system performance, Rosen, Libidinously, Smith, & Balder recommended to not over-engineer the security solution; instead, apply the same security to each client and service (Rosen, Libidinously, Smith, & Balder, 2008, up. 446-447). Highlight potential risks. The primary Service-Oriented Architecture risk is developing a poor architecture. An additional risk is poor coordination between the company and the company’s supplier with whom the company needs to interact; this could cause the structure to be reworked at additional cost.
Finally, trying to integrate the Service-Oriented Architecture in a single effort is not recommended and may leave many business leaders to dismiss the effort immediately (Hurwitz, Blood, Kaufman, & Helper, 2009, p. 37). Highlight your mitigation strategies. To mitigate the poor Service-Oriented Architecture risk, the company must create a Service-Oriented Architecture strategy. This involves the entire company (and specifically business leadership) to understand the effort and how a Service- Oriented Architecture will benefit the company overall and each business unit.
A successful Service-Oriented Architecture, according to Lanthanum, can be described by the following nine elements: improved efficiency, lower administrative costs, higher business process visibility, reduction in manual steps, service-level effectiveness increase, faster process implementation, faster time to market, reduced project cycles, and overall reduction in software costs (Lanthanum, 2009). Once business leaders embrace the positive effects of a Service-Oriented Architecture, the company could create and implement a Service-Oriented Architecture.
Coordination between the company and the supplier is paramount. If the supplier were unable to support the Service-Oriented Architecture, then the company would not benefit from that element of the Service-Relented Architecture. The strategy to mitigate this risk includes demonstrating the positive aspect of a Service-Oriented Architecture; provide an incentive to the supplier to work with the company to support the Service-Oriented Architecture; ND search for a supplier that will support a Service-Oriented Architecture.
While the last step may appear draconian, the Service-oriented Architecture discovered cost savings is expected to be extensive. An additional strategy one may try is to inform the supplier of your intent to find a supplier who is willing to support the company’s Service-Oriented Architecture effort and see if the supplier is pressured to change their position. A Service-oriented Architecture effort must be started by a good design and management agreement. To gain business leadership support, the first phase would be a high visibility element, such as the company inventory and company accounting systems.