CEng
491
Senior Project Seminar and Design I
Fall 2009 Syllabus
|
Instructors: |
Pınar Şenkul Karagöz, Ruken Çakıcı |
|
Assistants: |
Ahmet Ketenci, Alper Kılıç, Can Eroğul, Fatih Gökçe, Selma Süloğlu |
|
Classes: |
Monday 12:40 (BMB1) |
|
Course Objectives: |
Making student use their theoretical knowledge into practice by designing a complete solution to a real life computer problem. Giving basic analysis and design issues, methods and considerations. Improving the teamwork, communications skills and creativity. Providing an environment to learn and use the latest technologies and trends in the software and hardware development market. Making the students aware of ethics and legal issues in the computer engineering. |
|
Prerequisite: |
CEng 350 |
|
|
|
|
Date |
Topic |
Deadline for Deliverables (following Monday) |
|
September 28, 2009 Monday |
Introduction |
|
|
October 2, 2009 Friday |
Introduction |
|
|
October 9, 2009 Friday |
Report Writing |
Teaming Up + Project Topic |
|
October 23, 2009 Friday |
Analysis |
Proposal Report |
|
October 30, 2009 Friday |
Analysis |
|
|
November 6, 2009 Friday |
Ethics I |
|
|
November 13, 2009 Friday |
Ethics II |
Requirements Analysis |
|
November 20, 2009 Friday |
Design |
|
|
November 27, 2009 Friday |
Holiday |
|
|
December 4, 2009 Friday |
Invited Speaker II |
|
|
December 11, 2009 Friday |
How to make presentations |
Initial Design Report |
|
December 14, 2009 Monday |
Team presentations |
|
|
December 18, 2009 Friday |
Team presentations |
|
|
December 21, 2009 Monday |
Team presentations |
|
|
December 25, 2009 Friday |
Team presentations |
|
|
December 28, 2009 Monday |
Team presentations |
|
|
January 4, 2010 Monday |
Team presentations |
|
|
January 8, 2010 Friday |
Team presentations |
Detailed Design Report |
|
January 11-23, 2010 |
Final Exams |
Prototype Demo |
Proposal Report:
A short report about project specifications, what do you aim to achieve at the end of the term. The motivation, purpose and initial estimates and intentions.
Requirement Analysis Report:
A report including system requirement specifications represented formally and your work packages and work calendar.
Initial Design Report:
A report including the formal specification of your system solution. Description of system modules, data flow, database design, data dictionaries, E-R and/or UML diagrams, state diagrams, syntax specifications etc.
depending on your project and methodology.
Detailed Design Report:
An extended version of design report including data dictionaries and revisions on the first report. Also include a detailed implementation plan. This report should be complete enough for a group of programmers to start the implementation.
Prototype:
You will implement some key components of your problem, make some visualization, integration, solve basic capability problem etc. depending on your topic.
Weekly Progress:
Each week you will meet with the supervisors and they will grade your progress in that week. Your performance will be evaluated individually and as a group during that meeting.
Grading:
|
Proposal |
5 |
|
Requirements Analysis Report |
20 |
|
Initial Design Report |
11 |
|
Detailed Design Report |
22 |
|
Final Presentation |
10 |
|
Weekly Progress |
20 |
|
Prototype Demo |
7 |
|
Attendance and class Activity |
5 |
|
Best team(s) bonus |
5 |
Code of Honor: Any work you submit must be your own.
Newsgroup:
metu.ceng.course.490
Course
web page:
http://www.ceng.metu.edu.tr/courses/ceng490/