Course Name | Year | Term | Period | Faculty / Graduate School | All Instructors | Credits |
---|---|---|---|---|---|---|
35120:PBL: Team-based Design (G1) | 2019 | Fall | Wed3,Fri3 | College of Information Science and Engineering | COOPER ERIC WALLACE、SVININ MIKHAIL、TAKADA HIDEYUKI、DINH THI DONG PHUONG、NISHIMURA TOSHIKAZU、BAI YANG | 4 |
Campus
Class Venue
Language
Course Outline and Method
Student Attainment Objectives
1. Adapt the general design process to design systems, components, or processes to solve open-ended real world problems.
2. Produce a variety of potential design solutions tailored to meet functional specifications.
3. Compare the design solution against the problem objective.
4. Follow protocols when using techniques, skills, and tools.
5. Recognize a variety of working and learning preferences.
6. Apply principles of conflict management to resolve team issues.
7. Demonstrate punctuality, responsibility, and appropriate communication etiquette when working in a project.
8. Participate actively in team-work, contribute to the design and project presentation.
Recommended Preparatory Course
Course Schedule
Lecture/Instructor(When there are multiple instructors) | Theme |
---|---|
Keyword, References and Supplementary Information | |
1〜2 (all instructors) | Course introduction. Project and team formation. |
Engineering project objectives |
|
3〜4 (all instructors) | Socio-technical systems. |
Domain knowledge, Project organization: centralized, decentralized, and mixed-type |
|
5〜6 (all instructors) | Engineering system life cycle. |
Engineering product processes, Product life cycle models |
|
7〜8 (all instructors) | System models and formal specification. |
Domain knowledge, Conceptual and mathematical models, UML |
|
9〜10 (all instructors) | Techniques of requirements engineering. |
Requirements elicitation, Work with domain literature |
|
11〜12 (all instructors) | Techniques of software system design. |
Conceptual design, System architecture, Detailed design, Algorithm design |
|
13〜14 (all instructors) | Techniques of software system design. |
Conceptual design, System architecture, Detailed design, Algorithm design |
|
15〜16 (all instructors) | Techniques of software system design. |
Brainstorming, Component reuse-based design, Analogical reasoning |
|
17〜18 (all instructors) | Project workshop. |
Domain knowledge |
|
19〜20 (all instructors) | Laboratory practice. |
System requirements |
|
21〜22 (all instructors) | Laboratory practice. |
System design |
|
23〜24 (all instructors) | Laboratory practice. |
Algorithm design |
|
25〜26 (all instructors) | Design testing and verification. Design validation. |
Verification and validation methodologies |
|
27〜28 (all instructors) | Engineering project documenting. |
Project documentation, technical reports |
|
29〜30 (all instructors) | Project workshop. |
Project report preparation, project presentations |
Class Format
Recommendations for Private Study
All class activities will be conducted in English.
Grade Evaluation Method
Kind | Percentage | Grading Criteria etc. |
---|---|---|
Final Examination (Written) | 0 | |
Report Examination (A report to be submitted by the unified deadline) |
0 | |
Exams and/or Reports other than those stated above, and Continuous Assessment (Evaluation of Everyday Performance in Class) |
100 | Continuous assessment and attendance – 70%
|
Grade Evaluation Method (Note)
Students who miss more than five classes without a legitimate and documented reason automatically receive an “F” for the course.