Class - Industrial Programming

Welcome 🤗! In the next ~4h we will cover:

Test
Flowchart analysis
Peer feedback
Core programming concepts
Coding the process
E: Reflection

Spiral Staircase in Vatican Museum Source
© User:Colin / Wikimedia Commons CC BY-SA 3.0 — Spiral Staircase in Vatican Museum Source © User:Colin / Wikimedia Commons CC BY-SA 3.0

Before we begin with the class:

we need two Feedback persons.
Activate notifications for Discussions, if you did not do it yet.
Answer the poll in 📊 Live poll:
How much time did you spent for homework and preparation?
- 0-2 h 🕐🕐
- 3-4 h 🕐🕐🕐🕐
- 5-6 h 🕐🕐🕐🕐🕐🕐
- 7+ h 🕐🕐🕐🕐🕐🕐🕐🕐

Test¶

(15 min)

Accept the assignment

Flowchart analysis¶

Learning goals

Compare flowchart with the text description and check correctness

E: Checking correctness¶

Peer feedback¶

Learning goals

Give feedback based on criteria.
Use a GitHub pull request to give feedback.

Giving feedback¶

Feedback can be formulated easier, if it is based on criteria. Criteria can in return improve how you do a task.

Here is an example, how we can give feedback for Exercise 3:

Example exercise

Input age, then name and store age and name in a database. If the user wants to enter more input, repeat the process.

Example criteria with feedback

Criteria	Comments
Has a start and end	end is missing
Used correct shapes	ok!
Fits description	Age input must come first, more input condition missing
Overall	You have the basics! Try to read the description again after you have drawn the flowchart.

E: Peer feedback using GitHub¶

Exercise 2 (Peer feedback using GitHub)

(10 min)

The instructor will make everyone’s homework repositories public, so you can see your peers’ repositories.

Pick two peers you want to give feedback to. Ask your peers which flowchart they want feedback on. You will give in the class only feedback to one flowchart and one peer. The second peer will be for homework.
On https://github.com/indprog, clickRepositories:
Search and click the repository you want to give feedback to. On the top there is a search bar.
The repository names consist of three parts. For example, indprog-hello-flowchart-geko-st means:
1. Course abbreviation: always indprog
2. Assignment name, e.g., i-know-flowchart
3. The user whose work resides in the repository, e.g., geko-st
Inside the repository, click Pull requests tab:
In pull requests, click the pull request Feedback:
Here you can (1) see the changes the student have done (2) comment on them.
Click Files changed:
Click on the comment icon of the file you want to comment on:
SVG files flowlines are not visible?
If you cannot see the arrowlines between the shapes, then right click on the file and open it in a new tab.

Use the following feedback template and comment on it.

|  Criteria           | Comments | 
|---------------------|----------|
| Has a start and end |          | 
| Used correct shapes |          | 
| Fits description    |          | 
| **Overall**         |          |

Click Preview to see how your text will be rendered.
Click Start a review.
After giving your feedback comments, click Submit review:
A new window will show up.
You can enter concluding comment on your review and leave the rest as defaults. Click Submit review.
Then you will see your feedback in the conversation:

Finally, as the receiver, you should implement the feedback you received and resubmit your assignment as homework, so you have a better work to present in your exam.

Larger picture

We will use Feedback in Pull requests for giving feedback to each other. The feedback pull request presents all the changes the user has done.

Tracking changes is a superpower of repositories.

Core programming concepts¶

Learning goals

Recognize sequence, selection, iteration in processes
Find examples of sequence, selection and iteration
Differentiate between control and data
Recognize condition in selections

E: Matching the three concepts¶

The Big 3¶

We can describe any process using the following 3 structures.

	Structure	Example	Code
	Sequence		altitude-check-sequence.py `1 2altitude = int(input()) print(altitude)`
	Selection		altitude-check-selection.py `3 4 5 6if altitude > 100: print("Circling") else: print("Landing")`
	Iteration^[1]		altitude-check-iteration.py `3 4 5 6 7while altitude > 0: print("Landing\n") altitude = int(input()) print("Landed")`

Structure

Example

Code

Sequence

altitude-check-sequence.py

1
2
altitude = int(input())
print(altitude)

Selection

altitude-check-selection.py

3
4
5
6
if altitude > 100:
    print("Circling")
else:
    print("Landing")

Iteration^[1]

altitude-check-iteration.py

3
4
5
6
7
while altitude > 0:
    print("Landing\n")
    altitude = int(input())

print("Landed")

Control vs data¶

In programming, we distinguish between:

control: deciding what happens
data: the values being worked with

Example: In the altitude example, we have:

control:
- sequence of output, input
- iteration as long as altitude > 0
data:
- altitude
- the messages “Landing” and “Landed”

E: Control vs data¶

Selection vs condition¶

diamond shape is a selection.
- altitude > 100 is its condition.

Condition can be for example:

a == b
- Is a equal to b? Pay attention to double equal sign.
a != b
- Is a different from b?
a > b, a <= b etc
- you already know from math.

E: Selection vs condition¶

Coding the process¶

Now use the previous Big 3 table to code the following examples.

Tip

If you are not familiar with programming, I recommend to draw a flowchart first and then code using the following recipe and the Big 3 table

What is the first block in the process you have to code? Is it an input, output? Replace them with input() and print().
Do you want to introduce a new variable? Use new = x + y

Do you have a selection, or iteration? Use the templates from the Big 3 table, copy paste them, and modify them to fit your process.

While modifying, pay attention to the following concepts and their questions.

Sequence	What comes after what?
Selection	What is the condition? What does the condition decide?
Iteration	What is the condition? What is being iterated over?
Data	What values are being worked with?
Condition	Already part of selection and iteration.🤷

You can open the Big 3 table in a new window, so you can easily copy paste the code snippets into your editor.

E: Area of a square¶

E: Energy level manager¶

E: Counting laps¶

Exercise 8 (Counting laps)

(5 min)

You’re a sports enthusiast building a simple coach app for runners. Ask the runner how many laps they want to run (lap_count). For simplicity, you’ll start by just tracking lap numbers that you have completed. For each lap output the current_lap_number starting from 1 until lap_count laps are completed. Finally outputWorkout done! 💪.^[2]

Test with at least two inputs: 5 and 4. For example, the output for 5 should be:

1
2
3
4
5
Workout done! 💪

Code runner¶

You find the editor on website’s menu on the left: ▶️ Code runner.

E: VSCodium installation support¶

Next time we will use VSCodium to code.

Running a flowchart¶

Drawing flowcharts is already programming! See Running flowcharts, however flowcharts are often not enough to implement processes in detail compared to programming languages.

E: Reflection¶

Footnotes¶

There are other ways to iterate, e.g., do-while or for. We leave them out for now for simplicity.
↩
If you are experienced with coding, then you will say that this problem is better solved with a for iteration. For the sake of slow ramp up for beginners, we use currently only while for iterations.
↩