0. CSE 230: Introduction to Software Engineering
Topics covered:
Course outline and schedule

1. General information CSE 230 : Introduction to Software Engineering
Instructor : Swapna S. Gokhale
Phone :
Office : ITEB 237
Lecture time : Mon/Fri 11:00am – 12:15 pm
Office hours : By appointment
(I will hang around for a few minutes at the end of
each class).
Web page :
(Lecture notes, project, and general announcements will
be posted on the web page)
TA : Derek Doran
Office hours : The TA will announce his office hours.

2. Course goals
Appreciation and motivation for the study of software engineering
Software qualities and software engineering principles
Software design techniques
Traditional and object-oriented design.
Software specification techniques
Software verification techniques
Software production process
Management of software engineering
Software engineering tools and environments
Software architecture
Design patterns
Introduction to Java (though this is not a Java programming course)
Communication skills, and cooperative effort via a team project.

3. Expected learning outcomes
Be able to reason about the qualities that a software system must possess
Be able to describe traditional and object-oriented design.
UML class diagrams for describing an OO design
Demonstrate various software specification techniques
UML use-case, activity, and state-chart diagrams
Demonstrate software verification techniques
Empirical testing and informal analysis techniques
Be able to describe the software production process and various life cycle models
Describe and apply the management process to a software project.
Understand and be able to describe the importance of software engineering tools and environments
Become familiar with various architectural styles and design patterns
Develop communication skills and work effectively as a team

4. Textbooks Required text book:
1. Fundamentals of Software Engineering by Carlo Ghezzi, Mehdi Jazayeri,
and Dino Mandrioli, Second Edition, Prentice Hall, NJ.
Reference texts:
1. Software Engineering: A Practitioner’s Approach, By Roger S. Pressman
2. Budd book
3. The Mythical Man Month, By Fred P. Brooks
4. Any Java text book.
5. Papers may be handed out in the class.
6. Additional reference texts may be used from time to time, and will
be announced in the class

5. Course topics Introduction Software qualities
Historical perspective, state of the practice, why software engineering, relationship of software engineering to computer science and other disciplines
Software qualities
Qualities of the software product and process
Software engineering principles
General principles to be followed in the development of a software product
Software design
Traditional and OO design concepts, notations for describing traditional and OO designs
Software specification
Various techniques used for specifying the behavior and properties of software

6. Course topics (contd..) Software verification
Execution and non-execution based verification techniques
Verification of software qualities
Software production process
Phases in the software production, various life cycle models
Management of software engineering
Project planning, estimation and risk management
Software engineering tools and environment
Various tools to facilitate software engineering techniques
Software architecture and design patterns
Introduction to software architecture, software architectural styles and design patterns

7. Grading system Midterm #1, #2, #3: 45% Final : 30% Project : 25%
(Several parts)

8. Project The purpose of the project is to:
Introduce you to various aspects of software engineering, namely, requirements, design, implementation, and verification.
Enhance your communication skills, and your capability to cooperate and work as a part of a team.
Points will be allocated for documentation, requirements, and test plans in addition to demonstrating that your program works.
Projects will be carried out in teams of two.
Please select your team member and let the TA know within the next couple of weeks.
Your team member should be from the same lab section.

9. Course topics, exams and assignment calendar
Week #1 (Aug. 27):
Aug. 27: Course outline, schedule, Introduction
Aug. 31: Software Qualities (Chap. 2)
Week #2 (Sept. 3):
Sept. 3: Labor Day (No class)
Sept. 6: Software Engineering Principles (Chap. 3)
Week #3 (Sept. 10):
Sept. 10: Software Design (Chap. 4)
Sept. 13: Software Design (contd..) (Chap. 4)
Week #4 (Sept. 17):
Sept. 17: Software Design (contd..) (Chap. 4)
Sept. 20: Software Design (contd..) (Chap. 4)
Week #5 (Sept. 24):
Sept. 24: Software Design (contd..) (Chap. 4)
Sept. 27: Software Design (contd..) (Chap. 4)

10. Course topics calendar
Week #6 (Oct. 1)
Oct. 1: Software specification (Chap. 5)
Oct. 5: Software specification (contd..) (Chap. 5)
Week #7 (Oct. 8):
Oct. 8: Software specification (contd.) (Chap. 5)
Oct. 12: Software specification (contd..) (Chap. 5)
Week #8 (Oct. 15):
Oct. 15: Software specification (contd..) (Chap. 5)
Oct. 19: Software specification (contd..) (Chap. 5)
Week #9 (Oct. 22):
Oct. 22: Software verification (Chap. 6)
Oct. 26: Software verification (contd..) (Chap. 6)
Week #10 (Oct. 29):
Oct. 29: Software verification (contd..) (Chap. 6)
Nov. 2: Software verification (contd..) (Chap. 6)

11. Course topics calendar
Week #11 (Nov. 5):
Nov. 5: No class
Nov. 9: Software Production Process (Chap. 7)
Week #12 (Nov. 12):
Nov. 12: Software Production Process (contd..) (Chap. 7)
Nov. 16: Software Engineering Management (Chap. 8)
Week #13 (Nov. 19)
Thanksgiving break (no class)
Week #14: (Nov. 26)
Nov. 26: Software Engineering Management (contd..) (Chap. 8)
Nov. 30: Midterm #3
Week #15: (Apr. 26)
Dec 3: Software engineering tools.
Dec. 7: Make up class

12. Grading policy
Refer to the University policy regarding Student Conduct
(Plagiarism, etc.)
Grading of project/exams is handled by the TA, if you cannot
resolve a problem with the TA, see me.
Submit the lab assignments directly to the TA.
Late submissions are penalized by a loss of 33% per day late
(so 3 days late is as late as you can get).
If you have any conflict with the exam date, please see me in
advance for an alternative arrangement.
Project grading:
At the end of the semester, each one of you will be asked to provide
feedback about your team member
Your final project grade will take into consideration, the feedback
provided by your team member.

13. Attendance policy Attendance not mandatory. Attending classes helps!
Case studies in the class
Everything not in the lecture notes

14. Labs Labs will be handled by the TA
Java will be introduced in the labs.
Please feel free to discuss any Java related issues with the TA or me
I request you to attend the lab, as the project will be introduced on
a part by part basis in the lab.

15. Feedback
Please provide informal feedback early and often, before the formal
review process.