Transform imported custom requirements to table

[chris.lorentz@insitu.com]

After successfully importing the data from Excel, a file schema with data instances now exists. A stereotype has been created to identify the individual properties for the instances. Those properties have been added to the requirements table. The requirements table now shows the custom headings. The requirements table only recognizes a requirement data type.

Does the stereotype properties need to be mapped to the file schema properties? Does the stereotype need to be modified to be recognized as a requirements or should a process be run which does the translation? What is the next step?

Thank you!

[laurin]

Hello,

If we understand correctly, you are working with Instances.
MagicDraw has special Instance table, that allows managing instance specifications.

Please let us know, if this table is appropriate for you or give us more specific example (maybe screenshot and project file) what are you intend to model.

Best Regards,
No Magic Customer Support

[chris.lorentz@insitu.com]

Yes, I am working from instances of data which have been imported from Excel. The goal is to transform the instance into a recognized requirement type. I have attached several screen shots of the project so you can see the steps to date.

[laurin]

Dear Chris,

Thank your for the doc file.
Could you please convert it into pdf? Currently we couldn't see the images.

Is it possible for you to attach the project file (mdzip) as well?

Best Regards
No Magic Customer Support

[chris.lorentz@insitu.com]

Attached document with screen shots.

CameoImportedNoRequirements.pdf

[chris.lorentz@insitu.com]

Attached is the project file.

SampleRequirements.mdzip

[osvaldas.jankauskas@nomagic.com]

Hi Chris,

I took a look at your sample project. To successfully import, you need to map fileSchema properties with appropriate requirement properties first. For this, click File > Import From > Excel/CSV File and choose Create Mapping in the appeared dialog.

This and more you can find in the "Excel Import User Guide" (to open, select Help > Other > Excel Import User Guide from the main menu), section “Mapping a Schema Class to an Element” (31 page).

If you have any other questions or encounter any other problems, please feel free to contact us for further assistance.

Best regards,
No Magic, Inc. Customer Support

[chris.lorentz@insitu.com]

Thank you for your speedy response!
If you check the mdzip file sent earlier, you would see that the first row of the excel spreadsheet is used as the mapping. When the map import is completed the object has a type of fileSchema not requirement which is needed. The same is true after the data itself is imported. The requirements table only "sees" objects which have a requirement type. As a result loaded items cannot be used in the requirements table. I was experimenting with stereotype to setup the columns in the requirement table and wondered if some kind of rule which kicked off an operation might be needed or the stereotype might need another classifier added. Really appreciate a closer look at this puzzle. Thank you!

[osvaldas.jankauskas@nomagic.com]

Hello,

Could you please tell us with which version of MagicDraw you are working? I would create sample project for you where mapping is completed correctly.

Waiting for your response,
No Magic, Inc. Customer Support

[chris.lorentz@insitu.com]

H! The version I am using is 18.3. On Friday, I was able to get the generic columns with Id and Text to show up as a requirement by using the UML template for requirement with automated mapping. Using that I loaded the standard columns and made sure the excel columns matched. So the question is how do I use/create the stereotype with custom columns then generate an automated mapping which works. I am not sure whether the issue is a step missing with creating the stereotype for a requirement? so it can be mapped to the excel headers. Thank you for your help!