Integrative computing for dependable business work

Allow two hours. Prerequisites: introductory Python, basic SQL and the four linked readings. All records are synthetic. The database is in memory; no production files, services or credentials are used.

Algorithms: contract → representation → algorithm → invariant → review

Input A,B,A,C,B,D contains repeated A and B. Pairwise detection examines 15 pairs; the seen-set procedure runs six iterations. Predict both results, test empty/unique/repeated input and explain the equality rule. Counted iterations differ from processor operations and elapsed time. Submit a contract, invariant and scaling argument.

Databases: question → schema → constraint → query → review

Two customers and three orders produce C1 total300 and C2 total50. Enable foreign keys and reject an unknown customer reference. Submit keys, record grain, grouped query and interpretation. Structural correctness does not verify source accuracy, concurrent behaviour, logging or recovery. The fixture creates no on-disk database.

Software engineering: requirement → change → evidence → release → recovery

The amount contract accepts nonnegative integer smallest-unit values, including zero, and rejects negative values, booleans and nonintegers. Design tests from the requirement, not just the function's present output. Submit a user contract, failure case, version note and release/recovery checklist. A pure validator does not establish a complete order system.

Networks/cloud: request → identity → effect → failure → recovery

First R1/O1 creates event1; repeating it returns the same result without another effect. R2/O2 creates event2. Reusing R1 with O2 fails. Change the returned dictionary and check the fixture's internal record remains unchanged. Create a new fixture to observe loss of state on restart. This single-thread in-memory model provides no durable exactly-once distributed guarantee.

Run and test

Save integrative_systems.py and tests together.

python3 integrative_systems.py
python3 -m unittest integrative_systems_test.py

Expected results: duplicates A/B;15pairs versus6iterations; totals C1:300,C2:50; first and retry event1,new request event2;effects2. Set display order can differ; compare content rather than incidental ordering.

Departmental portfolio and review

Explain how sales identifies orders, operations controls proof versions, finance reconciles amounts, support investigates exceptions and IT maintains implementation. Who defines identity; whom an error affects; whose records apply; what changes; where state persists; when review happens; why the approach fits; which boundary remains; how recovery is checked? Include workload and customer effort. Submit four separate artefacts and a combined managerial memo.

Readings

• global brief 09
• global brief 10
• global brief 11
• global brief 12

Selected free primary resources

• MIT OCW algorithms syllabus, Spring2020 — archived prerequisites and topic outline; public course material is not enrolment or credit.
• CMU database systems schedule, Fall2025 — public outline with notes/slides links; not all assigned readings or projects audited.
• Missing Semester2026 — public tools, debugging, Git and code-quality material; selected index review only.
• Microsoft cloud responsibility guidance — illustrative provider guidance; actual service terms and configuration require their own review.

Sources inspected4October2026. Original integrative lessons do not claim comprehensive global university comparison or full coverage of any cited course.