|
|
COURSE SYLLABUS CEN 4010
|
CLASS SCHEDULE FOR ON-CAMPUS STUDENTS:
|
Activity |
Day |
Time |
Location |
|
Lecture |
Monday and Wednesday |
8:00am – 9:15 am |
LOV 103 |
EXAM SCHEDULE: See Course Schedule
COURSE SCHEDULE:
|
Week |
Topic |
Reading Assignment |
Homework/Assignmenti |
|
1 |
Introduction to Software Engineering |
Chapter1, 2.2.1 – 2.2.5 |
Problems 2.11 |
|
2 |
Software Processes |
Chapter 4 |
Problems 4.1, 4.2, 4.5 |
|
3 |
Software Requirements |
Chapter 6 |
|
|
4 |
Requirements Engineering |
Chapter 7 |
Problems 7.2 |
|
5 |
Review and Test |
Test Chapters 1, 4,6, 7 |
|
|
6 |
System Models |
Chapter 8 |
|
|
7 |
System Models and Database Design |
Chapter 8 + Notes |
Database Design |
|
8 |
Formal Specifications |
Chapter 10 |
|
|
9 |
Object Oriented Design |
Chapter 14 |
Problems 14.2, 14.4 |
|
10 |
Spring Break – No Class |
|
|
|
11 |
Rapid Development |
Chapter 17 |
|
|
12 |
Software Reuse - Patterns |
Chapter 18 |
|
|
13 |
Testing, Validation, Verification |
Chapter 22/23 |
Problems
22.1, 22.5 Problems 23.1, 23.5 |
|
14 |
Review and Test |
Test
Chapter 8, Notes, 10, 14, 17, 18, 22, 23 |
|
|
15 |
Project
Presentations |
|
|
|
16 |
Finals
Week |
Final
Exam |
Test
25 April, 10-12 |
PROJECT RELEASE PROCESS:
Projects are assigned near the beginning of the term. You will be graded on your individual work. Even though these projects will be combined into a single piece of work it is important that you do not rely on others to bring your grade up in an overall project. Each of you will be assigned a specific task to perform and will graded on the quality of that task.
COURSE PERSONNEL:
|
Lead Instructor: |
Dr. David A. Gaitros |
|
Responsibilities: |
Overall course coordination, lecture materials, code library, and projects |
|
Office: |
University Center C room C6131 |
|
Phone: |
644-4883 |
|
Email: |
dgaitros@fsu.edu |
|
Office Hours: |
Monday and Wednesday 9:30am - 11:00am or by appointment at other times |
|
|
|
COURSE
MATERIALS:
Either of these text books will be sufficient.
· Somerville, Ian (2001)Addison-Wesley Software Engineering 7th Edition). Massachusetts: Addison Wesley ISBN 0-321-21026-3
OR
· Somerville, Ian (2001)Addison-Wesley Software Engineering 8th Edition). Massachusetts: Addison Wesley ISBN 0-321-31379-8
ON-LINE RESOURCES:
The
following are useful on-line references:
|
o Ghostscript (.ps and .pdf passive reader) Download Site |
COURSE
DESCRIPTION:
In previous courses in computer science you were taught how to write code given a specific design and set of specifications. In this course, you will learn to develop those designs and specifications and the formal methods used.
Preface
from Software Engineering, by Ian Sommerville 7th and 8th
Editions: “Our current software
engineering methods and techniques have made us much better at building large
and complex systems than we were.
However, there are still too many projects that are late, are over
budget and do not deliver the software that meets the customer’s needs. While I was writing this book, a government
enquiry in the UK reported on the project to provide a national system to be
used in courts that try relatively minor offenders. The cost of this system was
estimated at ₤156 million and it
was scheduled for delivery in 2001. In 2004, costs of escalated to ₤390 Million
and it is still not fully functional. There is, therefore, still a pressing
need for software engineering education. “
The course will cover chapters 1,4,6,7,8,10,12,14,17,18, 22 and 23. However the student is encouraged to read all of the chapters. Time does not permit us to cover all topics in this book in just one semester. It is particularly important that the student place a great deal of emphasis in understanding the different design models and the sections covering requirements analysis and system specification. As it turns out, developing a complete set of requirements and specifications is one of the more difficult and critical tasks in software engineering.
The topics mentioned in the title of the course are Software Engineering, Software Processes, Project Management, Software Requirements, Prototyping, Specifications, OOD, Verification and Validation, Testing, Management of People, Cost Estimation, Legacy Systems, Reengineering, Formal Specifications, User Interfaces, Distributed Systems, and Requirements. It is important the students have taken data structures because there may be a programming problems required by all students where they will have to show their ability to solve a simple problem using data structures from scratch to completely develop a program.
During the course of this term the students will be involved with a real problem solving/software requirements and design situation. Students will be required to gather functional requirements, identify the problem, form a solution and present this solution to a prospective customer. The problems will be assigned in class.
COURSE
OBJECTIVES:
At the end of this course, the student should understand the following concepts:
· Follow a Software Design to Code Development
· The Software Crisis
- Software Processes and Models
- Requirements, specification, Architectural Design, and OOD
- Verification and Validation
- Testing
- Object Oriented Design
- Patterns
- Rapid Development
- Software Reuse.
COURSE
POLICIES:
Attendance
Policy:
The
University requires attendance in all classes. Attendance in this class shall
mean:
· Attending lectures at their regular scheduled times
· Regularly participating in class discussions
· Taking Exams at the scheduled time and place
· Submitting assignments correctly and on deadline
· Monitoring the class website and discussion boards.
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 scheduled exam: Evidence from a University official that you will miss the exam due to University sanctioned travel or extracurricular activity
· A note from a physician, University dean, or parent indicating an illness or other extraordinary circumstance that prevented you from taking the exam
· An emergency of unexpected origin
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.
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.
Late Assignment Policy:
· An assignment that is turned in no more than 24 hours late will be scored with a 10% penalty.
· An assignment that is turned in no more than 48 hours late will be scored with a 20% penalty.
· An assignment that is turned in more than 48 hours late will receive the score of zero (0). However, all assignments must be turned in to obtain full credit for the course.
Grade
of 'I' Policy:
The grade of
'I' is given to a student who, for circumstances beyond their control, missed
the opportunity to cover course materials. Under the conditions stated by the
University, the grade of 'I' means that a student is allowed the next semester
of their enrollment to make up all remaining course materials. It does not
allow a student the opportunity to hand in additional work or improve their grade
on previous assignments. 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.
GRADING/EVALUATION:
The overall grade for CEN 4010 is a calculation of the percentage of points from attendance, homework, exams, and group project. Homework, tests, projects, and attendance will be normalized to the point values listed below. The group project will have both a project grade and individual grade based upon the quality and participation of each student in the project.
There
are 800 total points that may be earned in the course distributed as shown in
Table 1. The final grade is determined using Table 2.
|
TABLE
1: Point Values
|
|
||||||||||||||||||||||||||||||||||||||
ASSIGNMENTS/RESPONSIBILITIES:
Assignments will be released at the beginning of each semester. Since students are give the assignments in advance, no excuses will be accepted for late turn in of assignments. Normal penalties for late turn in will be assessed.
ACADEMIC HONOR CODE:
Students are expected to uphold the Academic Honor Code published in The Florida State University Bulletin and the Student Handbook. The Academic Honor System of The Florida State University is based on the premise that each student has the responsibility (1) to uphold the highest standards of academic integrity in the student's own work, (2) to refuse to tolerate violations of academic integrity in the university community, and (3) to foster a high sense of integrity and social responsibility on the part of the university community.
Please
see the following web site for a complete explanation of the Academic Honor
Code.
http://www.fsu.edu/Books/Student-Handbook/codes/honor.html
http://www.fsu.edu/Books/Student-Handbook/
In particular, note that students may not give or receive help of any kind on programming projects. This means, among other things, that students are not permitted to read each other’s code (on paper OR on screen) or discuss design or implementation of programming projects with anyone other than the instructional personnel. Violations of this policy will result in the grade of zero for all parties involved.
AMERICANS WITH DISABILITIES ACT:
Students with disabilities needing academic
accommodation should: (1) register with and provide documentation to the
For more information about services available to FSU students with disabilities, contact the (T
Student Disability Resource Center
Dean of
Students Department
97 Woodward
Ave, South 108 Student Services Bld
Florida State
University
Tallahassee,
FL 32306-4167
(850)
644-9566 (voice)
(850)
644-8504 (TDD)
SDRC@admin.fsu.edu
http://www.fsu.edu/~staffair/dean/StudentDisability/
(This syllabus and other class materials are available in alternative format upon request.)
SYLLABUS CHANGE POLICY:
This syllabus is a guide for the course and is subject to change with advanced notice. Such notice will be in the form of an announcement to the Blackboard course web site.