Unit-3
Architectural modelling
Architectural Modelling
• In UML models, artifacts are model elements that represent the physical entities in a
software system. Artifacts represent physical implementation units, such as executable
files, libraries, software components, documents, and databases.
• Artifacts are commonly used in deployment diagrams, but you can also use them in
component diagrams to show the model elements, such as components or classes, that are
manifested in the artifact. Model elements can be manifested in several different artifacts.
• Artifacts are deployed on nodes and specify the physical pieces of information that the
deployment and operation of a system uses or produces. Artifacts can be supported for
deployment on several kinds of nodes.
• In diagrams, compartments display information about the attributes and operations of the
artifact.
• An artifact has a unique name that describes the file or software component that it
represents.
As the following figure illustrates, an artifact is displayed as a rectangle that contains the
name of the artifact. The rectangle also contains the stereotype «artifact» and the artifact
icon.
Patterns and frameworks
Mechanisms and frameworks
Patterns and architecture
Mechanisms
Frameworks
Modelling design patterns
Modeling Architectural patterns
Deployment diagram-A deployment diagram, models the run-time architecture of a system. It
shows the configuration of the hardware elements (nodes) and shows how software elements
and artifacts are mapped onto those nodes.
• Nodes that are devices describe physical pieces of hardware that you can touch.
• Artifacts, on the other side are often files, like source files or executable files for a
program. They are real, but you cannot touch them.
• Deployment diagram shows execution architecture of systems that represent the
assignment (deployment) of software artifacts to deployment targets (usually nodes).
• Nodes represent either hardware devices or software execution environments. They
could be connected through communication paths to create network systems of arbitrary
complexity.
• Artifacts represent concrete elements in the physical world that are the result of a
development process and are deployed on nodes.
• Note, that components were directly deployed to nodes in UML 1.x deployment
diagrams.
• In UML 2.x artifacts are deployed to nodes, and artifacts could manifest (implement)
components. So components are now deployed to nodes indirectly through artifacts.
ARTIFACT DIAGRAM
ARTIFACT DIAGRAM
SYSTEM,MODEL,VIEW
• A set of elements organized to achieve certain objectives form a
system. Systems are often divided into subsystems and described by
a set of models.
• Model − Model is a simplified, complete, and consistent abstraction
of a system, created for better understanding of the system.
• View − A view is a projection of a system’s model from a specific
perspective.
