Prototyping

Problem and intended use

• Defining what a prototype needs to demonstrate.
• Separating assumptions from observations before further development.

Proposed technical approach

Review the concept and interfaces, then agree the questions the prototype should explore.

Relevant capabilities

• Concept and interface review.

Indicative deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Prototype brief and agreed evaluation questions.

Information and resources required

• Share the concept, constraints and existing work.
• Identify available hardware, data and resources.
• Agree what the prototype should and should not be used to evaluate.

Evaluation questions and scope limitations

What should the prototype demonstrate, and which assumptions can be reviewed through documented observations?

This is a proposed project type for discussion. The prototype or implementation scope and review criteria must be agreed before work is scheduled.

Problem and intended use

• Defining what a prototype needs to demonstrate.

Proposed technical approach

Discuss integration planning against an agreed demonstration or implementation scope.

Relevant capabilities

• Concept and interface review.
• Hardware and software integration planning.

Indicative deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Prototype brief and agreed evaluation questions.
• Agreed demonstration or implementation scope.

Information and resources required

• Share the concept, constraints and existing work.
• Identify available hardware, data and resources.
• Agree what the prototype should and should not be used to evaluate.

Evaluation questions and scope limitations

Which integration questions should the demonstration explore, and what should it not be used to evaluate?

This is a proposed project type for discussion. The prototype or implementation scope and review criteria must be agreed before work is scheduled.

Problem and intended use

• Separating assumptions from observations before further development.

Proposed technical approach

Discuss evaluation and iteration using agreed questions, then document the observations and technical notes.

Relevant capabilities

• Iteration and evaluation discussions.

Indicative deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Prototype brief and agreed evaluation questions.
• Technical notes and documented observations.

Information and resources required

• Share the concept, constraints and existing work.
• Identify available hardware, data and resources.
• Agree what the prototype should and should not be used to evaluate.

Evaluation questions and scope limitations

Which observations answer the agreed questions, and what limits should be recorded before further development?

This is a proposed project type for discussion. The prototype or implementation scope and review criteria must be agreed before work is scheduled.