CS 425 Software Engineering Fall 2010 Course Syllabus Instructor: Sergiu Dascalu Department of Computer Science and Engineering August 23, 2010

Outline The Instructor & the TAs The Students The Course The Texts Initial Pointers Grading Scheme Policies A Look Ahead Tentative Schedule

The Instructor & TAs Instructor: Sergiu Dascalu TAs (volunteer): Room SEM-236 Telephone 784-4613 E-mail dascalus@cse.unr.edu Web-site www.cse.unr.edu/~dascalus Office hours: TUE 3:30 – 4:30 pm WED 5:30 – 6:30 pm or by appointment or chance TAs (volunteer): Muhanna Muhanna www.cse.unr.edu/~muhanna Sohei Okamoto www.soheiokamoto.com

The Students Registration as of today: Prerequisites: CS 425: 35 students Prerequisites: CS 446 Operating Systems, CH 201, ENG 102

The Course. Catalog description: Outline: 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]

.The Course 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.

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

Initial WWW Pointers Ian Sommerville’s web-page for the 9th edition of his Software Engineering book: http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/ The Software Engineering Institute, at Carnegie Mellon University: www.sei.cmu.edu The Object Management Group web-site: www.omg.org More will be indicated later

Grading Scheme.. Tentative (slight modifications are possible): Individual assignments 12% Team project 38% 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%

.Grading Scheme. 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

..Grading Scheme 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.

Grading Scale [regular] Numerical-letter grade correspondence (regular) A 90 -100 [maximum 100] A- 87 - 90 B+ 83 - 86 B 78 - 82 B- 74 - 77 C+ 70 - 73 C 65 - 69 C- 61 - 64 D+ 57 - 60 D 54 - 56 D- 50 - 53 F < 50

Grading Scale [honors] Numerical-letter grade correspondence (honors) A 100 – 110 [maximum 110] A- 96 - 99 B+ 91 - 95 B 85 - 90 B- 80 - 84 C+ 76 - 79 C 71 - 75 C- 67 - 70 D+ 63 - 66 D 59 - 62 D- 55 - 58 F < 55

Disability statement 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).

Policies.. 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)

.Policies. 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)

..Policies Plagiarism and cheating: Will not be tolerated. Please read the policies of University of Nevada, Reno regarding academic dishonesty: www.unr.edu/stsv/acdispol.html

A Look Ahead….. The 4 parts of Ian Sommerville’s textbook on Software Engineering (9th edition): Introduction to Software Engineering Ex: software processes, agile software development Dependability and Security Ex: sociotechnical systems, dependability and security Advanced Software Engineering Ex: software reuse, component-based software engineering Software Management Ex: project management, project planning

.A Look Ahead: tentative schedule…. Week # Dates (M, W) Contents 1 Aug 23, 25 Lectures (Introduction) 2 Aug 30, Sep 01 Lectures, A#1 given 3 Sep --, 08 Lecture, A#2 given A#1 due 4 Sep 13, 15 Lectures, Invited talks 5 Sep 20, 22 Lectures, Invited talks, Project P#1 given A#2 due 6 Sep 27, 29 Project meetings 7 Oct 4, 6 Lectures, Project P#2 given P#1 due

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

…A Look Ahead.. 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

….A Look Ahead. 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

…..A Look Ahead 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?

Course updates New edition of the textbook (9th), 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

Next class WED Aug 25: 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)