Web Content Monetization System Design

Web Content Monetization System Design and Development Plan The design, development, launch and continual maintenance of a Web content monetization system requires the integration of Web content management and order management systems at the most foundational level of the application. Rapid prototyping using Ruby on Rails (Viswanathan, 2008) to create AJAX-based applications will significantly reduce the development cycles (Serrano, Aroztegi, 2007) and lead the development of source code that can be audited for security (Gutierrez, Rosado, Fernandez-Medina, 2009). Using these technologies and development methodologies costs will be minimized.

The intent of this development plan is to define the development status and tasks, difficulties and risks, and assess costs as well. Development Status and Tasks The development of a Web Content Monetization System requires the integration of a Web content management system and distributed order management system to enable transactions and manage payments. Critical to the development of this system is XML integration across the main system components and databases of content to be bundled, packaged and sold (Mitakos, Almaliotis, 2009).

As the proposed Web Content Monetization System will be based on a Web Services architecture, which has significantly less costs associated with development (Serrano, Aroztegi, 2007) it is anticipated that the entire system can be created in ten months or less. At present a structural diagram of the application, its integration points to databases, and the initial graphical interfaces for content search and ordering are complete.

The development of ontologically-based data structures (Zhang, Li, Tan, 2010) to support enhanced search is also critically important to the overall performance of the AJAX-based applications that comprise the system as well (Serrano, Aroztegi, 2007). The initial ramp-up of sales will be accomplished by approaching the top twenty five content producers globally and asking for their feedback on potential use of the Web Content Monetization System. This ramp-up is expected to take between six to twelve months. B.

Difficulties and Risks Major design challenges include the integration to legacy and 3rd party databases of content that have their own unique taxonomies and ontologies, the unforeseen costs associated with XML integration to payment gateways from the distributed order management component of the application, and the use of XML to customize the interface for specific content provider's needs.

Through the use of Web Services running over XML the integration issues can be resolved (Mitakos, Almaliotis, 2009) and for the graphical interface the use of AJAX debugging tools and components will be critical (Schrock, 2009). In addition to all of these factors security of the Web Service needs to be taken into account and designed into both the Web content management and distributed order management areas of the application (Gutierrez, Rosado, Fernandez-Medina, 2009).

The impact of these factors on the costs of design and development will be approximately 30% of total development cost, and in a worst-case scenario require an additional six months of development time to get the legacy and 3rd party database integrations completely correctly. C. Product Improvement and New Products As the Web Content Monetization System has yet to be launched there are no significant product improvements committed to prospects or customers yet.

It is common during this phase of a new systems' development to have a series of 2nd and 3rd generation product enhancements which will be added over the systems' life. It is highly advisable that a Customer Advisory Council be created that seeks to gain insights and intelligence from the top twenty content providers globally to ensure the subsequent system configurations and plans are consistent with their specific needs. D. Costs The initial design and development budget are shown in Table 1.

This includes the costs of the development of the Web content management application, distributed order management system, AJAX security testing and audits to ensure the payment gateways are secure, multi-taxonomy support for content providers' unique approaches to organizing their content and consulting and training programs. Also included is an analytics platform for capturing key performance metrics of the system and also capturing which bundles, pricing strategies and programs are the most effective.

Table 1: Design and Development Budget Costs Web Content Management System Programming & Development $200,000 Distributed Order Management Module with XML Payment Gateway Links $800,000 AJAX Security Auditing and Ongoing Development of Payment Encryption $100,000 Multi-taxonomy Support for Content Providers $50,000 Consulting and Training Programs in AJAX and XML Programming $50,000 Analytics Applications tied to content management and order management apps $100,000 Totals: $1,300,000 E. Proprietary Issues The integration of Web Content management and distributed order management systems is highly proprietary and needs to be copyrighted. There is no potential for copyright infringement based on the design of.