Lesson map
Lesson 13. Map, example, EX059.
flowchart TD
A["Budgeting app would add a supplier"] --> B["Board asks security questions"]
B --> C{"Is there a signature or a new print row?"}
C -->|No| D["Keep the questions and the old print"]
C -->|Yes| E["The file does not show either"]
The map shaped a decision before money was spent. It did not record a signature.
Logical drawing
overview, used before a purchase
new supplier would hold transaction data
another dependency on the identity provider
board
asks vendor security questions before signing
not in the file
a signature
a vendor name
a new services-dictionary row
Learning outcomes
After this chapter, you should be able to:
- Keep the budgeting app as an unsigned proposal.
- Keep the board's questions as the recorded action.
- Leave the dependency print unchanged.
13.1 The board asked. The file does not show a signature.
When the board considers a budgeting app, the architecture overview shows a new supplier holding transaction data and another dependency on the identity provider. The board asks the vendor security questions before signing. A classmate treats the questions as a signature, names a vendor, and adds the app to the dependency dictionary so identity moves from 6 to 7. The book records the questions and does not record a signature or a name. Leah does not insert a row. She does not edit lab_deps.py. The older print stays the count already run.
13.2 Worked example
Lesson table; scroll horizontally to read all columns →
| Step | In the file | Decision |
|---|---|---|
| The app would add a supplier and an identity dependency | The overview discussion | May stay |
| Questions were asked before signing | The board's action | May stay |
| "They signed." | No signature | Refuse |
| "Add the app and print identity 7." | No new run | Refuse |
Synthetic case. No vendor is named. No contract is signed in this lesson.
Errors and limits
Questions before signing do not answer themselves. The book does not record what the vendor replied.
Apply
- EX059 — Did anyone sign? The board asks security questions about a budgeting app before signing. A classmate says the app was signed and adds it to the dependency print. What happened, and what do you not add?
Show marking criteria
Rubric: 3 = questions before signing stay the recorded action; a signature is not in the file; do not name a vendor; do not add a row; do not edit the script;; 2 = asking is not signing;; 1 = one of those;; 0 = none.