Sparx Enterprise Architect Excel Import

Create & update elements and relationships in Sparx Enterprise Architect from an Excel spreadsheet (xlsm file).

The spreadsheet shall have 2 sheets:

RTM, Design Objects

The Excel file shall have a Form to choose:

- Option 1: Import RTM

- Option 2: Import Design Objects

- Option 3: Validate RTM

- Option 4: Configure Settings

Worksheet 1

It shall list GUID, Alias, Name, Description, Type, Stereotype, Status, some Tag Value (e.g. Requirement Project Owner), a Design Object ID. These rows are Elements that are extensions of the Requirements stereotype. The Design Object ID column shall contain a set of Design Object IDs that are pipe separated.

Worksheet 2

It shall list GUID, Alias, Name, Description, Type, Stereotype, and some Tag Value (e.g. Design Project Owner). These rows represent Elements that are extensions of the Class stereotype.

Option 1:

When selecting the Import RTM action, the program shall first Validate the RTM and if there are no errors, it shall:

Go through each row from RTM worksheet and check if the Alias, Project, Stereotype combination already exist in the Sparx EA database. If it doesn't exist then check if each comma separated item in the Design Object ID column already exists in the Sparx EA database. If it doesn't exist, then log an entry in the Error Log for that row and move to the next row. At the end of the validation, if there are any errors, the Import shall stop with a Messagebox prompted to the user.

If there are no errors, then the program shall scan each row from the top again and if the GUID is populated then the row shall be treated as an update: the fields from the Name, Description, Type, Stereotype, Status, and Tag Values shall be updated in the Sparx EA database. Also, a Trace Connection shall be created between the Requirement object and the Design Object(s) listed in Design Object ID.

If the GUID isn't populated and the combination of Alias, Requirement Project Owner, Stereotype doesn't exists in the Sparx EA Database, then the row shall be treated as a new add of a Requirement. Before adding the element to the Sparx EA, the user shall be prompted with a message stating: Adding new element <Alias>. Do you want to proceed? (Yes) for proceeding, (No) for skipping. There shall also be a checkbox to apply the same answer to all future prompts.

When a new requirement is added, then the corresponding GUID shall be recorded in the RTM worksheet. Also, a Trace Connection shall be created between the Requirement object and the Design Object(s) listed in Design Object ID.

The program shall prompt the user with a message about the completion of the Import with a count of rows processed, elements created, and elements updated.

Option 2:

When selecting the Import Design Objects option, the program shall go through each row and, if the GUID column is populated, it shall treat that row as an update by updating Name, Description, Status, and Tag Values. Else the program shall check if the combination of Alias, Stereotype, and Design Project Owner exists. If it does exist, then the program shall log an error and move to the next row. If the combination does not exist, then it shall create the element in Sparx EA as a new add and populate the corresponding GUID in Worksheet 2.

The program shall prompt the user with a message about the completion of the Import with a count of rows processed, elements created, and elements updated.

Option 3:

The program shall go through the RTM worksheet and log any errors corresponding missing (i.e. the Design Object ID is not found when selecting Alias from the t_object table where stereotype = "design object") Design Objects from to the pipe separated items in the Design Object IDs column.

Option 4:

The program shall allow to define the path where to store the error log file.

.NET Excel Visual Basic Visual Basic for Apps

Project ID: #19369661

About the project