![]() The tools that I've seen attempt to auto-generate diagrams don't really help unless the desired aspect is quite simple. ![]() A modeling/diagramming tool cannot really determine what to include in a given diagram because it can't really know what aspect you mean to emphasize or what is important for the perspective or purpose you intend. Martin, I think your response is on the money but I may be able to add some value.ĬuttiePie, a diagram generally emphasizes some aspect of a system from a particular perspective and for a particular purpose - I'm sure I lifted that from one of the Three Amigos' books. ![]() I hope that helps you, and I'm sorry that it probably wasn't what you wanted to hear, I'd imagine once it is implemented and has associated unit tests (you do have unit tests, right?) then that would be sufficient implementation documentation? What are you after a sequence diagram for? Documentation after the fact? An approach could be to use the debugger, and make notes on the call stack during operations, so that you can then use Visio EA to diagram what you find? I'm not sure how useful a sequence diagram would be in terms of documentation, as it is often used to check for gaps in implementation, or to document how some functionality is to be implemented. You can certainly use Visio, or better still Visual Studio 2005 to do UML diagramming for class diagrams though, but it seems that you don't actaully want to do that? If you could do that then you'd only get a sequence diagram for that particular state data. Also the code should be sufficiently decoupled, and using interfaces such that you may not necessarily know which class implementation of an interface would be used whilst running you code, or at least not without supplying it with some form of state data. ![]() ![]() You wouldn't necessarily be able to infer a sequence diagram from code, since when it runs, it often has state, external resources and so on. As far as I'm aware Visio won't let you reverse engineer into sequence diagrams. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |