nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change management of requirements by scripting

medini_1064887566

Some customers want to know which requirements need to be reviewed when the upper requirements change, and this should be possible with scripting.

The use case could be that medini users need to check whether their requirements are appropriate when their customers change their requirements.

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023641097

Hello Ka-lip,

I did look into options for something like that. Be aware that this is a work in progress and is not tested in any way. Let me know if this could work.

This customization displays for each Requirement and Safety Goal changes of the respective Requirements or Safety Goals as well as changes of Requirements and Safety Goals upstream.

Changes in this context are changes of certain defined attributes.

Upstream in this context mean changes to direct and indirect parents (including Decomposition and Subrequirement Relation), Contribution, Correlation, and Independency.

To achieve that 10 Profile Properties, 1 batch script and 1 JavaScript Library were added.

With the batch script "set baseline" the current state of the requirements is saved depending on manually set checkmarks.

There are atomic checkmarks at each Requirement and Safety Goal as well as a Checkmark at the Requirement Model which overrides all other checkmarks if checked.

There is a property saving the date and time of the last baseline at the Requirement Model.

The Upstream changes detect additions and deletions of Requirements.

New Requirements and Safety Goals display a circle with "i" in it (i) in the "change" property.

New Requirements with any upstream connections display changed (!) in the "upstream change" property.

New Requirements without any upstream connections are shown as unchanged in the "upstream change" property.

New Requirements and Safety Goals switch to unchanged with a new baseline no matter if the manual checkmark is set.

Upstream changes of new Requirements and Safety Goals follow the default logic.

medini_1068871298

Hi Nino,

Thanks for sharing. I've tried this in my project. Attached is the snapshot.

If I change the TSR, the associated HSR will show alert as expected but the sub-requirement of the HSR does not have alert. I am not sure if this is the expected result.

I just consider it would be really helpful if the sub-requirement can show alert as well.

Thank you.

medini_1023641097

Hello Shelly,

thank you for pointing this out. This should be an easy fix.

In the script to "set baseline.js" you can find the function that is called to gather the data for the upstream changes:

In that function you will find that the requirements attribute that is used is "contributesTo" but instead we will need to use "contributedRequirements". The difference beeing that "contributesTo" only links to the directly (1 jump) contributed requirements while "contributedRequirements" states also requirements that are contributed to indirecly.

medini_1068871298

Hi Nino,

Yes. That fix works.

Thanks a lot.

medini_1023641097

Updated version of the scripts, including the above point and minor changes. Please be aware that this is a work in progress and is not tested in any way. Let me know if this could work.

To make it easy to understand how these scripts work I displayed some Profile Properties (shown below) that I would recommend to hide generally. I also disabled a function that compresses the data that is used to compare the baseline and the current state (this function basically makes a unique string from the string that is currently shown below).

If you prefer to hide these Profile Properties and use the function please carry out the changes below.

medini_1068871298

Hi Nino,

I have a question.

I've checked this requirement change alert applies to "ID", "Name", "Description", "ASIL", "Status" and "Kind" but it is not applicable to "Allocations". I discovered this because I tried to change the content of Allocations but the "Requirement unchanged" alert did not appear.

I am wondering how to add this alert.

Thank you.

regards,

Shelly

medini_1023641097

Hello Shelly,

please try to add sourceRelations and targetRelations to the script. The screenshot below shows all properties of requirements the beforementioned are marked.

Let me know if it works for you or if I could assist you with the implementation.

regards,

Nino

medini_1068871298

Hi Nino,

I tried to add sourceRelations and targetRelations to the script but it did not work. Maybe my modification to the script is wrong or I missed anything. Please help take a look.

Thank you.

regards,

Shelly

medini_1023641097

Hi Shelly,

you changed the script in the right spot. Please mind that any attributes ending with these brackets [] are lists in medini. To read in the information from the list you need to create a loop using a for-loop or a foreach loop like this:

req.sourceRelations.toArray().forEach(function (relation) {
	text += relation + "; ";
});

Please be aware that this will not only check the allocations but any kind of trace if you want to filter that you need to look at the attributes of the relation and only add the ones of the allocation type.

I hope this helps.

Best regards

Nino

medini_1068871298

Hi Nino,

Could I get your assistance for the implementations?

Thank you.

regards,

Shelly

medini_1023641097

Hello Shelly,

I am sorry I mixed up the variable in the post above. Please try this instead:

req.mediniGetTracedElements(Metamodel.sysml.SysMLElement).toArray().forEach(function (relation) {
 text += relation + "; ";
});

The function mediniGetTracedElements(Metamodel.sysml.SysMLElement) is medini specifc and needs to be used as there is no attribute to save the traces.

Best regards

Nino

medini_1068871298

Hi Nino,

Thank you for the feedback.

There's a further issue. Please help.

I've added the codes to the script. As expected, when I made changes to the "Allocation", the "Requirement unchanged" showed alert. Also, the downstream requirements reacted to it as shown in the "Upstream unchanged".

But, soon after that I encountered another issue. I closed the project ("Close Project" in medini), and then reopened the project ("Open Project" in medini). The alerts appeared for all requirements like the screenshot captured below.

I've tried other use case, It seems that the alert status will not stay the same when the project is reopened, compared to the status before it was closed."

Could you please help to check this?

Thank you.

Regards,

Shelly

medini_1023641097

Hi Shelly,

thank you for the feedback. I just learned that the Traces have elements that change when loading the project. Please try this script snippet instead:

req.mediniGetTracedElements(Metamodel.sysml.SysMLElement).toArray().forEach(function (relation) {
	relation.targetElements.toArray().forEach(function (target) {
		text += target + "; ";
	});
	relation.sourceElements.toArray().forEach(function (source) {

 text += source + "; ";
	});
});

Best regards

Nino

medini_1068871298

Hi Nino,

I've added the code, but the script cannot be executed. Please help to check the screenshots below. Thank you very much.

Regards,

Shelly

medini_1023641097

Hello Shelly,

thank you for finding this issue that the script is not working properly when the project or medini are closed and reopened! I tried to correct it in this file. Please be aware that I have not included the snippet above.

I only changed 2 functions which you can replace in your existing project. The issue was that the attributes contributedRequirements and contributedSafetyGoals are calcualted when loading the project and might have the internal elements in a different order.

function baselineReqUpstream(req){
	var arr = [];
	var arr = new Array();
	var text = "";
	if(req.contributedRequirements.size()>0){
		for(var i = 0; i < req.contributedRequirements.size(); i++) {
			 arr.push(baselineReq(req.contributedRequirements[i]));
		}
	}
	if(req.contributedGoals.size()>0){
		for(var j = 0; j < req.contributedGoals.size(); j++) {
			arr.push(baselineSG(req.contributedGoals[j]));
		}
	}
	arr.sort();
	arr.forEach(function(element){
		text+= element;
	});
	text = checksum(text);
	return text;



}
//creates string for upstream baseline as well as for compare for a Safety Goal
function baselineSGUpstream(sg){
	var arr = new Array();
	var text = "";
	var correlations = sg.sourceRelations;
	var text = "";

	correlations.toArray().forEach(function(correlation){
		arr.push(baselineSG(correlation.target));
	});
	arr.sort();
	arr.forEach(function(element){
		text+= element;
	});
	text = checksum(text);
	return text;
}

medini_1068871298

Hi Nino,

I quickly tried out the updated script, and it worked as expected so far.

Thank you for the update. I really appreciate the support.

Here are the updates:

I replaced the "baselineReqUpstream(req)" and "baselineSGUpstream(sg)" with the code you just provided in v0.63

In addition, the baselineReq(req) was also updated as below.

Regards,

Shelly