Choosing
to Use ER/Studio 2.0
22 Aug 1997 by Duncan Dwelle
ER/Studio |
PowerDesigner |
InfoModeler |
Silverrun |
System Architect |
ERwin |
||
Rank |
Issue |
2.0 |
6.0 |
3.0 |
2.4 |
4.5 |
3 |
0 |
Reliable operation |
YES |
yes |
YES |
YES |
YES |
YES |
1 |
Short learning curve |
YES |
YES |
no |
no |
no |
no |
2 |
Fast graphics manipulation |
YES |
YES |
YES |
no |
no |
no |
3 |
Fast object definition |
YES |
YES |
no |
no |
no |
no |
4 |
Sub-views |
YES |
YES |
YES |
yes |
no |
yes |
5 |
Logical uniqueness (AK) |
YES |
no |
YES |
yes |
YES |
yes |
6 |
Queryable metadata |
YES |
YES |
no |
no |
yes |
yes |
7 |
Model readable to team members |
YES |
YES |
no |
yes |
yes |
yes |
8 |
Adequate DDL/DBMS generation |
YES |
yes |
no |
no |
no |
no |
9 |
Extended constraints |
yes |
yes |
YES |
yes |
yes |
yes |
10 |
Dynamic object behaviors |
no |
yes |
no |
yes |
yes |
no |
Keep in mind that my initial role in the project above is database design, excluding actual code construction. Therefore I gave little weight to DDL and implementation issues. Nonetheless you may find this informative.
If you want see the comments and explanations attached to many cells, ypu can download a copy of this Excel 97 file.
Back to the review
© © 1997 Applied Information Science