1. Course Syllabus January 24, 2012 CS 426/CPE 426 Senior Projects in Computer Science/Computer Engineering University of Nevada, Reno Department of Computer Science & Engineering

2. 2  The Instructor  The Students  The Course: CS/CPE 426  The Texts  Grading Scheme & Grading Scale  Policies  Tentative Schedule

3. 3  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 11:00 am - 12:00 pm or by appointment or chance

4. 4 Registered as of today: CS 426: 38 students CPE 426: 6 students Prerequisite: CS 425 Software Engineering

5. 5  Classroom: AB-109, TR 9:30 - 10:45 am  Outline: A continuation of CS 425 Software Engineering, this capstone course emphasizes team collaboration and application of modern engineering approaches to software construction. The development by each team of an original, industry-strength software product is the main objective of the course.

6. 6  Outline [cont’d]: The instructor will present lectures on the Unified Modeling Language (UML) and its application to object-oriented analysis and design and the teams will report on their progress by giving presentations and submitting deliverables related to the project.

7. 7  Outline [cont’d]: The teams will deliver and present project work at the following stages: topic proposal and software specification (concept and requirements), design (model), and implemented software (in-progress and final product). At the beginning of the semester the teams will set up project websites, which will be updated regularly to reflect the progress of the projects. At the end of the semester there will be a public Senior Projects Workshop with project presentations, video clips, demos, and posters.

8. 8  Classroom: AB-201, MW 9:30 - 10:45 am  Outline: This capstone course emphasizes team collaboration and application of modern engineering approaches to building computer-based systems that include a significant hardware component. The development by each team of an original, industry-strength project (software + hardware system) is the main objective of the course. Projects must be designed and implemented in the context of realistic engineering constraints and must follow effective engineering standards and practices.

9. 9  Outline [cont’d]: The instructor will present lectures on the Unified Modeling Language (UML) and its application to object-oriented analysis and design and the teams will report on their progress by giving presentations and submitting deliverables related to the project.

10. 10  Outline [cont’d]: The teams will deliver and present project work at the following stages: topic proposal and software specification (concept and requirements), design (model), and implemented software (in-progress and final product). At the beginning of the semester the teams will set up project websites, which will be updated regularly to reflect the progress of the projects. At the end of the semester there will be a public Senior Projects Workshop with project presentations, video clips, demos, and posters.

11. 11  Required textbook: [Arlow’05] Jim Arlow and Ila Neustadt, "UML and the Unified Process: Practical Object-Oriented Analysis and Design," Second edition, Addison Wesley, 2005.  Recommended textbook: [Heim’07] Steven Heim, The Resonant Interface: HCI Foundations for Interaction Design, Addison-Wesley, 2007;

12. 12  Additional readings: For each individual project an additional book (project domain book) will be consulted, together with at least four reference articles (journal papers, conference papers, or web publications). This extra reading will be assigned shortly after the project topics will be defined by the teams. The project domain book and the articles will be used as references in presentations and project deliverables.

13. 13  Course website: www.cs.unr.edu/~dascalus/sp2012.htmlwww.cs.unr.edu/~dascalus/sp2012.html  The Object Management Group: www.omg.comwww.omg.com  Several other addresses of websites that contain project- related resources will be indicated later

14. 14 Tentative (subject to slight modifications): Project Deliverables [60%] Concept & Specification (P1) 10% Design (P2) 10% Progress demo (P3) 10% Implementation, Integration, and Testing (P4) 30% Project Presentations and Publications [25%] Presentations (design, workshop) (PRES-I, II, WKS) 9% Project website (WEB) 5% Project video clip (VIDEO) 6% Poster (POSTER) 5% Midterm examination (TEST) [12%] Class participation (classes & workshop, WKS) [3%]

15. 15 Notes on grading: For grade A: at least 90% overall, at least 90% in class participation and at least 60% in test To pass the course: at least 50% overall and at least 50% in project parts P3 and P4 There are no make-up tests or homework in this course Note that poor class participation can significantly decrease your overall grade

16. 16 Tentative (subject to slight modifications): Project Deliverables [60%] Concept & specs based on engineering standards (P1) 10% Design with realistic engineering constraints (P2) 10% Progress demo (P3) 10% Implementation, Integration, and Testing (P4) 30% Project Presentations and Publications [25%] Presentations (design, workshop) (PRES-I, II, WKS) 9% Project website (WEB) 6% Project video clip (VIDEO) 5% Poster (POSTER) 5% Midterm examination (TEST) [12%] Class participation (classes & workshop, WKS) [3%]

17. 17 Notes on grading: For grade A: at least 90% overall, at least 90% in class participation and at least 60% in test To pass the course: at least 50% overall and at least 50% in project parts P3 and P4 There are no make-up tests or homework in this course Note that poor class participation can significantly decrease your overall grade

18. 18 Numerical-letter grade correspondence A90 -100[maximum 100] A-87 - 89 B+83 - 86 B78 - 82 B-75 - 77 C+71 - 74 C66 - 70 C-63 - 65 D+59 - 62 D54 - 58 D-50 - 53 F< 50

19. 19 Late submission policy: No late days for presentations, demos, and test Maximum 2 late days per project deliverable Each late day penalized with 10% No subdivision of late days (e.g. in hours) Example: a 90/100 worth project deliverable gets 81/100 if one day late (90*0.9 = 81) or 72/100 if two days late (90*0.8 = 72)

20. 20  Legal notices on the world-wide web: Read and comply with accompanying legal notices on websites accessed  Specify references used  Do not plagiarize. 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 www.unr.edu/stsv/acdispol.html

21. 21 Week #Dates (T, R)Contents 1 Jan 24, 26Course syllabus, Introduction 2 Jan 31, Feb 02Lectures on UML & UP 3 Feb 07, 09 Project group meetings PWEB due 02/10/2012 4 Feb 14, 16Project group meetings 5 Feb 21, 23 UML Lectures Project concept & specification due (P1) 02/24/2012 6 Feb 28, Mar 01Presentations round 1 (PRES-I) 7 Mar 06, 08 Presentations round 1 (PRES-I) Project design due (P2) 03/07/2012

22. 22 8 Mar 13, 15UML Lectures/Invited speakers 9 Mar 20, 22Spring break, no classes 10 Mar 27, 29 Lecture/Invited speaker Midterm test (TEST) 03/29/2012 11 Apr 03, 05 Project group meetings Project poster (POSTER) due 4/06/2012 12 Apr 10, 12 Project progress demos (P3) Project video (VIDEO) due 4/16/2012 13 Apr 17, 19Presentations round 2 (PRS-II) 14 Apr 24, 26Presentations round 2 (PRS-II) 15 May 01, 03Implementation - internal project demos (P4) 16 May 04 Workshop presentations & public demos (PRS-III) 05/04/2012; Deliverables P4 due 05/08/2012