Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

3.
Need of SOUP <ul><li>SOA offers many benefits, but its initiative can suffer one or more of the following problems: </li></ul><ul><li>High time & short time to market, which increases the risk of failure. </li></ul><ul><li>Low tolerance for failure due to high cost & difficulty quantifying return on investment. </li></ul><ul><li>Dynamic requirement & business needs that need proper management. </li></ul>

4.
What is SOUP <ul><li>SOUP is a software methodology that uses the best elements from RUP & XP to build & manage a SOA project. </li></ul><ul><li>The key factors that can help SOA rollout succeed are: </li></ul><ul><li>A clearly defined development process. </li></ul><ul><li>Enhanced lines of communication across project teams that know the business. </li></ul><ul><li>Clear support & governance policies. </li></ul>

18.
Conclusion <ul><li>SOUP, a new methodology for building your SOA & then realizing the benefits of the architecture on individual projects. It explains how you use a formal RUP-like methodology to initially build a SOA & then move to an XP-style agile process for ongoing services rollout. By combining the best qualities of these two processes, you can rely on unified development scheme that provide the flexibility to manage the different stages of SOA life cycle. </li></ul>