Modules
It was mentioned that the framework can pass a user into a module at any page point. In some cases, the module might be completely standalone, such as the Bonner WBRS 2.0 system, or perhaps, may even be another website. But more often, a module will be one of 18 such database applications, some of which are already in use. Each of these applications will have to go through some level of advancement in order for them to become framework modules. As before, any application that is added to the framework, becomes available to all sites within. I’ve divided the 18 modules into three categories of development. Within the categories the estimated cost has been averaged, since most of the modules contain roughly the same amount of work. It is expected that some will entail more work and others less.
In conclusion, I’ve developed a system that would allow any number of web sites to be built, within an easy-to-use structure, and apply any number of integrated modules. The freedom to the administrator, as well as the time savings in building these sites and sub sites I believe is nearly incalculable. The system could easily contain 100 CBR sites without further modification from the template above. There is also no foreseeable reason why this software couldn’t see 5 years of usage. My point of course being that this is a viable investment into an obviously important part of the Bonner business structure. I also think it plays strongly together with the Bonner WBRS 2.0 system now going online, and lessons learned there will be applied to this system.
The bulk is of course application design and programming.
Also in this section:
Minor edits are needed to...
Major edits are needed to...