Biotechnology for Health (Biomedical Innovations)

Unit 1: Problem 1: Effective ER DesignBI 1.1Biomedical Innovation: prototyping & human factors

Log prototype revisions

Keep a clear record of each prototype change, why it was made, and what testing showed: so the design improves on purpose, one iteration at a time.

Builds on (2 levels back)inferred · med confidence

Testing a design against its criteria: A revision log only helps if each change is judged against the brief's criteria, so you first need to know how to test against them.
Recording what you observed, not just opinions: Logging revisions means writing down what testing actually showed; you need the habit of recording evidence before you can track changes honestly.

Prerequisites are inferred: pending teacher review.

Re-learn the skill with worked practice and clear examples.

A revision log records, for each prototype version, what changed, why, and what testing showed: turning random tweaks into deliberate iteration.

Step 1: Capture three things per entry

Every entry names (1) the change you made, (2) the reason for it, usually a failed test, and (3) the result when you tested the new version. Missing any one breaks the record.

Step 2: Tie each change to a test

A revision is iteration only if it answers a test result. You changed the trauma-bay signs because testers got lost; the next test checks whether they now find it. Change, test, repeat: that is one iteration each time.

Step 3: Use human-factors testing

The most useful tests put real people, often under time pressure, in front of the prototype. Watching how stressed users behave reveals problems that look fine on a clean drawing.

Practice

A team's revision-log entry reads: 'Version 2: moved the trauma-bay sign to eye level. Result: 5 of 5 testers found the bay.' What important piece is MISSING from this entry?

Reviewed

A.The reason for the change (what problem it was fixing)
B.The version number
C.The result of the test
D.Nothing is missing

Show the worked solution ▾

Answer: A. The reason for the change (what problem it was fixing)

Step 1: Check the three required parts: A good entry has the change, the reason, and the result. List what is present: the change (moved the sign) and the result (5 of 5 found it).
Step 2: Find the gap: There is no reason: it never says what problem the move was fixing, so a reader cannot tell why the sign was moved.

Why it's right: The entry gives the change and the result but never states the reason (the problem it was solving), which is one of the three parts a revision-log entry needs.

Why the others miss:

B: The version number is present: the entry begins with 'Version 2.'
C: The result is present: '5 of 5 testers found the bay.'
D: Something is missing: the entry never states the reason for the change.

Aligned to Iterative design: revision logging · reading level ~grade 9

Where you'd see this

A prototyping team keeps a version-by-version log so a new member can read why every change was made and never repeats a fix that already failed.

Careers that use this

Biomedical Engineer: Keeps a design-history log of every prototype change and test result, which is also required when a medical device is reviewed for approval.

Video library

Watch: Log prototype revisions

Logging Prototype Revision Evolving Without Breaking

Manuel Mendoza

Guided notes

Fill these in as you work through the lesson.

Big idea: Logging prototype revisions means writing down, for each new version, what you changed, why you changed it, and what testing showed: so the design improves one deliberate iteration at a time.

Key terms: write the meaning

Prototype (an early, testable version of the design):
Iteration (one round of change-then-test, repeated to improve):
Revision log (the record of what changed and why, version by version):
Human factors (how real users perform with the design, especially under stress):

The rule

Each entry in a revision log should record what you , why you changed it, and what the showed, so the next iteration is based on evidence and not on guessing.

Check yourself

Name the three things a useful revision-log entry should include.
Explain why testing a prototype on real users (human factors) gives better revisions than testing it only on paper.
Describe what 'one iteration' means using a change-then-test cycle.

Work one example

A team tested a paper ER floor plan and found that volunteers could not find the trauma bay. Write one revision-log entry for the next version: the change, the reason, and what you would test to see if it worked.