Robotics engineering

Problem and intended use

• Turning an application idea into a defined system requirement.

Proposed technical approach

Review the intended task and system interfaces before agreeing the prototype scope.

Relevant capabilities

• System and interface planning.
• Prototype evaluation and technical documentation.

Indicative deliverables

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

• System scope and interface outline.
• Agreed prototype or implementation notes.
• A review plan and documented observations.

Information and resources required

• Describe the intended task and operating context.
• Share available hardware, constraints and existing work.
• Agree evaluation criteria and access to required resources.

Evaluation questions and scope limitations

What task should the prototype demonstrate, and which observations would meet the agreed review criteria?

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

• Connecting sensing, movement and control within a prototype.

Proposed technical approach

Review sensing, movement and control interfaces in the context of the available hardware.

Relevant capabilities

• System and interface planning.
• Control and sensing integration discussions.

Indicative deliverables

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

• System scope and interface outline.
• Agreed prototype or implementation notes.

Information and resources required

• Describe the intended task and operating context.
• Share available hardware, constraints and existing work.
• Agree evaluation criteria and access to required resources.

Evaluation questions and scope limitations

Which interfaces need review, and how will their behavior be observed within the agreed prototype scope?

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

• Turning an application idea into a defined system requirement.
• Connecting sensing, movement and control within a prototype.

Proposed technical approach

Discuss the system requirements, available hardware and criteria for reviewing the prototype.

Relevant capabilities

• System and interface planning.
• Prototype evaluation and technical documentation.

Indicative deliverables

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

• System scope and interface outline.
• A review plan and documented observations.

Information and resources required

• Describe the intended task and operating context.
• Share available hardware, constraints and existing work.
• Agree evaluation criteria and access to required resources.

Evaluation questions and scope limitations

What observations should the review document, and what resources are required to make that review meaningful?

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