COURSE SYLLABUS

LANGSTON UNIVERSITY TULSA SPRING SEMESTER, 2006
COURSE TITLE: Software Engineering
CS-3163-51 (10346)
CLASS MEETING DAY: Tuesday
TIME: 8:20 PM-11:00 PM
ROOM NUMBER: T-MCB 2315
INSTRUCTOR: John H. Young
HOME PHONE NUMBER: 749-8547
E-MAIL ADDRESS: jhyoung@comsci.us
WEBSITE:http://www.comsci.us
CONFERENCES: By arrangement
REQUIRED TEXTBOOK: Roger S. Pressman, Software Engineering: A Practitioner's Approach, Sixth Edition
PREREQUISITE: CS 3153

CATALOG DESCRIPTION:

Examines principles of control for large programming projects requiring extensive software support. Develops strategies, methods, and procedures for the design, development, testing, implementation, and documentation of software and studies the history of successful projects. Student teams are organized to evaluate problems typically faced by professionals in software engineering.

RATIONALE:

Computer software is becoming increasingly complex, as more functionality and useability are demanded. Applications are developed by teams, and require coordination and management. Sound engineering approaches are required for the development of quality software.

GRADING SYSTEM:

Points will be distributed as follows:
# Assignment/Exam Points Possible Total
4 Exams 1-4 Approx. 30 points each 120
1 Final Exam Approx. 150 150
1 Class Project 150 150
Total 420
Percentage Grade
90-100% A
80-89% B
70-79% C
60-69% D
<=59% F

Exams will consist mainly of essay questions.

All grades will be included in the final grade. Make-up exams must be scheduled in advance of the scheduled exam date, and they must be taken within one week before or after the scheduled date.

Class attendance and participation will be used to determine borderline grades.

COURSE OBJECTIVES

Upon successful completion of the course, students should be able to:

  1. Work in large, coordinated teams.
  2. Use sound methodologies for software engineering.
  3. Deliver quality software.
  4. Apply metrics both to estimate effort and to evaluate software.

ATTENDANCE POLICY:

Attendance is required. While no points are deducted for absences, you will miss the points for any quiz or assignments you fail to turn in on a day you are absent. If you must be absent, check with the instructor about any assignment that may be due on the day you return. If you miss a day when an assignment is to be turned in, it is your responsibility to turn it in ahead of time.

STUDENTS WITH DISABILITIES:

If any member of the class feels that he/she has a disability and needs special accommodations of any nature, the instructor will work with you and the Office of Disabled Student Services to provide reasonable accommodations to ensure that you have a fair opportunity to perform in the class. Please advise the instructor of such a disability and the desired accommodations at some point before, during, or immediately after the first scheduled class period.

WITHDRAWAL FROM THE CLASS:

If, for whatever reason, you do not complete this course, you MUST FORMALLY WITHDRAW by filling out and turning in the proper paperwork. The responsibility is YOURS!

If your name appears on the final grade sheets and you have not accumulated enough points to pass the class, you will receive an F even if you are no longer attending.

TENTATIVE CLASS CALENDAR:

Session Date Lecture/Reading Assignment
Part One The Software Process
  January  
1 10 Chapter 1
Chapter 2		 Software and Software Engineering
Process: A Generic View
2 17 Chapter 3 Prescriptive Process Models
3 24 Chapter 4 Agile Development
Part Two Software Engineering Practice
4 31 Chapter 5
Chapter 6		 Practice: A Generic View
System Engineering
  February  
5 7 Chapter 7
Chapter 8		 Requirements Engineering
Analysis Modeling
6 14 Chapter 9 Design Engineering
7 21 Chapter 10 Architectural Design
8 28 Chapter 11 Component Level Design
  March  
9 7 Chapter 12 User Interface Design
10 14 Chapter 13
Chapter 14		 Software Testing Strategies
Software Testing Techniques
Part Three Applying Web Engineering
11 28 Chapter 16 Web Engineering
  April  
12 4 Chapter 17
Chapter 18		 Formulation and Planning
Analysis Modeling for Web Applications
13 11 Chapter 19 Design Modeling for Web Applications
14 18 Chapter 20 Testing Web Applications
15 25 Project Evaluation of Class Project
  May  
16 2 Comprehensive Final Exam

AFFIRMATIVE ACTION STATEMENT

Langston University in compliance with Title VI and VII of the Civil Rights Acts of 1964, Executive Order 1121 as amended, Title IX of the Educational Amendments of 1972, American with Disabilities Act of 1990, and other Federal laws and regulations, does not discriminate on the basis of race, color, national origin, sex, age, religion, handicap, or status as a veteran in any of its policies, practices, or procedures.  This includes but is not limited to admissions, employment, financial aid and educational services.

AMERICANS WITH DISABILITIES (ADA) STATEMENT

Langston University fully subscribes to all required standards of the ADA Act of 1990. Persons in need of assistance should contact the ADA Compliance Officer in the Office of Student Affairs, Room 119 Page Hall, 405-466-3445.  This should be reported at some point before, during, or immediately after the first scheduled class period so accommodations can be provided for the student to be successful in that class.

  • Comportment: Students are expected to abide by the School's dress code and code of ethics.

  • This syllabus may be amended at anytime during the semester.  All changes will be discussed in class.

  • All reading assignments must be completed before class session.

Policy on Electronic Devices in the Classroom:

All electronic devices (e.g., cell phones, pagers, palm pilots, beeper watches) are considered unnecessary distractions and are to be turned off and (with the exception of watches) concealed during class.  Thus, interacting with these devices during class will not be tolerated.  Instructors may make exceptions for instructional purposes.  A student who anticipates an emergency and expects to be contacted in class by an outside source must go directly through the emergency dispatch system identified on each of the respective campuses.  The emergency dispatcher will take the message and deliver it to the instructor. 

A student who fails to comply with this policy will be initially dismissed from the class and (per the Instructor's discretion) may be counted absent.  Points may be deducted for work missed during that time.  A student who violates this policy a second time will be dropped from the course for disruptive behavior.  A student whose electronic device is activated during an exam will be dismissed from the class and denied the opportunity to complete or take that exam.  An Instructor may elect not to grade that exam.