K-12 System Engineering Curriculum

[xitaqua]

Hello fellow Systems Engineers,

INCOSE is planning to make a major push into K-12 Systems Engineering curriculum using robotics as a learning platform....

What kind of topics you think should be covered ?

Cheers,
Marcos.

[dtengineering]

Torque. (http://botshop.wordpress.com/2008/09/15/torque-it-all-comes-down-to-torque/)
I'd say that 90% of the first order of approximation robot design equations that I assign to students to solve are all based on moments.

Jason

[xitaqua]

Very cool !. What I really like about the information you have provided is that it is "Mechanical Engineering K-12 ready".

This is the type of information hopefully INCOSE can collect, and also working with other professional organizations be able to develop something to help the mentors work with the teams.

From System Engineering perspective, I see the following processes :

0) Team Building Development (Survey)
1) Requirement Shaping.
2) Brainstorming.
3) Downselect.
4) Design - Decompose
5) Detailed Design
6) Testing (Structure)
7) Testing Mission
8) Testing (Performance)
9) Reporting
10) Upgrade for Demo Robot.

Let me know what you guys think......

Cheers,
Marcos.

[Siri]

(Note: not a systems engineer)

I like your 0-10 list, especially #1 (and #1, and also #1).

The big things I'd highlight (other than #1) are the role/importance of SysE, flowing down and tracking back all the way to 0-level, trade-offs/partials and margins. Oh, and documentation. And then some more documentation. And then maybe a little more.

From a different angle, our student space systems lab loves using the stuff from Gentry Lee's JPL talks (http://spacese.spacegrant.org/index.php?page=videos). He does a great job describing the personal traits of SysEs. Lee's also a fantastic lecturer himself, but they do run a little long in full (45min-1hr).