系統工程
System Engineering
| 節 | 週三 |
|---|---|
A 18:30–19:20 | 系統工程 MB405（光復） 3 節連堂 |
B 19:30–20:20 | |
C 20:30–21:20 |
* 根據陽明交大上課時間表所列
We live inside systems: hospitals, semiconductor supply chains, drone delivery networks, traffic infrastructure, and many others. None of these are built by one expert or one discipline. They are built by teams who must agree on what the system should do, who it serves, what situations it must handle, and how every part connects, behaves, and is verified. That disciplined agreement — structured, traceable, and tested against reality — is what systems engineering exists to produce. This course begins with a simple question: what is a system? A system is not only a collection of parts. It is defined by boundaries, relationships, interfaces, behaviors, constraints, and emergent outcomes. Learning to see these connections is the foundation of systems thinking. We will study systems engineering as both a technical discipline and a leadership discipline. Systems engineers help teams clarify stakeholder needs, define Use Cases, resolve conflicts, evaluate trade-offs, control changes, and turn complex intentions into buildable and verifiable designs. In the AI era, this discipline becomes even more important. Large language models and agentic AI tools can accelerate development, but they also require stronger judgment, traceability, verification, and human ownership. Specifications may evolve faster, but change still must be controlled. Systems may become more adaptive, but safety and accountability cannot be lost. In this course, you will first learn traditional document-based systems engineering: CONOPS, Use Cases, requirements, functional architecture, interfaces, verification plans, and traceability matrices. You will then move into Model-Based Systems Engineering, or MBSE, where interconnected models make system structure, behavior, requirements, Use Cases, interfaces, and verification logic more visible and consistent. Students will also use AI-assisted tools to support modeling and documentation, while learning to audit, question, and own what those tools produce. By the end of this semester, you will not only know about systems engineering. You will have practiced it — from stakeholder needs and Use Cases to a connected, traceable, and verifiable system design. The goal is to help students think like a systems engineer in the AI era. 你每天都生活在系統裡。 醫院、半導體供應鏈、交通基礎設施、無人機配送與 AI Agent，都不是由單一專業完成，而是由不同領域共同建構。系統工程，就是讓這些複雜系統被清楚定義、彼此連接，而且可以被驗證的方法。 這門課會從一個基本問題開始：什麼是系統？ 系統不只是元件的集合，更包含邊界、關係、介面、行為、限制，以及各元素互動後產生的整體結果。學會看見這些關係，就是系統思維的基礎。學生將學習如何從 Stakeholder Needs 與 Use Cases 出發，建立 Requirements、Functional Architecture、Interfaces、Verification Plan 與 Traceability，並進一步進入 Model-Based Systems Engineering（MBSE），把分散的文件轉化成彼此連結、可以追溯的系統模型。 在 AI 時代，這些能力更加重要。AI 可以快速產生需求、文件與模型，但更快不代表更正確。系統工程師仍然必須負責判斷、追溯、驗證與最終決策。 因此，這門課不只是教你使用 AI，而是教你如何管理 AI 所參與的系統工程工作。學期結束時，希望你不只知道什麼是系統工程，而是能真正從需求出發，建立一套可連結、可追溯、可驗證的系統設計。 在 AI 時代，學會像系統工程師一樣，看見關係、理解整體結構、管理系統的複雜性。
Upperclassmen required. (Junior above 大三以上 才能選修） 本課程是跨校區選修課程。 部分課程提供遠距教學。
無備註
System Engineering Body of Knwledge (SEBok) https://sebokwiki.org/wiki/Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK)
• Homework, Case Study Write-ups, Paper/journal review comments: 30% • Class Attendance & Class Discussion Participation, 10% • Mid Term: Mixed of test and team project presentation, 20% • Assigned System Engineering subject presentation: 10% • Term Project: 30%
教師未提供此項資料
| 週次 | 主題 |
|---|---|
| 第 1 週 | What is a system? Why SE is needed; modern complex systems; systems thinking in the AI era. |
| 第 2 週 | System boundary, stakeholders, field observation, user pain points, operational context, and problem framing. |
| 第 3 週 | V-model, lifecycle logic, needs -> requirements -> design -> verification, and review gates. |
| 第 4 週 | Stakeholder analysis, Use Case thinking, operational scenarios, CONOPS logic, and domain specialist input. |
| 第 5 週 | How to write good system requirements; requirement hierarchy; ambiguity; rationale; verification logic. |
| 第 6 週 | From system requirements to functional requirements; functional decomposition; FFBD/activity logic. |
| 第 7 週 | Interface definition, requirement-function-interface links, traceability matrix concept, and change impact thinking. |
| 第 8 週 | Mid-Term Written paper test plus team presentation of system requirements. |
| 第 9 週 | INCOSE framework, SE handbook logic, SE roles, reviews, technical leadership, and professional language. |
| 第 10 週 | Why MBSE; document-based SE vs. model-based SE; model as single source of truth. |
| 第 11 週 | Group presentations (10%) on assigned SE topics; peer questions and instructor feedback. |
| 第 12 週 | Agile Development, introduce Sys ML (system modeling language for MBSE development |
| 第 13 週 | Case Study |
| 第 14 週 | Using LLMs for MBSE requirement audit, model extraction, traceability checking, model consistency review, and documentation support. |
| 第 15 週 | Model consistency, AI audit, V&V logic, final presentation coaching, and peer review. |
| 第 16 週 | Final: AI-assisted MBSE presentation and documentation review. |
• Required Textbook: Kossiakoff, A., Sweet, W. N., Seymour, S. J., & Biemer, S. M. (3rd ed.). Systems Engineering: Principles and Practice. Wiley. - Recommended References (optional): • INCOSE Systems Engineering Handbook (4th or 5th Edition) – for process language and certification alignment. Selected journal and conference papers on systems engineering applications in manufacturing, cyber-physical systems, and healthcare (to be announced during the semester).
- 地點
- MB 514
- 時間
- 教師未提供此項資料
- 聯絡方式
- 教師未提供此項資料