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 - Stephen Kropp

Pages: [1]
1
Uml Process / Information Flow vs. Dependency Relationship
« on: October 28, 2016, 03:19:09 am »
I am working on a SysML Block Definition Diagram to display the as-is relationship of actors within my system. For my example let's call one of the actors the "Service Department" with a generalization to the second actor called a "Field Service Technician".

I have an information flow depicted between the two actors, as well as a dependency relationship between the same two actors.

I am trying to convey that the Service Department depends on the Field Service Technician to complete a task. The task is conveyed between the two actors via an information flow "Request for Onsite Service".

My question: Is a dependency relationship implied by the information flow? Can I delete the dependency flow and instead rely on the information flow to convey the same meaning without cluttering up the diagram?

Maybe the answer lies in the multiplicity details, because the Service Department (multiplicity = 1) depends on multiple Field Service Technicians (multiplicity = *), but the information flow between the Service Department (multiplicity = 1) would depend on one Field Service Technician (multiplicity = 1). Since this seems like an important part of the context, I would lean in favor of keeping the dependency relationship and the information flow depicted on the block definition diagram.

Thanks,

Steve

2
General Board / These Templates Are Driving Me Crazy
« on: October 18, 2016, 11:16:34 am »
I have been messing with various template options for a couple days and I can't seem to get something to work 100% so please help me get this solved! I feel like I am very close but everything I try breaks something else or gets me worse off.

I am trying to display one template when showing requirement details, and another for everything else.

The content I am trying to display is arranged in multiple packages like this:
<root package>
<package 1><package 1 notes></package 1>
<package 2><package 2 notes><Behavioral Diagram 1><Behavioral Diagram 1 Notes><Behavioral Diagram 1 Embedded Blocks><Behavioral Diagram 1 Embedded Block Notes></package 2>
<package 3><package 3 notes><Use Case Diagram 1><Use Case Diagram 1 Notes><Use Case Diagram 1 Embedded Use Cases><Use Case Diagram 1 Embedded Use Case Notes></package 3>
<package 4><package 4 notes><Requirements Diagram 1><Requirements Diagram 1 Notes><Requirements Diagram 1 Embedded Requirements><Requirements Diagram 1 Embedded Requirement Notes></package 4>
<package 5><package 5 notes></package 5>
</root package>

Below is the structure to what seems to be getting all of the content I want but it is displaying State Diagrams (appears to be considering "StateNodes" as "Requirement" elements) and Block Definition Diagrams twice.
---------------------------------------------------
package >
{Pkg.Name}
{Pkg.Notes}
{Template - Activity Diagram Template Fragment}
{Template - Requirement Diagram Template Fragment}
package element >
linked document >
< linked document
< package element
element >
< element
child packages >
< child packages
< package>
--------------------------------------------------------

The Activity Template Fragment has an Exclude Filter for
1) "Exclude details for" "Requirement"
2) "Exclude diagram type" SysML1.3::Requirement
Below is the structure of the Activity Template Fragment:
------------------------------------------------------
package >
diagram >
{Diagram.DiagramImg}
Figure 1: {Diagram.Name} Diagram (version {Diagram.Version})

{Diagram.Notes}
element >
< element
<diagram
element >
{Element.Name} - {Element.Notes}
< element

< package
-------------------------------------------------------

The Requirement Template Fragment has an Exclude Filter for
1) "Exclude details for" eveything except "Requirement"
2) "Exclude diagram type" everything except "SysML1.3::Requirement"
Below is the structure of the Requirement Template Fragment:
------------------------------------------------------
package >
diagram >
{Diagram.DiagramImg}
Figure 1: {Diagram.Name} Diagram (version {Diagram.Version})

{Diagram.Notes}
element >
< element
<diagram
element >
(Table Header)
(Table Row){Element.Name} - {Element.Notes}
< element

< package
----------------------------------------

 I have tried following the example to make a Template Selector but I am getting lost in the Section loops and am missing content that I can get to display with the previous templates... Why do these Sections need to be this convoluted????

Attempt 1)
----------------------------
package >
{Pkg.Name}
{Pkg.Notes}
{Template - Template Selector} <------ Putting here does not get any of the embedded content, only displays package name and package notes.
package element >
linked document >
< linked document
< package element
element >
< element
child packages >
< child packages
< package>
--------------------------------------------------------

