Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - jplusip

Pages: 1 [2] 3
Uml Process / A way to create a text based class/template?
« on: July 26, 2014, 12:47:07 am »
What I mean is this:

I would like to have a model element that I would have in a library that users could drag from the library, onto their diagram, and have an instance of these annotations appear on their diagram (where each instance will have the information filled in). However, if I make any changes to the parent model element in the library, those changes would propagate throughout the model.

Is this doable in Sparx EA?
(And before anyone brings it up, I know the Diagram type is in the top-left, this is just how I was instructed to make this).

Uml Process / <<signal>> in EA
« on: July 25, 2014, 02:51:46 am »
I'm trying to model a group of signals that will inherit from a primary signal type, however, it doesn't seem that signals in EA have structural properties (as a block would).

So should I just treat signals as I would in UML (that is, given them attributes) or is there some other way to assign value properties to signals? I've made BDDs using composition between a signal and various Properties, but I can't seem to find a way to verify that the signal has those properties (or that they are being inherited by the specialization signals).

Uml Process / Inheritance of attributes in EA
« on: July 17, 2014, 01:58:23 am »
I made a thread like this earlier but deleted it when I realized that my operations would only be inherited by my subclass if I created the generalization association after I had filled in the operations.

However, now I'm running into an issue where the attributes of a superclass are not being inherited by the subclass regardless of what I do. Is there something I need to switch on in EA so that attributes can be inherited in a generalization association?  :-?

Uml Process / How to view metamodels for stereotypes in EA?
« on: July 10, 2014, 07:24:03 am »
Hi all,

 I'm a new user to EA (long time fan of UML (and more recently SysML) though).

I'm playing around with EA and I noticed that under the steretypes drop-box there is a considerable amount of stereotypes, but I have no idea what the point of these are. Is there a way I can access the profile(s) for EA and have a look at the metamodels so I can understand the different stereoptypes?

Generally I've just used it to bring in model elements, but now my team is trying to bring in an Access database that has relationships built in.

Is there a way for them to export CSV files in such a way that we can create the relationships between model elements that they have in their database?

Using a SQL query, how do I pull the image of a diagram out? Looking at the tables in Inside EA, I'm not seeing anything for the actual diagram image.

Automation Interface, Add-Ins and Tools / Weird template selector issue
« on: October 14, 2015, 05:05:59 am »
This is actually related to the SQL issue I posted about earlier (of course, once the SQL issue was fixed, another one arose).

Basically, I have a template selector that's supposed grab an element with a specific stereotype and then call another fragment that will run the following SQL query:

select p.Name as Property, p.Note as Description, v.Name as DataType, u.Value as Unit
from t_object as s, t_object as p, t_object as v, t_objectproperties as u
where p.ParentID = s.Object_ID and v.ea_guid = p.PDATA1 and u.Object_ID = p.Object_ID and u.Property = 'unit'

Now, for the template selector I'm using the type signal and a special stereotype for each element (to generate a table for each element at different parts of the auto-generated document). So let's say the selector statement looks like this:


Then I have a template that calls the template selector.

Now, when I run the template, the selector grabs the proper element and generates the proper table... and then keeps going with a bunch of other elements (basically, it seems to be grabbing random parts from other signals in the project and placing them in the table). I've added SQL statements to display the package names and parent names of the additional elements, and they aren't child packages or child elements of what I'm originally running the reports on. In fact, even if I run the generator on the one package that (only) contains the element I'm trying to run the report on, for some reason the table keeps adding stuff from other packages and elements. I've even tried moving all of the parts out of the signal, deleting the signal, and then recreating it from scratch, and I still get the same issue. Then I tried moving all of the parts of the signal and running the report again: this time none of the parts that I wanted in the table were there (as they shouldn't have been as I moved them out of the signal), but all of the extraneous stuff was still there.

I also tried adding the SQL statement s.Name = "NameoftheElement" and abandoning the selector, but then the table generated itself repeatedly for 364 pages.

Any idea on what might be happening here?

Using a selector, I'm grabbing a stereotyped signal and then trying to generate a table based on its parts. The SQL query is:

