Unified
Modeling Language Links
Prerequisite: CSC 216, CSC 220.
Text: The Complete UML Training Course
Authors: Booch, Rumbaugh, Jacobson
Publisher: Addison Wesley Longman, 1999, ISBN: 0-13-087014-5
Attendance: Mandatory. Refer to Mississippi College Policies and Procedures for details(Attendance requirements may also be found on page 50-51 of the 2001-2002 Mississippi College General Bulletin). Since this is a TR class, you may not miss more than 25%, 8 classes, without penality of an automatic grade of F. When a student must miss class for whatever reason, it is his/her responsibility to present a vaild excuse to the instructor as soon as possible. All previously assigned work, exams, and quizes are to be made up within one week. If missed assignments or exams or tests are not made up within the week , then the student will get a grade of 0 on the requirement. Should the student find it impossible to make up the requirements within one week upon returning to normal class attendance, then a mutual agreement with the instructor of the class must be obtained as soon as reasonable regarding times for completion of the delinquent course requirements. The last day to drop this course is Friday, November 5, 2001.
Objectives: 1.The student should be able to use the Unified
Modeling Language to design and develop a software solution for a typical
small scale business or commercial application.
2.The student should be able to use C++ to implement a program solution
to a UML designed software application.
Academic Honesty
Academic Integrity Policy: online here
This statement on academic honesty in computer science courses is an addendum to the Mississippi College policy 2.19 found at www.mc.edu/publications/policies/ 219.html . In a computer science class individual effort is expected. Student misconduct not only includes cheating on tests, but also extends to copying or collaborating on programming assignments, projects, lab work or research unless otherwise specified by the instructor. Using other people's accounts to do your work or having others do your work is prohibited. Close proximity in lab does not mean sharing solutions. Discussing logical solutions to problems is acceptable, exchange of code, pseudocode, designs, or procuring solutions from the Web, other texts, the Internet or other resources on or off campus is not acceptable.
First offense: grade of 0 for all parties involved unless the "guilty"
party can be determined. Second offense: grade of F in the course
Grading:
The following grading scale will be used : A- 90-100 %, B-80-89%,
C-70-79%, D-60-69%, F- 0-59%
Assessment:
| 2 regular Exams @ 15 % each | 30% |
| Projects 40% | 40% |
| Homeworks,Class attendance and participation | 10% |
| 1 final exam @ 20% (comprehensive) | 20% |
| Total | 100% |
Course Topics
General Topics
Standardization and the UML
Why Bother with Analysis and Design?
Case Tools
Modeling Techniques
Use cases
Class Diagrams
CRC Cards
Package Diagrams
Design by Contract
State Diagrams
Interaction Diagrams
Activity Diagrams
Process Techniques
Incremental Development
Translation
Patterns
Refactoring
Resources
Unified
Modeling Language Links