Rational Modeling: Components Diagram

Component diagrams

In UML, component diagrams show the structure of the software system, which describes the software components, their interfaces, and their dependencies. You can use component diagrams to model software systems at a high level or to show components at a lower, package level.

This type of diagram supports component-based development in which a software system is divided into components and interfaces that are reusable and replaceable.

Component diagrams are useful for the following reasons:
  • Defining the executable and reusable aspects of a software system
  • Revealing software configuration issues through dependency relationships
  • Showing an accurate depiction of a software application before you make changes or enhancements
You can also use component diagrams to depict the following physical parts of a software system:
  • Source code files that you develop in an integrated development environment
  • Executable files that are necessary to deliver a running system
  • Physical databases that store information in the tables of a relational database or in the pages of an object-oriented database
  • Adaptable systems that have components that migrate for load balancing and failure recovery
Note: Component diagrams are distinct from deployment diagrams. A component diagram defines the composition of components and artifacts in the system. A deployment diagram shows components and artifacts in relation to where they are used in the deployed system.

The following topics describe model elements in component diagrams:

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值