in reply to UML and perl

I think we have a bit misunderstanding of what UML is for:

It is definitely a good idea to describe your system and user requirement in UML, and that is true across prorgamming languages.

To me, UML is the tool to reduce miscommunication among people.

Replies are listed 'Best First'.
Re: Re: UML and perl
by exussum0 (Vicar) on Dec 24, 2003 at 02:18 UTC
    UML class and sequence diagrams can be directly translated to any language supplying the types exist in that language which you point out (indirectly). That seems to be his goal and what he's asking for advice on.. if it's smart or good or whatever... not if by using UML, will he avoid writing any code.

    Play that funky music white boy..
[reply]
Re: Re: UML and perl
by drfrog (Deacon) on Dec 24, 2003 at 17:15 UTC
    I agree!

    the point i am making is that ramping up to development from the pre-production stage is possible from properly laid out uml diagrams

    i find problems in uml's how-to's in describing perl objects.

    I guess i could reverse engineer some perl objects to see how it should look!

    Again , i do think UML's main purpose is to help in pre-production, but i also think it can provide a useful linkage to production, helping a developer set up the perl modules for a project, wasting less time in setting up for the development stage
[reply]
      It also helps in post and in production systems. When a system breaks or needs to be maintained, jumping into someone's code isn't easy. With various UML diagrams, it's really easy to at least know what relates to what.

      Play that funky music white boy..
[reply]

In Section Seekers of Perl Wisdom