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.


Messages - ChB

Pages: 1 [2] 3
16
Peter
I can't quite follow your issue and I notice nobody has replied.  Perhaps if I show how I'm trying (and failing) to reproduce and understand your scenario we'll get this thread moving.

In EA 12.1 Sys Eng Ed...
I create a SysML 1.4 Block Definition Diagram.
On that diagram I add a valueType (myType) and an interfaceBlock (myIblk).
In the interfaceBlock I create an out flowProperty of type myType.

I then add both a block and an interfaceBlock (I'm not sure which you're using) and add a generalisation connecter between them and the first block, myIblk (with the arrow at the first block's end).

If I use right-click, Structural Elements, on the two new blocks the flowProperty is shown, in the compartment of the child blocks, as out, not inout as you describe.

However, via the Properties dialog for the two new flowProperties, in the Tags tab, I see inout shown.


Is this what you're doing Peter?  Does my scenario demonstrate your issue?


17
Bugs and Issues / Re: Handling of enumeration Tagged Vlaues
« on: April 15, 2016, 06:19:53 pm »
I was just thinking: "Yes, that must be irritating", but then "why has it never bothered me?".
The reason is that I'm only using tagged values in combination with UML Profiles (like they should be used in fact  ;D).
So I never need to add a tagged value myself, they are already there.
Geert

Insightful, thanks Geert.
But bother (lol), I wish I was confident about setting up profiles.  I'm working with SysML <<blocks>> at the moment and I want everyone of them to have an enumerated tag that I've created.  I can only imagine how Geert's suggestion would work ;-)

18
Bugs and Issues / Re: Handling of enumeration Tagged Vlaues
« on: April 14, 2016, 06:33:12 pm »
However, if you're manually creating it using the Add Tagged Value, once selected,  the default value is provided but the value can't be changed.  You have to create the value then go back in and change it.
Is it just me, or does this suck conceptually? 

+1
Me too: I've been irritated by this and feel it could be improved.

19
General Board / Re: SysML enumerations
« on: April 08, 2016, 07:49:06 pm »
Yes, it's working for me too.  I've converted some of my model to use an enumeration that's stereotyped as a valueType.   Where I used to use an "ordinary" valueType I'm now using an enumeration stereotyped as a valueType.

It's looking good so far and "makes sense" for human-to-human communication using my model.

Thanks all. Hope this thread is useful to others.

20
General Board / Re: SysML enumerations
« on: April 08, 2016, 06:00:02 pm »
The ValueType stereotype can be applied to an enumeration...

Oh yes, that could be exactly what I want.  Thank you.

21
I suggest it's simply a "weakness" of the book - nothing more than that.
I feel the weakness starts in Chapter 1, Figure 4, where the Model System Behaviour roadmap does not show Activity Diagram creation even though the text beneath states that Activity Diagrams are part of Behavioural modelling.

Activity Diagrams are mentioned in Chapter 3 (last paragraph between figures 11 and 12, and in second from last paragraph of Chapter 3) .

I think the book could be "improved" by including Activity Diagramming in the Chapter 1, Figure 4, roadmap and with an example in Chapter 3.

Activity Diagrams feature more heavily in Chapter 7 when discussing code generation.

I've found it a "good book" as it discusses a "process" or "methodology" that I can apply to the type of work I do.

(My opinions only. Hope this helps.)

22
General Board / Re: Change use case color
« on: April 07, 2016, 01:01:10 am »
MatthiasVDE

If you want to color your Use Case (or other) elements according to some "status" then Rudi's suggestion of a Legend could be what you need.

And you can change/add to the list of built-in status using:
  • the menu option: Project, Settings, Project Types, General Types, Status
  • or menu option: Diagram, Appearance, Configure Status Colors...
That will let you add status of Busy and Done and choose what color you want for them.

See here in the User Guide: http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/statustypes.html  Note the bit about "Applies To" Use Cases.

And for Legends: http://sparxsystems.com/cgi-bin/search/search.pl?Terms=Legend&Realm=12.1+help

Note that I'm using EA 12.1, I think some menus have changed from version to version.

23
Yes I see what you mean. I've managed to reproduce the problem (and the workaround of making the port bigger than apparently necessary).

The width of the port (or height depending on which edge the interfaces are on) needs to be long.   I get the same problem with nested and not-nested ports.

24
Have you tried: Right click on port (the owning port), Advanced, Port Size Customizable.  And then make the owning port larger to make space for the nested ones?
Is that the problem/solution?

25
General Board / Re: SysML enumerations
« on: April 06, 2016, 06:19:42 pm »
Yes, SysML spec. has several weaknesses and a good example is the enumeration that is just mentioned to be existed but nothing else.

For the record, for other people searching this forum:

Agreed, I could not find a useful explanation or example of Enumeration in the SysML 1.4 spec.
Furthermore "A Practical Guide to SysML" by Friedenthal, Moore and Steiner (3rd edition covering 1.4) didn't help either.

I'm not sure but I think Enumerations would be useful when creating type (stereotype) extensions in a company or project specific profile.... but that's a dark mystery for me at the moment.

26
General Board / Re: SysML enumerations
« on: April 06, 2016, 12:01:11 am »
Many thanks Peter, that's a clear explanation and suggestion.

Regarding enumerations you said: "it goes for some reasons into the properties compartment".

I suggest this is not an EA quirk because the SysML 1.4 spec states:
Quote
A property typed by a SysML ValueType is classified as a value property, and always has composite aggregation.  [...]  Properties of any type may be shown in a “properties” compartment or in additional compartments with user-defined labels.
(That's from section 8.3.2.3 of http://www.omg.org/spec/SysML/1.4/PDF/ )

This feels like an SysML weakness, not an EA weakness but I like your suggestion Peter, I think that generalisation connector will convey sufficient detail.

27
General Board / SysML enumerations
« on: April 05, 2016, 10:42:25 pm »
Hello All,

I'm using SysML 1.4 in EA 12.1 SysEng Edition to model a system (electronics, software and some mechanical aspects).

I'm performing high level design using SysML 1.4  <<block>> elements and have been happily giving some blocks "value" properties typed by a <<valueType>>.

I've defined valueTypes for things like "speed", "power", "temperature".   All good so far.  I can create value properties for blocks using these valueTypes.  And I can use the same valueTypes for flow properties.

I'd like a block to have a value property which is of an enumeration type.  How do I model that?  I can create <<enumeration>> elements and use literal attributes to define the set of possible values of that enumeration but I can't use the <<enumeration>> to type a block's value property.  Block properties that are typed with <<valueType>> are shown as "values" whereas those typed with <<enumeration>> are shown as "properties".

How do I define a valueType for something like "color" which can only have values Red, Orange, Yellow, Green?  And use that as the type of a block's value property?

Note that the purpose of the "model" is to communicate to other team members, we're not intending to generate code or perform simulations etc, it all about human-to-human communication.

28
Partially solved:

A bit more Google-foo and I've worked out how to get just the date part of the date-time field.  Thanks Geert for the hint that refined my Googling:

select count(*) as Count,
       format(t_object.CreatedDate,"short date") as Creation_Date
  from t_object
 where t_object.Stereotype like '*requirement*'
 group by format(t_object.CreatedDate,"short date")
 order by format(t_object.CreatedDate,"short date")


I then copy those results to Excel for charting.

I shame I can't use EA's built in time-series charting gadget.


29
General Board / Extracting date-series data from EA (not date-time)
« on: March 23, 2016, 10:32:37 pm »
I'd like to have some time-series graphs such as "requirement count over time" and "Use Case count over time".

I think the built-in time-series dashboard chart can't be run retrospectively: I think it only generates a data point when it is run manually.  I want a graph that starts from a date in the past.

I'm using EA 12.1 with a local .eap file (jet).

I'm thinking I'll write a simple SQL Query to extract the data and then chart that in Excel.

An SQL Query like the following doesn't work because the CreatedDate field is a date & time.
select t_object.CreatedDate,
       count(*)
  from t_object
 where t_object.Stereotype like '*requirement*'
 group by t_object.CreatedDate


How do I get my query to return (and group by) the date part only (not a date-time)?

I assume I'd manually run the SQL Query in EA and then copy the data to Excel.

30
Suggestions and Requests / Re: Relationship Matrix Filtering
« on: March 23, 2016, 01:00:11 am »
Thanks Geert.
I think using a custom SQL search (as you suggest) in the Source or Target of the Relationship Matrix gives me the filtered view I want.  That might be what the original poster needed too.

Pages: 1 [2] 3