Every industry requires software and often those involved in a discussion with a software team or an outsourcing software company might not be technical people. For instance, if a medical practice in the USA is looking for an EHR software or an educational institution requires an ERP system – they are business leaders and knowledge experts in their field but it is not often that they be aware of software terminology. Here is a quick guide to technical terms that may inevitably crop up in a software discussion at the start as well as once the product goes into development life cycle.
Common technical terms and what they mean
There may be countless technical words used in the software industry and it may be impossible to cover them all. However below are some of the most commonly used phrases in the software world, that will give you a good head start.
Greenfield is a software development term that refers to the development of a brand new system from scratch. There are no source codes (or legacy code), no older versions of the software, and no dependencies or restrictions.
Technical debt usually refers to the cost involved in reworking code when short cuts or poorly rewritten code are taken during the development cycle to develop a quicker solution. Imagine a project where there are 2 potential options – one is quick and simpler but will require extensive modification in the future. The second has a better design but will take more time to implement. As obvious, there is a technical debt in terms of finance and resource outlay in the first option. However, it can be considered when developing a minimal viable product or MVP to go to market fast.
Also known as microservices architecture, this framework develops a separate container for every function. Each function will communicate with the different containers or functions u