Fall 2011 Course Syllabus Instructor: Sergiu Dascalu Department of Computer Science and Engineering August 30,

 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   Web-site  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. (Major capstone course.) Pre-requisite: CS446  Outline: This course covers the software development process, from requirements elicitation and analysis, through specification 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 such as software processes, project management, people management, software requirements, system models, architectural and detailed design, user interface design, programming practices, verification and validation, and software evolution. Although the emphasis will be on modern, object- oriented approaches some more traditional, structured software engineering techniques will also be discussed. 6

 Textbook: [SE-9] Ian Sommerville, Software Engineering, 9 th Edition, Addison-Wesley,  Lecture notes:  Presentations by the instructor  Notes you take in the classroom  Additional material as indicated later by the instructor 7

 Ian Sommerville’s web-page for the 9 th edition of his Software Engineering book:  The Software Engineering Institute, at Carnegie Mellon University:  The Object Management Group web-site:  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 or homework in this course  Poor class participation will impact significantly 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 technical essay is required, worth 10%. In this essay you must obtain at least 50% (in addition to the passing conditions on the previous page). Thus, honors students will have a maximum possible of 110 points for the course. 11

 Numerical-letter grade correspondence (regular)  A [maximum 100]  A  B  B  B  C  C  C  D  D  D  F< 50 12

 Numerical-letter grade correspondence (honors)  A100 – 110 [maximum 110]  A  B  B  B  C  C  C  D  D  D  F< 55 13

 If you have a disability for which you need to request accommodations, please contact as soon as possible the instructors or the Disability Resource Center (Thompson Student Services - 107). 14

 Late submission policy:  Maximum 2 late days per assignment/project deliverable  Each late day penalized with 10%  No subdivision of late days  Example: a 90/100 worth assignment gets 81/100 if one day late (90*0.9 = 81) or 72/100 if two days late (90*0.8 = 72) 15

 Legal notices on the world-wide web: Read and comply with accompanying legal notices of downloadable material  Specify references used in assignments and project  Do not plagiarize (see next slide) 16

 Plagiarism and cheating: Will not be tolerated. Please read the policies of University of Nevada, Reno regarding academic dishonesty: 17

 The 4 parts of Ian Sommerville’s textbook on Software Engineering (9 th 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 1Aug 30, Sep 02Lectures (Introduction) 2Sep 06, 08Lectures, Invited talks, A#1 given 3Sep 13, 15 Lectures, Invited talks, A#2 given A#1 due 4Sep 20, 22 Lectures, Invited talks, A#3 given A#2 due 5Sep 27, 29 Lectures, Project meetings, Project P#1 given A#3 due 6Oct 04, 06Project meetings 7Oct 11, 13 Lectures, Project P#2 given P#1 due 19

8Oct 18, 20Lectures, Technical essay given (TESS) 9Oct 25, 27 Lecture, Project P#3 given Midterm [10/27] 10Nov 01, 03 Lecture Project P#2 due 11Nov 08, 10Lectures, Project P#4 given 12Nov 15, 17 Lecture, Invited talk Project P#3 due 13Nov 22, -Lectures 14Nov 29, Dec 01 Lectures, [Project presentations] Technical essay (TESS) due 15Dec 06, Dec 08Lectures, [Project presentations] 16Dec 13, - Project P#4 due, Demo (12/12 & 13) Final EXAM 20

 Summary of course objectives:  Comprehensive study of software engineering concepts, principles, and techniques  Extensive coverage of the phases and activities of the software process  Study of several advanced software engineering topics  Practical software development work within the framework of integrated development environments 21

 Our intentions/expectations:  Provide guidance in the complex software engineering spectrum  Help you be better prepared for practical software development work  Open perspectives on software engineering  Hope that you will both work hard and enjoy the work in this course 22

 Your intentions/expectations?  In what ways do you think this course could help your professional development?  What topics are you most interested in?  What suggestions do you have for the instructors and the course? 23

 New edition of the textbook (9 th ), substantially different 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 and practitioners  Students’ introduction (be prepared to talk 1 minute or so about yourself) 25