This page (revision-33) was last changed on 07-Jul-2022 01:31 by admin

This page was created on 07-Jul-2022 01:31 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
33 07-Jul-2022 01:31 5 KB admin to previous
32 07-Jul-2022 01:31 5 KB admin to previous | to last
31 07-Jul-2022 01:31 5 KB admin to previous | to last
30 07-Jul-2022 01:31 5 KB admin to previous | to last
29 07-Jul-2022 01:31 5 KB admin to previous | to last
28 07-Jul-2022 01:31 5 KB admin to previous | to last
27 07-Jul-2022 01:31 5 KB admin to previous | to last
26 07-Jul-2022 01:31 5 KB admin to previous | to last
25 07-Jul-2022 01:31 5 KB admin to previous | to last
24 07-Jul-2022 01:31 5 KB admin to previous | to last
23 07-Jul-2022 01:31 5 KB admin to previous | to last
22 07-Jul-2022 01:31 5 KB admin to previous | to last
21 07-Jul-2022 01:31 5 KB admin to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 11 changed one line
We have over 30 years' experience each in consulting on and designing many hundreds of projects for business clients - liaising with 3rd parties and managing the deployment and testing of systems, typically developing bespoke / customised software components, integrating major packages and datasets, and providing the training, procedures development, and support required for success.
We have over 30 years' experience each in consulting on and designing many hundreds of projects for business clients - liaising with 3rd parties and managing the deployment and testing of systems, typically developing bespoke / customised software components, and providing the training, procedures development, and support required for success.
At line 26 changed one line
%%add-css .quote {font-size:14px;} /%
At line 28 changed 3 lines
%%quote LanTastic Networking (circa 1990s) with Coaxial cable and manual interrupt configuration has given way to zero configuration Wifi and managed plug-and-play office switches. \\ \\ DOS, Windows3.1, WindowsNT, Windows 95/98/ME, WindowsXP, Windows2000, Windows Vista, Server2003, Windows7, Server2008, Windows8, Server 2012, Windows10, Server2016... a new Microsoft Operating System on average every 2 years over the last 30. \\ \\
Databases, Accounting Systems, Cloud Technology, Web App Technology, Servers, Workstations, Mobile devices, Networks, Backups, Security, AntiVirus... \\
...all on the endless shifting sands of evolution that we navigate every day for our clients. /%
%%quote LanTastic Networking (circa 1990s) with Coaxial cable and manual interrupt configuration has given way to zero configuration Wifi and managed plug-and-play office switches. \\ \\ DOS, Windows3.1, WindowsNT, Windows 95/98, WindowsXP, Windows2000, Windows Vista, Server2003, Windows7, Server2008, Windows8, Server 2012, Windows10, Server2016... a new Microsoft Operating System on average every 2 years over the last 30. \\ \\
Databases, Accounting Systems, Cloud Technology, Web App Technology ... all on the endless shifting sands of evolution that we navigate every day for our clients. /%
At line 33 removed 33 lines
!!Do It Once, Do It Right
This is a significant determining factor in Return On Investment.
Maximising the lifetime of the system provides return over a longer period.\\
Minimising the cost of change lengthens the lifespan and minimises maintenance costs.\\
Minimising the cost of change allows you to start with a small working system,\\
responding to requirements and feedback in steps towards the ultimate goal.\\ \\
%%columns
We have seen (as anyone relying on complex systems does after a time) that smaller efforts and working systems (as opposed to big specifications and long timeframes) provide faster, more certain returns, and are not so prone to issues like requirements change or platform evolution (or worse, platform end of life).
\\ \\
The issues with platform evolution (changes to the stack over time) and eventual end of life are critical to tackle if you want to maximise return on investment in business systems software.
\\ \\ \\
The service lifetime of a software program depends on:
* choice of platform (every element of 'the stack' is important)\\
* prioritising future maintenance as highly as feature creation.
----
%%label-warning A team sport ('the stack')/%
%%quote
Technology - especially software, is a team sport. A software program relies on a 'stack' - other programs and hardware it requires in order to run properly. For example, a complex Excel Spreadsheet is at the top of a stack, requiring a particular version of Excel, a compatible version of Windows to run Excel on, and a compatible PC or Laptop or Tablet to run Windows on. If any of the levels in the stack fail or become incompatible, the program doesnt run anymore - and needs to be maintained or rewritten for the new stack. /%
/%
%%columns
\\If you do it right, it is possible to avoid the trap that most software falls afoul of - the inability to adapt. \\ \\Requirements change constantly. Software has to keep up or it has to be replaced.
----
%%label-warning Adapt or Perish.../%
%%quote
If the future maintenance of the system is of lower priority than features, the costs per adaptation increases exponentially over the software's lifetime, until the software cannot be economically adapted and must be replaced (the end of returns on that investment).
/%
/%
At line 74 removed 2 lines
\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\