An example use-case for the ADT

I designed my tooling with a particular type of use case in mind.

Say your town has 4 or 5 libraries in it. Maybe you might like to have a fully accessible (as in specifically designed for use by people with disabilities such as sight loss), multi-lingual ready, moderated, validated identity required social network for each library and its catchment area.

The way I would commission a project like that is that I would

• Work out what the application's function is to be and what specific requirements I have of it for maximum usage and impact within the catchment area of that library
• Decide what CMS system I want to use to build the solution (lets say we choose Joomla because accessibility is very important to us).
• Commission Joomla experts (who are for the most part volunteers like me so it shouldn't cost a whole heap of coin) to build the core application in a "write once use many times" ethos, or, if you prefer, "develop once deploy many times" ethos.
• Once you are happy with the function of your commissioned application deploy it to each of the libraries in turn using the agile deployment toolkit.
• Once the application is live make it available to the public. To join their local library centred social network, they need to provide proof of ID and proof of address (to show that they are within the catchment area of the specific library) at which point an account is set up for them by library staff with an immutable login and email which they are then responsible for all behaviours associated with that account.

That would be just one example use-case that I had a vision for the ADT and there's possibly a lot of other use cases wherever there is a "develop once deploy multiple times" need.

As another example of how you might make to make use of my work...if you are a charity with a presence in multiple towns then you might like to develop a single application customised to the needs of your charity and deploy it to each town you are present in in turn. The application that your charity commissions using a (supported) CMS system is intended to be customised for the particular clientel of your charity. If your charity is for elderly people you might, for example, want a simple to navigate interface with enlarged fonts by default. If your clientel is young students at a college or something then your application will likely be customised very differently. If your clientel were to be a social network for a cruise ship then a commissioned application would be designed around the needs of what people who go on cruises would likely want. I think you get the idea. My ambition has been to provide a solution that can repeatedly deploy applications that meet a specific business need. So, for example, when we lose the competition, if one college were to commission an application for its students to use it could open source what it has commissioned so that other colleges can use their application rather than each college re-inventing the wheel on its own because there is likely to be a lot of commonality of use case between different colleges.