1. |
Exposition of PBL, organization of teams and definition of a problem to be solved |
Considering keywords for PBL's theme |
60minutes |
2. |
Requirements analysis and definition (objective, current situation, needs) (in teams) |
Gathering items of objective, current situations and needs,and summarizing them |
120minutes |
3. |
Goal setting and budget planing (in teams) |
Summarizing a goal, and making budget planing |
120minutes |
4. |
1st design review for system planing and budget planing |
Summarizing comments of design review |
100minutes |
5. |
Feed back results of 1st DR to modify system planning and budget planing (in teams) |
Represent comments in design review to goal and budget plan |
120minutes |
6. |
Verification & Validation (V&V) planing (in teams) |
Summarizing V&V items |
120minutes |
7. |
Activities (research, design, modelling) |
Documentation of activities' results |
120minutes |
8. |
2nd design review for activities (in teams) |
Summarizing comments of design review |
100minutes |
9. |
Feed back results of DR, and activities (simulation, trial or prototyping) (in teams) |
Represent comments in design review to activities |
120minutes |
10. |
Activities (simulation, trial or prototyping) (in teams) |
Documentation of activities' results |
120minutes |
11. |
Feed back results of activities to improve work (in teams) |
Documentation of activities' results |
120minutes |
12. |
V&V for project results and documentation for final presentation (in teams) |
Preparing the final presentation material |
120minutes |
13. |
Final design review for projects |
Summarizing comments of final presentation |
100minutes |
14. |
Documentation for system specification (in teams) |
Represent comments in final presentation to final report |
100minutes |
Making post-review via final presentation |
20minutes |
15. |
Discussion for this PBL |
|
|
Total. |
- |
- |
1560minutes |