Leverage existing SQL skills – probably one of the most abundant IT skills available, to cost effectively create software solutions that target multiple technologies.
All you need is SQL.
SQL is the only technical skill required to develop solutions using FrameworX. Everything in FrameworX across the entire range of bulding blocks is implemented using SQL.
As your technology base used over time across various projects grows, so too does the risk and cost of maintaining a set of in-house skills that remains relevant to the currently supported systems.
Traditionaly when targeting a new technology, either existing software developers would need to be up-skilled, or skilled developers would need to be sourced externally. Either way, there is usually a painful cost in terms of both time and expense. Often there is no real up-skilling or sourcing of skill and the existing developers just have to learn on the fly – very often at the direct expense of quality and performance.
The following sequence of diagrams highlights why FrameworX is able to significantly reduce skill dependency while at the same time open up the solution to multiple technologies.
The diagram represents various technologies as they appear over time. T(n) represents present day technology, while T(n-1) and T(n+1) represent past and future technologies.
At any given time, the set of software developers possess between them various technologies. Initially maybe the entire team is made up of T(1), but as time goes by, various ‘pockets’ of technology specific skills develop within the set of developers. Some pockets overlap allowing certain developers to use more than one technology while other pockets are isolated exclusively to a particular technology. The net result is that the development team is fragmented and not able to be applied as a whole to solutions.
When identifying a technology on which to implement a solution, the choice its very often influenced by the spread of technologies within the developer pool. Ultimately though a particular technology is picked which typically maps to a specific subset of the developer set. The solution is then implemented by the specific developers and the resulting solution likewise only targets one technology.
