File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Agile and Other Processes and the fly likes RUP and non-OOP Development Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "RUP and non-OOP Development" Watch "RUP and non-OOP Development" New topic
Author

RUP and non-OOP Development

Marcellus Tryk
Ranch Hand

Joined: May 31, 2001
Posts: 64
I work in a AS/400 shop where development is done in RPG. In case you aren't familiar with RPG, it is a distinctly non-Object-Oriented language. We are interested in adopting or developing a disciplined development process and there's some interest in the RUP. My impression of the process is that it is strongly rooted in UML and OOAD. I can see elements (e.g. use cases) that could be very beneficial to us and others that might be difficult to map to our development technology (e.g. class diagrams). I realize that the RUP also includes large pieces that must be universally appropriate (e.g. test planning). I would really be interested to hear comments from folks who have experience with the RUP on how difficult it might be to apply to a non-OOP development environment.
Thanks!
Marcellus Tryk
[ January 10, 2003: Message edited by: Marcellus Tryk ]
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
RUP is a process *framework*, that is, it gives you a bunch of elements to construct you own process from. You have to decide for yourself how to combine those elements so that they make sense to your situation - or you could start with a pre-configured instance and adapt it as you learn about your needs.
http://www.objectmentor.com/resources/articles/RUPvsXP.pdf describes an instance of RUP wich is IMHO very well suited for a colocated team of up to a dozen developers. It isn't dependend on the used programming paradigm.
[ January 11, 2003: Message edited by: Ilja Preuss ]

The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Marcellus Tryk
Ranch Hand

Joined: May 31, 2001
Posts: 64
I understand that the RUP is like a 'salad-bar' methodology. But I would like to know if anyone out there has experience applying any or all of the process to non-OOP development.
Thanks,
Mars
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Well, *there are* non-OO projects using XP (the instance of RUP described in the paper above).
The XP practice which seems most coupled to the used paradigm seems to be refactoring to me. I already successfully used refactoring in a small Prolog project, so I am rather positive that there shouldn't be many hurdles. Can't help you with more experience in this regard, though.
Are there any more specific doubts you'd want to discuss?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: RUP and non-OOP Development