Skip to main content

Cab Control

Received another call today from a company interested in my Cab Control Software. Basically it's taxi management . The software needs a re-write to get it from Windows Forms onto the web. I have great hopes for the software. It really just needs to time and ingenuity pouring into it. I have loads of ideas for it but just have so little time. 

It currently has this functionality which I'll need to get across: 
  1. Add drivers and Taxis and keep track of their contact details, addresses, licence details, CRB checks and eligibility to work in the UK.
  2. Basic account management functions, such as creating a customer account and putting the account on hold. 
  3. Add Bookings for drivers and customers
  4. Creating reports for customer accounts that could be exported as a CSV file for billing purposes. 
  5. Creating reports for drivers to know how many pickups the drivers had made.
  6. Query the bookings for enquiries and police check up reports.
  7. Provide management tools to check MOT and Service details on Taxis
But I am hoping to add at least these ideas to it as well:
  1. Improved booking facility so when making a booking the booking administrator can see which drivers are currently working and which are not currently on a call or are nearby for a pickup. 
  2. Ability for drivers to be booked in when they are signing on and off a shift.
  3. Customer facing interface so that companies and potentially individuals can sign up with a taxi firm, make bookings, change contact details and monitor the usage of their account with taxi firms. 
  4. Improved ability to query, monitor and report on Taxi condition and MOT/Service dates and expiry.
  5. Improved ability to query driver details and report on licence expiries and other details such as points on licence and subs paid owed to the firm.
  6. Ability for taxi firm to track and report on drivers and any that currently owe subs.


There are many other improvements that could be added in the future. These are just some initial ideas. Another area in the future that would be interesting to take Cab Control Online into would be to develop handheld software (either for Windows Phone 7 or Android)  so that both taxi drivers can keep track of their next booking and that customer accounts could book a taxi. 


Anyway, I have written a little proposal to my director and am hoping if we can decide that money can be made from it then I will be able to code it at work through Open Projects. I have some ideas on cost models as well but they are my business ;-)
Here was the original introduction to my Cab Control program....


There are quite a few videos about the programming behind it and how to use it that you can find by visiting the website.



Gina said…
Hi there, I couldn't find any other way to contact you, so hopefully you'll get updates for comments! I work for a small taxi firm, which could really make good use of your CabControl software (and I'd benefit from the upgrade from pen & paper haha!). If it is something you'd consider sharing, please contact me in order to discuss the options that would be available for the company.Regards,-- Gina

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second