Skip to content

Commit

Permalink
add lab slides
Browse files Browse the repository at this point in the history
  • Loading branch information
Solomon Berhe committed Feb 7, 2025
1 parent aa5d58c commit e907e14
Show file tree
Hide file tree
Showing 2 changed files with 255 additions and 1 deletion.
256 changes: 255 additions & 1 deletion i40/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,8 @@ <h4>Welcome<br> Software Engineering in Industry 4.0 Ecosystems</h4>
<tr style="color: #ccc;">
<td style="padding: 6px; border: 1px solid #666;">4 (Feb <a href="./#/feb-3">3</a>, <a
href="./#/feb-5">5</a>,
7)</td>
<a href="./#/feb-3">3</a>, <a href="./#/feb-7">7</a>)
</td>
<td style="padding: 6px; border: 1px solid #666;"><a href="./#/module-4">Development
Processes in Industry 4.0</a></td>
<td style="padding: 6px; border: 1px solid #666;">Project Part 1 (4w)</td>
Expand Down Expand Up @@ -2844,6 +2845,259 @@ <h3>Question?</h3>
</ul>
</section>

<section id="feb-7">
<h4>February 7, 2025</h4>
<ul>
<li>Development Processes in Industry 4.0</li>
<li>Course Project - Feature Branch Workflow</li>
<li>Course Project - Ticket / Workflow Integration/Automation</li>
<li>Course Project - Sprint #2 Demo</li>
<li>Practice Questions</li>
</ul>
</section>

<section data-background="white">
<h4>Development Processes in Industry 4.0</h4>
<img style="height: 400px;"
src="https://www.researchgate.net/profile/Max-Santos-4/publication/314665883/figure/fig1/AS:562033478127616@1511010631572/Model-life-cycle-for-the-automotive-software-testing.png"
alt="Feature Branch Workflow" style="max-width: 80%; height: auto;">
</section>

<section>
Focus on End-to-End Testing, Verification, and Validation
</section>

<section data-background="white">
<h4>Development Processes in Industry 4.0</h4>
<img style="height: 400px;" src="scrum-wf.png" alt="Feature Branch Workflow"
style="max-width: 80%; height: auto;">
</section>

<section>
Focus on Fast and Incremental Outcome (not Output)
</section>

<section>
<h4>Development Processes in Industry 4.0</h4>
<table border="1">
<thead>
<tr>
<th>Aspect</th>
<th>Apply Scrum</th>
<th>Apply V-Model</th>
</tr>
</thead>
<tbody>
<tr>
<td>Legal Compliance</td>
<td><span class="highlight">After</span> requirements phase </td>
<td><span class="highlight">During</span> requirements phase</td>
</tr>
<tr>
<td>UI/UX Design</td>
<td><span class="highlight">Minor</span> changes</td>
<td><span class="highlight">Major</span> requirements</td>
</tr>
<tr>
<td>System Updates</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Implementation</span> phase</td>
</tr>
<tr>
<td>Sensor Data Collection</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Implementation/testing/production</span> phase</td>
</tr>
<tr>
<td>Integration Testing</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Testing</span> phase</td>
</tr>
<tr>
<td>Hardware Development</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Implementation</span> phase</td>
</tr>
<tr>
<td>Functional Specifications</td>
<td><span class="highlight">Minor</span> function changes at any phase</td>
<td>At <span class="highlight">requirements</span> phase</td>
</tr>
<tr>
<td>Iterative Feature Development</td>
<td><span class="highlight">Minor</span> feature changes at any phase</td>
<td>At <span class="highlight">requirements</span> phase</td>
</tr>
<tr>
<td>End-to-End Testing</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Testing/production</span> phase</td>
</tr>
<tr>
<td>Quality Assurance</td>
<td>Every <span class="highlight">sprint</span></td>
<td><span class="highlight">Testing/production</span> phase</td>
</tr>
<tr>
<td>Purchase Hardware</td>
<td>As <span class="highlight">early</span> as possible</td>
<td><span class="highlight">Implementation</span> phase</td>
</tr>
<tr>
<td>Communication with Stakeholders</td>
<td>Weekly at <span class="highlight">sprint demo</span></td>
<td><span class="highlight">System testing</span> phase</td>
</tr>
</tbody>
</table>
</section>

