Under the configuration management, use the tools such as tagged values, author, version number…etc, for each file. Identify the different files used in the source code. A component may be A source code component A run time components An executable component Dependency relationship.Ĥ 33.3 Modelling Techniques To model a system’s source code The diagram can be shown at a very high level, with just the large-grain components, or it can be shown at the component package level. Its purpose is to show the dependencies that the software has on the other software components. A component diagram provides a physical view of the system. UML component diagrams are great for identifying the architectural landscape for a system as they enable us to model the high-level software components, and more importantly the interfaces to those components. Presentation on theme: "Component and Deployment Diagrams"- Presentation transcript:Ģ 33.1 Component Diagram The main purpose of a component diagram is to show the structural relationships between the components of a system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |