Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CMS Driven Applications


Published on

Web Content Management has given the web developers a way to control all aspects of a website instead of being held hostage by the web team to make changes to a site. Todays business applications are facing a similar challange where changes to an application have to be completed by the development team. Moving to a CMS driven application infrastructure allows this control to move from the developers to the business team.

Building on a solid foundation such as Magnolia for your application development brings great benefits in security, scalability, time to market and maintenance of a business application.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

CMS Driven Applications

  1. 1. CMS Driven Applications <ul><ul><li>Speaker: Ruben Reusser </li></ul></ul><ul><ul><li>Company:, Inc </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>
  2. 2. CMS Driven Applications <ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Stakeholders </li></ul></ul><ul><ul><li>Application Types </li></ul></ul><ul><ul><li>Life Cycle of a shrink wrapped Application </li></ul></ul><ul><ul><li>Life Cycle of a custom built Application </li></ul></ul><ul><ul><li>How complicated are changes? </li></ul></ul><ul><ul><li>Zachman Framework </li></ul></ul><ul><ul><li>CMS/WCM </li></ul></ul><ul><ul><li>Magnolia before 4.0 </li></ul></ul><ul><ul><li>Magnolia after 4.0 with STK </li></ul></ul><ul><ul><li>Building the Application </li></ul></ul><ul><ul><li>Making Changes to the Application </li></ul></ul><ul><ul><li>CRUD Example </li></ul></ul><ul><ul><li>References </li></ul></ul><ul><ul><li>Questions </li></ul></ul>
  3. 3. CMS Driven Applications <ul><ul><li>Definition: </li></ul></ul><ul><ul><li>CMS Driven Applications make use of content as a primary driver for the functionality and are built on top of a content management system. </li></ul></ul>
  4. 4. CMS Driven Applications <ul><ul><li>Stakeholders in an Application </li></ul></ul><ul><ul><li>Decision Makers </li></ul></ul><ul><ul><li>Project Owner </li></ul></ul><ul><ul><li>Architects </li></ul></ul><ul><ul><li>Developers </li></ul></ul><ul><ul><li>Users </li></ul></ul><ul><ul><li>Maintenance and Support </li></ul></ul>
  5. 5. CMS Driven Applications <ul><ul><li>Application Types </li></ul></ul><ul><ul><li>Shrink Wrapped Applications </li></ul></ul><ul><ul><li>Custom Built Applications </li></ul></ul>Custom Built Shrink Wrapped
  6. 6. CMS Driven Applications <ul><ul><li>Life Cycle of a shrink wrapped application </li></ul></ul><ul><ul><li>Major Release </li></ul></ul><ul><ul><li>Customer buys the application </li></ul></ul><ul><ul><li>Customer adapts to the application </li></ul></ul>
  7. 7. CMS Driven Applications <ul><ul><li>Life Cycle of a shrink wrapped application </li></ul></ul><ul><ul><li>major release, customer buys it, customer uses it and adapts how he/she works around the software (there is a need for this type of application, the user wants to use it the way it's built or uses the software of the competitor instead)‏ </li></ul></ul>
  8. 8. <ul><ul><li>Application is built in conjunction with the stake holders, then released. Application is released in a partial state if it already helps in the business process, development continues until the full application is ready, features are frequently added over the life of the application to adopt to the business. </li></ul></ul>
  9. 9. CMS Driven Applications <ul><ul><li>Life Cycle of a custom built application </li></ul></ul>Partial Release Build Business Change Final Release Application Change
  10. 10. CMS Driven Applications <ul><ul><li>What happens with the team once the major development is completed? </li></ul></ul><ul><ul><li>Reassignment of core team to other projects </li></ul></ul><ul><ul><li>Contractors may disappear </li></ul></ul><ul><ul><li>New team members are assigned for maintenance and support </li></ul></ul>
  11. 11. CMS Driven Applications <ul><ul><li>How complicated are changes? </li></ul></ul><ul><ul><li>Development team has to be involved for small changes </li></ul></ul><ul><ul><li>Application has to be released and fully retested to make sure it is still functioning properly </li></ul></ul><ul><ul><li>Resources have to be drawn back into the project </li></ul></ul>
  12. 12. CMS Driven Applications <ul><ul><li>How big is the team that makes changes? </li></ul></ul><ul><ul><li>Full team including developer </li></ul></ul>
  13. 13. CMS Driven Applications <ul><ul><li>Lesson from the above: </li></ul></ul><ul><ul><li>Don't forget the maintenance aspect when building an application! </li></ul></ul>
  14. 14. CMS Driven Applications <ul><ul><li>Zachman Framework </li></ul></ul>
  15. 15. CMS Driven Applications <ul><ul><li>CMS/WCM is addressing this problem for the web site building use case </li></ul></ul><ul><ul><li>Developer is not involved in production changes </li></ul></ul><ul><ul><li>User can make changes </li></ul></ul><ul><ul><li>Fast reaction to business needs without the burden of full development cycle </li></ul></ul>
  16. 16. CMS Driven Applications <ul><ul><li>Magnolia before 4.0: </li></ul></ul><ul><ul><li>User can change content </li></ul></ul><ul><ul><li>Developer manages the overall look </li></ul></ul><ul><ul><li>Release Cycle is needed for new look </li></ul></ul>
  17. 17. CMS Driven Applications <ul><ul><li>Magnolia before 4.0: </li></ul></ul>
  18. 18. CMS Driven Applications <ul><ul><li>Magnolia after 4.0 with STK: </li></ul></ul>
  19. 19. CMS Driven Applications <ul><ul><li>Advantages: </li></ul></ul><ul><ul><li>Very flexible </li></ul></ul><ul><ul><li>Inexpensive maintenance and support </li></ul></ul><ul><ul><li>Fast release cycles </li></ul></ul><ul><ul><li>Disadvantages: </li></ul></ul><ul><ul><li>Too much flexibility can introduce errors </li></ul></ul>
  20. 20. CMS Driven Applications <ul><ul><li>Why not do the same for application development? </li></ul></ul>
  21. 21. CMS Driven Applications, why? <ul><ul><li>What is a Content Management System? </li></ul></ul><ul><ul><li>A Content Management System (CMS) supports the creation, management, distribution and publishing of corporate information. </li></ul></ul><ul><ul><li>It covers the complete life cycle of the pages on your site, from providing simple tools to create the content, through to publishing and finally to archiving. </li></ul></ul><ul><ul><li>It also provides the ability to manage the structural layout of the site, the appearance of the published pages and the navigation provided to the users. </li></ul></ul><ul><ul><li>(src: ) </li></ul></ul>
  22. 22. CMS Driven Applications <ul><ul><li>Today's web sites also contain or are applications! </li></ul></ul>
  23. 23. CMS Driven Applications <ul><li>Definition: </li></ul><ul><li>A CMS Driven Application is an application which includes as many steps as possible into the content part while having the logical part as a base. This allows for easy changes and maintenance. </li></ul>
  24. 24. CMS Driven Applications <ul><ul><li>Building the Application </li></ul></ul><ul><ul><li>The team builds a more modular application, taking data and configuration from the CMS and render it for its application purposes </li></ul></ul><ul><ul><li>The team then uses the modules created on the CMS to build out the actual application </li></ul></ul>
  25. 25. CMS Driven Applications <ul><ul><li>Making changes to the application </li></ul></ul><ul><ul><li>Changes can now be made by modifying content/configuration in the CMS directly. Changes can be viewed immediately and can be made by business people, designers or developers without redeploying. </li></ul></ul>
  26. 26. CMS Driven Applications <ul><ul><li>Easier Maintenance Cycle </li></ul></ul><ul><ul><li>Application changes are now managed the same way as content changes. </li></ul></ul>
  27. 27. CMS Driven Applications <ul><ul><li>Less to build </li></ul></ul><ul><ul><li>Magnolia already comes with security, caching, deployment and activation work flow </li></ul></ul><ul><ul><li>Less risk for critical security issues </li></ul></ul><ul><ul><li>Developers focus on business logic and build more reusable code. </li></ul></ul>
  28. 28. CMS Driven Applications <ul><ul><li>CRUD example </li></ul></ul><ul><ul><li>(create, read update delete)‏ </li></ul></ul>
  29. 29. CMS Driven Applications <ul><ul><li>Module built: </li></ul></ul><ul><ul><li>Generic CRUD module connecting to a database or a repository, including form handler, error messages, operations, added GUI designer to create the forms. </li></ul></ul><ul><ul><li>Module can be reused for any form screen, forms can be managed by users, no developer needed to make changes (better error messages?)‏ </li></ul></ul>
  30. 30. CMS Driven Applications <ul><ul><li>Magnolia Project References: </li></ul></ul><ul><ul><li>Healthcare web site for costco members </li></ul></ul><ul><ul><li>swissroots – a community web site </li></ul></ul><ul><ul><li>Open Enrollment – a healthcare application platform </li></ul></ul>
  31. 31. CMS Driven Applications Questions? [email_address]