By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 1,876 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Suggestions for modeling

P: n/a
I'm starting up on big project that will take much of my time in next year
or two. Until now I was mostly self-employed on small projects so I didn't
spent so much time modeling system before implementation. Sure, I wrote use
cases now and then, draw UML in Visio but it wasn't matter of life and
death.

But because of scope in next project I'm kinda frighten that sooner or
latter I along my team will get lost in poorly documentet envoirement where
no one will know what is truly purpose of system's part that they are
working on or how to connect it to another.

So, since lot of envisioning and planning are up ahead I was thinking about
sharing tought or two regarding UML modeling, drawing use case diagrams and
similar subject. What programs for creating solution architecture you people
recommend? I'm in need of something that can truly succesfuly
reverse-engeenier and forward-engeneer (UML <-> C#.NET solution). What are
your views on 2005 generation of tools (VS.NET 2005 with Visio 2005) that
are comming next month? Anyone played long enough with Beta?
Nov 17 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Of course, you will expect me to give a vote of confidence to the class
modeling tools in VS2005, and I do, to a point. You get only class diagrams
from Whitehorse and the format isn't standard UML.

If you need to actually document a system design, consider a product called
Enterprise Architect from Sparx Systems. Excellent round-trip engineering
in C#, really nice modeling environment, and is capable of working
effectively if you have one designer or a team of designers. Price is
really competitive.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Mike" <mi**@noremedy.com> wrote in message
news:Og**************@TK2MSFTNGP10.phx.gbl...
I'm starting up on big project that will take much of my time in next year
or two. Until now I was mostly self-employed on small projects so I didn't
spent so much time modeling system before implementation. Sure, I wrote
use cases now and then, draw UML in Visio but it wasn't matter of life and
death.

But because of scope in next project I'm kinda frighten that sooner or
latter I along my team will get lost in poorly documentet envoirement
where no one will know what is truly purpose of system's part that they
are working on or how to connect it to another.

So, since lot of envisioning and planning are up ahead I was thinking
about sharing tought or two regarding UML modeling, drawing use case
diagrams and similar subject. What programs for creating solution
architecture you people recommend? I'm in need of something that can truly
succesfuly reverse-engeenier and forward-engeneer (UML <-> C#.NET
solution). What are your views on 2005 generation of tools (VS.NET 2005
with Visio 2005) that are comming next month? Anyone played long enough
with Beta?

Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.