Fall 2011
Course Syllabus
Instructor: Sergiu Dascalu
Department of Computer Science and Engineering
August 30, 2011
1
The Instructor
The Students
The Course
The Texts
Initial Pointers
Grading Scheme
Policies
A Look Ahead
Tentative Schedule
2
Instructor: Sergiu Dascalu
Room SEM-236
Telephone 784-4613
Office hours:
TUE 11:00 am – 12:30 pm or by appointment or chance
3
Registration as of today:
CS 425: 42 students (35 + 7)
Prerequisites:
CS 446 Operating Systems, CH 201, ENG 102
4
Catalog description:
Lecture + Lab: 3 + 0; Credit(s): 3
Requirements specifications, structured analysis,
modeling, top down design, testability,maintainability, portability, verification and validation,modification, configuration, management, reliability,efficiency, complexity, compatibility, modularity,interfacing, hardware and language issues. (Majorcapstone course.) Pre-requisite: CS446
Outline:
This course covers the software development process,from requirements elicitation and analysis, throughspecification and design, to implementation,integration, testing, and evolution (maintenance).
[continued on next page]
5
Outline [cont’d]: A variety of concepts, principles,techniques, and tools are presented, covering topics suchas software processes, project management, peoplemanagement, software requirements, system models,architectural and detailed design, user interface design,programming practices, verification and validation, andsoftware evolution.
Although the emphasis will be on modern, object-oriented approaches some more traditional, structuredsoftware engineering techniques will also be discussed.
6
Textbook:
[SE-9] Ian Sommerville, Software Engineering, 9thEdition, Addison-Wesley, 2011.
Lecture notes:
Presentations by the instructor
Notes you take in the classroom
Additional material as indicated later by theinstructor
7
Ian Sommerville’s web-page for the 9th edition of hisSoftware Engineering book:
More will be indicated later
8
Tentative (slight modifications are possible):
Individual assignments 15%
Team project 35%
Midterm test 15%
Final exam (comprehensive) 30%
Class participation 5%
TOTAL 100%
Note that there are no make-up tests orhomework in this course
Poor class participation will impactsignificantly your grade, beyond 5%
9
Passing conditions (all must be met):
50% overall &
50% in tests (midterm test and final exam) &
50% in assignments, project, class participation
For grade A: at least 90% overall and at least 90%in class participation
10
In addition, for honors students a technicalessay is required, worth 10%. In this essay youmust obtain at least 50% (in addition to thepassing conditions on the previous page). Thus,honors students will have a maximum possibleof 110 points for the course.
11
![Grading Scale [regular]](data/images/img14.png){kind=small}
Numerical-letter grade correspondence (regular)
A90 -100 [maximum 100]
A-87 - 89
B+83 - 85
B78 - 82
B-74 - 77
C+70 - 73
C65 - 69
C-61 - 64
D+57 - 60
D54 - 56
D-50 - 53
F< 50
12
![Grading Scale [honors]](data/images/img15.png){kind=small}
Numerical-letter grade correspondence (honors)
A100 – 110 [maximum 110]
A-96 - 99
B+91 - 95
B85 - 90
B-80 - 84
C+76 - 79
C71 - 75
C-67 - 70
D+63 - 66
D59 - 62
D-55 - 58
F< 55
13
If you have a disability for which you needto request accommodations, pleasecontact as soon as possible the instructorsor the Disability Resource Center(Thompson Student Services - 107).
14
Late submission policy:
Maximum 2 late days per assignment/projectdeliverable
Each late day penalized with 10%
No subdivision of late days
Example: a 90/100 worth assignment gets 81/100if one day late (90*0.9 = 81) or 72/100 if two dayslate (90*0.8 = 72)
15
Legal notices on the world-wide web: Read andcomply with accompanying legal notices ofdownloadable material
Specify references used in assignments andproject
Do not plagiarize (see next slide)
16
Plagiarism and cheating: Will not be tolerated.Please read the policies of University ofNevada, Reno regarding academic dishonesty:
17
The 4 parts of Ian Sommerville’s textbook onSoftware Engineering (9th edition):
Introduction to Software Engineering
▪Ex: software processes, agile software development
Dependability and Security
▪Ex: socio-technical systems, dependability and security
Advanced Software Engineering
▪Ex: software reuse, component-based software engineering
Software Management
▪Ex: project management, project planning
18
Week #
Dates (M, W)
Contents
1
Aug 30, Sep 02
Lectures (Introduction)
2
Sep 06, 08
Lectures, Invited talks, A#1 given
3
Sep 13, 15
Lectures, Invited talks, A#2 given
A#1 due
4
Sep 20, 22
Lectures, Invited talks, A#3 given
A#2 due
5
Sep 27, 29
Lectures, Project meetings, Project P#1 given
A#3 due
6
Oct 04, 06
Project meetings
7
Oct 11, 13
Lectures, Project P#2 given
P#1 due
19
8
Oct 18, 20
Lectures, Technical essay given (TESS)
9
Oct 25, 27
Lecture, Project P#3 given
Midterm [10/27]
10
Nov 01, 03
Lecture
Project P#2 due
11
Nov 08, 10
Lectures, Project P#4 given
12
Nov 15, 17
Lecture, Invited talk
Project P#3 due
13
Nov 22, -
Lectures
14
Nov 29, Dec 01
Lectures, [Project presentations]
Technical essay (TESS) due
15
Dec 06, Dec 08
Lectures, [Project presentations]
16
Dec 13, -
Project P#4 due, Demo (12/12 & 13)
Final EXAM
20
Summary of course objectives:
Comprehensive study of software engineeringconcepts, principles, and techniques
Extensive coverage of the phases and activities of thesoftware process
Study of several advanced software engineering topics
Practical software development work within theframework of integrated development environments
21
Our intentions/expectations:
Provide guidance in the complex softwareengineering spectrum
Help you be better prepared for practical softwaredevelopment work
Open perspectives on software engineering
Hope that you will both work hard and enjoy thework in this course
22
Your intentions/expectations?
In what ways do you think this course couldhelp your professional development?
What topics are you most interested in?
What suggestions do you have for theinstructors and the course?
23
New edition of the textbook (9th), substantiallydifferent from previous editions
Only one midterm instead of two
More emphasis on project prototyping
Hopefully, more project topics from industry
Possibly, one short class presentation on project
24
THU Sep 01:
Class on the need for software engineering &short videos with well-known SE researchers andpractitioners
Students’ introduction (be prepared to talk 1minute or so about yourself)
25