Systems architecture

Choosing the right architecture influences a system’s robustness, and ease of use

A system’s architecture is one of the biggest factors in its success. That sounds obvious, but in our experience this is part of systems development that needs all the attention it can get.

Whether a system should be created in Microsoft Excel or Microsoft SQL Server will have an impact on how easy it is to use, how much it costs to develop, and how robust it will be. Only by understanding the business requirements, and the environment in which the system will work, can anyone judge which the right approach. Even then, software tools can be used in a number of different ways depending on what the system is designed to achieve. And different emphasis can be given to different aspects of the system.

So getting the right architecture is important, and will impact on the eventual success and usability of the system.

We use a layered approach when designing the architecture for a system, thinking about the data layer, the business logic layer, and how the user will interact with the system. By splitting the thinking, and the code, we can focus on each area and ensure there is a clean division between them. Then if things change, the system doesn’t have to be rewritten to accommodate the changes.

We work to agreed standards wherever possible, and use good coding practices. We believe these things matter in robust systems that will work well for people. So it’s part of everything we do.

Contact us to discuss how systems architecture cuts costs, and improves usability.