基于核准列表校验Sparx Enterprise Architect类模型元素的方案咨询

Hey there! Since you're a long-time lurker asking your first question, let's tackle this Sparx EA validation problem head-on. Here are a few practical workarounds to implement custom checks against your approved list before converting to XSD:

1. Use EA's Built-in Scripting Interface #

Sparx EA has a powerful scripting engine (supports VBScript, JScript, and Python via add-ins) that lets you write custom validation logic directly in the tool. Here's a quick breakdown:

• Store your approved list: Save it as a simple CSV file (e.g., approved_elements.csv) with columns like element name, type, allowed attributes.
• Write a validation script: Use EA's API to iterate over all elements in your class model, cross-reference them against the approved list, and flag discrepancies.
• Example VBScript snippet:

  Dim approvedList : Set approvedList = CreateObject("Scripting.Dictionary")
  ' Load approved elements from CSV (simplified example)
  Dim fso : Set fso = CreateObject("Scripting.FileSystemObject")
  Dim file : Set file = fso.OpenTextFile("C:\path\to\approved_elements.csv", 1)
  Do Until file.AtEndOfStream
      Dim line : line = Split(file.ReadLine(), ",")
      approvedList.Add line(0), line(1) ' key: element name, value: allowed type
  Loop
  file.Close
  
  ' Iterate over class elements in current package
  Dim pkg : Set pkg = Repository.GetTreeSelectedPackage()
  Dim elem : Set elem = pkg.Elements.GetFirst()
  Do While Not elem Is Nothing
      If Not approvedList.Exists(elem.Name) Then
          Session.Output("ERROR: Element '" & elem.Name & "' is not in the approved list")
          ' Optional: Add to EA's Issues list
          Repository.AddIssue elem.GUID, "Unapproved Element", "Element is not in the pre-approved list", 2 ' 2 = Error severity
      End If
      Set elem = pkg.Elements.GetNext()
  Loop
  

• Run the script: Add it to EA's script library and bind it to a custom menu button for one-click validation.

2. Build a Custom EA Add-In #

For more robust, reusable validation (like auto-checking on save), create a dedicated add-in using C# or VB.NET. Here's what you can do:

• Use EA's official Add-In API to hook into events like EA_OnPostSave or EA_OnPreExport.
• Read your approved list from any format (JSON, XML, database) during add-in initialization.
• Implement validation logic that scans the model, highlights invalid elements, and generates detailed reports within EA.
• The add-in can also integrate with EA's native validation framework, so results show up alongside built-in checks.

3. Export to XMI and Validate Externally #

If you prefer not to modify EA itself, export your class model to XMI (EA supports multiple XMI versions) and use external tools to validate against your approved list:

• Export XMI: Right-click your package > Export > XMI 2.1 (or compatible version).
• Validate with external scripts: Use Python, XSLT, or Java to parse the XMI file and compare elements against your approved list. For example, with Python's lxml library:

  from lxml import etree
  
  # Load approved list
  approved_elements = set(line.strip() for line in open("approved_elements.txt"))
  
  # Parse XMI
  tree = etree.parse("model_export.xmi")
  ns = {"uml": "http://www.omg.org/spec/UML/20131001"}
  for elem in tree.xpath("//uml:Class/@name", namespaces=ns):
      if elem not in approved_elements:
          print(f"ERROR: Unapproved class found: {elem}")
  

• Generate a validation report and cross-reference it back to your EA model.

4. Customize MDG Technology (Advanced) #

For deep integration with EA's native validation system, create a custom MDG technology:

• MDG technologies let you define custom metamodels, rules, and validation logic that EA recognizes natively.
• You can embed your approved list directly into the MDG's validation rules (using XML-based rule definitions) or link to an external file.
• This requires learning EA's MDG authoring tools, but it's the most seamless solution if you need ongoing, enterprise-wide validation.

Each approach has its own tradeoffs—start with scripting if you need a quick fix, or go for an add-in/MDG if you need long-term maintainability.

内容的提问来源于stack exchange，提问作者TheVampyre