Project Timeline

The timeline for deploying the proposed webservice would be somewhat tight. Here it is presented in two-week blocks:

Considering the large variety of persistence methods, and . In total, a minimum of four or five technologies would be required for this. A framework language, front-end language, database, and hosting provider would all be required, not to mention pre-made services for actually hosting and serving each of the components. Week one would be dedicated to selecting these technologies, and building proofs of concept for varied parts of the final application, to ensure that the selected technology is workable, and would fit the task. The following technologies would be suited in some way or another for each of these areas:

• Framework
• Java, Spring framework
• C#, ASP.Net
• Front-end
• Javascript
• Actionscript (Adobe flash)
• Database
• MySQL
• MongoDB
• Hosting
• AWS
• Google App Engine

After appropriate technologies are selected, the remainder of the next week would go into planning, structured around architecture and team roles. After this, initial structure framework (Read: Testing and interface writing) would finish week 2.

The next two weeks would be devoted to creating an initial marketing/display page, integrating the database technology, and creating accounts on that database.

Weeks 5 and 6 begin the development on the customizeable ruleset engine, and rendering on the front-end site. Considerations towards how a user would interact with the creation of rulesets would occur here, and making the framework easy enough for a lay-person to use, but general enough to create a huge variety of rulesets would be first and foremost.

The next major milestone occurs at week 9, with the deployment of a partially functional alpha version. One ruleset would be completed by this time, and any users that had signed up for the site would be able to log in and use it, with the ability to submit problems they may encounter on the site itself. Along with handling some of these bug reports, development would continue on exposing the ruleset creation to the user.

At week 11, the ruleset creation feature would be exposed to the user, along with another sample ruleset. At this point, most of the development effort would be pointed to bug reports, with some minor planning on what next to implement and how, if anything.

By week 12, a working webservice would be hosted online, and the project would be open-sourced. The ability to purchase additional features and subscribe would become available, and continued development would be community-directed.