Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>So the question is: <a href="http://www.infoq.com/articles/SOA-Agile-Friends-Or-Foes" rel="noreferrer">Are SOA and Agile friends or foes?</a></h2> <p>In summary, Service Oriented Architecture (SOA) and Agile software development both help companies become more flexible and better align business and IT. As a result, many have noted that SOA and Agile seem like a natural fit.</p> <p><i>SOA introduces a controlled environment in which changes are accommodated in support of Agile processes, where quality, efficiency and productivity are increased through the appliance of design patterns, standards and governance procedures. Design patterns like service reusability, composability and abstraction, to cite a few, are leveraged to provide flexible and adaptable ecosystems. Agile methods also enable the lifecycle to be more incremental and interactive, allowing the business to get/give faster feedback from/to IT. They both support the continuous business-IT cycle that is needed to allow businesses to set up strategies aligned with IT. --<a href="http://www.zdnet.com/blog/service-oriented/what-does-soa-bring-to-agile-or-agile-to-soa/8041" rel="noreferrer">What does SOA brings to Agile? Or Agile to SOA?</a></i></p> <h2>Explanation</h2> <p>As you can see in the <a href="http://www.soa-manifesto.org/" rel="noreferrer">SOA Manifesto 2009</a> and <a href="http://www.agilemanifesto.org/" rel="noreferrer">Agile Manifesto 2001</a>, there are plenty of common values, such as Agility, Flexibility, To see changes as oportunities and a lot more. Some see SOA as an evolution of Agile, due to Cloud Computing [2008], Web Services [2004] and so on. These people, who have written the manifestos, were unhappy with <a href="http://en.wikipedia.org/wiki/Waterfall_model" rel="noreferrer">Waterfall Model</a> because the clients were unhappy due the limited software delivered. The clients couldn't change the requirements without burocracy and sometimes they only knew what they want or need in the middle of the process, in this time a contract had been already signed. It looked like Fred Brooks, Jr said <i>"Plan to throw one [implementation] away; You will, anyhow!"</i>. </p> <p>So the people started to make things in Agile way. And it brought happiness to clients. They, somehow, started to be satisfied by the software and the software was more accurate than ever, with minor bugs and according to the requirements.</p> <p>With the distributed systems's BOOM!, in my opnion started with Google, some people start develop things on the internet, such as public or private web services and external API, and the good practice of SOA was buzz word. They wrote the manifesto and it became a major architectural design.</p> <h2>Notes</h2> <ol> <li><p>Waterfall isn't bad or wrong! For some people like NASA, it still good, and it works well for important software that specs won't change.</p></li> <li><p>There are much more architectural design patterns, such as Layers and so on. What you need to know is if this pattern fit into your project or not. Maybe SOA won't fit.</p></li> <li><p>Futhermore, There is no silver bullet!</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload