MCS 7013 Collaborative Research Project I
MCS 7033 Collaborative Research Project II
CJ Chung
Lawrence Technological University
Math and Computer Science Department
Credit Hours: 3
Prerequisite: Permission of [Department
Chairperson or Graduate Program
Director] and the instructor
Lecture Room: Generally N/A
Lab.: M219; Robotics Lab (CW21)
Instructor: CJ Chung, Ph.D.
- Office Room: Science 116D or M219
- Phone: (248) 204-3504
- Fax: (248) 204-3518 (this fax number is for
the whole building and senders
should be sure to place instructor's name on the fax)
- Dept. Secretary: (248) 204-3560
- Math/CS Drop Box: in front of S120 door.
- Email: CHUNG @ltu.edu
- LTU webpage at http://qbx6.ltu.edu/chung
(syllabus, announcements, lecture notes, etc.)
- Office Hours: check out http://http://qbx6.ltu.edu/chung and click
on Office Hours
Required Text: N/A, project by project
Recommended Text: Any Software Engineering Textbook
Course Objectives
- Further theoretical and practical study/research
on each student's areas of concentration, which are Intelligent Systems (Artificial
Intelligence), Distributed Computing, Database Systems, and Software Engineering.
- Intensive study of
special/practical/real-world problems in the software system (or embedded
system) development.
- Students will be involved in a whole software
life cycle, which includes requirement specification, design,
implementation, and testing of complex software systems.
- Teamwork
experience, if necessary.
Development Life-cycle, Deliverables, and Assigned Points
See below table in which the concept of spiral
model is being adopted. All the deliverables need to be posted on the instructor's
homepage.
Week |
Deliverables |
Points |
1st |
Project proposal & description due
|
|
2nd |
Project requirements specification (and initial test case
documents)
|
10 |
3rd |
System design document due
|
5 |
4th |
First demo of the prototype |
20 |
5th |
Final
requirement spec, test cases, and design document due
|
5
|
8th |
Second demo
|
20 |
11th
|
Third demo
|
30 |
15th
|
Public presentation if necessary and field trial;
Delivery of the project executables, source, and documentations
|
100 |
Grading:
Total 200 points
- Grades will be based on the results of the above activities and submitted products
- Criteria to decide the points for the documentations:
completeness, consistency (between documents),
readability, and clarity, etc.
- Criteria to decide the points for the implemented system:
functional completeness, functional consistency, consistency between documents and the system,
complexity, size, correctness,
reliability, robustness, reusability, user-friendliness, usability, and quality
- The rest 10 points are decided by the instructor considering the following factors:
creativity, teamwork, scientific finding, educational value, and new technologies used, etc.
- The instructor uses this form when grading the project
- The instructor will ask contribution percentage for each team member, if the project is done by a group.
This score will be translated into a letter grade based upon the
percentages given below.
A |
90-100% |
C+ |
75-78% |
A- |
89% |
C |
70-74% |
B+ |
85-88% |
C- |
69% |
B |
80-84% |
|
|
B- |
79% |
|
|
Intellectual Property and
Copyrights
All the
deliverables may be reused/modified/upgraded by another students and/or
instructor later on for educational purposes only. The instructor will make sure
to give appropriate credits and acknowledgements to the previous
students.