Recent Posts

Pages: [1] 2 3 ... 10
Will do once it's available.

General Board / Re: Where do I put user stories in my model?
« Last post by Kulagin on August 21, 2019, 07:23:31 pm »
I'm not sure I am following your argument, but it seems to me you could get what you want using the Specification Manager to list the contents of the Package containing the User Story Artifacts. This would show each Artifact, the notes on each Artifact and (if you enable the Document column in the Field Chooser dialog) whether the Artifact has a linked document containing the text of the User Story. You would then click on the Document icon to open the linked document. You can also add columns for specific Tagged Values, which you can create to hold any any other annotation you want, and display that in the Specification Manager as well.
Ok. From your guidelines I managed to make this:

Now I wonder how to make new element called something like ProperUserStory, add it to the toolbox, so I can drag and drop it into specification manager and it will have these 3 tagged values from the start: Description, Estimate, Priority. So I don't have to add 3 tagged values to every artifact I add or come up with hacks like having template item artifact in specification manager which I copy every time I want to create new user story.

Also it would make more sense to create new element and put Description, Estimate and Priority into requirements:

Why are they called requirements? These look much more like properties to me: status, difficulty, priority, etc.

Are you looking for a prescriptive template to create a User Story from? There isn't one 'out of the box', but you can create one to meet your personal or corporate requirements and base your User Stories on that.

So how do I create new element which meets my needs with Description, Estimate and Priority properties, which will show in specification manager and on the diagram?

General Board / Re: Diagram frame(s) are currently being displayed.
« Last post by mse on August 21, 2019, 07:17:30 pm »
Just figured it out by accident. I right click anywhere on the diagram and get a context menu. Click on Hide Diagram Frame. Save the diagram. Move the diagram to the other package. Afterwards you can show the diagram frame again.
General Board / Diagram frame(s) are currently being displayed.
« Last post by mse on August 21, 2019, 07:13:21 pm »
I get an error when trying to move an IBD or BDD diagram to another package:

Diagram frame(s) are currently being displayed.

Please disable them and save the diagram(s) before continuing.

How can I correct this?
General Board / Re: Remove version controlled view.
« Last post by Geert Bellekens on August 21, 2019, 06:54:26 pm »
First check it in, then delete it.
(if the parent package is also in version control you'll need to check-out that package as well)

General Board / Remove version controlled view.
« Last post by oiwuernnslkdjf on August 21, 2019, 06:21:56 pm »

I created a version controlled 'View' under my root model and would like to delete the view. But EA gives me the following message:

You cannot delete the selected package tree at this time.
The contained package 'FW-Tasks', is currently checked-out in this model.   

(Only reporting first found checked-out package...)

In my SVN repository a name-of-view.xml packages was created. Can I just remove xml file? I would assume not.


Please check the Versions in the Health Checks page of Prolaborate. If there is a mismatch between current and latest versions, run the latest database schema on the Prolaborate database. Choose SQL / MySQL schema based on the database server used for Prolaborate. You can get the schemas from the Prolaborate team

You might face this issue even if the above point is fine if your Prolaborate DB is on MySQL. While this bug is expected to be fixed in the upcoming build, there is a workaround available for now. Set the dashboard access to required Users/User groups as per this guide and the dashboards should work fine.
Latest News / Enterprise Architect 15.0 - Build 1508
« Last post by sparks on August 21, 2019, 05:22:35 pm »
A new build of Sparx Systems Enterprise Architect 15.0 has been released for Registered Users!

The complete release notes for the current version can be found at:
   The Readme.txt file in the EA folder, which can be accessed from with-in EA from the Start Ribbon | Help drop down | Read me...

For more information on what is new in version 15.0, please see:

Registered Users can download the release from the following location:

NOTE: Enterprise Architect now requires a Version Activation Code to be started. Your Version Activation Code is available from the Registered Users Page.

To report any issues please use the registered bug report forms:

General Board / Missing class after importing .NET solution
« Last post by mlorenz on August 21, 2019, 04:24:09 pm »
I am just trying out the Enterprise Architect Corporate edition using the 30 days trial license.
As a start I tried to import some of our .NET projects.
For hat purpose I created a Visual Studio solution containing all the projects of interest.
The resulting solution is a mix of C# and VB.NET projects.
I imported the solution using the Code->Project->Import a Visual Studio Solution
option from the ribbon.
After the import I am missing at least one important class from a VB project, although
the base class of this class which is defined in the same project has been imported.
Has anyone an idea what could be the reason or is there some kind of import log file
that could contain any information ?
You should definitely place internal block diagrams within the block itself. There are many benefits which this approach, there is simply no other way. Yes, documentation can be a little tricky, especially if I have multiple ibd:s within a block. How can you output elements from one diagram at a time in this case? I have had success doing it with document scripts following this guide:

Block definition diagrams on the other hand is normally not placed within a block, but can be in some special cases. One example is the diagram 7.10 in the book A Practical Guide to SysML (second edition). There you see the diagram header bdd [block] Camera (Power Subsystem) which indicates that the context for the diagram is a block which indicates that the diagram can be placed under the block itself.
Pages: [1] 2 3 ... 10