Re: does a software architect need UML skills?
- From: "Chris Mullins [MVP - C#]" <cmullins@xxxxxxxxx>
- Date: Mon, 5 Nov 2007 09:37:18 -0800
"Jon Skeet [C# MVP]" <skeet@xxxxxxxxx> wrote
UML is the standard for diagrams in the industry.
That doesn't mean it's the only - or even the most effective - way to
communicate.
Certainly true. But for the same reason I'm unlikey to write this message
out in Hmong, I'm unlikey to go with a Software Diagraming language nobody
has ever heard of.
The reason we write is (often) to be understood by as wide a range of people
as possible. If we each created a new diagraming language for each problem
we came across, the results would be a complete lack of ability to
communicate with each other.
Every professional field has a set of language tools they use to communicate
with each other. In some professions, these languages and tools have evolved
over a very long people of time and are very mature. Civil Engineers, for
example, can reasonably expect to read a set of plans put together by just
about any other Civil Engineer the world over. Electrical Engineers and
Architects as well can expect this.
In Software Engineering this is now possible through UML. This langauge
allows engineers well versed in Java, C++, .Net, Basic, and other langauges
to communicate with each other.
--
Chris Mullins
.
- Follow-Ups:
- Re: does a software architect need UML skills?
- From: Jon Skeet [C# MVP]
- Re: does a software architect need UML skills?
- Prev by Date: Re: Drag and Drop
- Next by Date: Re: Predicate methods like TrueForAll() for IEnumberable<T>?
- Previous by thread: Re: does a software architect need UML skills?
- Next by thread: Re: does a software architect need UML skills?
- Index(es):
Relevant Pages
|