EE 360F - Introduction to Software Engineering
Office Hours
Tuesday and Thursday -- 11:00-12:00 am in ENS 623A
Summer: By Appointment
Syllabus
This course is an introduction to software engineering with an emphasis on
the methods, techniques and technology to build and evolve software
systems. The emphasis is on software engineering principles, and not
on programming (an assumed skill and a relatively small part of building
and evolving systems). We will cover the main activities of building
systems (requirements engineering, system architecture and design,
system construction, and deployment and maintenance) and the elements
that are integral to those activites (evolution, measurement and
evaluation, teamwork, and management of project artifacts). In addition
we will cover process engineeering and project management.
Additional information
A sample exam
Class Policies
Grading:
- 10% -- Class Participation
- 30% -- EXAM 1
- 30% -- EXAM 2
- 30% -- EXAM 3
- NOTE: improvement provides extra weighting on the final grade.
Examinations
-
Each exam covers all the lectures and papers since the previous exam
-
Closed book exams -- no notes, books, etc allowed
-
No leaving the room during the exam
CHEATING:
Simply stated: the work on any homework and any exam MUST be your own
work. Collaborating in any way on homework (unless specifically
allowed) is cheating. Plagiarizing from any source for homework is
cheating. Using any sources for homework (unless explicitly allowed)
is cheating.
You may, of course, study in groups for exams, BUT during the exam
providing information to, or obtaining information from, another
student is cheating. Obtaining information from books, notes, etc
during a closed-book exam is cheating.
Official ECE Policy: Faculty in the ECE Department are
committed to detecting and responding to all instances of scholastic
dishonesty and will pursue cases of scholastic dishonesty in
accordance with university policy. Scholastic dishonesty, in all its
forms, is a blight on our entire academic community. All parties in
our community -- faculty, staff, and students -- are responsible for
creating an environment that educates outstanding engineers, and this
goal entails excellence in technical skills, self-giving citizenry,
and ethical integrity. Industry wants engineers who are competent and
fully trustworthy, and both qualities must be developed day by day
throughout an entire lifetime. Scholastic dishonesty includes, but is
not limited to, cheating, plagiarism, collusion, falsifying academic
records, or any act designed to give an unfair academic advantage to
the student. The fact that you are in this class as an engineering
student is testament to your abilities. Penalties for scholastic
dishonesty are severe and can include, but are not limited to, a
written reprimand, a zero on the assignment/exam, re-taking the exam
in question, an F in the course, or expulsion from the
University. Don't jeopardize your career by an act of scholastic
dishonesty.
University Honor Code
Any students with disabilities may request appropriate academic
accommodations from the Division of Diversity and Community Engagement,
Services for Students with Disabilities, 471-6259.
Reading Assignments
Frederick Brooks, Mythical Man Month, 20th Anniversary Edition
-
By Exam 1, Chapters 1-4, 16, 17
-
By Exam 2, Chapters 5-11
-
By Exam 3, Chapters 12-15, 18, 19
27 Aug: Introduction - Systems and Complexity - Overview
[lecture notes]
-
Brooks, Chapters 16 & 17: No Silver Bullet & No Silver Bullet Refired
1 Sept: Ethics in Software Engineering
[lecture notes]
3 Sept: Elements of engineered software systems
[lecture notes]
-
Perry, Dimensions of Software Evolution
[pdf]
-
Lehman & Belady, Chapter 19, sections 1-2
[pdf]
8 Sept: Requirements - Elicitation
[lecture notes]
-
Potts et al, Inquiry based requirements analysis
[pdf]
10 Sept: Requirements - World & Machine; Prototyping
[lecture notes]
-
Jackson, The World and the Machine
[pdf]
-
Luqi & Royce, Status report: computer-aided prototyping
[pdf]
15 Sept: Architecture - overview
[lecture notes]
-
Perry & Wolf, Foundations for the study of Software Architecture
[pdf]
17 Sept: Architecture - Mismatch, Example of Linux, Product Line Architecture
[lecture notes]
-
Garlan et al, Architectural mismatch ...
[pdf]
-
Bowman et al, Linux as a case study ...
[pdf]
22 Sept: EXAM 1
24 Sept: Design - Design Principles
[lecture notes]
-
Parnas, Designing SW for ease of extension and contraction
[pdf]
-
Parnas & Clements, A Rational Design Process ...
[pdf]
29 Sept: Design - Design Methods
[lecture notes]
-
Bergland, A Guided Tour of Program Design Methodologies
[pdf]
1 Oct: Design - Design Experience
[lecture notes]
-
Lampson, Hints for System Design
[pdf]
6 Oct: Construction - Building and Composition
[lecture notes]
-
Wolf/Rosenblum, A Study in SW Process Data Capture/Analysis
[pdf]
8 Oct: Deployment and Maintenance
[lecture notes]
-
Hall et al, The Software Dock
[pdf]
13 Oct: Maintenance and Evolution
[lecture notes]
-
Perry/Stieg, Software Faults in Evolving a Large ...
[pdf]
-
Lehman/Belady, Chapter 19, sections 3-end
[pdf]
15 Oct: Artifacts and their Management - Configuration Mgmt
[lecture notes]
20 Oct: Measurement & Evaluation - Reviews & Testing
1[lecture notes]
-
Porter et al, An experiment to assess the costs-benefits
of code inspections in large scale developments
[pdf]
-
Kaiser etal, Infuse: fusing integration test mgmt ...
[pdf]
22 Oct: EXAM 2
27 Oct: Measurement & Evaluation - Empirical Studies I
[lecture notes]
29 Oct: Measurement & Evaluation - Empirical Studies II
[lecture notes]
-
Perry/Stieg, Software Faults
[pdf]
-
Bradac etal, Prototyping a Process Monitoring Experiment
[pdf]
-
Perry etal, People Organizations and Process Improvement
[pdf]
3 Nov: Team Work -
[lecture notes]
-
Perry/Kaiser, Models of SW Development Environments
[pdf]
-
Grinter etal, The Geography of Coordination
[pdf]
5 Nov: NO CLASS
10 Nov: Process - Introduction
[lecture notes]
-
Osterweil, SW Processes are SW Too, Revisited;
[pdf]
-
*Wolf/Rosenblum, A Study in SW Process Data Capture/Analysis
[pdf]
12 Nov: Process - Measurement & Evaluation
[lecture notes]
-
Carr etal, Experiments in Process Interface Visualizations ...
[pdf]
-
*Perry etal, People Organizations and Process Improvement
[pdf]
17 Nov: Process - Architecture, Design
[lecture notes]
-
Dandekar/Perry, Barriers to Effective Process Architecture
[pdf]
19 Nov: Process - Improvement
[lecture notes]
-
Dandekar etal, Studies in Process Simplification
[pdf]
24 Nov: NO CLASS
26 Nov: NO CLASS - Thanksgiving
1 Dec: Project Management
[lecture notes]
[final exam details]
-
relevant Project Management chapters in Brooks MMM
3 Dec: EXAM 3
|
Dewayne E. Perry
- This information last updated August 2009
|
|
Copyright © 1996-present. All rights reserved.
|