Are new systems becoming legacy faster..?
After evaluating around 300 IT Projects around ICMG IT Architecture Methodology, we had certain findings which was reflecting the actual maturity of the IT Architecture practise ;-)
It’s interesting to know that <10% of projects had business process models,
System requirements completeness is 40-50%,
Logical models ( Functional, Data, UI, Network,, Time, Rules) is 10-20% coverage,
Same is true for Technical (Specification) Models ( Functional, Data, UI, Network, Time, Rules),
Traceability, impact analysis, simulations are seen as luxury.
Most of the cases, development teams are using new buzzwords that promises results by ignoring step1, step2, step4, step5, step6.
Unfortunately, the idea of IT "Architecture" is often confused with IT "Implementation".
Abhijit BangudeGeneral Manager - IT
As quoted "development teams are using new buzzwords that promises" In my opinion these remain promises forever awaiting existence in reality
Peter Mũya HFounder | Finder | Funder
The word change probably is most abused. Maybe we do have artificial change versus natural change. The former driven by immature approaches to meet the demands of whatever it is they were intended eg the case of projects mentioned herein. The latter probably using mature approach that is more aligned and holistically meeting the needs. When I make a bad mattress that is initially adopted in the market then complaints arise about its inability to meet orthopaedic needs which should have been modelled, by releasing a mattress 2.0 with super orthopaedic functionality am creating an artificial change that never was. My inability to properly address orthopaedic needs in the first release is masked by the new buzzword
Alan LloydDirector, CIO . Co founder cuuble - social cell - peer to peer systems, GDPR, retirement villages, social inclusion
Architecture - the key codification step in an engineering process is oriented around the doctrine, materials , tools and expectations of the day.. some times constrained by regulations , quality control and alike. The software engineering industry is so different to what it was when I started in the 70s (process centric) then it became network centric, then customer centric, but the contribution from millions now as to open source, device compatibility, JS, jquery, html, social system monitors, SEO agenda - and web analytics (usage and monitoring tools) has made the software dev business so much different from the past. Thats the trouble with EA to some degree - its tool set, materials (frameworks) , approaches - seem to promote business and IT (as it was in my journey - a while back) , but the software industry (the creation industry of IT) has made its own world. Globalisation and interconnected systems have made both opportunity and competition at breakneck speeds - not saying that is good, just say thats the way it is.
Mattias DouhanAdvisor - Retail innovation
Could not agree more, speed is everything, all systems are legacy before they are even deployed,
Stephen CheySecurity Client Executive
I think a lot of ‘agile’ practices are sacrificing quality for speed
Alan LloydDirector, CIO . Co founder cuuble - social cell - peer to peer systems, GDPR, retirement villages, social inclusion
Hi Stephen sort of agree - but its a question of the speed and the tools and experimentation perhaps..In the past with systems dev and business process TQM and alike essential.. But in the software and information systems world - sometimes we experiment, stand on a milk crate on top of a ladder just to see whats there, look and learn and what we discover.. we can do that with software - we have a quality foundation on which we run innovations and slowly stabilise whats the new material is with the core elements. I think in EA we should stop seeing software as a 100% qualified and quantified and formalised unless thats in the contract of course, but rather the clay of the art and science of soft engineering. to be used for advantage where ever it can
Michael Poulin • FollowingService-oriented Enterprise Solution Architect
Yes, Stephen, and this raises a question - do we really need the outcomes of that quolity after all?
Michael Poulin • FollowingService-oriented Enterprise Solution Architect
@Sunil Dutt Jha interesting who business processes look like if a business needs not processes by results? Goddy Epie, TOGAF, SOA, ITIL, Cloud Certified
Goddy Epie, TOGAF, SOA, ITIL, Cloud CertifiedLead Enterprise Architect and Digital Strategist at QUALISYS CONSULTING
It is when you start hearing of legacy clouds that you understand how deep the evil is rooted. Unfortunately many focus their attention on hype and sales propaganda. The cost of getting in may be interesting but what would be the cost of getting out?
1 view0 comments