CS 425 / CS 625 Software Engineering Fall 2005 Course Syllabus August 29, 2005

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

The Instructors Sergiu Dascalu Room SEM-236 Telephone 784-4613 E-mail dascalus@cse.unr.edu Web-site www.cse.unr.edu/~dascalus Office hours: Tuesday and Wednesday 2:30 – 3:30 pm or by appointment or chance

The Students Registration as of today: Prerequisites: 425: 27 students CS311 Challenges and Social Aspects in Computing and Senior standing

The Course. 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: ISBN: 0-321-21026-3 Lecture notes: [SE-7] Ian Sommerville, Software Engineering, 7th Edition, Addison-Wesley, 2004. ISBN: 0-321-21026-3 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 7th edition of his Software Engineering book: www.software-engin.com The Software Engineering Institute, at Carnegie Mellon University: www.sei.cmu.edu The Object Management Group web-site: www.omg.com More will be indicated later

Grading Scheme.. Tentative (slight modifications are possible): Individual assignments 12% Team project 35% Midterm tests 22% Final exam (comprehensive) 26% Class participation 5% TOTAL 100% Note that there are no make-up tests or homework in this course

.Grading Scheme. Passing conditions (all must be met): 50% overall & 50% in tests (midterm tests 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 graduate and 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, graduate students and 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- 86 - 89 B+ 83 - 85 B 77 - 82 B- 73 - 76 C+ 70 - 72 C 64 - 69 C- 61 - 63 D+ 58 - 60 D 54 - 57 D- 50 - 53 F < 50

Grading Scale [grad/honors] Numerical-letter grade correspondence (grad/honors) A 99 – 110 [maximum 110] A- 95 - 98 B+ 91 - 94 B 85 - 90 B- 80 - 84 C+ 77 - 79 C 71 - 76 C- 67 - 70 D+ 64 - 66 D 60 - 63 D- 55 - 59 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 6 parts of Ian Sommerville’s textbook on Software Engineering (7th edition): Overview Requirements Design Critical Systems Verification and Validation Managing People

.A Look Ahead: tentative schedule…. Week # Dates (M, W) Contents 1 Aug 29, 31 Lectures [Overview] 2 -, Sep 7 Invited Talk [IT], A#1 given 3 Sep 12, 14 4 Sep 19, 21 Lectures [Overview, Requirements], A#2 given A#1 due 5 Sep 26, 28 Lectures [Requirements] 6 Oct 3, 5 Lectures [Requirements], Project P#1 given A#2 due 7 Oct 10, 12 Lectures [Design], Technical essay given

..A Look Ahead: tentative schedule… 8 Oct 17, 19 Lectures [Design] Midterm T#1 (10/19) 9 Oct 24, 26 Lectures [Design], Project P#2 given Project P#1 due 10 Oct 31, Nov 2 Lecture [Design], Project P#3 given 11 Nov 7, 9 Lecture [Critical Systems], Invited talk [IT] Project P#2 due 12 Nov 14, 16 Lecture [Verification & Validation] 13 Nov 21, 23 Lecture [Verif. & Validation] Midterm T#2 (11/21) 14 Nov 28, 30 Lecture [Managing People], Invited talk [IT] 15 Dec 5, 7 Lecture [Managing People] Technical essay (TESS) due (12/12) 16 Dec 12, - Project P#3 due, Demo (12/12) Final EXAM (12/19)

…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 such as real-time software designs, agile methods, and critical systems 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?