Attempt 2)
----------------------------
package >
{Pkg.Name}
{Pkg.Notes}
package element >
linked document >
< linked document
< package element
element >
{Template - Template Selector} <------ Putting here gets some of the content I want but not all of it like the non-template selector did.
< element
child packages >
< child packages
< package>
--------------------------------------------------------

Attempt 3)
----------------------------
package >
{Pkg.Name}
{Pkg.Notes}
package element >
linked document >
< linked document
< package element
diagram >
{Diagram.DiagramImg}
Figure 1: {Diagram.Name} Diagram (version {Diagram.Version})

{Diagram.Notes}
element >
< element
< diagram
element >
{Template - Template Selector} <------ Putting here gets some of the content I want but not all of it like the non-template selector did. It is missing the embedded elements for Activity Diagrams, it misses all states in a State Diagram except for the two StateNodes (initial and final), it misses all blocks except for embedded ports on a block. Also all tables now show up with a table header in each table row.
< element
child packages >
< child packages
< package>
--------------------------------------------------------

Attempt 4)
----------------------------
package >
{Pkg.Name}
{Pkg.Notes}
package element >
linked document >
< linked document
< package element
diagram >
{Diagram.DiagramImg}
Figure 1: {Diagram.Name} Diagram (version {Diagram.Version})

{Diagram.Notes}
element >
{Template - Template Selector} <---- Same results as Attempt 3
< element
< diagram
element >
{Template - Template Selector} <---- Same results as Attempt 3
< element
child packages >
< child packages
< package>
--------------------------------------------------------

Attempt 5)
----------------------------
package >
{Pkg.Name}
{Pkg.Notes}
package element >
linked document >
< linked document
< package element
diagram >
{Diagram.DiagramImg}
Figure 1: {Diagram.Name} Diagram (version {Diagram.Version})

{Diagram.Notes}
element >
{Template - Template Selector} <---- Same results as Attempt 3
< element
< diagram
element >
{Template - Template Selector} <---- Same results as Attempt 3
< element
embedded elements >
{Template - Template Selector} <---- Same results as Attempt 3
< embedded elements
child packages >
< child packages
< package>
--------------------------------------------------------

The Template Selector Fragment has the following Custom Query text:
1) Requirement::Requirement Template Testing
2) Requirement: Customer : Requirement Template Template Testing
3) default::Element Template Testing

Below is the structure of the Template Selector Fragment:
-------------------------------------------------------
custom >
< custom
--------------------------------------------------------

The Requirement Template Testing Fragment doesn't have an Exclude Filter

Below is the structure of the Template Testing Fragment:
------------------------------------------------------
package >
diagram >
element >
< element
<diagram
element >
(Table Header)
(Table Row){Element.Name} - {Element.Notes}
child elements >
< child elements
< element
child packages >
< child packages

< package
-------------------------------------------------------

The Element Template Testing Fragment  doesn't have an Exclude Filter
(I have tried multiple arrangements of the the Element Tags but nothing seems to get the same content as the previous templates do)

Below is the structure of the Element Template Testing Fragment:
------------------------------------------------------
package >
diagram >
element >
< element
<diagram
element >
{Element.Name} - {Element.Notes}
child elements >
< child elements
< element
child packages >
< child packages

< package
----------------------------------------

3
General Board / Exclude Details for Block?
« on: October 13, 2016, 05:51:26 am »
I am trying to create an Exclude Filter within my Document Options for a Block (actually I want to exclude everything else except for a block). I see every other kind of element except for a block within the "Exclude details for" list. Does a block go by a different name that is contained in that element list? If not, why isn't a block included in the list?

Thanks,

Steve

4
I have been struggling with developing my own RTF Templates to document my model effectively and would like to know if anyone has created some Templates or Fragments they would be willing to share that they have found effective in documenting their model? Is there an add-in, tool, or book that I should consider?

I realize that templates can be specific to an organization and/or a process but I'm talking about documentation at the basic element level (a use case, a requirement set, an activity, etc.) that have a pattern that could be followed.

