COP 3331
Object Oriented Design and Analysis
Spring 2007 Syllabus
Instructor Information
Position |
Name |
E-mail |
Office |
Office hours |
Course Instructor |
Bob Myers |
myers@cs.fsu.edu |
Love 205-A |
TR 11:00 AM - 12:30 PM |
TA / Grader |
Corey Latislaw |
latislaw@cs.fsu.edu |
MCH 101-A |
W 12:00 - 3:00 PM |
TA / Grader |
Joandy Iglesias |
iglesias@cs.fsu.edu |
MCH 114 |
M 1-3 PM (for next few weeks), W 11:00 AM - 12:00 noon |
TA / Grader |
Ryan Walega |
walega@cs.fsu.edu |
MCH 101-B |
T 3:15 - 6:15 PM |
Class Schedule
Lecture
TR 9:30 - 10:45 AM, MCH 201
Recitation
Section |
Room |
Day |
Time |
Instructor |
1 |
LOV 301 |
Wed |
11:15 AM - 12:05 PM |
Walega |
2 |
LOV 301 |
Wed |
12:20 - 1:10 PM |
Walega |
Course Requirements:
Prerequisite Course
- COP 3330: Object Oriented Programming
Course Website:
Textbooks:
- Object-Oriented Software Engineering, 2nd ed., Bruegge and
Dutoit.
ISBN: 0-13-047110-0
Course Description
This course introduces you to programming in Java, object oriented
design as well as concepts in software engineering and ethics in computer
science. Most importantly, this course focuses in on the important
activities that should precede the writing of computer code. We
will buil on many of the concepts and procedures you learned in the
previous courses. In the previous courses, you were acquainted with the
fundamental concepts of computer science.
Thus far, you have dealt with small, relatively well-defined problems.
In the world of commerce and industry, technological issues and problems
are much larger and more complex. These problems are well beyond the scope
of a single individual. Software engineers, in collaboration with others,
often spend much of their time brainstorming, discussing, and creating
documentation of problems and problem solutions (often incorporating
complex diagrams), and a relatively small amount of time writing code.
Java will be introduced in this course as a means to illustrate
the practices of object oriented design and as a mechanism to illustrate
design features.
Analysis and design are two of the key activities
involved in software development. These activities can be carried out
using a number of different methods and tools. Many modern software
development methods are based around the object-oriented approach. It is
this approach that we will focus upon in this course, and it is assumed
you are already familiar with the basic principles of object orientation.
It is important to recognize that there is no one right or wrong way to
develop software. Two companies can organize the process of development
very differently, yet both may produce successful systems. The overall
efficiency of the development process is more critical to the success of
the project than the particular method or tool that is used. In order to
be efficient, software developers need to give as much consideration to
their development process as they do to the product.
In this course, you will gain practical skill in analysis and design
that will complement your skills in programming. You will learn about the
problems of and approaches to developing large computer systems, and will
acquire an understanding of what constitutes a development methodology.
In this course, students will gain practice in developing
object-oriented designs to solutions of problems and then converting
those designs into code.
This course is designed to complement the programming course COP
3330: Object-Oriented Programming, in which you have gained the
programming experience needed to convert completed designs into computer
executable code.
Course Objectives:
- Be able to describe the concepts of Object Oriented Design and
Programming techniques
- Write small Object Oriented style Java Programs using the current
Java SDK
- Understand the issues of ethics in field of Computer Sciences
- Describe and explain the main stages, methods, tools, techniques, and
problems involved in systems and software engineering.
- Explain the main concepts and goals of analysis and design.
- Demonstrate practical skill in the use of an analysis and design
notation using the Uniform Modeling Language (UML)
- Be able to translate UML design into actual code.
- Become proficient in the use of a UML tool such as Rational Rose
Grading Policy:
The final course grade will be computed as follows:
Homework/Recitation Assignments |
40 % |
Term Tests |
30 % |
Final Exam |
30 % |
Letter Grade Scale:
Letter | Numerical Average |
A | 92.00 - 100 |
A- | 90.00 - 91.99 |
B+ | 88.00 - 89.99 |
B | 82.00 - 87.99 |
B- | 80.00 - 81.99 |
C+ | 78.00 - 79.99 |
C | 72.00 - 77.99 |
C- | 70.00 - 71.99 |
D | 60.00 - 69.99 |
F | 0.00 - 59.99 |
Tests:
There will be at least two term tests, and a cumulative final exam as regularly
scheduled by the university.
Test Dates: (Test 1 and 2 tentative)
Test 1 |
Feb 15 |
Test 2 |
Thurs, March 29 |
Final Exam |
Tues, April 24, 10:00 AM - 12:00 noon |
Link to Spring 2007 Final Exam Schedule
Recitation / Quizzes
Periodic quizzes may be given, in lecture or in recitation class, to help
students gauge their progress in the class, and to gauge attendance.
No makeup quizzes will be given (no exceptions). Attendance and
participation is expected, both in lecture and recitation class. There
may also be some hand-in exercises done in recitation class.
Assignments
- Assignment instructions will be posted on the course web page
- Turn in all assignments on time! Late assignments
will be accepted one day after the due date, with the deduction of a
letter grade (10%). Assignments more than a day late will not be
accepted.
Miscellaneous Policies:
- A student will be allowed to make up a missed test if he or she has
a notice of illness from the Student Heath Center or family physician.
Any other excuses that are not medical or emergency related will be at
the discretion of the instructor, and must be approved in advance.
- It's your responsibility to check the web page frequently. It will be
continually updated with essential course materials, including assignments,
notes outlines, instructions on course tools, etc.
- Please turn OFF all cellular phones, beepers, etc. in the classroom.
- COP 3330 is a PREREQUISITE for this course. Students who have not
taken this course will be dropped without notice.
Academic Honor Code:
It it your responsibility to read, understand, and conform to the
Academic Honor Code
as set forth in the FSU General Bulletin and the Student
Handbook. In addition to this information, please be aware of the
following:
- Students are expected to do their own work on any classwork or
test submitted for a grade (unless designated as a group assignment).
- It is NOT appropriate to work on assignments with other students or
to give or receive solutions to or from anyone before an assignment
is due and handed in (by all parties).
- Discussing solutions and techniques on assignments with other
students after the assignment has been graded and handed back
is okay, and encouraged.
- When you turn in work with your name on it, you are representing that
work as your own. If your submission matches that of
another student, this is considered a violation of the
Academic Honor Code.
- If a group project is given, then names of all group
members would appear on the single program submission. This is
appropriate
- Examples found in the course textbook
may be used in programs, as long as the source is cited. This is
appropriate, as some hand-in assignments may be based on program examples
found in the book or contain other code that is provided to you in the
assignment specification
- A first violation of the honor code will result, at minimum
(but not limited to), a penalty of a 0 grade on the assignment
or test involved, along with a reduced letter grade in the course.
- Any second violation of the honor code will result in an automatic F
in the course, and possible proceedings before the Honor Court.
Accommodation of Disabilities:
Students with disabilities needing needing special
accommodations should register with and provide documentation to the
Student Disability Resource
Center (SDRC), and they should bring a letter from the SDRC to the instructor
indicating what accommodations are needed. Any notice of special
accommodations should be given at least a week in advance.
Students taking exams at the SDRC office are expected to take exams
at the regularly scheduled time. Any exception to this will only
be granted with a valid documented reason and must be approved by the instructor
a week before the exam.