|
|
COURSE SYLLABUS |
|
|
COURSE SYLLABUS |
This class has students attending in two distinct modes:
The content, objectives, assignments, assessments, and grading are the same for all students. Obviously, however, on-campus, mixed-mode, and distance students sometimes participate in different ways.
For all students: Regular participation via the Blackboard course interface is required. Official course announcements, lecture materials, assignments, and help archives will all be on-line at this site. Note that all registered students should have the course web site listed on their My FSU portal page. Be sure to test this and resolve any difficulties no later than the first week of classes.
For on-campus/local students: Class (lecture and recitation) will be met and attendance is required. (See schedule details below.) All exams will be given in class during scheduled class time.
For on-line/distance students: All exams must be proctored and taken during the exam window. It is the student's responsibility to arrange for proctored exams in compliance with the FSU standards. Go to the URL http://online.fsu.edu/learningresources/proctoredexam/ for details.
Note that students may be required to identify themselves with official FSU ID to sit an exam.
Event Location Dates Day Time Lecture TEC 129 Jan 10 - Apr 25 (excluding Mar 7) Tue 5:00pm - 7:30pm (Central Time)
There will be two exams in COP 3331, a midterm exam and a final exam. The dates for the two exams are shown in the following table.
Exam Calendar Exam On-Campus Distance Window (Inclusive) Midterm Exam Tue Feb 28 Fri Mar 3 - Mon Mar 6 Final Exam Tue Apr 25 Fri Apr 21 - Mon Apr 24
Chris Lacher, Faculty
Responsibilities: Course Policies and Standards, On-Site and On-Line Instruction, Assessment
Office: 112 Faculty Annex B / Panama City Campus Office Phone (during office hours): 850-522-5502 or 850-644-2090 ext 251 Mobile Phone/Voice Mail (24/7): 850-510-5575 Email: lacher@cs.fsu.edu Fax: 850-872-7720 Mail & Delivery: Florida State University
4750 Collegiate Drive
Panama City, FL 32405-1099
Lacher Weekly Schedule Effective Jan 9 - Apr 29, 2006 (excluding Jan 17 and Mar 7-11)
Adria Peaden, Teaching Assistant
Responsibilities: Distance Student Mentor, On-Line Interaction, Assessment
Email: peaden@cs.fsu.edu
The course COP 3330 is a required prerequisite for COP 3331. In addition, COP 4530 is highly recommended as either a pre- or co-requisite. Prerequisites will be enforced. Students not meeting the prerequisite requirement will be dropped from the class.
Once a student has achieved a strong background and significant experience in programming with classes and objects, it is appropriate to consider the creation of large-scale software at a higher level. Object-oriented design and analysis is that level.
This course covers the core material in an Object Oriented Software Engineering course for the first-time user. While it is assumed that the student has substantial expertise in programming in an object oriented language, it is not assumed that the student has any design experience.
The course of necessity cannot produce professional expertise in one semester. Some things will be immediately familiar; some things will be immediately perceived as useful; and some things may need to be taken on faith as potentially useful as the student gains experience in software.
In the vast landscape of software engineering, this first course will emphasize those elements that make sense for individuals: UML modelling, analysis, and design. Topics that pertain to, or of necessity require multiple personnel, will be introduced but will not receive as much emphasis in this introductory course.
This course is about software engineering, with over-riding emphasis on object-oriented software engineering. The following objectives should be taken in this context:
- Appreciate Goals of Software Engineering:
- Build complex software systems in the context of frequent change
- Understand how to produce a high quality software system
- within allocated time and resource constraints
- while dealing with complexity and change
- Acquire technical knowledge (main emphasis)
- Understand System Modeling
- Learn UML (Unified Modeling Language)
- Learn different modeling methods:
- Use Case modeling
- Object Modeling
- Dynamic Modeling
- Issue Modeling
- Component-Based Software Engineering
- Reinforce the importance of Design Patterns and Frameworks
- Acquire managerial knowledge
- Understand the Software Lifecycle
- Process vs Product
- Learn about different software lifecycles
- Greenfield Engineering, Interface Engineering, Reengineering
In particular, the student should have a strong understanding of the following recurring software cycle
do { requirements elicitation analysis design implementation testing } while ( )Note that this is a never-ending loop for most software products.
The overall grade for COP 3331 is an average of two equally weighted parts: Exams and Assignments. Exams consist of a midterm exam and a final exam. Assignments consist of six minor ("homework") assignments and two major ("project") assignments. The dates for the two exams are shown in the Exam Calendar above. Due dates for other deliverables will be available on the Course Calendar.
There are 1000 total points that may be earned in the course (not counting possible extra credit opportunities), distributed as shown in Table 1. At least 350 exam points (midterm and final exams) and 350 assignment points (projects and homework) must be earned to get a course grade of C or better. In addition, working solutions for every assignment must be submitted in order to be eligible for the grade of A or A-. Once meeting these constraints, the final grade is determined using Table 2.
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NOTE: You must earn at least 350 points in both Exams (in-term and final exams) and Assignments (projects and homework) to be awarded a course grade of C or better. In addition, you must submit a working version of every assignment in order to be eligible for the grade of A or A-.
Late Deliverables: Assignments should be submitted by the due date published in the course calendar. Late deliverables will be treated as non-existent.
Course textbook (required):
Object-Oriented Software Engineering, 2nd ed
B. Bruegge and A. Dutoit
Prentice Hall, 2004
ISBN=0-13-0471100
First Day Attendance Policy: Official university policy is that any student not attending the first class meeting will be automatically dropped from the class. For distance students, this policy is interpreted as posting to the discussion forum "First Day Attendance" no later than the first day of the semester.
Regular Attendance Policy: The university requires attendance in all classes. Attendance in distance classes shall mean regular access to the course web site via campus.fsu.edu and regular participation in the class discussion forums. Here, "regular" shall mean a substantial amount of time on a weekly basis. Note that individual access statistics are maintained by Blackboard.
Proctored Exam Policy: All exams must be proctored and taken at an approved testing site during the exam window or in class on the designated date. It is the student's responsibility to arrange for proctored exams in compliance with the FSU standards. Go to http://online.fsu.edu/learningresources/proctoredexam/ for details.
Exam Makeup Policy: An exam missed without an acceptable excuse will be recorded as a grade of zero (0). The following are the only acceptable excuses:
- If submitted prior to the day of the scheduled exam:
- A written and signed explanation as to why the exam will missed. Illness or required professional travel are acceptable, while discretionary or personal travel are not. In any case the explanation should be accompanied by corroborating documentation, including names and contact information, and the explanation must be accepted by the instructor prior to missing the exam.
- Evidence from a university official that you will miss the exam due to university sanctioned travel or extracurricular activity.
- If submitted on or after the day of the scheduled exam:
- A note from a physician, university dean, spouse, parent, or yourself indicating an illness or other extraordinary circumstance that prevented you from taking the exam and could not be planned for in advance. Again, corroborating information should be supplied.
All excuses must be submitted in writing, must be signed by the excusing authority, and must include complete contact information for the authority, including telephone numbers and address.
Missed exams with acceptable excuse will be made up or assigned the average grade of all other exams, at the option of the course instructor.
Missed, and acceptably excused, final exams will result in the course grade of 'I' and must be made up in the first two weeks of the following semester.
Grade of 'I' Policy: The grade of 'I' will be assigned only under the following exceptional circumstances:
- The final exam is missed with an accepted excuse for the absence. In this case, the final exam must be made up during the first two weeks of the following semester.
- Due to an extended illness or other extraordinary circumstance, with appropriate documentation, the student is unable to participate in class for an extended period. In this case, arrangements must be made to make up the missed portion of the course prior to the end of the next semester.
Completion of Work Policy: To be eligible for the grade of A or A-, working versions of all programming assignments must be submitted.
All students are expected to uphold the Academic Honor Policy published on-line here. Please note the following items are defined and made violations by the policy:
- Plagiarism
- Cheating
- Unauthorized Group Work
- Fabrication, Falsification, and Misrepresentation
- Multiple Submission
- Abuse of Academic Materials
- Complicity in Academic Dishonesty
- Attempted ...
Violations of the academic honor policy may result in failing grades and/or dismissal from the university. All students are expected to read and understand the policy.
