Sobre

Graffiti \Graf*fi"ti\, s.m.
desenhos ou palavras feitos
em locais públicos. 
Aqui eles têm a intenção de 
provocar papos sobre TI e afins.

O Graffiti mudou!

Visite a nova versão em pfvasconcellos.net

Há tempos não falo nada sobre meu 'tema do ano', né? Saca aquela sensação de 'saco-cheio' quando vc mergulha muito num tema? Então.. Mas isso não indica de forma alguma que se tratava de 'fogo de palha'. Longe disso. Mas confesso uma bela 'travada' na conclusão do artigo. Parece que aguardo a queda d'uma ficha que falta.

Enquanto ela não cai, me resta acompanhar evoluções e discussões sobre SOA. Uma muito interessante pingou na última edição do ZAPFlash. Saca só um trechinho:

... " While all software projects must naturally start with the requirements of the business, with SOA, the primary business requirement is the “meta-requirement” of implementing an architecture in a way that responds to unpredictable change—in essence, implementing an agile architecture. Nevertheless, the architect must first be aware of specific business requirements on IT, for example, some new business capabilities, new products, new business relationships, or new budgetary constraints. Regardless of these business needs, however, the Service-oriented architect must realize that these requirements are never the end of the story, but rather the beginning.

SOA projects, after all, are not your typical IT projects. Typical IT projects begin with a fixed set of business requirements, and the architect or someone else on the team sits down with the business stakeholders (the people with the requirements) and distill a set of use cases for those requirements. Use cases for SOA projects, however, are a different kettle of fish entirely. Instead of laying out specific “I want the system to behave this way” kinds of requirements, SOA use cases describe how various users may wish to leverage the Services that will be at their disposal—Services the architect must then identify, design, and schedule. And so, rather than assuming a set of fixed requirements ahead of time, Service-oriented architects must expect requirements to change. The resulting solution must then not just meet the transitory requirements of the business, but must also be able to meet future requirements as necessary."


...

0 responses to "SOA :: Diferente de 'Cabo a Rabo'"

Leave a Reply