One of the first things we do when we initiate a new software application project is attempt to gather a set of software requirements. These are often broken down into Functional and Non-Functional Requirements. The Functional Requirements are then generally further...
The simple answer is knowing what your application needs to do to be successful! If only life were that simple! If you don't have complete and correct requirements, you simply can't succeed. Application projects in many organizations rush to development too soon -...
As customers, most of us pay little attention to the implementation process between ordering and delivery - we happily give little thought to the underlying infrastructure and technology as we receive our new fancy red toaster! Our attention is more towards the...
As your business critical software applications age, the technology they depend upon also ages, reaches "end of support" and/or "end of life". We also find that as applications age, they drift from their original purpose as business requirements change. They...
Many business analysts spend most of their time in meetings documenting business process requirements, explaining what they mean to developers, waiting for weeks and then figuring out why the implementation didn't match the documentation, rinse and repeat endlessly!...
The US Federal Aviation Administration (FAA) was recently in "stormy weather" because of a major computer system failure. As per BBC News: "US air safety officials say that the glitch that led to travel chaos at airports last week was actually caused by a contractor...
There is a lot of hype in the news about the step change in AI technology with major companies talking about how AI will be a game changer for their business. The challenges facing many organizations today are: how will we incorporate AI into our products to drive...
Application Shelf Life and Technology Expiry Dates Most organizations use forms-based custom software applications that have hard-coded the business functionality. These applications are implemented on a set of specific technologies: source code in one (or more)...
There are many good use cases for No Code / Low Code technology when building simple applications that collect and maintain records for a few simple forms. Most of these technologies include some form of a canvas designer where Citizen Developers can drop and style...
What is Technical Debt and where does it live? Wikipedia defines technical debt as: "the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer." A lot of technical debt can be...