CS 3354 Section 001
Software Engineering
Fall 2004
Instructor:
Office: ECSS
3.204, ECS, UTD
E-mail: chung@utdallas.edu
Phone: 972-883-2178
Web page:
http://www.utdallas.edu/~chung/SE/syllabus.htm
Office hours: M
Lectures: MWF
TA: Yu Qi (yxq014100@utdallas.edu), Office: ECS 3.209; Office hours: TR
Textbook:
Software Engineering: A Practitioner's
Approach, 6th Edition, Roger S. Pressman, New York: McGraw-Hill
References:
Software Engineering, Ian Sommerville,
Addison-Wesley
The Mythical
Man-Month, Frederick P. Brooks, Jr., Addison Wesley
The Unified Modeling Language User Manual, G. Booch, J. Rumbaugh and I. Jacobson, Addison-Wesley, 1998.
Prerequisites: CS 2305 (Discrete
Mathematics for Computing I) & CS 2315
(Computer Science II)
Objectives: Introduction
to software life cycle models. Software requirements engineering, formal
specification and validation. Techniques for software design and testing. Cost
estimation models. Issues in software quality assurance and software
maintenance. Prerequisites: CS 2315 or CS 3333, and CS 2305. (Same as SE 3354)
Computer Usage:
You
can obtain a trial version of Rational Rose to run the program(s) on your home
PC from http://www.rational.com/tryit/index.jsp,
demo and online tutorial from http://www.rational.com/tryit/rose/seeit.jsp . A student
version is also available.
If you wish, you can use the facilities at UTD too (ES2.104 on the ground floor in ECS). All PC’s in the labs of UTD are installed with Rational Rose. There are several open access labs: http://www.utdallas.edu/ir/tcs/labs/locations.htm. You will need to get a user ID for the lab, https://netid.utdallas.edu. Need help? 972-883-2911, assist@utdallas.edu, http://www.utdallas.edu/ir/tcs
Project: There
will be a 3-phase project. Each project
phase should be submitted by the expected due date in the beginning of the
class that day. Project phases should be
submitted with student name, student ID, student email address, project phase
#, and class/section written on the first page.
The project
will be done by teams of 3 students. (Teams with more or less than 3 members
will be allowed only under exceptional circumstances). All students in a team
will get the same mark for the work they do unless they unanimously agree (in
writing) to an unequal division. You are to choose your own team members. An
orphan will be assigned to a team by the instructor.
Tests:
There will be two tests, one in
the middle (test 1) and the other at the
end (test 2) of the course.
Late work: Any assigned
work will have 10 points deducted for each week passed.
Grading:
|
Project (3 x 10) |
Sept 27; Oct 25;
Nov 22 |
30 % |
|
Test 1 |
Oct 4 |
25 % |
|
Test 2 |
Nov 29 |
45 % |
Important Dates:
1.
Aug 19 (Friday)
- first day of class for this course
2.
Sept 27
(Monday) – project phase
1
3.
Oct 4 (Monday)
– test 1
4.
Oct 25
(Monday) – project phase
2
5.
Nov 22 (Monday) – project phase 3
6.
Nov 29
(Monday) -- test 2
The
dates above are due dates. You can choose to turn in your project deliverables
early.
Cheating/Dishonesty:
The University of Texas System Policy on
Academic Honesty (The Regents and Regulations, Part One, Chapter VI, Section 3,
Paragraph 3.22):
Any student who commits an act of
scholastic dishonesty is subject to discipline. Scholastic dishonesty includes
but is not limited to cheating, plagiarism, collusion, the submission for
credit of any work or materials that are attributable in whole or in part to
another person, taking an examination for another, any act designed to give
unfair advantage to a student or the attempt to commit such acts.
The minimum penalty for academic
dishonesty is a failing grade (zero)
§
Requirements Analysis & Specification [PDF] [PostScript]
Houses, architectural
blueprints
More on
Component Diagrams & Architectures
Design Document Example – System
Design; Object
Design
Test Plan Template;
Test
Case Specification Template