I have tried using the standard EA templates but they all seem to miss the mark. I've worked hard to follow SysML standards to get the information into my model in a repeatable and structured way and find it frustrating that I have to spend even more effort to 1) find the information I want to get out of the model 2) arrange the information into a structure or format that makes sense and flows nicely 3) formatted for my specific documentation template. I can understand #3 being specific to me and is (in my opinion) why a configurable Template was created by EA in the first place but I really feel #1 and #2 should be EA (or possibly SysML) efforts to make their product (or language) more user friendly and effective.

Some of the companies I have worked for in the past were very reluctant to allow modeling efforts because they were seen as a waste of time drawing stick figures... which speaks directly to my point, in that there were tons of details associated to those stick figures but getting that information conveyed was a problem.

I'm currently trying to solve this problem by creating very specific Fragments that filter out all elements except for the elements I want to document in a specific way (e.g. a use case). My goal is to be able to convey in a natural English structure the specifics of the element and how it relates to other elements within the model. This request seems like such a fundamental concept of using the tool that I felt that I should pause my development and ask if someone else has developed something beyond the EA examples?

One last point. I really appreciate EA and the people in this forum for all of the expertise they bring. My intent is not to throw rocks at the tool, I simply want to find a more effective way of using the tool because it really does help manage complexity better than any other method I've used as a systems engineer.

Thanks!

Steve

5
1) I propose adding a <<Satisfy>> Requirement Partition to the working model of SysML and/or EA in much the same spirit as the <<Allocate>> Activity Partition is used (see "A Practical Guide to SysML", Section 14.6.3 Modeling Functional Allocation using Allocate Activity Partitions (Allocate Swim Lanes)). The idea would be to clean up and provide structure to my requirement diagrams by efficiently satisfying components (blocks) via adding requirements to the proposed partitions.

One obvious problem with this approach is that a requirement can satisfy multiple blocks but I think the same problem exists with the existing Allocate Activity Partition.

2) I would really prefer not having to make a new partition at all, rather I'd like to be able to specify the relationship of a Swimlane within a diagram so that I have less things to keep track of. To do this, I would add another column to the "Swimlanes" table within the "Swimlanes, Matrix and Kanban" dialog box. The proposed column would be added after the "Classifier" column and would be something like "Relationship". All items placed within the swimlane would then inherit the relationship specified to the classifier object.

6
General Board / Documentation Vs. Document Bookmark
« on: October 05, 2016, 05:39:40 am »
I have been playing around with the documentation features of EA and am at a loss as to how to accomplish the following situation efficiently:

I have some packages that I would like to report on in multiple documents, let's call one of the packages, "Regulatory Requirements" but there are others. My organization would like the Regulatory Requirements to be reported in a section within multiple Word templates but they also would like those requirements to be sub-divided into categories such as "Environmental Regulatory Requirements" (but these categories vary based on the template).

1) I first tried creating a document from EA (Right-Click "Documentation", then selecting "Generate Documentation") by creating my own custom Templates and Fragments, which worked great until I noticed that I needed to include some of the same information in multiple locations... so I tried the next approach:

2) I then tried copying and pasting items into a new structure to continue using the EA documentation approach but I didn't like that the copied elements are unique and don't get updated when the original element is updated. I also tried just copying the diagram and the 3 copy methods available (shallow, deep, and smart) to see if I could somehow duplicate the elements without creating a unique instance but that didn't work... so I then tried the next approach, however this is the approach I would like to get working if there is a way to copy a "clone" of an item that gets updated when the original is updated?

3) I then tried using a Document Bookmark based on a master RTF document but I'm not sure I like the complexity of this approach and am wondering if there is a better way? This approach makes it hard to re-categorize the subsections of "Regulatory Requirements" since it just re-uses the original package contents.

Thanks,

Steve

7
General Board / Generate Documentation Options - Skip Root Package
« on: October 04, 2016, 06:52:39 am »
I am trying to use the Generate Documentation feature efficiently and am finding that I am using the "Skip root package" option for every report that I want to generate. Is there any way to auto-select this option without having to select it each time?

8
Uml Process / Actors in a BDD
« on: September 24, 2016, 07:21:29 am »
Can anyone help me understand the finer details of a BDD, I'm trying to understand if I can add an Actor to a BDD instead of creating a block for the same actor? EA appears to let me add Actors to a BDD but is there a reason why I shouldn't do this?

I have been using "A Practical Guide to SysML" by Friedenthal et al. for reference but all of the examples from that book are using blocks.

Thanks,

Steve

Pages: [1]