Course Syllabus

Course Information：

Year-Semester Course Number Course Name Phase Credits Hours Required/Elective Instructor Class Student NO. Withdraw Note

Spring Semester
Year 2025 342740 Object-Oriented Analysis and Design 1 3.0 3 ★ CHEN, WOEI-KAE GCSIE 52 7 資工四.資工所合開，兼任週四346

Year-Semester	Course Number	Course Name	Phase	Credits	Hours	Required/Elective	Instructor	Class	Student NO.	Withdraw	Note
Spring Semester Year 2025	342740	Object-Oriented Analysis and Design	1	3.0	3	★	CHEN, WOEI-KAE	GCSIE	52	7	資工四.資工所合開，兼任週四346

Course Plan：

Instructor CHEN, WOEI-KAE

Email woeikaechen@ntut.edu.tw

Last Updated 2024-12-16 20:56:29

Course Objective 本課程探討應用物件導向方法從事軟體設計的過程與步驟, 透過課程專題製作, 學者將學習以UML記載分析與設計之結果, 並使用一個物件導向語言(如Java或C++)實作之. 課程內容: 1. 物件導向模型 -- UML介紹 2. 物件導向程式語言與環境 3. 物件導向軟體發展週期 3.1 物件導向分析 - 需求分析, 使用個案, 觀念模型, 有限狀態模型 3.2 物件導向設計 - 實際使用個案, 合作圖, 類別圖, 設計模板, 3.3 程式撰寫 - 設計與程式之應對 4. 專題 This course familiarizes the students with the principles and techniques for object-oriented software development. The students will use UML and an object-oriented language such as Java or C++ to complete a term programming project. Course contents: 1. Object-oriented modeling with UML 2. Object-oriented languages and environments 3. Object-oriented software development process 3.1 Object-oriented analysis - requirement analysis, use case analysis, conceptual models, finite state machine models 3.2 Object-oriented design - real use cases, collaboration diagrams, class design diagrams, design patterns 3.3 Construction - mapping design to codes 4. Term project.

Course Schedule 1. This course covers object-oriented modeling for software development. Materials covered include class models, state models, and interaction models in UML, a reference process model based on Unified process, implementation issues, and software engineering principles. This course is thinking and programming-intensive. 2. Students are required to complete a non-trivial software project. Only object-oriented languages such as C++/Java/C# are allowed. A project team may have 1-4 students. A single person team is allowed but is not encouraged. 3. There will be no exams; instead, there are 7 homework assignments, several in-class exercises, and two project reviews. All assignments turned in must be typed (handwriting will not be accepted).

Evaluation and grading policy Homework assignment schedule and grading policy: Week #1 Homework #1 Project proposal 0% Week #2 Homework #2 Iteration 1: Use case 7% Week #4 Homework #3 Iteration 1: Domain model 7% Week #6 Homework #4 Iteration 1: Design class diagram (3 weeks) 7% Week #7 Homework #5 Iteration 1: Implementation class diagram (4 weeks) 7% Week #i Exercise In-class exercise: 6-9 hours. 12% Week #11, #12 Midterm review Project presentation. Ten teams, decided by lottery on the presentation date, will present/demo their projects for 30 minutes. The rest of the teams need to turn in their slides and demo videos. 16% Week #12 Homework #6 Iteration 2: Use case and domain model 7% Week #14 Homework #7 Iteration 2: Design and implementation class diagram 7% Week #17, #18 Final review Project presentation; 15 minutes per team. 20% Week #1-#18 Attendance Attendance records account for 10% of the final grade 10%

Materials All right reserved. Do not reproduce without permission.

Foreign-language textbooks:Yes
C. Larman, Applying UML and Patterns, 3rd Ed., Prentice Hall, 2004.

The access to curricular consultation 開學(課)前有課程諮詢需求時，請使用電子郵件(woeikaechen小老鼠ntut.edu.tw)與老師聯絡，開學(課)後請於上課時間或使用Teams找老師討論。

Expanding teaching and resources

The course corresponds to the SDGs 無（None）

Does the course incorporate AI

Note
　

Instructor	CHEN, WOEI-KAE
Email	woeikaechen@ntut.edu.tw
Last Updated	2024-12-16 20:56:29
Course Objective	本課程探討應用物件導向方法從事軟體設計的過程與步驟, 透過課程專題製作, 學者將學習以UML記載分析與設計之結果, 並使用一個物件導向語言(如Java或C++)實作之. 課程內容: 1. 物件導向模型 -- UML介紹 2. 物件導向程式語言與環境 3. 物件導向軟體發展週期 3.1 物件導向分析 - 需求分析, 使用個案, 觀念模型, 有限狀態模型 3.2 物件導向設計 - 實際使用個案, 合作圖, 類別圖, 設計模板, 3.3 程式撰寫 - 設計與程式之應對 4. 專題 This course familiarizes the students with the principles and techniques for object-oriented software development. The students will use UML and an object-oriented language such as Java or C++ to complete a term programming project. Course contents: 1. Object-oriented modeling with UML 2. Object-oriented languages and environments 3. Object-oriented software development process 3.1 Object-oriented analysis - requirement analysis, use case analysis, conceptual models, finite state machine models 3.2 Object-oriented design - real use cases, collaboration diagrams, class design diagrams, design patterns 3.3 Construction - mapping design to codes 4. Term project.
Course Schedule	1. This course covers object-oriented modeling for software development. Materials covered include class models, state models, and interaction models in UML, a reference process model based on Unified process, implementation issues, and software engineering principles. This course is thinking and programming-intensive. 2. Students are required to complete a non-trivial software project. Only object-oriented languages such as C++/Java/C# are allowed. A project team may have 1-4 students. A single person team is allowed but is not encouraged. 3. There will be no exams; instead, there are 7 homework assignments, several in-class exercises, and two project reviews. All assignments turned in must be typed (handwriting will not be accepted).
Evaluation and grading policy	Homework assignment schedule and grading policy: Week #1 Homework #1 Project proposal 0% Week #2 Homework #2 Iteration 1: Use case 7% Week #4 Homework #3 Iteration 1: Domain model 7% Week #6 Homework #4 Iteration 1: Design class diagram (3 weeks) 7% Week #7 Homework #5 Iteration 1: Implementation class diagram (4 weeks) 7% Week #i Exercise In-class exercise: 6-9 hours. 12% Week #11, #12 Midterm review Project presentation. Ten teams, decided by lottery on the presentation date, will present/demo their projects for 30 minutes. The rest of the teams need to turn in their slides and demo videos. 16% Week #12 Homework #6 Iteration 2: Use case and domain model 7% Week #14 Homework #7 Iteration 2: Design and implementation class diagram 7% Week #17, #18 Final review Project presentation; 15 minutes per team. 20% Week #1-#18 Attendance Attendance records account for 10% of the final grade 10%
Materials	All right reserved. Do not reproduce without permission. Foreign-language textbooks:Yes C. Larman, Applying UML and Patterns, 3rd Ed., Prentice Hall, 2004.
The access to curricular consultation	開學(課)前有課程諮詢需求時，請使用電子郵件(woeikaechen小老鼠ntut.edu.tw)與老師聯絡，開學(課)後請於上課時間或使用Teams找老師討論。
Expanding teaching and resources
The course corresponds to the SDGs	無（None）
Does the course incorporate AI
Note