1. 1 CS 425 / CS 625 Software Engineering Fall 2008 Course Syllabus August 25, 2008

2. 2 Outline The Instructor & the TA The Instructor & the TA The Students The Students The Course The Course The Texts The Texts Initial WWW Pointers Initial WWW Pointers Grading Scheme Grading Scheme Policies Policies A Look Ahead A Look Ahead Tentative Schedule Tentative Schedule

3. 3 The Instructor & TA Instructor: Sergiu Dascalu Instructor: Sergiu Dascalu –Room SEM-236 –Telephone 784-4613 –E-mail dascalus@cse.unr.edu dascalus@cse.unr.edu –Web-site www.cse.unr.edu/~dascalus www.cse.unr.edu/~dascalus –Office hours:  TUE 3:00 – 4:00 pm and WED 5:30 – 6:30 pm or by appointment or chance TA (partial): Muhanna Muhanna, PhD candidate TA (partial): Muhanna Muhanna, PhD candidate –Web-site www.cse.unr.edu/~muhanna www.cse.unr.edu/~muhanna

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

5. 5 The Course. Catalog description: 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 : 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]: 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: Textbook: [SE-8] Ian Sommerville, Software Engineering, 8 th Edition, Addison-Wesley, 2006. Lecture notes: 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: 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 http://www.cs.st- andrews.ac.uk/~ifs/Books/SE8/index.html The Software Engineering Institute, at Carnegie Mellon University: www.sei.cmu.edu The Software Engineering Institute, at Carnegie Mellon University: www.sei.cmu.eduwww.sei.cmu.edu The Object Management Group web-site: www.omg.com The Object Management Group web-site: www.omg.com www.omg.com More will be indicated later More will be indicated later

9. 9 Grading Scheme.. Tentative (slight modifications are possible): Tentative (slight modifications are possible): – –Individual assignments 12% – –Team project 40% – –Midterm test 14% – –Final exam (comprehensive) 28% – –Class participation 6%   TOTAL 100% Note that there are no make-up tests or homework in this course Poor class participation will impact significantly your grade, beyond 6% Poor class participation will impact significantly your grade, beyond 6%

10. 10.Grading Scheme. Passing conditions (): 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 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. 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.

12. 12 Grading Scale [regular] Numerical-letter grade correspondence (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) 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: 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 Legal notices on the world-wide web: Read and comply with accompanying legal notices of downloadable material Specify references used in assignments and project Specify references used in assignments and project Do not plagiarize (see next slide) 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: 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): 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 25, 27Lectures [Overview] 2-, Sep 3Lecture [Overview], A#1 given 3Sep 8, 10Lectures [Overview] 4Sep 15, 17 Lectures [Overview, Requirements], A#2 given A#1 due 5Sep 22, 24Lectures [Requirements], Invited talk [IT] 6Sep 29 Oct 1 Lecture [Requirements], Project P#1 given A#2 due 7Oct 6, 8Lectures [Analysis], Technical essay given [TESS]

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

21. 21 …A Look Ahead.. Summary of course objectives: 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

22. 22 ….A Look Ahead. Our intentions/expectations: 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? 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?

24. 24 New in 2008/2009 Only one midterm instead of two Only one midterm instead of two In project part #3, focus on analysis instead of design In project part #3, focus on analysis instead of design More emphasis on project prototyping More emphasis on project prototyping Hopefully, more project topics from industry Hopefully, more project topics from industry Possibly one project team will collaborate with students in Geneva, SUI Possibly one project team will collaborate with students in Geneva, SUI Likely, one short team project (class presentation) Likely, one short team project (class presentation)

25. 25 Next classes WED Aug 27: class on the need for software engineering & short videos with well-known SE researchers and practitioners WED Aug 27: class on the need for software engineering & short videos with well-known SE researchers and practitioners WED Sep 03: students’ introduction (be prepared to talk about 1 minute about yourself) & Chapter 1: Introduction WED Sep 03: students’ introduction (be prepared to talk about 1 minute about yourself) & Chapter 1: Introduction