Vous êtes sur la page 1sur 5

CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.

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

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: TBP


E-mail: Hours -
Office

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 ABET ABET Objectives


1. Ability to analyze and evaluate software processes e,f,k a. An ability to apply knowledge of
mathematics, science and engineering.
2. Ability to establish software requirements and e,f,k b. An ability to design and conduct
specifications experiments as well as to analyze and
interpret data.
3. Ability to design software b,c,e,k c. An ability to design a system, component or
process to meet desired needs.
4. Ability to perform verification and validation of a,c,e,k d. An ability to function on multidisciplinary
software specifications teams
5. Ability to use software project management tools c,e,k e. An ability to identify, formulate and solve
and techniques engineering problems.
6. Ability to use CASE tools for software development c,e,k f. An understanding of professional and
ethical responsibility
7. Ability to understand formal methods in software a,e,k g. An ability to communicate effectively.
development

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

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 http://cstalon.utdallas.edu/3354/3354f05.htm

PROJECT TEAMS ASSIGNMENT

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)

Software Project Scheduling Ch 24 Notes 6


(673-693)

Requirements and Analysis Modeling Ch 8 Notes 7


(175-225)

some thoughts on analysis


models
Sept 23 Review
Sept 26 Test One Part 1 Chapters 1 - 8
; 21-24 BRING A SCANTRON
narrow green Form 882-E
and Lectures and a number 2 pencil
Picture of Scantron
882E
Sept 28 Test One Part 2 (Practical Exercise) I will supply the paper
for the practical
exercise.

Design Engineering Ch. 9 (226-253) Design

Architecture Design Ch 10 (254-291)

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

Software Testing Strategies Ch 13


(354-387)
Software Testing Techniques Ch 14
(388-428)
Metrics for Software Products Ch 15
(429-466)
Web Engineering Ch 16
(467-481)
Planning for Web Engineering Ch 17
(482-506)
Analysis Modeling for Web Applications Ch 18
(507-526)
Design Modeling for Web Applications Ch 19
(527-561)
Testing Web Applications Ch 20
(562-594)
Oct 21 Review2
Oct 24 Test Two Part 1 Chapters 11 -
20 and BRING A SCANTRON
Lectures narrow green Form 882-E
and a number 2 pencil
Picture of Scantron
882E
Oct 26 Test Two Part 2(Practical Exercise) I will supply the paper
for the practical
exercise.
Project Management Concepts Ch 21
(596-616)

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

PLEASE BE SURE I HAVE A SOFT

4 of 5 8/23/2005 9:54 AM
CS 3354-002 http://cstalon.utdallas.edu/3354/3354f05.htm

COPY OF YOUR COMPLETE WORK


(ALL DELIVERABLES TO INCLUDE
CODE)
Nov 28 No Class

5 of 5 8/23/2005 9:54 AM

Vous aimerez peut-être aussi