1. 1 CS 790z Seminar on Software Engineering Fall 2010 Course Syllabus (tentative) August 23, 2010

2. 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 & Scale Grading Scheme & Scale Policies Policies Summary of Course Objectives Summary of Course Objectives A Look Ahead A Look Ahead

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:   T 3:30 - 4:30 pm; W 5:30 – 6:30 pm or by appointment or chance

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

5. 5 The Students Registered as of today: 18 students Prerequisite: CS 425 Software Engineering or Instructor’s approval

6. 6 The Course. Classroom: Classroom: CB-111, MW 4:00 - 5:15 pm This course explores research and development topics in software engineering, with emphasis on software architecture. The research and study focus will be on concepts, principles, methods, and tools pertaining to architecting software systems. Examples include, but are not limited to, architectural styles, specifying requirements, design principles, modeling languages and architectural descriptions, software architecture quality, documenting software architecture, architecting complex systems, and the role of architects. Outline : This course explores research and development topics in software engineering, with emphasis on software architecture. The research and study focus will be on concepts, principles, methods, and tools pertaining to architecting software systems. Examples include, but are not limited to, architectural styles, specifying requirements, design principles, modeling languages and architectural descriptions, software architecture quality, documenting software architecture, architecting complex systems, and the role of architects.

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

8. 8 The Texts. Required textbook [to be confirmed!]: Taylor, R.N., Medvidovic, N., and Dashofy, E.M., Software Architecture: Foundations, Theory, and Practice, Wiley, 2009. ISBN: 978-0470167748

9. 9.The Texts Recommended textbooks (initial): Peter Eeles and Peter Peter Cripps, The Process of Software Architecting, Addison-Wesley, 2010. ISBN: 0-321- 35748-5. Ian Sommerville, Software Engineering, 9th Ed., Addison- Wesley, 2010. Jim Arlow and Ila Neustadt, UML and the Unified Process: Practical Object-Oriented Analysis and Design, 2 nd Ed., Addison Wesley, 2005. Jim Arlow and Ila Neustadt, UML and the Unified Process: Practical Object-Oriented Analysis and Design, 2 nd Ed., Addison Wesley, 2005. 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. 10 Initial WWW Pointers IEEE’s Digital Library, via www.ieee.org IEEE’s Digital Library, via www.ieee.orgwww.ieee.org ACM Digital Library, via www.acm.org ACM Digital Library, via www.acm.orgwww.acm.org 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, www.omg.org The Object Management Group, www.omg.orgwww.omg.org IBM/Rational Software, www.rational.com IBM/Rational Software, www.rational.comwww.rational.com More will be indicated later More will be indicated later

11. 11 Grading Scheme. Grading Scheme (subject to modifications): Grading Scheme (subject to modifications): Assignments: A 1, 2, 315% Presentations: PRES 1, 2, 3 10% Midterm test: TEST 25% Project: P 1, 2, 3, 430% Paper:DRAFT, PAPER15% Class participation: PART* 5% [* assumes very good presence; a large number of absences will affect the grade much more significantly] TOTAL 100%

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

13. 13 Grading Scale Numerical-letter grade correspondence Numerical-letter grade correspondence A90 -100 A90 -100 A-87 - 89 A-87 - 89 B+84 - 86 B+84 - 86 B79 - 83 B79 - 83 B-75 - 78 B-75 - 78 C+72 - 74 C+72 - 74 C68 - 71 C68 - 71 C-65 - 67 C-65 - 67 D+61 - 64 D+61 - 64 D56 - 60 D56 - 60 D-50 - 55 D-50 - 55 F< 50 F< 50

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

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

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

17. 17 Summary of Course Objectives Course objectives: Course objectives: Extension of SE knowledge, in particular of software architecture concepts, principles, methods, and tools Extension of SE knowledge, in particular of software architecture concepts, principles, methods, and tools 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

18. 18 A Look Ahead. My intentions & expectations: My intentions & expectations: Provide guidance in the SE spectrum; widen perspectives on SE research Provide guidance in the SE spectrum; widen perspectives on SE research 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

19. 19.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?

20. 20 Tentative schedule. WeekClass DatesContents 1Aug 23, 25 Course syllabus Students’ introduction 2Aug 30, Sep 1 Lectures by the instructor, A#1 given Draw for presentations’ order 3-, Sep 08 Lecture by the instructor, A#2 given Project teams set up (Sep 10) A#1 due 4Sep 13, 15 Individual project meetings with the instructor 5Sep 20, 22 Lectures by the instructor, P#1 given, PRES#1 guidelines A#2 due 6Sep 27, 29 Presentations by students (PRES#1), P#2 given Project concept due (P#1) 7Oct 04, 06 Presentations by students (PRES#1)

21. 21.Tentative schedule WeekClass DatesContents 8Oct 11, 13 Lectures by the instructor, P#3 given Project specification due (P#2) 9Oct 18, 20 Presentations by students (PRES#1), Paper DRAFT given 10Oct 25, 27 Lectures by the instructor, P#4 given Project design due (P#3) 11Nov 01, 03 Lectures by the instructor, A#3/PRES 2 guidelines Paper DRAFT due 12Nov 08, 10 Lecture by the instructor, PAPER given Midterm exam (TEST - Nov 10) 13Nov 15, 17 Presentations by students - additional readings (PRES#2) 14Nov 22, 24 Presentations by students - additional readings (PRES#2) 15Nov 29, Dec 1 Presentations by students - project (PRES#3) 16Dec 06, - Project implementation (demos) due (P#4 - Dec 08 & 09) Paper due (PAPER - Dec 14)

22. 22 Next class Students’ introduction: be prepared to talk 2-3 minutes about yourself; you are encouraged to have few slides prepared. Students’ introduction: be prepared to talk 2-3 minutes about yourself; you are encouraged to have few slides prepared. More on the need for software engineering & short videos with well-known SE researchers and practitioners More on the need for software engineering & short videos with well-known SE researchers and practitioners