Deployment Diagram

Deployment Diagram

1. Text of three paragraphs

   • Paragraph one: The Deployment Diagram is a structured diagram that shows the architecture of the system from the point of view of the deployment (distribution) of the software artifacts in the deployment destinations.
   • Paragraph two: The artifacts represent concrete elements in the physical world that are the result of a process of development. Examples of artifacts are executable files, libraries, files, database schemas, configuration files, etc.
   • Paragraph tree: Deployment destination is usually represented by a node that is either hardware devices or some software execution environment. The nodes can be connected through communication channels to create network systems of arbitrary complexity.

2. Main idea of ​​the text

   • The Deployment Diagram is a structured diagram that shows the architecture of the system from the point of view of the deployment (distribution) of the software artifacts in the deployment destinations.

3. VOCABULARY

   • Unknown Vocabulary
     • Architecture: is a set of patterns that provide a necessary frame of reference to guide the construction of software, allowing programmers, analysts and the entire set of software developers to share the same line of work and cover all the objectives and restrictions of the application.
     • Deployment diagram: The deployment diagrams are the complements of the component diagrams that, together, provide the view of the implementation of the system. The topology of the system describes the structure of the hardware elements and the software that executes each one of them.
     • Software artifacts: They are the result of partial or final work that is produced and used during a project. The artifacts are used to capture and carry project information. An artifact can be: A document: as a Business Case or a document of the architecture of the Software. A model: as a use case model. An element of a model: as a single class of the entire Class Diagram.
     • Executable files: Executable files consist of instructions that have been translated from their original source code to machine code, also called machine language or object code through the use of a specialized program called compiled.
     • Node: a node is a point of intersection or union of several elements that converge in the same place
     • Software ejecution: Software tests consist of the dynamics of the verification of the behavior of a program in a finite set of test cases, duly selected from usually infinite domain executions, against the expected behavior.
     • Arbitrary complexity: The complex condition is made up of several events. When the condition is complex, the effects of the legal act will occur, suspensive condition, or cease, condition resolutory, when all the events put as a condition have been made.
     • Architecture: is a set of patterns that provide a necessary frame of reference to guide the construction of software, allowing programmers, analysts and the entire set of software developers to share the same line of work and cover all the objectives and restrictions of the application.