<section>
Questions?
</section>

<section>
<h4>February 7, 2025</h4>
<ul>
<li>Development Processes in Industry 4.0 &check;</li>
<li>Course Project - Feature Branch Workflow</li>
<li>Course Project - Ticket / Workflow Integration/Automation</li>
<li>Course Project - Sprint #2 Demo</li>
<li>Practice Questions</li>
</ul>
</section>

<section>
<h3>Feature Branch Workflow</h3>
<img style="height: 400px;"
src="https://wac-cdn.atlassian.com/dam/jcr:34c86360-8dea-4be4-92f7-6597d4d5bfae/02%20Feature%20branches.svg?cdnVersion=2542"
alt="Feature Branch Workflow" style="max-width: 80%; height: auto;">
</section>

<section>
<h4>Course Project - Feature Branch Workflow</h4>
<ul>
<li>Create feature branch for each user story</li>
<li>Avoid feature branch for epics or tasks</li>
<li>Feature branch <span class="highlight">must</span> start with <span
class="highlight">"feature-ticket-"</span></li>
<li>Push to main branch through pull request review</li>
</ul>
</section>

<section>
<h4>Step 1 </h4>
<p>Please start visual studio</p>
</section>

<section>
<h4>Step 2</h4>
<pre><code>
git clone https://github.com/SE4CPS/PlantWaterSystem.git
</code></pre>
</section>

<section>
<h4>Step 3</h4>
<pre><code>
git checkout -b feature-ticket-123-add-refresh-button
</code></pre>
</section>

<section>
<h4>Step 4</h4>
<pre><code>
git commit -m "Added flower data refresh functionality"
</code></pre>
</section>

<section>
<h4>Step 5</h4>
<pre><code>
git push origin feature-ticket-123-add-refresh-button"
</code></pre>
</section>

<section>
<h4>Step 6</h4>
<a href="https://github.com/SE4CPS/PlantWaterSystem/pulls" target="_blank">GitHub Pull Requests</a>
</section>

<section>
<h4>February 7, 2025</h4>
<ul>
<li>Development Processes in Industry 4.0 &check;</li>
<li>Course Project - Feature Branch Workflow &check;</li>
<li>Course Project - Ticket / Workflow Integration/Automation</li>
<li>Course Project - Sprint #2 Demo</li>
<li>Practice Questions</li>
</ul>
</section>

<section>
<h4>Course Project - Ticket / Workflow Integrating</h4>
<p>Performing through <span class="highlight">automated ticket closing</span></p>
</section>

<section>
<h4>Git Commit Close Ticket Example</h4>
<pre><code>

git commit -m "Closes #123: Added flower data refresh functionality"

</code></pre>
</section>

<section>
<h4>Git Commit Close Ticket Example</h4>
<pre><code>

git commit -m "Fixes #123: Added flower data refresh functionality"

git commit -m "Resolves #123: Added flower data refresh functionality"

</code></pre>
</section>

<section>
<h4>Fixes vs. Resolves in GitHub Commits</h4>
<ul>
<li><strong>Fixes #123:</strong> Used when the commit directly addresses a bug or issue
<br>➡️ The issue is automatically closed when merged
</li>
<li><strong>Resolves #123:</strong> Used for enhancements or non-bug-related improvements
<br>➡️ The issue is closed when merged, but it implies a major resolution rather than just a
bug fix
</li>
</ul>
</section>

<section>
Questions?
</section>

<section>

<a href="https://github.com/SE4CPS/PlantWaterSystem/issues/19" target="_blank">Sprint #2 Demo 🙂</a>

</section>

<section>
<p><a href="https://github.com/SE4CPS/PlantWaterSystem/issues" target="_blank">Backlog Grooming</a>
</p>
</section>

<section>
<p><a href="https://github.com/orgs/SE4CPS/projects/19" target="_blank">Sprint Planning</a>
</p>
</section>

<section>
<p><a href="https://github.com/orgs/SE4CPS/projects/19/settings" target="_blank">Sprint
Retrospective</a>
</p>
</section>

<section id="module-5">
<h4>Module 5<br>Architectural Design for Industry 4.0 Applications</h4>
</section>
Expand Down
Binary file added i40/scrum-wf.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit e907e14

Please sign in to comment.