반응형
Notice
Recent Posts
Recent Comments
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |
Tags
- 운영체제
- Programming
- 컴퓨터과학과
- 인간과 교육
- Book
- architecture
- Compiler
- Computer
- 법
- 영어
- 컴퓨터
- 백과사전
- Software
- Algorithms
- 용어
- EJB
- 교육
- 알고리즘
- ISBN:89-20-34523-6
- 방송통신대학교
- 광고
- 프로그래밍언어
- 데이터베이스
- Database
- Java
- OS
- 영화
- 컴파일러
- 책
Archives
- Today
- Total
Digital Intelligence
PowerDesigner® vs. ERwin Technical Comparison 본문
반응형
PDF file
PowerDesigner® vs. ERwin Technical Comparison
A white paper from Sybase, Inc.
http://www.sybase-iad-services.com/powerdesigner/pdf/PD10_vs_Erwin_wp.pdf
Conclusion
In conclusion, both of these data modeling tools are very popular and provide the user with
a many useful functions. However, PowerDesigner has a more sophisticated user interface
and functions that are easier to find and use for the novice.With its advanced control over
graphics and its stronger reporting facility, PowerDesigner produces better quality documentation
than ERwin. ERwin has a good handle on the databases it supports, but PowerDesigner
starts with better support and lets the user customize the database definitions. ERwin has
some sophisticated features when dealing with standard domains and naming conventions
that are superior to PowerDesigner. PowerDesigner is stronger in the dimensional modeling
area, having more functions specifically for handling multi-dimensional hierarchies.
ERwin has made strides in loosening their link between logical and physical models, but
still the lack of true conceptual modeling is a detriment. The fundamental differences in
philosophy concerning conceptual, logical and physical models and the limitations ERwin
enforces concerning attributes and data items give PowerDesigner an edge when creating
business-oriented models.
BPwin is a more mature tool than the BPM module and does a good job of modeling
business processes and functions, but it is a separate package.
The ACM is disappointing, with a poor user interface and a steep learning curve when
moving from the other CA tools. It is also crippled by not being able to share the same
repository as the other tools. If CA can somehow merge their modeling tools together,
things would be much better.
Although they both share the ability to integrate multiple models, only PowerDesigner was
truly able to share objects between models. The bottom line is that PowerDesigner is a tightly
integrated suite of modules with a strong common user interface while CA’s tools are obviously
from different sources without any consistency between them.
In conclusion, both of these data modeling tools are very popular and provide the user with
a many useful functions. However, PowerDesigner has a more sophisticated user interface
and functions that are easier to find and use for the novice.With its advanced control over
graphics and its stronger reporting facility, PowerDesigner produces better quality documentation
than ERwin. ERwin has a good handle on the databases it supports, but PowerDesigner
starts with better support and lets the user customize the database definitions. ERwin has
some sophisticated features when dealing with standard domains and naming conventions
that are superior to PowerDesigner. PowerDesigner is stronger in the dimensional modeling
area, having more functions specifically for handling multi-dimensional hierarchies.
ERwin has made strides in loosening their link between logical and physical models, but
still the lack of true conceptual modeling is a detriment. The fundamental differences in
philosophy concerning conceptual, logical and physical models and the limitations ERwin
enforces concerning attributes and data items give PowerDesigner an edge when creating
business-oriented models.
BPwin is a more mature tool than the BPM module and does a good job of modeling
business processes and functions, but it is a separate package.
The ACM is disappointing, with a poor user interface and a steep learning curve when
moving from the other CA tools. It is also crippled by not being able to share the same
repository as the other tools. If CA can somehow merge their modeling tools together,
things would be much better.
Although they both share the ability to integrate multiple models, only PowerDesigner was
truly able to share objects between models. The bottom line is that PowerDesigner is a tightly
integrated suite of modules with a strong common user interface while CA’s tools are obviously
from different sources without any consistency between them.
PowerDesigner와 ERwin 비교백서에서 발췌
반응형
'F2:사례 Example' 카테고리의 다른 글
17세부터 20세까지, 상황별 연령제한은 제각각 (0) | 2008.12.28 |
---|---|
데이터 모델링(Data Modelling) (0) | 2008.09.19 |
Vista64bit에서 PC매니저 실행시 FsUsbService64 에러 창이 뜨는 경우 조치방법 (1) | 2008.05.28 |
2007년 구입했던, 내 PC 사양 (0) | 2008.02.03 |
Google 경영진 이력 보기 (1) | 2007.06.20 |