Class Designer is a tool in Visual Studio which enables visualization of class structures, class building and refactoring. It uses a diagramming notation that is loosely based on the UML Class Diagram standard, but presents specific language terminology. Class Designer was first introduced in Visual Studio 2005, with support for the VB and C# languages. Support for C++ was developed in Visual Studio 2008.
The Class Designer team is now looking for feedback on the product. This is your chance to help us identify key areas we should consider in future versions of the Class Designer.
You can share your ideas here about new features that you hope to see in the future or your pain points. Even better, if you could try the following link to our survey form, it should only take a few minutes to complete.
Class Designer Survey: https://connect.microsoft.com/Survey/Survey.aspx?SurveyID=4421&SiteID=450
Your feedback will be highly appreciated!
Class Designer Team
Class Designer for C++ in VS2008
The most important aspect is being able to create class diagrams from existing code - quickly, easily, customizably. It would be nice to see cardinality relationships automatically reflected when, for instance, one class contains a std::vector of another.
Going the other way around (diagram to code) is a bit of a pipe dream so might be best to focus all energy on the useful direction of code to diagram.
This will sound like a rant but it isn't, after all it has been 10 years of neglect on your primary platform, and *primary cause* for migration to other tools and OSes.
First of all, I would presume you guys need to work fast on catching up with Eclipse extensibility models.
Second is that VCCodeModel or whatever it is nowhere near well documented and bug free.
The ability to create any diagram or anything else for that matter is dependant on the above.
And while finally looking to address C++ community, why not expose the tools for db work, open up the compiler front-end and plenty more.
The root of all the problems is in the front-end data model, and quality of it, how you expose it (or lack of), I wouldn't care less if bloated CLR libraries generate my diagrams or vice verse, but I will care if cannot generate what I need or be able to switch tools.
Being on the cutting-edge team (lets not go onto .NET hopefuls), you guys know better than anyone that C++ and tools for it are evolving rapidly; most importantly, without hacks that will be punished on new architectures.
And you also know that to be up-to-date with competition would be quite a challenge if you just had to do everything yourself, in standards, tooling, and an open perspective.
all while resources are leaking into all the MSIL handicaps.
Andrews cardinality suggestion is a good one. I'd also like to see some integration with the Sandcastle docgen tool. I agree that the focus should be on code->diagram rather than diagram->code, though. Thirty years has shown that classic visual CASE tools aren't all they're cracked up to be, so lets focus on the proven use cases.
Thank you for taking the survey, we got precious ideas from you!
The survey will be closed by the end of this week, but you can still share
with us your thought about Class Designer.
Our site accepts suggestion and bug submission all year round:
Thanks again for your help!
Please make template class friendly. VC2005 has some sort of difficult on dealing with class templates. It would be nice seeing class dependency regardless of its template arguments.
My 2 cents.
This is non-intuitive since you're discussing modeling tools, but it is very important for coders (who lives in Unix world and want to move to Microsoft world). Please add feature in C++ ( or any DotNet languages ) to allow annotations within the code specific to the modeling tool. Mouse clicking in a modeling tool is very tiresome and non-productive for coders, even if it is the best modeling tool it the world (I've used CASE tools like IEF).
Then, allow the modeling tool to scan the source code for those annotations to quickly build a graphical representation of the BUSINESS logic (not the c++ syntax like Doxygen tool on unix).
Think of PerlDoc as a precursor to the in-line documentation/notation for your Modeling annotation syntax in C++ source code.
This will eliminate the 'writer block' that a coder would face when using a modeling tool for the first time. i.e. why sit for an hour with a mouse, when one could start coding already. :)
Round-trip engineering is severly handicapped. Having annotations specific to the modeling tool would eliminate this discrepancy. :)
Class Designer team would like to thank you for taking our survey and sharing with us a lot of great ideas.
Top areas where people think we should pay attention to in future Class Designer are:
Customizable code template
Creating more types through CD
Better support for large diagram
Keep up with language innovation
Thanks again for the feedback!
All I want is for VC++ to have
Code -> Diagram, and
Diagram -> Code
"Real time" C# like would be nice, but I'll take roundtrip for design and later documentation.
I am pretty sure we were promised that for next release when it was cut from 2005 studio 2 years ago.
just like rational rose please
Dear all, Class Designer is a tool in Visual Studio which enables visualization of class structures, class building and refactoring. It uses a diagramming notation that is loosely based on the UML Class Diagram standard, but presents specific languag