|
CitySprintiFleet Management application
Structure and ScalabilityProblem:
1After our initial consultation with CitySprint it became apparent that iFleet, the proposed custom built application, would need to be built in a way which would be both scalable and extendable to meet their growing needs. Solution:
In reply, we developed the application based upon modern object-oriented design pattern which allowed us to develop the application over a course of two years. This makes the iFleet application highly maintainable and easily extendable.
This application was lated adopted by WestOne Cars, a leading provider of private hire passenger car services across the UK. In the WestOne Cars deployment of iFleet we developed the accounts part of the application which was possible due to the adaptability of the iFleet framework. This allowed drivers and the accounts department in the head office to view and keep track of their daily earnings. SecurityProblem:
2Today more than ever before, online security is a priority. As criminals become more and more innovative in their techniques to steal online data, online applications are required to become more and more resourceful in their security systems. Solution:
Developing the application provided an opportunity to implement security best practice from the start. Management of the complete development lifecycle from requirements analysis through to configuration, deployment and operations allowed us to address security issues to ensure a safe and risk-minimised project.
Access Control List (ACL) systemProblem: 3CitySprint needed a system, which would allow different groups to have access to different functionality and restricts the fields and documentation shown to the user. For instance the driver’s financial details is required to be only shown to the accounts department while photocopies of the Passport's and Drivers license are only shown to the Fleet department.
Solution: In reply, we developed and bespoke solution, which allows different groups to have access to different functionality and restricts the fields and documentation shown. This was addressed in two parts: the first being the development of the ALC system and the second part was to develop the iFleet application in a way which would allow the ALC system to control which users is able to access what part or object. This approached allowed for greater flexibility as the ALC system works irrespective of the iFleet screens. In essence its job allows different ‘user groups’ to access different parts (or objects) within the system, while iFleet component manages how the data is stored and display. By separating these components we were able to extent the ACL control to new elements as and when they are develop, making the system highly adaptable and flexible. |

