The objective of this course is to help you develop into a more qualified computer professional. As the course name suggests, the course has three primary objectives:
There is no textbook for this course. However, we will use UML to represent designs, so it would be helpful to have a good book on UML. See the section below for some suggestions from Dr. Lewis.
Most course-related information (this syllabus, homework and reading assignments, etc.) will be made available via the World Wide Web. The course Web page is a starting point for Web-accessible course material; you can find it linked from my home page (http://www.cs.trinity.edu/~bmassing), directly at http://www.cs.trinity.edu/~bmassing/Classes/CS3194_2004spring/, or via Tiger's Lair (http://bb.trinity.edu/).
Here are some reasonable UML references.
Grades in this course will be determined on the basis of class attendance/participation, an ethics presentation, and the design project, weighted as follows.
| Component | Maximum points |
|---|---|
| Class participation | 10 |
| Ethics presentation | 15 |
| Project | 75 |
Numeric grades will be calculated as a simple percentage, by dividing points earned on the above components by maximum points. These numeric grades will then be converted to letter grades based on a curve, but in no case will the resulting letter grades be worse than students would receive based on the following scheme.
| Numeric grade | Letter grade |
|---|---|
| 90 - 100 | A |
| 80 - 89 | B |
| 70 - 79 | C |
| 60 - 69 | D |
| 0 - 59 | F |
Detailed requirements will be provided via the course Web page. Ethics presentations by juniors are scheduled for February 25.
Detailed requirements will be provided via the course Web page. Briefly, however: The class will be split into groups of about five students each. All groups will work on the same problem, first analyzing the requirements and then developing a design and a prototype solution. Each group will turn in a written report (including UML diagrams) and do an in-class presentation. Each group member will also turn in an evaluation of other members of his/her group. Design presentations by juniors are scheduled for April 21. Reports and prototype code are due April 28. Interim progress reports and evaluations will also be required; details will be provided via the course Web page.
Regular class attendance is strongly encouraged; class participation grades will be based largely on attendance.
Course-related announcements will sometimes be made by sending e-mail to the Trinity e-mail addresses of all registered students. Students are strongly encouraged to read mail sent to their Trinity addresses frequently. An archive of such announcements will be provided via the course Web page.
Since most of the due dates for this course are linked to scheduled in-class events, they should be considered to be inflexible. Exceptions are possible only in very unusual circumstances; if you know you will be unable to meet a deadline, please notify the instructor as far in advance as possible.
Some work for this course is to be performed in groups; some (e.g., the evaluations of other group members) is to be performed individually. Detailed requirements for the project and ethics presentation will spell out which is which. Work submitted by an individual student must represent that student's own effort. Work submitted by a group must represent the efforts of members of the group only (i.e., collaboration between groups is not allowed). Work that is identical beyond coincidence is in violation of Trinity's Academic Integrity Policy and will result in disciplinary action, including, but not limited to, a failing grade on that assignment for all parties involved. You are responsible for the security of your work, both electronic and hard copy.