engleski

Service-Oriented Architectures Maturity Models

Service oriented architecture (SOA) represents a new evolutional spiral in the software- applications development and in the evaluation of the information systems’ concept. SOA is based on Web services, so called "granulated distributed program entities" that independently coexist in interaction with other programs and services. They can revile it and be used under special conditions determined by service publisher. Those entities are connected in complete software solution in the case of SOA. SOA represents an extraordinary challenge at scientific, practical and economical level. That is a reason why SOA represents the topic of many different researches originating from different sources. SOA represents a framework for business processes and information and communication technology integration in form of components (services) that are reusable and interoperable, and that satisfy the needs and demands of dynamical business processes. (Vrček, Gerić, Kermek, IIS, 2006.) [7.] Until present different researches have been done related to SOA, and some technical standards like: Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), Universal Discovery Description and Integration (UDDI) were developed. Important program's equipment manufacturers (like IBM, Oracle and Microsoft) are working intensively and are investing in SOA and necessary standards development. From published development strategies it is clearly that SOA represents an essence of their future development. So, it is clearly that SOA will be developed in domain of practice, but in the scientific researches as well, because it opens a set of questions that can not be resolved just by technical standardization. Besides the basic infrastructure standards, SOA has a significant influence on business processes, and because of that, standardized and not-standardized specifications, like XML Process Definition Language (XPDL), Web Services Flow Language (WSFL), Business Process Modelling Language (BPML), Business Process Execution Language for Web Service (BPEL4WS), Web Services Choreography Description Language (WS-CDL) are developed in this domain. Unified Modelling Language (UML) gave also a strong motivation for SOA development, and in the last few years necessary UML profiles were developed. Service oriented security aspect is resolved as well – different technological standards and protocols have been developed, e.g Secure Sockets Layer (SSL), Security Assertion Markup Language (SAML), Web Services Security (WSS), eXtensible Access Control Markup Language (XACML), XML signature, XML encryption. Based on these facts, we may conclude that the implementation and usage of service oriented architectures is mostly organizational, and not a technical issue [6.]. The use of service oriented architecture from legislative point of view is mostly defined by national laws, protocols and rules. Relationship between the service provider and service user is usually defined by service level agreements that are unique for each implementation and usage of service oriented architecture. The domain that is still not understood completely is the influence that service oriented architectures has on business process reengineering and organizational prerequisites that should be fulfilled as a presumption for successful SOA implementation. We believe that the main reason for this is the fact that SOA is still not understood and observed as the most complicated form of information system. It is not easy to define a unique set of criteria, or prerequisites that organization has to fulfil in order to successfully implement SOA. The variety of organizations and their business environment is simply too large for identifying a unified set of such criteria. Because of this the ability for organization to adopt service oriented architecture can be estimated by service oriented architectures maturity models (SOAMM). This bring us to the goal of this paper – to find out if different SOAMM's, and their maturity levels are compatible and equivalent ; how do different SOAMM correlate, and do they define similar or the same levels of SOA implementation?

SOA; IS; maturity; CMMI

nije evidentirano