Debug Workbench – New in Enterprise Architect 6.5 – Enterprise Architect 6.5 now comes with a new Workbench feature.

Debugging Java – Importing, debugging and running Java source code in Enterprise Architect, and automatic generation of sequence diagrams.

Visualizing ASP.NET – Visualizing and inspecting your ASP.NET web service is made easy using Enterprise Architect.

Debugging C# – Importing, debugging and running C# source code in Enterprise Architect, and automatic generation of sequence diagrams.

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.

Features:

Node
A Node can either be a hardware or a software element and is shown via a three-dimensional box shape.

Node Instance
For example, node instances are shown on diagrams. You can distinguishe an instance from a node, if its name is underlined and has a colon before its base node type. An instance can or can not have a name before the colon.

Node Stereotypes

There are a lot standard stereotypes provided for nodes:
«cdrom»
«cd-rom»
«computer»
«disk array»
«pc»
«pc client»
«pc server»
«secure»
«server»
«storage»
«unix server»
«user pc»
Displayed by an appropriate icon in the top right corner of the node symbol.

Artifacts
Artifacts are products of a software development process including  process models, source files, executables, design documents, test reports, prototypes and user manuals.

Association
The association represents a communication path between nodes.

Node as Container
Within a node you can also contain other elements, like components or artifacts.

Role Binding
The role binding connector draws from a collaboration to the classifier that fulfils the role, shown by a dashed line.

Represents
Represents are drawn from a collaboration to a classifier showing that a collaboration is used in the classifier. Graphically viewed by a dashed line with arrowhead and the keywort “represents”.

Occurrence
To show that a collaboration represents its classifier, an occurrence connector is drawn from a collaboration to a classifier, shown as adashed line with arrowhead and the keyword “occurrence”.

Here you can read part 1 of the UML 2 composite structure diagram.

Part
Parts are elements which represent a set of one or more instances that are owned by a containing classifier instance and it is shown as an unadorned rectangle contained within the body of a class or component element.

Ports
Ports are defining interaction between a classifier and its environment, shown with a named rectangle on the boundary edge of its owning classifier.

Interfaces
Interface operations are public and abstract and they are similar to a class having a lot of restrictions. It can be shown as a circle.

Delegate Connector
The delegate connector connects an external contract of a component as shown by its ports to the internal realization of the behavior of the component’s part to view an internal working of a component’s external ports and its interfaces.

Don’t miss part 2 of the UML2 composite structure diagram.

Generalizations
With a generalization you indicate inheritance. If it’s drawn from a specific classifier to a general classifier, the generalize implication is that the source inherits the target’s characteristics.

Aggregations
Aggregations are depicting elements which are made up of smaller components. This aggregation relationships will be shown by a white diamond-shaped arrowhead pointing towards the target or parent class.

Association Classes
With an association class you can construct an association connection to make operations and attributes.

Dependencies
If you need to model a wide range of dependent relationships between model elements you use dependencies. This will be done early in the design process. Later on the dependencies will be stereotyped or replaced with more specific data.

Traces
With traces yo can easily track requirements or model changes, because it is a specialization of a dependency, linking model elements or sets of elements, representing the same idea across models.

Realizations
A realization expresses traceability and completeness in a model.

Nestings
Nestings are connectors showing source elements within a target element.

Click to read part 1 of the UML 2 Class Diagram

Definitions:
Classes
Classes are elements that define the attributes and behaviors of an object . A behavior describes possible messages of the class along with operations. Within classes you can also define constraints, tagged values and stereotypes.

Class Notation
A class shows the name of the class and optionally the name of the operations and attributes. The compartments divides the class name,  attributes and operations.

Interfaces
The interface is a contract with a specification of behaviors that implementers agree to meet. In an interface, classes are guaranteed to support the required behavior. You may draw the interface in a similar style to a class, specified with operations, or you draw it as a circle with no details to explicit operations.

Tables
Tables are not a part of the base UML, it’s more an example of what can be done with stereotypes. When a table is drawn you can see a small table icon in the upper right corner.

Following in part 2 of the UML Class Diagram.

With components you define boundaries and group elements into logical structures. These component diagrams are similar in practice to package diagrams, the differences between package diagrams and component diagrams are, that component diagrams are offering  more semantically rich grouping mechanism and  in component diagrams all elements of the model are private, whereas package diagrams are displaying public items.

Key features for rich modeling power with UML 2.1 and Enterprise Architects:

• Seamless integration of Enterprise Architect and UML 2.1 into Microsoft Visual Studio
• Navigate and refine the development model using UML, allowing model and code to become one
• Generate high quality, template driven, reports in Rich Text and HTML format
• Share blueprints between analysts, architects and developers
• Collaborate with team members and improve communication using the built-in model discussion forum
• Fast-track development with MDA transforms
• Visualise and model database schemes, WSDL and XSD documents

Here you can download the MDG Integration VS Trial Version, a fully functional 30 day version. Click to purchase the full version of MDG Integration for Visual Studio.

Please be sure you have installed

- Enterprise Architect Version 7.1 Build 826 (or greater), Professional and Corporate Editions only
- Visual Studio 2005/2008

on your system.

For further information on MDG Integration into UML take a look at this sites:

• 1 page summary
• Detailed PowerPoint presentation
• 20 Minute multimedia presentation
  • Streaming media (Shockwave)
  • Downloadable zip file (22Mb)

If you have questions, don’t hesistate to contact us directly at sales(at)sparxsystems.at.