1 files changed, 37 insertions, 0 deletions
diff --git a/src/uml/qumldependency.cpp b/src/uml/qumldependency.cpp
index db2eeeb5..6620b41e 100644
--- a/src/uml/qumldependency.cpp
+++ b/src/uml/qumldependency.cpp
@@ -60,12 +60,19 @@ QT_BEGIN_NAMESPACE
 
     \brief A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation. This means that the complete semantics of the depending elements is either semantically or structurally dependent on the definition of the supplier element(s).
  */
+
+/*!
+    Creates a new QUmlDependency. Also creates the corresponding QObject-based representation returned by asQModelingObject() if \a createQModelingObject is true.
+*/
 QUmlDependency::QUmlDependency(bool createQModelingObject)
 {
     if (createQModelingObject)
         _qModelingObject = qobject_cast<QModelingObject *>(new QUmlDependencyObject(this));
 }
 
+/*!
+    Returns a deep-copied clone of the QUmlDependency.
+*/
 QModelingElement *QUmlDependency::clone() const
 {
     QUmlDependency *c = new QUmlDependency;
@@ -92,6 +99,12 @@ QModelingElement *QUmlDependency::clone() const
 
 /*!
     The element(s) dependent on the supplier element(s). In some cases (such as a Trace Abstraction) the assignment of direction (that is, the designation of the client element) is at the discretion of the modeler, and is a stipulation.
+
+    \sa addClient(), removeClient()
+
+    \b {Subsetted property(ies):} QUmlDirectedRelationship::sources().
+
+    \b {Opposite property(ies):} QUmlNamedElement::clientDependencies().
  */
 const QSet<QUmlNamedElement *> QUmlDependency::clients() const
 {
@@ -100,6 +113,11 @@ const QSet<QUmlNamedElement *> QUmlDependency::clients() const
     return _clients;
 }
 
+/*!
+    Adds \a client to clients.
+
+    \sa clients(), removeClient()
+ */
 void QUmlDependency::addClient(QUmlNamedElement *client)
 {
     // This is a read-write association end
@@ -119,6 +137,11 @@ void QUmlDependency::addClient(QUmlNamedElement *client)
     }
 }
 
+/*!
+    Removes \a client from clients.
+
+    \sa clients(), addClient()
+ */
 void QUmlDependency::removeClient(QUmlNamedElement *client)
 {
     // This is a read-write association end
@@ -138,6 +161,10 @@ void QUmlDependency::removeClient(QUmlNamedElement *client)
 
 /*!
     The element(s) independent of the client element(s), in the same respect and the same dependency relationship. In some directed dependency relationships (such as Refinement Abstractions), a common convention in the domain of class-based OO software is to put the more abstract element in this role. Despite this convention, users of UML may stipulate a sense of dependency suitable for their domain, which makes a more abstract element dependent on that which is more specific.
+
+    \sa addSupplier(), removeSupplier()
+
+    \b {Subsetted property(ies):} QUmlDirectedRelationship::targets().
  */
 const QSet<QUmlNamedElement *> QUmlDependency::suppliers() const
 {
@@ -146,6 +173,11 @@ const QSet<QUmlNamedElement *> QUmlDependency::suppliers() const
     return _suppliers;
 }
 
+/*!
+    Adds \a supplier to suppliers.
+
+    \sa suppliers(), removeSupplier()
+ */
 void QUmlDependency::addSupplier(QUmlNamedElement *supplier)
 {
     // This is a read-write association end
@@ -160,6 +192,11 @@ void QUmlDependency::addSupplier(QUmlNamedElement *supplier)
     }
 }
 
+/*!
+    Removes \a supplier from suppliers.
+
+    \sa suppliers(), addSupplier()
+ */
 void QUmlDependency::removeSupplier(QUmlNamedElement *supplier)
 {
     // This is a read-write association end