A Formal Model of Services
In particular, given the size and distribution of the systems we envision, it is
practically impossible to describe completely all the behaviors of all the components
involved. Instead, we only have a partial view of the requirements on the overall system.
The earlier approaches to structuring complex systems mentioned before do not support
working with partial specifications. Therefore, to address the complexities of both
today's and future systems, we well need to better understand the interplay between
partial and complete specifications. In this article, we develop a theory for services and
components representing partial and complete information about system structure and
behavior, respectively.
3.1.1 Streams
Timed streams are used to represent histories of communications of data messages in a time
frame.
The syntactic interface indicates which types of messages can be exchanged, but tells
nothing in particular about the interface behavior.
A service provides a partial view onto a component.
본 논문은 15page까지만 보았다.(수식이 많고 잘 이해가 안 된다.) 핵심은 다음과 같다. component와 service의 차이는 totality와 partialiy의 구분으로 설명될 수 있다. 즉, 전자의 경우에는 all behavior를 고려하게 되지만 후자의 경우에는 그러하지 않다. 즉, input의 범위에 제한적인 조건이 따라가는 것이다. 그리고 이러한 특성을 반영하여 component, service기반의 formal model을 설명한다.