select p.Name as Property, p.Notes as Description, v.Name as DataType, u.Value as Unit
from t_object as s, t_object as p, t_object as v, t_objectproperties as u
where p.Parent_ID = s.Object_ID and v.ea_guid = p.PDATA1 and u.Object_ID = p.Object_ID and u.Property = 'unit'
order by p.Name, p.Notes, v.Name, u.Value

Where s should be the signal, p should be its parts, v should be the value type that types the part, and u should be the unit (SysML 1.3 tag).

For some reason I keep getting a DAO error saying there are too few parameters, and then when the document is generated it's blank aside from the line of text I'm using to confirm that the selector is working.

I assume there is something simple I'm missing, but I'm just not catching it.

So, in a SysML project, I have some parts (otherwise Properties) that are being typed by defined valueTypes. I would like to extract this type in a SQL statement, but all Object_Type extracts is Property (which is the type).

Is there an alternate "Object_Type" that I can use to grab this information?

Automation Interface, Add-Ins and Tools / What is wrong with this SQL query?
« on: September 23, 2015, 11:48:13 am »
I'm trying to write a SQL query that will do the following:

Considering a signal with properties (parts in this case, as it's SysML), some of which have properties of their own as embedded elements, I want to output a table such as:

FieldDescriptionData TypeUnit

Where the Field will be the name of the property, the Description should be the name(s) of the children properties of that property, the Data Type should be the Type of the subproperty,  and the Unit should be the stereotype of the subproperty (since I don't know how to grab the "unit" defined in the value types that I'm using).

The SQL is as follows:
select s.Name as Signal, f.Name as Field, p.Name as Description, p.Type as DataType, p.Stereotype as Unit
from t_object as s, t_object as f, t_object as p
where f.ParentID = s.Object_ID and p.ParentID = f.Object_ID
order by s.Name, f.Name, p.Name, p.Type, p.Stereotype

And during document generation I get an error DAO.Database[3061] Too few parameters. Expected 1, and the resulting document is... blank.

Any ideas on what I'm doing wrong here?

So, I'm trying to make a template selector so that whenever the document generator hits a property it generates a table with the property's name and any associated requirements.

So I create a template fragment called Property-Req:

Then I create another template fragment called Prop-Req-Selector and went to Document Options and set the query under Template Selector:

I then made a template called testing where I just run the Template Selector:

But the only thing that pops up when I run that is the name of the package (despite a property and satisfied requirement being in the package; also, only one package name runs, so its the one being called in the original template, not the one in the selected fragment).

What am I doing wrong here?

These are SysML properties I'm trying to work with. Might that make a difference?  :-/

Specifically, I'm working with the Template Selector and I want to know what the type for a SysML sequence diagram is. I looked at the Template Selector example, and I see UMLDiagram, but does that apply to the SysML diagrams?

What I would like to do:
Run a report on the Root package that goes through the entire model and generates a report, where different packages have different reports.

I guess the best way to describe it is that it would be like a Template Selector, only instead of looking at types/stereotypes, it would just look at PackageID and run a fragment on that package only.

Though now that I think about it, maybe applying different stereotypes to those packages would work. I guess I'll test that out, but if there's a better way I'm all ears!

Stereotype idea didn't work (if anyone is wondering). The Selectors just ran the fragments on the packages and ignored the elements within them.

So... back to square one: how do I do this in the tool?

When using the built-in document generation capability in EA, how do I get to information about the parameters/action pins on an activity/action? The Child Elements selection doesn't seem to be picking these up, and I have no idea what else they would be listed under.

What I would like to do:
Have a package A which contains packages B, C, D, and E.
B, C, D, and E each has a sequence diagram in it.

I want to run a report on A that uses the following template fragment to report on information from said sequence diagrams.

Ideally, I would like to run one report, as opposed to running a separate report for each package and inserting that information into the larger report. I know the report generator function can go more than one package deep (the Model Report does this), but for the life of me I can't get it to do this. childpackage> is too far down the list and I can't insert elements from those packages from there, and inserting template fragments only works under package>, not childpackage>, so I'm not able to say "OK, starting with this package, only extract the elements from the child packages".

Any help would be greatly appreciated.

Picture isn't working (on my browser at least) for some reason, so the direct link is here:

Pages: 1 [2] 3