Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: ChB on March 22, 2016, 02:42:28 am

Title: Profiles and how to extend SysML extendedRequirement.
Post by: ChB on March 22, 2016, 02:42:28 am
When working with requirements written by my customers I often have "requirements" that are actually "titles" and "information" rather than actual requirements.  I want to include these in my model - there's value for myself and my customer to do so.   I'm using SysML 1.4 which has an <<extendedRequirement>> type from which  <<functionalRequirement>>, <<interfaceRequirement>>, <<designConstraint>> and others are based.

I'd like to add two more stereotypes, based on <<extendedRequirement>> called "titleRequirement" and "informationRequirement".

I think I do that using a Profile but I'm finding that an overwhelming subject and haven't succeeded yet.  Here's what I've been trying:

I can see my profile in the toolbox but I can't see my new titleRequirement type.   What have I missed or done wrong?

I'm using EA 12.1 (1228) System Engineering Edition and sysML 1.4.
Title: Re: Profiles and how to extend SysML extendedRequirement.
Post by: Geert Bellekens on March 22, 2016, 03:55:41 am
If you post an image of your profile diagram we might be able to spot the error.

Geert

PS. "Post image" means put it somewhere on a public image hosting site such as imgur.com and put the link in an img tag.
Title: Re: Profiles and how to extend SysML extendedRequirement.
Post by: Glassboy on March 22, 2016, 11:40:15 am
Hi there, in my experience if something doesn't appear you probably have a spelling mistake.  If it appears and doesn't work, you are probably extending the wrong UML type in a toolbox definition.
Title: Re: Profiles and how to extend SysML extendedRequirement.
Post by: KP on March 22, 2016, 01:21:17 pm
Quote from: ChB on March 22, 2016, 02:42:28 am
On the profile diagram I created in step 1 I've created a new stereotype element called titleRequirement using these instructions: http://www.sparxsystems.com/enterprise_architect_user_guide/12/extending_uml_models/addingelementsandmetaclass.html  which are similar to these instructions: http://www.sparxsystems.com/enterprise_architect_user_guide/12/extending_uml_models/non_uml_metatypes.html
Do you have a metaclass element named "Requirement" with an Extension connector from "titleRequirement"? And do you have an abstract stereotype element named "SysML1.4::extendedRequirement" with a Generalization connector from "titleRequirement"? You will need both.
Title: Re: Profiles and how to extend SysML extendedRequirement.
Post by: ChB on March 22, 2016, 08:34:57 pm
Quote from: KP on March 22, 2016, 01:21:17 pm
Do you have a metaclass element named "Requirement" with an Extension connector from "titleRequirement"? And do you have an abstract stereotype element named "SysML1.4::extendedRequirement" with a Generalization connector from "titleRequirement"? You will need both.

KP's post showed me where I went wrong.  Three elements are needed on the profile diagram.  The instructions I'd presumably not followed carefully enough are these, especially steps 3 to 7:
http://www.sparxsystems.com/enterprise_architect_user_guide/12/extending_uml_models/non_uml_metatypes.html

I picked up further hints from KP's post to get the naming of my elements appropriate.

I've added three images here that should help illustrate what I think works for me: http://imgur.com/a/eaLDE
(Not sure if the images are visible because of my local corporate network restrictions - I'll fix from home tonight if necessary).

Thanks all for your responses.