⏱ 5 min read
Introduction
Sparx Enterprise Architect (EA) is a solid modeling tool, but like any enterprise repository system, it can suffer from performance degradation, orphaned elements, or data integrity issues over time—especially in collaborative environments. EA’s built-in Project Integrity Check is a powerful utility that scans the repository for inconsistencies and offers the option to repair them. Yet many users overlook this tool or run it improperly. Sparx EA training
This covers best practices for using EA's Project Integrity Check to maintain a clean, healthy modeling environment and ensure consistent behavior across teams and integrations. integration architecture diagram
1. What Does the Integrity Check Do?
The Integrity Check tool performs a scan of the EA repository and identifies: free Sparx EA maturity assessment
- Orphaned elements (objects not associated with any diagram or package)
- Dangling connectors (references to non-existent elements)
- Corrupt stereotype or tagged value definitions
- Missing or incorrect references in system tables
The tool then allows you to select and apply fixes either individually or in bulk.
2. When and Why to Run It
Regular use of the Integrity Check is critical in collaborative or large-scale projects. Recommended triggers include:
- Before exporting models to XMI for team exchange
- After model merges or Pro Cloud Server integration
- Following a database migration or upgrade
- After restoring from backup
- Prior to baselining or auditing model content
3. How to Run the Integrity Check
- Open your EA project.
- Go to Configure > Integrity > Project Integrity
- Select which tests to perform (or use Check All)
- Click Run to begin scanning
- Review the issues and choose to Fix Selected or Fix All
Tip: Always back up your .eap or DB repository before fixing issues.
4. Common Issues Detected
- Orphaned Elements: Common when packages are deleted without cleanup
- Dangling Connectors: Often result from manual database manipulation
- Unused Attributes/Operations: Especially after reverse engineering
- Corrupted Stereotypes: Resulting from imported MDG technologies or profile mismatches
5. Interpreting Results Carefully
Some "errors" are expected and context-dependent. For example, orphaned elements might be deliberate placeholders. Never fix without understanding the context, especially in shared repositories.
6. Integrity Checks in SQL-Based Repositories
For EA models hosted in SQL Server, PostgreSQL, or Oracle, always ensure:
- Read/write access to the DB during integrity operations
- No conflicting access or locks during cleanup
- Integrity check is run outside of peak hours to avoid performance issues
7. Pro Tips for Ongoing Health
- Automate monthly integrity scans using EA scripting API
- Use Prolaborate dashboards to flag potential model inconsistencies
- Encourage modelers to clean up as they go—adopt modeling standards
Conclusion
The Project Integrity Check is EA’s unsung hero for repository hygiene. With regular use, clear interpretation of results, and informed application of fixes, you can significantly improve model quality, stability, and trustworthiness. Clean models aren’t just easier to work with—they’re more resilient to integration, export, and governance processes.
Enterprise Architect, EA Integrity Check, Sparx EA Best Practices, EA Repository Health, EA Data Cleanup, EA Orphaned Elements, EA Dangling Connectors, EA Corruption Repair, EA Maintenance, Prolaborate, EA Model Governance, EA Project Tips Sparx EA best practices
If you’d like hands-on training tailored to your team (Sparx Enterprise Architect, ArchiMate, TOGAF, BPMN, SysML, or the Archi tool), you can reach us via our contact page.
Repository maintenance as a continuous practice
Architecture repositories degrade without active maintenance. Elements become stale as systems change, relationships break as integrations are modified, and views become misleading as the architecture evolves. Three maintenance practices prevent degradation: quarterly ownership review, automated drift detection, and annual model housekeeping.
Quarterly ownership review verifies that every element has a current owner (not someone who left the organization six months ago), every element's status reflects reality (not "Active" when the system was decommissioned), and every element's tagged values are current (not carrying a 2023 risk assessment for a system that was rebuilt in 2025). Run a script that flags elements whose Last_Reviewed date is older than 6 months.
Automated drift detection compares the model against runtime reality. Query the CMDB, cloud provider APIs, or monitoring systems to discover which applications and infrastructure actually exist, then compare against the model. Discrepancies are either model gaps (real systems not yet modeled) or zombie entries (modeled systems that no longer exist). Both degrade model trustworthiness if left uncorrected. enterprise cloud architecture patterns
Frequently Asked Questions
What is enterprise architecture?
Enterprise architecture is a discipline that aligns an organisation's strategy, business operations, information systems, and technology infrastructure. It provides a structured framework for understanding how an enterprise works today, where it needs to go, and how to manage the transition.
How is ArchiMate used in enterprise architecture practice?
ArchiMate is used as the standard modeling language in enterprise architecture practice. It enables architects to create consistent, layered models covering business capabilities, application services, data flows, and technology infrastructure — all traceable from strategic goals to implementation.
What tools are used for enterprise architecture modeling?
Common enterprise architecture modeling tools include Sparx Enterprise Architect (Sparx EA), Archi, BiZZdesign Enterprise Studio, LeanIX, and Orbus iServer. Sparx EA is widely used for its ArchiMate, UML, BPMN and SysML support combined with powerful automation and scripting capabilities.