Funky System Prototype Background

Funk.tional System Prototype Background

What is a Funk.tional Prototype?

A FUNKtional prototype is one for which existing parts have been hacked and brought together in a manner that approximates a system without making a costly commitment to any one configuration, technology, or geometry. It is a low-commitment, rapidly assembled, concept prototype that still allows for objective evaluation and testing. The emphasis is on creating a physical system that performs the desired function.

This is not a critical function prototype; it is a system level prototype. This shift in perspective is important for two reasons:

• It is the beginning of an understanding of what will be required in terms of integration. Systems integration can be challenging, and is usually underestimated in terms of the time commitment involved.  For now, skimp on "low-risk" subsystems and components, as well as finishing and stylizing. However, you should produce a systems-level diagram to illustrate what you think will be involved

• This prototype also marks the beginning of convergence toward a common view for Stanford and overseas teams on what the project will ultimately encompass. By the end of winter quarter, we expect a unified understanding of the project scope. What all should be demonstrated in June to have a convincing project? What is beyond scope?

Manufacturability is not an issue ...yet. Your audience is an internal one. In the case of a startup company, this would be your advisory board; in the case of ME310, it’s your TTeam, liaison, coach and peers. You want to demonstrate to them that:

• You understand the scope of the problem

• You are on-track with a viable solution or approach

• You have a workable plan to achieve success

At all times keep a record of:

1. what you did

2. why you did it

3. what you learned from doing it.

The Funk.tional Prototype Review will be scored on the following criteria:

• Content: What the prototype is. Its ability to answer critical questions.

  • Content includes your understanding of completeness of the system. What will "the system" ultimately encompass?

• Presentation: The clarity of information and line of reasoning that guided your choice of questions and prototype. The effectiveness of your bench top presentation, demonstration, and handout.

Attendance: Attend and participate in peer review of at least one other team's session.

Why does this mission belong on your Resume?

This Mission is evidence that you can deliver team-based, integrated "proof-of-concept" systems, rapidly and at low cost.

Rationale for the Industry Liaisons (in case they do not understand)

Too often the professional work environment dictates that "prototypes" must be up to professional standards of excellence, craftsmanship, and precision. We argue that getting the problem and solutions space defined correctly trump precision and craftsmanship at this stage of development.

"The clothes are funky, the sideburns are long, and the attitude is far out."