The concept of Service Component Architecture (SCA) represents, compared to the other standard technologies, a different view to the term information system or application, especially to their design and implementation. Service Component Architecture (SCA) is based on the principles of a Service Oriented Architecture (SOA), which extends in some respects. The information system is viewed as a collection of individual services that independently implements a specific activity and which are interconnected. Therefore they create the desired overall functionality. One of the objectives of the Service Component Architecture (SCA) is to allow both the usage of the new services realized, for example, by using web services, or other modern technologies, and the reuse of the functionality of older systems that can be created in various, currently scarcely used programming languages, etc. The primary objective of the Service Component Architecture (SCA) is a separation of design and implementation of the application and communication (i.e. messaging, security, etc.). There is another aspect to increase the possibility of re-usability of individual components. As with the Service Oriented Architecture (SOA), the aim is to create a loose coupling among the services, instead of a tight coupling, which are often produced by other approaches or technologies. Another approaches, see Informatics.
SCA (Service Component Architecture)
What is
SCA (Service Component Architecture)
The concept of Service Component Architecture (SCA) represents, comparing to other standard technologies, a different view to the term information system or application, especially to their design and implementation. Service Component Architecture (SCA) is based on the principles of a Service Oriented Architecture (SOA), which extends in some respects.
Related terms and methods:
Related management field:
Last update: 27.07.2016
Comments
You cannot contribute to the discussion because it is locked