Although I would agree that Ada makes it easy to partition code and hence
responsibilities, I would also say that diagramming in UML, or Booch etc.,
is a necessary thing to do in order to model the system you are building
before writing package specs. Of course this depends on the complexity level
of what you are building.
Forget about having a pissing contest on which diagram technique to use; the
thing with UML is that it is a global standard, hence a language that all
developers can use to communicate design ideas. The important thing is to
utilize the diagrams to develop a design. You don't need fancy expensive
tools for this; although at some point they might help you manage/maintain
your designs. The essential thing is good old fashioned thinking and
blueprinting, and any decent drawing tool will do.
From: Team Ada: Ada Advocacy Issues (83 & 95)
[mailto:[log in to unmask]]On Behalf Of Wojtek Narczynski
Sent: Thursday, February 13, 2003 4:58 AM
To: [log in to unmask]
Subject: Re: Designing for Ada 95?
Steven Lim wrote:
>I'm wondering if there's a preferred design template for Ada?
Well, design is in fact the work of dividing the task into smaller,
manageable ones, and specifying how they interact. Ada aids this with
the package system and spec files. So other languages need external
tools for this while in Ada it is built-in.
>UML is pretty much for OO designs and Ada 95 isn't exactly OO.
Ada 95 is exactly OO - there isn't any feature missing. Or can you name
You can use UML with it, there are tools that support it, I can't recall
the name but Google for UML and Ada and you will find it.
But IMHO the whole UML is "The Emperorís New Suit" (by Hans Christian
Andersen), if you know what I mean.