CSCE 491: CAPSTONE COMPUTER SYSTEM PROJECT
Catalog Description:
491—Capstone Computer System
Project.
(3) (Prereq: CSCE 240, 311) Advanced computer systems engineering. Team
projects
Prerequisite(s) By Topic:
Operating systems
Programming in C++
Textbook(s) and Other
Required Material:
Build Your Own
PC, 2nd Ed.
Morris Rosenthal, McGraw-Hill, 2001
Red Hat Linux For Dummies, Jon Hall and Paul G. Sery,
IDG Books, 2000. (or similar reference)
Computing Platform: Linux
Course Objectives: {Assessment Methods Shown in
Braces}
1.
Develop and follow an effective project plan; {oral & written
reports}
2.
Design, and build a PC-class computer from off-the-shelf
components; {oral & written reports}
3.
Port system and application software to new hardware, test the
system, analyze the problems, and provide fixes to the software; {oral &
written reports}
4.
Develop and work in a networked-computer environment; {oral & written reports}
5.
Measure, compare, and tune the performance of a networked computer
system; {oral & written reports}
6.
Document and explain work on a project of significant
complexity; {oral & written
reports}
7.
Work
as a part of a small team and of a larger group to accomplish a large
multi-step project. {oral & written reports}
Topics Covered:
1. Plan project to build PC and measure its performance
2. Construct and verify the PC hardware.
3. Port Linux and server software to the PC and verify that they are
working correctly.
4. Connect the PC to a network.
5. Write benchmark programs
6. Evaluate the performance of the system using standard benchmarks
7. Tune the system to optimize its performance relative to the
benchmarks.
Laboratory Projects
The entire course is centered around students' work
in the lab—building the PC, porting and writing the software, measuring the
system’s performance.
Syllabus Flexibility: Medium. The Undergraduate Committee approves the
choice of textbook; project details vary every semester.
Relationship of Course to
Program Outcomes:
The contribution of each course objective to meeting
the program outcomes is indicated with the scale:
3 = major contributor, 2 = moderate contributor, 1 = minor contributor. Blank if not related.
|
|
Program Outcomes |
||||||||||
|
1.
Logic & Math |
2.
Computing Fundamentals |
3.
Apply Computing Principles |
4.
Work on teams |
5.
Communicate Effectively |
6.
Liberal arts & Soc. Sciences |
7.
Basic Science and Lab Procedures |
8.
Learn New Tools & Processes |
9.
Employed upon Graduation |
10.
Application Area |
11.
Electronics and Digital Sys Design |
|
|
1. Develop and follow an effective project plan |
|
|
|
2 |
2 |
|
|
3 |
2 |
|
|
|
2. Design, and build a PC-class computer |
|
3 |
3 |
2 |
1 |
|
|
1 |
3 |
|
3 |
|
3. Port system and application software, test, analyze fix
problems |
|
3 |
3 |
|
|
|
|
1 |
1 |
|
|
|
4. Measure, compare, and tune the performance of a networked
computer |
|
3 |
3 |
|
|
|
2 |
1 |
1 |
|
1 |
|
5. Document and explain work on a project of significant
complexity |
|
3 |
|
2 |
3 |
|
|
|
1 |
|
|
|
6.
Work as a part of a small team and of a larger group |
|
|
|
3 |
|
|
|
|
3 |
|
|
Estimated CSAB Category
Content:
Algorithms: 0.5
hr
Data Structures: 0
Software Design: 0
Concepts of
Programming Languages 0.5
hr
Organization and
Architecture 2
hr
Oral
and Written Communication:
Students write about 5 intermediate
project reports and give weekly status report presentations in a formal
setting. There is also a final oral and
written report.
Social
and Ethical Issues: none
Theoretical
Content:
analysis of benchmark results
Analysis
and Design:
Design of system, measuring and
interpreting benchmark results
Class/Laboratory
Schedule:
Lecture: 2 periods of 75 minutes per week
Recitation: Generally one group meeting with
instructor each week
Laboratory: Students have free access to
laboratory
Course
Coordinator: John Bowles
Modification
and Approval History:
Initial description, January 2000
Revised, April 2001