Doing nothing is always the best option when acceptable. So optionally if an existing technology is a good candidate to be an ISA part and that it meets all the requirements above, then it should be retained.
This post is also the opportunity to initiate the building process of ISA.
April 2015
You are browsing the site archives for April 2015.
ISA should offer a basic common management for specification, design, test, delivery and the like.
The purpose of ISA is to provide a common set of blocks on which any people involved in software can rely at anytime and anywhere.
Another aspect ISA should address is the continuity in the problem/solution chain thru specification/realisation and the abstraction levels.
Think and design ISA to be durable for several decades. The main design patterns should be incorporated as much as possible. This architecture should not limit itself in changes that it can elaborate to have good performances. And this in both dimensions hardware and software. Remain native : It is the condition to do at best of the possible. Define a solid base and then incorporate an extension mechanism.
Continue reading ISA Wish N°6 – Modern, performant and durable