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 - RoyC

Pages: 1 ... 68 69 [70] 71 72 ... 81
Uml Process / Re: help me please
« on: March 07, 2013, 04:45:52 pm »
Can you explain why you are asking the question? What is the problem you are trying to address? (And therein lies a clue to the answer you are seeking!).

Uml Process / Re: Icon in Node
« on: August 30, 2012, 09:31:35 am »
Yes, your custom element would have a stereotype that applies a shape script to define the object's appearance. Part of this shape script would define the position and appearance of a decoration, which is what the 'in element' icons are.

There is a small example of adding a decoration in a shape script, towards the end of the Write Scripts Help topic.

So, your MDG Technology would contain a profile that defines Stereotypes, one of which would apply to your custom Node element, and that stereotype would contain a shape script that defines a decoration.

Uml Process / Re: VHDL
« on: July 17, 2012, 05:03:15 pm »
That's true - Hardware Description Languages can only be generated in the Systems Engineering and Ultimate editions of EA.  What is your 'standard' edition - Professional or Corporate?

If you are going to work with VHDL, it might be worth your while upgrading to the Systems Engineering edition.

Uml Process / Re: VHDL
« on: July 17, 2012, 09:27:53 am »
Have you looked up VHDL in the Help index? There is a Diagram Toolbox for modeling VHDL - View | Diagram Toolbox: More Tools | HDL | VHDL Constructs.

Uml Process / Re: Skipping steps in a use case alternate flow
« on: February 23, 2012, 09:30:50 am »
(Extrapolating from the letters of your steps) wouldn't you make your alternative path take effect at step w of the main flow and say "if {condition} then step out and rejoin Main at step z"?

Uml Process / Re: View vs Model
« on: October 17, 2011, 05:05:52 pm »
Starting from scratch, you create a Project. Within your project, you create one, or more than one, root node model. You can call these what you like, but there is no automatic difference between them. They are simple containers for the model structure.

Under the root node, you can create either:

  • A context-specific Model (or Model Package), using the Model Wizard; this model contains a framework of packages, diagrams and elements from which you can develop your model, or
  • A View (NOT through the Model Wizard) which is not generated with any components. It starts life completely empty, and is there for you to add another layer of classification within your model. Five of the Views have special icons, but these are purely visual flags in the Project Browser, to remind you that "Ah - there is where I am creating all my Use Case stuff".
You can then go on to create the model structure underneath the Model Packages or Views, noting that:

  • You can create a hierarchy of Model Packages under the View or the top Model Package
  • You cannot create a View underneath anything other than a root node.
BUT we come to this variation of the Model Package called a Simple UML View. Regard these as Views, but with three differences:

  • A SUV is generated with an empty diagram
  • There are three extra SUVs - Requirements, Analysis and Testing
  • You can create SUVs at any level of the model, not just under a root node.
Don't get too wrapped up with Views - they are there to give you a little extra flexibility in slicing and dicing your model structure, but they are not vital components.

Uml Process / Re: UML best practice: Attribute or Association
« on: August 10, 2011, 04:53:57 pm »
Geert, you're a block-head.

(Well, you DID say....)

Nah - you're a very respectable gentleman, guv'nor.

Uml Process / Re: UML to XML
« on: December 20, 2010, 09:31:42 am »
I asked one of our engineers to take a quick look, and this is his response:

>> The attribute "e1" is referring to the class "C2". Whereas, the attribute "e2" is referring to "Unknown" which does not exist in the model.

When generating XSD, the XSD Generator could resolve the type of the attribute "e1" (as it exists in the model) and hence it has no trouble validating this attribute.

But, it throws a warning when validating the attribute "e2" because "Unknown" does not exist in the model.<<

There is a screenshot too, but I can't seem to get it into this post. I'll email it to you - if I can.

Uml Process / Re: UML to XML
« on: December 09, 2010, 02:29:16 pm »
I would say that you have not (properly) defined a file path for the XSD file being generated. Please follow this procedure carefully:

There are a few points where you help the generator locate and use the file path for the generated file.

Let us know if things still don't work.

Uml Process / Re: Triggers, Events and Signals
« on: October 11, 2010, 09:45:30 am »

Did you read this topic in the Help? (Sorry, I know you want to be a Hoopy, Froody kind of guy, but just assume that the Help, too, begins with the words "Don't Panic".)

You can create Triggers as properties of Transition relationships, and they are of type CallEvent, SignalEvent, ChangeEvent or TimeEvent (although EA code gen for state machines currently only supports the last two).

You shall go to the ball. Sorry about the planet though.

Uml Process / Re: Triggers, Events and Signals
« on: October 05, 2010, 10:33:53 am »
OK - I take the point. I'm also not going to stand around being pedantic whilst Neil is being so casual with loaded guns!

Does Dan understand the distinctions now?

Uml Process / Re: Triggers, Events and Signals
« on: October 04, 2010, 04:44:31 pm »
No - I think beginner is correct. He isn't saying that a trigger causes a transition, he is saying that a trigger is a transition, which is broadly true. Nothing happens until the trigger occurs, then the triggered event takes place. A bullet remains static until the trigger changes state from NotPulled to PulledRightBack, at which point a firing pin causes an explosion and the bullet gains velocity. (I guess you can analyse a process down to the atoms and beyond, but there is a point of no return somewhere up to which is stasis and beyond which is reaction).

Uml Process / Re: Statecharts
« on: October 20, 2010, 09:11:21 am »
I'm guessing that you might have already seen this page:

but it does explain the relationship between State diagrams, State Machine diagrams and State Charts, and it links to the following topic on generating SW code from State Machine diagrams.

These are applicable to build 856 of release 8.0.

Uml Process / Re: mapping to Reference Models
« on: September 14, 2010, 03:51:31 pm »
Sorry Geert - you might have to be more precise in describing your set up. Can you distinguish between projects, databases and models?

It sounds to me as if you have a project on database A and a project on database B, and each project contains a Solution Architecture model plus a [copy of the] reference model. I don't think that Neil is concerned (yet) about the security and version control of the reference data model.

Looking at the question that Neil asked in his original post, if the project contains two models (which is quite common), there is little difficulty in creating relationships between elements and objects in one model and objects in the other. Your last post seems to discuss that. The Relationship Matrix might be the easiest tool to do that.

If you are saying that the Reference Model lives in another project (on another database?) then things are more complicated as beginner suggests. In that case ... carry on, Sar'nt Major.

Pages: 1 ... 68 69 [70] 71 72 ... 81