27 Jan What to Expect When Your Custom Application Has Been Completed
- There can be an error screen from a bug. These are rare, but on occasion, it may occur.
- Some of these occasional bugs are actually unaccounted for case scenarios. For example; maybe a page in the application works fine until someone tries to order a negative quantity of an item, or they schedule an event to last for 72 hours when the system had only been programmed with an assumption of a maximum time of 4 hours. These bugs are harder to cover under warranty and are generally caused by the grey zone of requirements. A discussion is usually required to determine if these are warranty or enhancement items.
Enhancements are items that can be seen as a lack in functionality that escalate in priority until the items are worth building:
- A column missing on a report
- A missing step in workflow… if we just automated this then it would be so much easier
- Keeping up with new technology
- Staying compliant with new security measures
- Scaleability – The system might respond fine to a few thousand users (or hundred thousand records), but starts to crash under tens of thousands of users (and millions of records)
It will also be necessary to ensure your new application undergoes routine updates. Think of it like car maintenance; done regularly, it’s mostly painless, left unchecked, you end up stranded with your family along the side of the interstate and your vacation is ruined. This is why your developer should be talking to you about maintenance early on in the engagement so that you understand what to budget for. Open communication is the key!
Inverse-Square is a custom software company in Indianapolis. We focus on workflow automation software that improves process efficiency . Whether you are looking to replace excel, or build a background screening application, we can help!Request a Consultation