CS 3354-002


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 Section 002 meets M W F 3:00 PM – 3:50 PM
Room ECS 2.412

Instructor: Anthony D. Sullivan, Ph.D.

UTD Office: ECSS 4.701

Office Hours: Wednesday 12:50-13:50 Thursday 20:15 -21:15

UTD Telephone: (972) 883-6620

E-mail: sulliva@utdallas.edu

Teaching Assistant: E-mail: Office

TBP Hours -

Textbook: Software Engineering A Practitioner’s Approach, Sixth Edition by Roger S. Pressman, McGraw-Hill, ISBN: 0-07-285318-2.

Course Objectives: This course is intended to provide an introduction to software engineering, software lifecycle models, software requirements engineering, formal specifications and software validation. Topics will include the software engineering techniques for the design, analysis, specification, development, testing, quality control, implementation, and evolution of large-scale software systems. Introductory study of project management, feasibility analysis, cost estimation models, CASE tools, information system proposals and presentations, database design, systems operations and support, and use of software metrics. Class Objectives
1. Ability to analyze and evaluate software processes 2. Ability to establish software requirements and specifications 3. Ability to design software 4. Ability to perform verification and validation of software specifications 5. Ability to use software project management tools and techniques 6. Ability to use CASE tools for software development 7. Ability to understand formal methods in software development

e,f,k e,f,k

ABET Objectives
a. An ability to apply knowledge of mathematics, science and engineering. b. An ability to design and conduct experiments as well as to analyze and interpret data. c. An ability to design a system, component or process to meet desired needs. d. An ability to function on multidisciplinary teams e. An ability to identify, formulate and solve engineering problems. f. An understanding of professional and ethical responsibility g. An ability to communicate effectively.

b,c,e,k a,c,e,k c,e,k c,e,k a,e,k

1 of 5

8/23/2005 9:54 AM

CS 3354-002


8. Ability to understand functional and non-functional software specifications 9. Ability to establish and participate in an ethical software development team 10. Ability to use metrics to evaluate and forecast software developmental effort


k. An ability to use the techniques, skills, and modern engineering tools necessary for engineering practice.

d,f,g,k a,e,k

Course prerequisite: CS 2305, and CS2315 or CS333.

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.

Assignments: TBA in class sessions, project report, and project presentation.
Homework 1 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.

STUDENTS MUST CHECK THE CLASS WEBSITE AND NEWS AT www.utdallas.edu/~sulliva AT LEAST ONCE A WEEK ---ALL CHANGES AND ASSIGNMENTS WILL BE PUBLISHED-- THERE AND NO WHERE ELSE...YOU ARE RESPONSIBLE FOR ANY ASSIGNMENT CHANGES PUBLISHED PRIOR TO THAT WEEKS CLASS. The schedule below is subject to change 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. Course Topics Sequence and Road Map of Events CS/SE 3354 FAll 2004

2 of 5

8/23/2005 9:54 AM

CS 3354-002


Date Topics Outline of Course Activities and Events. Software Engineering Text Readings Ch. 1 (1-18), Form project teams Ch. 2 (19-44) Ch. 3 (45-70) Ch. 4 (71-94) Ch. 5 (95-121) Ch 21 (596-616) Ch 22 (617-641) Ch 23 (642-672) Ch 24 (673-693) Ch 8 (175-225) Lecture Notes

Software Process Process Models Agile Development Software Engineering Practice Project Management Concepts Process and Project Metrics Software Project Estimation

Notes 1 Notes 2 Notes 3

Notes 4 Notes 5

Software Project Scheduling

Notes 6 Notes 7

Requirements and Analysis Modeling

some thoughts on analysis models Sept 23 Sept 26

Test One Part 1 Chapters 1 - 8 ; 21-24 and Lectures BRING A SCANTRON narrow green Form 882-E and a number 2 pencil

Sept 28

Test One Part 2 (Practical Exercise)

Picture of Scantron 882E I will supply the paper for the practical exercise.

Design Engineering

Ch. 9 (226-253) Ch 10 (254-291)

Architecture Design Component-Level Design

Ch 11 (292-323) class design Ch 12 (324-353) UIdesign notes

User Interface Design


3 of 5

8/23/2005 9:54 AM

CS 3354-002


Software Testing Strategies Software Testing Techniques Metrics for Software Products Web Engineering Planning for Web Engineering Analysis Modeling for Web Applications Design Modeling for Web Applications Testing Web Applications Oct 21 Oct 24

Test Two Part 1

Ch 13 (354-387) Ch 14 (388-428) Ch 15 (429-466) Ch 16 (467-481) Ch 17 (482-506) Ch 18 (507-526) Ch 19 (527-561) Ch 20 (562-594) Review2 Chapters 11 20 and Lectures

BRING A SCANTRON narrow green Form 882-E and a number 2 pencil

Oct 26

Test Two Part 2(Practical Exercise)

Picture of Scantron 882E I will supply the paper for the practical exercise.
Ch 21 (596-616) Ch 26 (712-738) Ch 27 (739-768) Ch 28 (769-795) Ch 29 (796-814) Ch 30 (815-836) Ch 31 (837-859, Ch 32 (860-870) Sample final report QM

Project Management Concepts

Quality Management Change Management Formal Methods Cleanroom Software Engineering Component-Based Software Engineering Reengineering The Road Ahead Project Presentations Project Presentations Project Presentations Review Test 3 parts 1 and 2 BRING A SCANTRON narrow greenForm882E and a number 2 pencil

Part 5

Nov 23

Chapters 13-15, 21-27 Class Notes

Review 3

Picture of Scantron 882E PLEASE BE SURE I HAVE A SOFT


4 of 5

8/23/2005 9:54 AM

CS 3354-002


Nov 28 No Class


5 of 5

8/23/2005 9:54 AM

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.