Results2Match

I‘m an old information engineering (IE) fan, having worked for the father of software engineering Dr. James Martin, and spending time as developer of supporting IE planning models and training modules. Since the nineties I was involved in the sales and implementation of the supporting tools created by TI Software. We were early adopters of Rapid Application Design (RAD) and Service Oriented Architecture (SOA) concepts (at that time called Component Based Development [CBD]) and sometimes too early for the market. Luckily we have successors using agile concepts and more powerful tooling to keep the information engineering school alive.

Showing its first version to the world in 1985, the application development tool was called IEF. It was based on ERD-modeling and pseudo coding the process model, all that used for 100% code generation. And it worked! Initially for host terminal applications, later on also supporting two and three tier client server and web based application. The methodology evolved from cascaded stages into RAD type of approaches. And with the introduction of component based development in 1994 the foundation for SOA was laid. IEF went through many name changes since. Today it is still around as AllFusion by CA and used by many large development shops around the world.

Although the product is robust and versatile, it lacks some of the 360 degree information asset elements like requirements planning and project management. And it is not a light weight implementation.

On the methodology front agile approaches, using focused development teams lead by Scrum Masters, help delivering in multiple 2 to 3 week so called Sprints working parts of the application. High customer interaction in (re-)scoping, (re-)defining, (re-)prioritizing and testing drive and complement the effort and make sure the result is what the business needs.

Although there are many (partial) suppliers of the above, I came across a very mature integrated implementation by OutSystems. From initial requirements definition, via prioritizing and planning to development, up to documentation, testing notes and next version requirements, this product offers true 360 degree support for business focused application development. Although designed to work in agile environments, also more traditional development shops could have a lot of value using it.

Biggest selling argument? Invite a business manager for a few hours to work on his or her requirements with the tool.

Biggest risk? All advantages being marginalized by the “Prince police” who seem to be more interested in paperwork and procedures than output.

Biggest help? Show the IT architects that they can include their guidelines in the integral requirements and see them used.

Although many years away from my IEF-days, seeing a product like this not only walks me down memory lane but also gives me appetite again.

Any exposure to agile system development and agile tooling yourselves? Please share your experiences with me.

Results2Match has a strong vision on proven and successful business management solutions and result driven implementations.

This blog is written by Hans van Nes. Hans is a very experienced interim manager and (radical) change management consultant. You can contact Hans through his Results2Match email address.