Hi All I am entirely with Steve in this post on the importance of contracts (Contracts really matter - without them everything becomes tightly bound no matter what people claim about "dynamism").
However, I wonder whether the concept of "contract" that we have (based on stating pre- and post-conditions) is sufficiently general and flexible to handle all the situations we face in defining and building service software. I have been thinking about this for a while, specifically in the context of extended service collaborations, and written a short paper (available at http://www.metamaxim.com/download/documents/contracts.pdf ). I would be interested to know what others on this list think about this -- in particular whether there is any experience of devising or using other kinds of software behaviour contract. Rgds Ashley > > > You can read this at: > http://service-architecture.blogspot.com/2010/06/rest-has-put-enterprise-it-back-five.html > > Gervas > > Reply to sender | Reply to > group | Reply via web post | > Start a New Topic > Messages in this topic (1) > Recent Activity: > New Members 4 > > Visit Your Group > MARKETPLACE > Stay on top of your group activity without leaving the page you're on - > Get the Yahoo! Toolbar now.
