1 CS691z / CS 791z Topics on Software Engineering Spring 2007 Course Syllabus (tentative) January 23, 2007

2 Outline The Instructor The Instructor The Students The Students The Course The Course The Texts & Initial WWW Pointers The Texts & Initial WWW Pointers Grading Scheme: CS691z/791z & Scale Grading Scheme: CS691z/791z & Scale Policies Policies Summary of Course Objectives Summary of Course Objectives A Look Ahead A Look Ahead

3 The Instructor. Sergiu Dascalu Room SEM-236 Telephone Web-site Office hours:   T 4:00 - 5:00 pm; R 5:00 – 6:00 pm or by appointment or chance

4.The Instructor Sergiu Dascalu PhD, Dalhousie U., Halifax, NS, Canada, 2001 Faculty member at UNR since July 2002 Lecturer & RA at Dalhousie University, (software engineering focus) Teaching and research at the University Politehnica Bucharest, Romania, (RTS focus) Consultant for software development companies in Canada and Romania

5 The Students Registered as of today: 8 in CS691z + 4 in CS791z Prerequisite: CS 425 Software Engineering or Instructor’s approval

6 The Course. Classroom: Classroom: LP-104, TR 2:30 - 3:45 pm This course explores research and development topics on software engineering, encompassing principles, methods, and tools. Areas of research include software processes, requirements analysis and specification, design, prototyping, implementation, validation and verification, evolution, documentation, project management, UML-based modeling, development environments, and domain-specific applications. Outline : This course explores research and development topics on software engineering, encompassing principles, methods, and tools. Areas of research include software processes, requirements analysis and specification, design, prototyping, implementation, validation and verification, evolution, documentation, project management, UML-based modeling, development environments, and domain-specific applications.

7.The Course Outline [continued] : The course will allow the students to broaden their knowledge of software engineering concepts, principles, techniques and tools, study relevant research publications in the field, prepare and present a high quality software engineering project and, based on this project, write a paper that could be submitted to a scientific conference.

8 The Texts. Required textbooks [to be confirmed]: Albert Endres, Dieter Rombach, A Handbook of Software and Systems Engineering: Empirical Observations, Laws, and Theories, Pearson Addison- Wesley, ISBN:

9.The Texts Recommended textbooks (initial): Ian Sommerville, Software Engineering, 8th Ed., Addison- Wesley, Jim Arlow and Ila Neustadt, UML and the Unified Process: Practical Object-Oriented Analysis and Design, Addison Wesley, 2002.ISBN: Jim Arlow and Ila Neustadt, UML and the Unified Process: Practical Object-Oriented Analysis and Design, Addison Wesley, 2002.ISBN: Lecture notes: Lecture notes: Presentations by the instructor Presentations by the instructor Notes you take in the classroom Notes you take in the classroom Additional material (papers, tutorials, etc.) that will be indicated later by the instructor Additional material (papers, tutorials, etc.) that will be indicated later by the instructor

10 Initial WWW Pointers IEEE’s Digital Library, via IEEE’s Digital Library, via ACM Digital Library, via ACM Digital Library, via The Software Engineering Institute, at Carnegie Mellon University, The Software Engineering Institute, at Carnegie Mellon University, IEEE Computer Society’s Technical Council on Software Engineering, IEEE Computer Society’s Technical Council on Software Engineering, The Object Management Group, The Object Management Group, IBM / Rational Software, IBM / Rational Software, More will be indicated later More will be indicated later

11 Grading Scheme.. Grading Scheme (subject to slight modifications): Grading Scheme (subject to slight modifications): Assignments: A1, 2, [3]10% Presentations: PRES1, [2], 3, 4 15% Midterm test: EXAM 20% Project: P1, 2, 3, 430% Paper:DRAFT, PPR20% Class participation: PART* 5% [* assumes good presence; a large number of absences will affect the grade much more significantly] TOTAL 100%

12.Grading Scheme. CS791Z versus CS691Z CS791Z versus CS691Z In CS791Z there will be: One more assignment One more presentation Longer paper – by 1 page, 2-column IEEE format [possibly] one more question in the midterm exam

13..Grading Scheme Passing conditions (): Passing conditions (all must be met): 50% overall & 50% overall & 50% in test & 50% in test & 50% in project and paper & 50% in project and paper & 50% in assignments, presentations, and class participation 50% in assignments, presentations, and class participation For grade A: at least 90% overall, at least 90% in class participation and at least 60% in test For grade A: at least 90% overall, at least 90% in class participation and at least 60% in test Note that there are no make-up tests or homework in this course

14 Grading Scale Numerical-letter grade correspondence Numerical-letter grade correspondence A A A A B B B B B B C C C C C C D D D D D D F< 50 F< 50

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 (e.g. in hours) No late days for presentations and test 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.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 Specify references used Do not plagiarize (see next slide) Do not plagiarize (see next slide)

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:

18 Summary of Course Objectives Course objectives: Course objectives: Extension of SE knowledge, in particular of software process phases and modeling notations Extension of SE knowledge, in particular of software process phases and modeling notations Study and presentation of relevant research publications Study and presentation of relevant research publications Development of a high quality software project Development of a high quality software project Writing a paper that can be submitted to a scientific conference Writing a paper that can be submitted to a scientific conference

19 A Look Ahead. My intentions & expectations: My intentions & expectations: Provide guidance in the SE spectrum Provide guidance in the SE spectrum Help you be better prepared for research and development in SE Help you be better prepared for research and development in SE Guide you in writing an SE research paper Guide you in writing an SE research paper Hope that you will both work hard and enjoy your work in this course Hope that you will both work hard and enjoy your work in this course

20.A Look Ahead Your intentions & expectations: Your intentions & expectations: Why do you take the course? Why do you take the course? In what ways do you think this course could help your professional development? In what ways do you think this course could help your professional development? What is your experience so far with SE? What is your experience so far with SE? What topics are you interested in? What topics are you interested in? What suggestions do you have for the instructor? What suggestions do you have for the instructor?

21 Tentative schedule. WeekClass DatesContents 1Jan 23, 25 Course syllabus: course objectives, outline, organization Students’ introduction 2Jan 30, Feb 1 Lectures by the instructor Draw for presentations’ order 3Feb 6, 8 Lectures by the instructor Project teams set up (Feb 8) A#1 due – SE tool (Feb 9) 4Feb 13, 15 Individual project meetings with the instructor 5Feb 20, 22 Presentations by students based on A#1 (PRES-1) A#2 due – Background (Feb 19) 6Feb 27, Mar 1 Presentations by students based on A#1 (PRES-1) Project concept due (P1- Feb 26) 7Mar 6, 8 A#3 due, CS791z only, textbook presentation (Mar 5) Presentations by students based on A#3 (PRES-2, text, CS791z only)

22.Tentative schedule WeekClass DatesContents 8Mat 13, 15 Lectures by the instructor Project specification due (P2 - Mar 16) 9Mar 20, 22 Spring break, no classes 10Mar 27, 29 Lectures by the instructor Project design due (P3 - Mar 30) 11Apr 3, 5 Invited talk & Lecture by the instructor, recap for midterm Paper draft due (DRAFT – Apr 6) 12Apr 10, 12 Lecture by the instructor Midterm exam (TEST - April 12) 13Apr 17, 19 Presentations by students - project (PRES-3) 14Apr 23, 25 Presentations by students – additional book reading (PRES-4) 15Apr 30, May 2 Presentations by students - additional book reading (PRES-4) 16May 7 Project implementation (demos) due (P4 - May 7) Paper due (PPR - May 14)