Regarding VP-UML 6.0 Professional Build sp1_20070420
On Mac OS X 10.4.9
I am using the following work flow which seems to work very well, except for two steps where I have to copy and paste or manually recreate existing data.
Current development workflow.
Create Use Case Diagram.
Fill in all Use Case Details.
Create Textual Analysis as a sub-diagram from Use Case Details.
Getting the details text into Textual Analysis seems to require a copy, paste and formatting from Use Case Details.
Question: Is there a way to create a new Textual Analysis based on a selected Use Case Detail and automatically copy the detail text?
Create classes in Textual Analysis.
Create Actions in Textual Analysis which will become class methods.
Create Class and Action models.
Create Class diagram.
Classes can be dragged from Model to Diagram.
Actions can be dragged from Model to Diagram, but not to a class.
Class Operations must be created manually.
Operation details must be copied and pasted from Actions to Operations via the Properties pane, Documentation tab.
Question: Is there a way to add Operations to a Class by dragging Actions from the Model onto a Class or other method?
Complete Class diagram in all detail.
Generate code from Class diagram.
Continue developing code outside VP-UML
If you could advise me on how to overcome the manual steps in the questions above or a better work flow, that would be very much appreciated.
If there currently is no way to accomplish what I have described, please consider an enhancement request.
Question: Is there a way to create a new Textual Analysis based on a selected Use Case Detail and automatically copy the detail text?
I tried your steps, the text written in use case detail will be brought to the textual analysis. (see attached image)
Question: Is there a way to add Operations to a Class by dragging Actions from the Model onto a Class or other method?
Actually operation and actor are in two different levels. Action cannot be an operation. But we are now considering to support identifying operation and attribute from textual analysis.
Thank you for the detailed instruction. Actually, I was creating the textual analysis through the cascade menu of the use case shape. Please read the attached image.
But I think your path make sense, in fact, much intuitive. I will ask our engineers to support that path as well. Thanks for your post.
Actually, I was creating the textual analysis through the cascade menu of the use case shape. Please read the attached image.
I did not see an image attached… But I presume you were referring to:
Right-Click Use Case shape in Use Case Diagram
Select Sub Diagrams
Select Textual Analysis
This did work as expected, Thank you.
I do agree that creating a Textual Analysis from the Use Case Details/Diagrams screen is the more intuitive way. This should be a useful addition to VP-UML.
From the other posts you created, I believe that you are already using Service Pack 2. But I still wanted to let you know that you can run the updater inside $vp-suite-install-dir/bin to advance to the latest release of Service Pack. Because you were using a patch, upgrading to the latest stable release is preferred.