EA has a great model-integrity feature: the relationship matrix. Click on "Project" in the menu bar, then on "Relationship Matrix...; choose the source and target packages (I suggest you choose the project root for both), choose your most important dynanic/behavioural elements as the first "Type" (Sequence, preferably, if you are using sequence diagrams), then your most important structural element as the second type (Class, if you have not already converted your classes into tables), then choose the appropriate Link Type (Sequence, if you are using sequence diagrams): you will obtain a pseudo-CRUD (Create, Read, Update, Delete) matrix, in which you can check for model completeness and integrity.
All non-abstract classes should be linked by a sequence message to a dynamic/behavioural element. Instances of the most critical classes, at least, should be Created, Read, Updated and Deleted by behavioural elements; otherwise you're missing something: suppose you have an operation that reads instances of Customer, but your model does not have the operation that should create those customers in the first place...
If a class does not have a link to the appropriate behavioural elements (for instance, a log-in interface does not have a link to User in the matrix) it means your model is definitely incomplete.
This, of course, is only one of the possible uses of the matrix: you can also check for "realization" of requirements in use cases, and many, many other consistency criteria as well.
This is not a fully automated feature, but I should say it comes pretty close.
