1. 1 CS 425 / CS 625 Software Engineering Fall 2007 Course Syllabus August 27, 2007

2. 2 Outline The instructor The students The course The texts Initial web pointers Grading scheme Policies A look ahead Tentative schedule

3. 3 The Instructor Sergiu Dascalu –Room SEM-236 –Telephone 784-4613 –E-mail dascalus@cse.unr.edudascalus@cse.unr.edu –Web-site www.cse.unr.edu/~dascaluswww.cse.unr.edu/~dascalus –Office hours: MW 3:00 – 4:00 pm or by appointment or chance

4. 4 The Students Registration as of today: CS 425: 23 students CS 625: 4 students Prerequisites: CS 446 Operating Systems

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

6. 6.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.

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

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

9. 9 Grading Scheme.. Tentative (slight modifications are possible): –Individual assignments (2)12% –Team project (4 parts and demo)38% –Midterm tests (2)20% –Final exam (comprehensive) 24% –Class participation 6%  TOTAL 100% Note that there are no make-up tests or homework in this course

10. 10.Grading Scheme. Passing conditions (all must be met): –50% overall & –50% in tests (midterm tests and final exam) & –50% in assignments, project parts 1-3, class participation & –50% in project implementation and demo For grade A: at least 90% overall and at least 90% in class participation

11. 11..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. Also, for graduate and honors students there will be at least an additional question in each test and final exam.

12. 12 Grading Scale [regular] Numerical-letter grade correspondence (regular) –A90 -100 [maximum 100] –A-86 - 89 –B+83 - 85 –B77 - 82 –B-73 - 76 –C+70 - 72 –C64 - 69 –C-61 - 63 –D+58 - 60 –D54 - 57 –D-50 - 53 –F< 50

13. 13 Grading Scale [grad/honors] Numerical-letter grade correspondence (grad/honors) –A 99 – 110 [maximum 110] –A-95 - 98 –B+91 - 94 –B85 - 90 –B-80 - 84 –C+77 - 79 –C71 - 76 –C-67 - 70 –D+64 - 66 –D60 - 63 –D-55 - 59 –F< 55

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

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

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

17. 17..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

18. 18 A Look Ahead….. The 7 parts of Ian Sommerville’s textbook on Software Engineering (8 th edition): –Overview –Requirements –Design –Critical Systems –Verification and Validation –Managing People –Emerging Technologies

19. 19.A Look Ahead: tentative schedule…. Week #Dates (M, W)Contents 1Aug 27, 29Lectures [Overview] 2-, Sep 5Lecture [Overview], A#1 given 3Sep 10, 12 Lecture [Overview], Invited talk [IT] 4Sep 17, 19 Lectures [Overview, Requirements], A#2 given A#1 due 5Sep 24, 26Lectures [Requirements], Project P#1 given 6Oct 1, 3 Lecture [Requirements], Invited talk [IT] A#2 due 7Oct 8, 10 Lectures [Design], Project P#2 given Project P#1 due

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

21. 21 …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 and agile methods –Practical software development work within the framework of integrated development environments

22. 22 ….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

23. 23 …..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 instructor and the course?