Interview: Ivar Jacobson on the UP, UML, MDA, and the future of methodologies
The Essential Unified Process (Ess UP) is a streamlined version of the UP which, as the name implies, captures the essential practices required to be successful on a UP project.
Jacobson says, in the interview:
With agile methods there's not much to study, thin books, beautiful books but thin! Whereas if you go to Unified Process, in particular Rational Unified Process, there's no one that ever will be able to read it completely... if you want to adopt it, there's no way you can adopt it without having coaches or mentors that help you. I wouldn't even try to adopt Unified Process without having people who have done it before. It's too expensive and too risky to do it. But that is how it is today; it won't be like that in the future.His vision includes collaborative 'Intelligent Agents' to help make sense of the possibilities inherent in a large methodology, automated agents which make customization recommendations based on usage patterns.
Jacobson also talks about his views on UML, MDA, AOP, and the future of software development methodologies. Watch the interview: Ivar Jacobson on UML, MDA, and the future of methodologies.
When answering the question What actually is intelligence agents, is like the paper clip in Microsoft Word? Ivar talks about Expert Systems, not expo system, and Rule-Based Systems, not Ruby systems. Also, it's intelligent agent and not intelligence agent. Answering So what do you think about MDA? he talks about model and model-driven and not modern and modern-driven.
I think his views on agile development are very true. Agile development relies on the tacit knowledge of the developer's knowing what to do in software development (the process), and hopes that each developer has the same (or similar) tacit process. I also agree that most everything in the "agile manifesto" should be assumed by default - working with the client, incremental and iterative development, ...
However, I do think he left out one main difference (as I see it) between agile development and a more developed (for want of a better word) methodologies.
This is the fact that (as I see it) agile development sees the source code as the primary model for the development. To me, trying to capture analysis information, design information and all other information in the source code is a nightmare. The only thing it has going for it is that it removes the redundancy that usually (but not necessarily) exists if you have multiple models.
Perth, Western Australia
mrhatken at mac dot com
Re: Great Interview
Re: Great Interview
Martin Thompson Jul 27, 2014