Automated MkDocs build
This commit is contained in:
@@ -1168,14 +1168,14 @@ An animal object <em>is part of</em> a compound object (semantically) but the an
|
||||
<span class="w"> </span><span class="p">}</span>
|
||||
<span class="p">}</span>
|
||||
</code></pre></div>
|
||||
<p><img alt="Image" src="../assets/1.png" /></p>
|
||||
<p><img alt="Image" src="/lectures/dms/assets/1.png" /></p>
|
||||
<p><em>Composition</em> - The object only exists if the parent object exists, if the parent object is deleted then so is the child object.
|
||||
The zoo object owns the compound object. If the zoo object is deleted then the compound object is also deleted.</p>
|
||||
<div class="highlight"><pre><span></span><code><span class="kd">public</span><span class="w"> </span><span class="kd">class</span> <span class="nc">Zoo</span><span class="w"> </span><span class="p">{</span>
|
||||
<span class="w"> </span><span class="kd">private</span><span class="w"> </span><span class="n">Compound</span><span class="w"> </span><span class="n">dogArea</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="k">new</span><span class="w"> </span><span class="n">Compound</span><span class="p">();</span>
|
||||
<span class="p">}</span>
|
||||
</code></pre></div>
|
||||
<p><img alt="Image" src="../assets/2.png" /></p>
|
||||
<p><img alt="Image" src="/lectures/dms/assets/2.png" /></p>
|
||||
<p><strong>Inheritance</strong>
|
||||
A way of forming new classes based on existing classes. Has a "is-a" relationship.</p>
|
||||
<p><em>Polymorphism</em> - A concept in object oriented programming. Method overloading and method overriding are two types of polymorphism.
|
||||
@@ -1193,7 +1193,7 @@ A way of forming new classes based on existing classes. Has a "is-a" relationshi
|
||||
<span class="p">}</span>
|
||||
</code></pre></div>
|
||||
<p>The super keyword called the parent class' constructor.</p>
|
||||
<p><img alt="Image" src="../assets/3.png" /></p>
|
||||
<p><img alt="Image" src="/lectures/dms/assets/3.png" /></p>
|
||||
<p><strong>What is the difference between an abstract class and an interface</strong>
|
||||
- Java abstract class can have instance methods that implement a default behaviour. May contain non-final variables.
|
||||
- Java interfaces have methods that are implicitly abstract and cannot have implementations. Variables are declared final by default.</p>
|
||||
|
||||
@@ -1158,7 +1158,7 @@
|
||||
<li>Helps to manage the complexity</li>
|
||||
<li>Enables reuse of design</li>
|
||||
</ul>
|
||||
<p><img src="assets/4.png" alt="img" style="zoom:80%;" /></p>
|
||||
<p><img src="/lectures/dms/assets/4.png" alt="img" style="zoom:80%;" /></p>
|
||||
<h2 id="object-orientated-analysis">Object Orientated Analysis<a class="headerlink" href="#object-orientated-analysis" title="Permanent link">¶</a></h2>
|
||||
<p><strong>Use case diagrams</strong></p>
|
||||
<ul>
|
||||
@@ -1184,7 +1184,7 @@
|
||||
<p><strong><code><<include>></code></strong>- multiple use cases share a piece of same functionality which is placed in a separate use case.</p>
|
||||
<p><strong><code><<extend>></code></strong> - Used when activities might be performed as part of another activity but are not mandatory for a use case to run successfully.</p>
|
||||
<p><strong>Use case diagram of a fleet logistics management company</strong></p>
|
||||
<p><img alt="image" src="../assets/5.png" /></p>
|
||||
<p><img alt="image" src="/lectures/dms/assets/5.png" /></p>
|
||||
<p><strong>Base Path</strong> - The optimistic path (best case scenario)</p>
|
||||
<p><strong>Alternative Path</strong> - Every other possible way the system can be used/abused. Includes perfectly normal alternate use, but also errors and failures.</p>
|
||||
<p>Use Case: <code>Borrow copy of book</code></p>
|
||||
|
||||
Reference in New Issue
Block a user