This paper presents a design and development plan for a Web Content Monetization System that integrates web content management with a distributed order management platform. The plan outlines the system's architectural foundation in XML and Web Services, the use of Ruby on Rails rapid prototyping and AJAX-based interfaces, and an ontologically-based search infrastructure. It addresses key development risks — including legacy database integration, payment gateway security, and multi-taxonomy support — and projects a ten-month development timeline. A detailed budget of $1.3 million is itemized, and a strategy for initial market ramp-up through engagement with top global content producers is described. Proprietary and copyright considerations round out the 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 development cycles (Serrano & Aroztegi, 2007) and produce 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, address difficulties and risks, and assess costs.
The development of a Web Content Monetization System requires the integration of a web content management system and a 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 system will be based on a Web Services architecture — which carries significantly lower development costs (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 (Serrano & Aroztegi, 2007). The initial ramp-up of sales will be accomplished by approaching the top twenty-five content producers globally and soliciting their feedback on potential use of the Web Content Monetization System. This ramp-up is expected to take between six and twelve months.
Major design challenges include the integration of legacy and third-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 providers' 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 these factors, security of the web service must 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 could require an additional six months of development time to complete the legacy and third-party database integrations correctly.
"Future enhancements and Customer Advisory Council strategy"
"Itemized $1.3 million development budget breakdown"
"Copyright protection and legal liability considerations"
Always verify citation format against your institution’s current style guide requirements.