Messages

1

General Board / Re: Deployment of components

« on: October 03, 2007, 06:33:39 am »

I think it was changed in 2.0, but it might have been 2.1.

EA didn't enforce it initially, but eventually one of the 6.5 builds declared it a "non-compliant" association.

2

General Board / Re: Deployment of components

« on: October 01, 2007, 11:32:30 am »

I could be mistaken, but its my understanding that the latest UML specification doesn't support the deployment of components directly.  Components are manifested as artifacts and the artifacts are then deployed to nodes.

I believe that was the response I got when I reported this a while back.

3

General Board / Re: Sharing Enterprise Model to a Project Model

« on: December 09, 2006, 06:29:30 am »

In our scenario, I think we've solved the ability to lock the enterprise repository.

What we did was create two seperate subversion repositories, one for the Enterprise and a second one for the projects.  Since each of them is in a seperate folder on the file system, we can set read-only access at the file system level for the Enterprise folder.  This allows EA to do things like get latest, but not establish a check out.

Thanks,
Paul

4

General Board / Re: Sharing Enterprise Model to a Project Model

« on: December 04, 2006, 01:44:20 pm »

I've looked at the controlled packages and it seems to work.

Here is the scenario that I followed and a question around "security":

Place packages in the Enterprise area under control.

When extending an Enterprise package, you must add the package from the enterprise repository.

You must add the Enterprise configuration management to the project model.

Do not allow users to check out these areas under their project.  (This is my question now)

Users can use the elements from the Enterprise packages in other areas of their model, but they can not modify the Enterprise elements without checking out the Enterprise package.

When the project package is brought into the Enterprise, then links are established to the Enterprise components.

How can I prevent the users from being able to check out the Enterprise packages?

5

General Board / Sharing Enterprise Model to a Project Model

« on: December 04, 2006, 10:29:58 am »

I’m wondering how EA supports the following scenario (I’ve tried searching the forums, but no luck on this scenario - perhaps I'm using the wrong terms):

In Model A I’ve got a package with elements in it, let’s say components like Microsoft Server 2003 and Microsoft SQL Server.  In Model A these components are associated with different things in other packages within Model A.

In Model B I want to use these components and associate them with things specific to Model B, but I don’t want to create new elements since I’ve already got those elements modeled.

Model A and B are currently separate EAP files.  I’ve tried exporting the Package from Model A and importing it into Model B.  After the initial import, the links for the elements show the Model A associations.  However after adding new associations in Model B, those Model A associations disappear.  Additionally, when I then export from Model B and go to import into Model A, the original associations are gone and only the Model B associations are present.  Also, existing diagrams have the Model A specific associations disappear because the import from Model B did not contain them.

Does this particular setup seem reasonable?  We’ve got a repository of things that we’ve already modeled (Enterprise view) and we want to allow others to use them in their models (project view), but we want to control their ability to update the repository.  Can we do this with separate EAP files or do we have to setup a SQL Server repository?  How would we secure that setup and still allow people to use repository elements when they wouldn’t have update authority on the repository.

I know this sounds and awful lot like the “merge” functionality that people have been talking about and if it is the same, is that on the horizon?

6

General Board / Re: Setting Instance Inherited Attribute Values

« on: December 08, 2006, 05:55:30 pm »

Thanks Paolo, that was exactly what I was looking for.

Maybe you can tell me how to get the HTML generator to include the Run States too?  The RTF generator does include the Run States.

Paul

7

General Board / Re: Setting Instance Inherited Attribute Values

« on: December 08, 2006, 03:24:53 pm »

I've got it showing the attributes in the Instance, but I'm trying to actually set attribute values associated with the instance.  

I thought that because it was an instance you could set those attribute values specifically for that instance.

Paul

8

General Board / Setting Instance Inherited Attribute Values

« on: December 08, 2006, 01:45:07 pm »

My issue is around setting the attributes of the instances that are added because of the generalization.  Perhaps I'm missing a core UML concept and somebody can explain it to me.

Class1 is a generalization of Class2.  Each class has attributes assigned (attrib1 for Class1 and attrib2 for Class2).  After turning on the show inherited stuff feature, Class1 correctly shows both attributes (attrib1 and attrib2).

Now I want to create an instance of Class1 named Paul.  Again it correctly shows both attributes within the box, however it doesn’t show me attrib2 in the attributes box, where I could set values associated with the instance.  I can set a value for attrib1, which is directly contained within the classifier that the instance is based on.  Why can’t I set a value for attrib2 which is included because of the generalization?  Also, when I change the attribute values on the instance it updates the original class as well.  I wouldn't have expected an instance to update the source class.

Thanks,
Paul