Académique Documents
Professionnel Documents
Culture Documents
htm
CS 3354 Software Engineering: (3 semester hours) 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.
Fall 2005
1 of 5 8/23/2005 9:54 AM
CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.htm
8. Ability to understand functional and non-functional e,f,k k. An ability to use the techniques, skills, and
software specifications modern engineering tools necessary for
engineering practice.
9. Ability to establish and participate in an ethical d,f,g,k
software development team
10. Ability to use metrics to evaluate and forecast a,e,k
software developmental effort
Grading Weights: Test One 25%; Test Two 25%; Project and Presentation 20% and Assignments 10%; Test 3
20%. Highest student score in each event will become the divisor to determine individual event percentage score; final
class weighted score, and class grade curve. Any missing or late event scores will be given a zero grade in the
calculation of a course grade. Incomplete grades will not be issued.
http://www.stsc.hill.af.mil/crosstalk/frames.asp?uri=1998/04/dimensions.asp
and
http://www.sei.cmu.edu/publications/documents/00.reports/00tr023.html as
a start
Homework 2
Class Project
Team List
Student Responsibilities
While teamwork and collaboration is encouraged, identical assignment or test deliverables are not
acceptable. Regular class attendance and participation is expected. The sick leave policy for this class
allows one day per month for excused student absence due to illness, work or family related reasons. Student
will sign class attendance log in each class session. Should a student exceed four (4) class absences during the
approximately 44 class sessions, the course final score will be lowered by 13% (2/16) in the calculation of the
course grade. All UTD student conduct policies and standards will be in effect.
At the end of the course you will be required to turn in project evaluations and peer reviews. Failure to
turn in an evaluation will reduce your final grade 5 points.
2 of 5 8/23/2005 9:54 AM
CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.htm
Class Schedule
Date Topics Text Lecture Notes
Readings
Outline of Course Activities and Events. Ch. 1 (1-18),
Software Engineering
Form project
teams
Software Process Ch. 2 (19-44) Notes 1
Process Models Ch. 3 (45-70)
Agile Development Ch. 4 (71-94) Notes 2
Software Engineering Practice Ch. 5 (95-121)
Project Management Concepts Ch 21 Notes 3
(596-616)
Process and Project Metrics Ch 22
(617-641)
Software Project Estimation Ch 23 Notes 4 Notes 5
(642-672)
Component-Level Design Ch 11
(292-323)
class design
User Interface Design Ch 12 Architecture
(324-353)
UIdesign notes
3 of 5 8/23/2005 9:54 AM
CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.htm
Quality Management Ch 26 QM
(712-738)
Change Management Ch 27
(739-768)
Formal Methods Ch 28 Part 5
(769-795)
Cleanroom Software Engineering Ch 29
(796-814)
Component-Based Software Engineering Ch 30
(815-836)
Reengineering Ch 31
(837-859,
The Road Ahead Ch 32
(860-870)
Project Presentations Sample final
report
Project Presentations
Project Presentations
Review
Nov 23 Test 3 parts 1 and 2 Chapters Review 3
13-15,
BRING A SCANTRON narrow greenForm882E 21-27
and a number 2 pencil
Picture of Scantron 882E Class Notes PEER REVIEW FORM
4 of 5 8/23/2005 9:54 AM
CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.htm
5 of 5 8/23/2005 9:54 AM