Whilst many of us probably do not want to hear this, planes often break; parts become defective and components frequently need replacing. When they do, the airline operators are often able to claim the cost of these repairs and services against the aircraft manufacturer and Original Equipment Manufacturers. Aerospace Warranty Management Limited help to process, manage and facilitate this process.
Our requirements when we began the project were to create a web application to assist in creating and processing these claims, including creating an easy-to-use workflow that made it as simple as getting a quote on your car insurance. Over the years we've help grow the system to enable all these requirements and even expanded the application to become a management tool and an analytical engine.
On of our proudest achievements as a company has been to help Aerospace Warranty Management Limited become the first company in the World to interface directly with Airbus to transmit warranty claims to them. We're currently on course to achieve the same feat with Boeing too.
Aerospace Warranty Management Limited
Phase 1: Requirements Gathering
Meetings were held with key personnel and users and requirements were collected. Discussions over which methodology to use for the project took place. The decision was made to utilise Agile software development. This was due to the flexible approach to changing specifications and the close cooperation between stakeholders and the development team.
Software Development Methodologies
Phase 2: Design & Prototyping
A prototype was produced to experiment with key features and to get feedback on potential designs and user experience as early as possible. We often like to use prototypes on larger projects due to the feedback loop they provide. We also find they frequently highlight issues and discussion points early in the process rather than at the development stage when they can be a lot more costly to change.
User Interface Design
Phase 3: Creating the App
Development took place over several phrases to deliver key particular features. All phases took place with frequent communication between the development team and the client. The design and implementation of certain features often change throughout the development phase as requirements were change or expanded on and the capabilities of the software were fully realised.
Phase 4: Lets make sure this thing works!
For a project this size, testing is vitally important. Not only to make sure that the software works as intended once a development phase is completed, but also to ensure performance is as expected, that unexpected actions do not result in unexpected outcomes and, most importantly, that no bugs are introduced as further features are added to the application.
On this project a Continuous Integration system was deployed along with Automated Testing. Both of these systems allowed testing to be done thoroughly and quickly with each code change to ensure the stability and security of the application as development progressed.