Re: why can't vs 2005 class designer do UML ?
- From: "Cowboy \(Gregory A. Beamer\)" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 4 Nov 2005 07:19:34 -0600
I am not sure of all of the specifics. The class designer is very similar to
UML, although it misses many of the diagrams. I still use UML for use case
diagrams, etc., but I will stick with the class designer for work in VS
2005.
The reasons stated for moving away from UML in Visual Studio 2005 are:
1. does not translate very directly into today's technologies (in the case
of .NET, not all types)
http://weblogs.asp.net/pgielens/archive/2005/11/01/429138.aspx
2. UML has not significantly contributed to productivity
http://msdn.microsoft.com/library/en-us/dnvs05/html/vstsmodel.asp
It could also be that additional licensing for UML was cost prohibitive or
even that Microsoft found it easier to create a new type of meta-language
rather than implementing UML in VS.
Microsoft is moving towards a software factory approach, with domain
specific languages for the designers. The idea is further productivity. Will
it work?
I would say that is certainly will for those solutions that have been done
before (in nearly the same implementation). A software factory can, for
example, save time on items like workflow, which often takes a lot of time.
Software factories are not a silver bullet, however, so on has to have other
tools to simplify the R&D aspect of programming.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***********************************************
Think Outside the Box!
***********************************************
"bonk" <schwertfischtrombose@xxxxxx> wrote in message
news:%23uPFuqR4FHA.2816@xxxxxxxxxxxxxxxxxxxxxxx
> Cowboy (Gregory A. Beamer) schrieb:
>> As the class designer information is stored as XML, you can create a tool
>> that consumes the XML and makes valid UML. The main reason it is not
>> valid UML is the fact that UML is running behind .NET at this point so MS
>> scrapped the idea. If you have Team System Architect, you also have
>> access to Visio for Enterprise Architects, 2005 version, which can create
>> UML, although it is a bit of a painful route from my experience.
>>
>
> In what way is UML behind. I don't really see a .NET construct that can't
> be visualized using UML ....
.
- References:
- why can't vs 2005 class designer do UML ?
- From: bonk
- Re: why can't vs 2005 class designer do UML ?
- From: Cowboy \(Gregory A. Beamer\)
- Re: why can't vs 2005 class designer do UML ?
- From: bonk
- why can't vs 2005 class designer do UML ?
- Prev by Date: Re: Visual Studios 2005
- Next by Date: Re: What does VS2005 Conversion do
- Previous by thread: Re: why can't vs 2005 class designer do UML ?
- Next by thread: What does VS2005 Conversion do
- Index(es):
Relevant Pages
|
Loading