1 / 12

Visual Content Management System

Visual Content Management System. Bruno Coelho Viatecla Software http://bcoelho.blog.com bscmcoelho@netcabo.pt. 10-06-2007. Agenda. The problem How to manage contents in different domains of the information life cycle? The first solution: Content Management System What is it?

etana
Download Presentation

Visual Content Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Visual Content Management System Bruno Coelho Viatecla Software http://bcoelho.blog.com bscmcoelho@netcabo.pt 10-06-2007

  2. Agenda • The problem • How to manage contents in different domains of the information life cycle? • The first solution: Content Management System • What is it? • What does it do? • Advantages? • CMS’s problems • The solution: Visual CMS • What is it? • What does it do? • How does it work? • Demo • Conclusions

  3. The problem • Organize • Acquire • Manage • Deliver • Analyze One resource to... ...generates confusion and errors Many resources... ...generates many confusion and errors

  4. Content Management System The first solution • What is it? • A CMS is an informatic system. • What does it do? • The CMS’s main goal is to offer control over the different domains mencioned before for the end-user. • What are it’s advantages? • Control • Agility • Security What abou disadvantages?

  5. The CMS’s problems • They aren’t user-friendly • Lost of control over the system • Increases the tasks time to complete • Increases suport costs • Generates errors • It’s hard to understand complex system • It’s hard to switch between CMSs

  6. VCMS – What is it? • Visual modeling environment • CASE Tool • Domain specific language

  7. VCMS – What does it do? • “An image is worth more than a thousand words” • Increases the abstraction... • ... Without ambiguity... • ... Complying with sintax and semantic rules • Build consensus! • Understand complex systems • Adapts it self to different CMSs • Shows the chosen CMS specific properties • Transmit the right actions to the CMS based on what was visual modeled • Creates a strongly typed visual language • Creates the .NET types that represent the visual and domain elements

  8. VCMS – How does it work? • The VCMS’s layered architecture... • Visual Content Management • Visual modeling environment • Visual Content Provider • Comunication between the VCM and the CMS • Content Management System • The CMS’s API • Ables: • Abstract comunication between the VCM and the CMS • The same visual modeling environment for different CMSs Fig. 1 – VCMS’s layers

  9. VCMS – How does it work? • The VCMS makes available the interaction between the user and the CMS across different domains. • Each domain has unique characteristics that are represented by a domain language in the VCMS. Fig.2 – VCMS’s architecture across different domains

  10. VCMS – How does it work? • In each domain... • ...it’s possible to interact with different CMSs... • ... using a associated Visual Content Provider... • ... that implements the domain's programmatic interfaces. • Based on the strategy design pattern. • See it to believe it! Fig.3 – The VCMS’s architecture in the context of a domain

  11. Conclusions • Present: • The VCMS is a visual modeling sistem that overcomes the CMSs disadvantages and interacts with different CMSs using a associated Visual Content Provider that implements the domain's programmatic interfaces. • It was implemented the Organize domain using Viatecla’s CMS - Scriptor Server 2006 - and a dummy CMS. • Future: • Create a Software factory for the Web Application Integration Domain

  12. References • DSL Tools • http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=61&SiteID=1 [April 24th 2007] • http://msdn2.microsoft.com/en-us/vstudio/aa718368.aspx [April 24th 2007] • Visual Studio SDK • Boiko, B. (December, 2001). Content Management Bible. Wiley. • Hackos, J. (April, 2004). Content Management for Dynamic Web Delivery. Wiley • McGovern, G. e Norton R. (October, 2001). Content Critical: Gaining competitive advantage through high-quality web content. Financial Times Prentice Hall. • http://www.vignette.com/dafiles/docs/Downloads/WP0507_VCM_Capabilities.pdf [April 24th 2007] • www.Metatorial.com [April 24th 2007] • http://en.wikipedia.org/wiki/Computer-aided_software_engineering [April 24th 2007] • www.aiim.org [April 24th 2007] • JavaScript Libraries • http://script.aculo.us/ [April 24th 2007] • http://developer.yahoo.com/yui/ [April 24th 2007] • http://www.xulplanet.com/ [April 24th 2007] • http://wf.netfx3.com/ [April 24th 2007] • Ajax • http://dojotoolkit.org/ [April 24th 2007] • http://mochikit.com/ [April 24th 2007] • http://www.plextk.org/trac/wiki/ [April 24th 2007] • http://www.prototypejs.org/ [April 24th 2007] • http://rialto.application-servers.com/wiki/ [April 24th 2007] • http://openrico.org/ [April 24th 2007]

More Related