|
1 .
What is EA's ability to export and import CSV files
for
EA provides the ability to import
and export CSV files, which can export EA's models,
such as use cases, as an excel list that can be imported
into another user's EA model, as well as manage the
list of use cases in Excel.
To use CSV files to import and
export element data between EAs, you must first set
up one or more CSV file specifications. This is done
because the specification defines what types of values
are to be imported from a spreadsheet and how information
is to be converted between the spreadsheet and Enterprise
Architect.
2 . How does the EA export import
CSV function work?
EA can export and import the data of the requirements, use
cases, classes and other elements in the model as
a CSV file, and can define the attributes at the time
of export and import, which can become the column
names and data of the table in the exported and imported
CSV file.
3 . What needs to be set for
the EA export import CSV function
The following is the parameter setting screen for exporting/importing
a CSV file:
The following is a description
of the interface
| Interface properties
|
Illustrate |
| Specification |
• If you
create a new specification, type a unique specification
name.
• If you are editing an existing specification,
click the drop-down arrow and select the specification
name. |
| Delimiter |
• Click
the drop-down arrow and select the character separator
you want to use between the record fields.
• If a field contains instances of
a delimiter, the field will be exported to enclose
" (in quotation marks), and any instances
of " in the field will be doubled (i.e.,
"becomes "). ）。
|
| Note
|
Write a brief description
of the specification.
|
| Default |
• Type the
default file location and file name to use when
importing and exporting.
• Alternatively, click the browse button
and browse the location.
|
Default
|
• Click
the drop-down arrow and select the default action
- Import or Export.
• Each specification can be used in
either direction. |
Default Types
|
Type a comma-separated
list to limit the types of elements to export;
For example: classes, requirements, components,
nodes, objects.
• If you specify an element type, only
those types of elements are exported or imported.
Therefore, for the Keep Hierarchy option to work
properly (if checked), you must include the package
as an element type, otherwise there is no package
to keep the hierarchy
• If no default element type is specified,
all elements, including the package, are exported
or imported, and the hierarchy can be preserved
|
Preserve Hierarchy
|
Select this check box
to include fields for enterprise architects to
embed/rebuild package hierarchies.
|
| Available Element Field
|
• Click
the name of an available field, and then double-click
it to add it to the specification (it appears
at the end of the File Specifications list).
• Hold down Ctrl while selecting multiple
fields, but use the Add Field button to transfer
them all to the File Specifications list.
|
Select Element Field
|
• View assigned
record fields, listed in the order in which they
were plotted in the spreadsheet.
• If you want to change the field sequence,
click the field name, and then click the Up or
Down green arrow icon button to move the field
name up and down in the list.
|
Add Tagged Value
|
Click this button to
add the Tagged Value column to the CSV specification
to import or export the value that an element
has for a specific tag.
|
Add Field
|
Click this button to
move all selected fields from the Available Fields
list to the File Specifications list.
|
Remove Field
|
Click this button to
move all selected fields from the File Specifications
list back to the Available Fields list.
|
4 . A how-to guide for EA to
export the import CSV feature
Example of a CSV file export
Example 1:
Let's take the example of exporting
the main element feature data from the Functional
Use Cases package in the Requirements Model to see
how to export a CSV file.
Here's the list view interface
for the Feature Use Cases package:
First,
let's define the CSV export specification, which is
the interface for defining the specification as follows:
After defining the export specification, click the
"Import and Export" menu, select the defined
specification, configure the file type, etc., and
click the "Run" button, as follows:
Then click on the "View File" button, and
here is the main element feature data of the "Functional
Use Cases" package in Excel exported:
Example 2:
Let's take another example of
exporting the main element feature data in the Test
Case package to see how to export a CSV file.
Here's the list view interface
for the Test Cases package:
First,
let's define the CSV export specification, which is
the interface for defining the specification as follows:
After defining the export specification, click the
"Import and Export" menu, select the defined
specification, configure the file type, etc., and
click the "Run" button, as follows:
Then click the "View File" button, and here
is the main element feature data of the "Test
Cases" package in Excel that is exported:
CSV file import example
Example 1:
Let's show you how to import the
exported Job Responsibilities .csv file into EA.
Here's a CSV file Job Responsibilities
.csv to import:
The
following is the CSV import specification setting
interface: (The Work Blame .csv file has been exported
to EA in the previous period)
After
defining the export specification, click the "Import
and Export" menu, select the defined specification,
configure the file type, etc., and click the "Run"
button, as follows:
After
importing the specification settings, click the Run
button to see the imported Job Responsibilities .csv
file data in the model list view.
Here's a list view of the Job
Responsibilities .csv elements imported into EA:
Example 2:
Let's show you how to import an
exported Job .csv file into EA.
Here's a CSV file to import, Work
Assignment .csv:
Here
is the CSV import specification setup screen: (The
Work Task .csv file has been exported to EA in the
previous period)
After defining the export specification, click the
"Import and Export" menu, select the defined
specification, configure the file type, etc., and
click the "Run" button, as follows:
After
importing the specification settings, click the Run
button to see the imported Work Assignment .csv file
data in the model list view.
The following is imported into
EA's Work Task .csv element list view:
postscript
I hope you have benefited from
reading this article.
If you are interested in sharing
your experience, please feel free to contribute to
us, and if you are interested in our training, consulting
and tools, please learn about:
• Modeling Tools： EA
• MBSE platform： iSpace
• Model web browsing
tool： WebEA
• Course： System Design and Modeling Based on SysML and EA
• Course： System analysis and design based on UML and EA
• Consulting Solution：
MBSE (Model-Based Systems Engineering).
• Consulting Solution：
Model-driven development based on UML
• All modeling-related
courses： http://www.modeler.org.cn/course/index.asp
• Consulting Solution：
Model-Based Project Management
If you
would like to learn more:
Welcome to the Modelers Channel
http://modeler.org.cn/
You are also welcome to contact
us directly at umlooo@hotmail.com
|
