Automated MkDocs build
This commit is contained in:
@@ -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