Last post Jun 24, 2011 11:23 AM by LudovicoVan
Jun 24, 2011 08:30 AM|ugh3012|LINK
I hope I posted this in the correct forum. I am working on existing huge web site. It consists of multiple projects (or solutions as the term is used in VS 2008) that work together on the production server. What I need to do is to reverse engineer them into
some kind of diagram using MS Visio. I looked it up on the internet and I see that there are different kinds of diagram. All serves it purposes, but, in your opinion, which diagram would you use to document all the aspx pages with their conditions that determines
which page to go next.
Jun 24, 2011 08:46 AM|anujtripathi|LINK
My personal suggestion, no particular diagram. I would rather look into the business flow of the applcation and decide the strategy/design flow which suits my requirement.
Some page requires Sequence diagram as they have heavy logic inside them, an simple example below
If it is needed to be documented in PDF/DOC then you can embedd your pages in a diagram like below
if you website is quite huge then it would become too messy to incoporate all the pages in one page, a business workflow can make the collection of pages which falls under the same categories and then you can define each category.
Jun 24, 2011 09:06 AM|GPankaj|LINK
I assume you are using VS 2008. You can right click on the project and generate class diagram.
Here is a link that gives a nice representation of the diagram
Reverse engineer a VS 2008 solution into a UML diagram
In VS 2010 we have the architecture diagram
Hope this helps
Jun 24, 2011 11:23 AM|LudovicoVan|LINK
> which diagram would you use to document all the aspx pages with their conditions that determines which page to go next
Look up Interface Flow Diagrams.