授業科目名 年度 学期 開講曜日・時限 学部・研究科 全担当教員 単位数
35120:PBL: Team-based Design(G1) 2019 秋セメスター 水3,金3 情報理工学部 COOPER ERIC WALLACE、SVININ MIKHAIL、高田 秀志、DINH THI DONG PHUONG、西村 俊和、白 楊 4

キャンパス

BKC/BKC

授業施設

ISSEコース実験室１　ＣＣ205/ISSEコース実験室１　ＣＣ205

授業で利用する言語

英語

授業の概要と方法

This is the second Engineering Information System Project (EISP) course in the project-based education sequence designed to serve as core for practice-oriented learning, and thus to present all practical aspects of the engineering system life cycle and professional communications in a consistent cross-engineering and multi-disciplinary framework. The course focuses on software system design, engineering project organization, and teamwork. The student coursework is organized in a semester-long project: Project C with emphasis on team-based design techniques and professional communication.

受講生の到達目標

Upon completion of the course, students should be able to:
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.

事前に履修しておくことが望まれる科目

Students must have successfully completed the “PBL: Problem Analysis and Modeling” course. They should be able to communicate in English, including comprehending scientific and technical texts, and writing short essays/reports. Basic knowledge of mathematics is required, while knowledge of a programming language would be desired although not absolutely necessary.

授業スケジュール

授業回数/
担当教員（複数担当の場合） 		テーマ
キーワード・文献・補足事項等
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

授業実施形態

授業外学習の指示

It should be expected that students will have to spend two to four hours per week in addition to class hours to prepare for the project work.
All class activities will be conducted in English.

成績評価方法

種別 割合(%) 評価基準等
定期試験（筆記） 0

レポート試験
（統一締切日を締切とするレポート）		 0

上記以外の試験・レポート、平常点評価
（日常的な授業における取組状況の評価）		 100

Continuous assessment and attendance – 70%

Team report submitted after week 15, during the examination week – 30%
The team report should describe the team organization and project progress, stressing each member’s individual responsibilities and contributions, along with the envisaged design and/or a system virtual prototype developed by the team.
Assessment policy. The student deliverables are graded with equal weights on the following aspects of coursework:
1) Problem analysis: focus on comparing the outcome of a design solution to the original problem definition.
2) Design: focus on planning and risk assessment.
3) Communications: focus on interpersonal (within the team) communication and project document writing.
4) Ethics and equity: focus on the student’s role in and contribution to the team project.

成績評価方法(備考)

Any indication of academic dishonesty, such as cheating, plagiarism (including “copy-pasting” from electronic documents and Web resources, such as Wikipedia), collusion, the submission of any work (e.g. report) that is attributable in whole or in part to another person, and similar behavior, will not be tolerated in any form. All persons involved in an act of academic dishonesty shall be disciplined – will receive an “F” for the course, and would be suspended or expelled from the College.

Students who miss more than five classes without a legitimate and documented reason automatically receive an “F” for the course.

受講および研究に関するアドバイス

教科書

教科書(使用頻度、その他補足)

There is no textbook for this course. Students will be provided with materials recommended for reading.

参考書

参考書(使用頻度、その他補足)

参考になるwwwページ

授業内外における学生・教員間のコミュニケーションの方法

学生との直接対話

備考