1 CS 426 Senior Projects Spring 2006 Course Syllabus January 24, 2006

2 Outline The Instructor The Students The Course The Texts Grading Scheme & Scale Policies Tentative Schedule

3 The Instructor Sergiu Dascalu Room SEM-236 Telephone Web-site Office hours:   TR 1:30 - 2:30 pm or by appointment or chance

4.The Instructors Brian Westphal Room SEM-255 A#1 or SEM-205 Telephone Web-site Office hours:   Tuesday 4:00 - 5:00 pm and Wednesday 1:30 – 2:30 pm or by appointment or chance

5 The Students Registered as of today: 24 students Prerequisite: CS 425 Software Engineering

6 The Course.. Classroom: Classroom: SEM 347, TR 9: :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.

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

8..The Course Outline [cont’d]: T The teams will deliver and present project work at the following stages: topic proposal (concept), software specification (requirements), design (model), and implemented software (final product). At the beginning of the semester the teams will set up websites for their projects, websites that will be then 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, demos, and posters.

9 The Texts. Required textbook: [Arlow’02] Jim Arlow and Ila Neustadt, "UML and the Unified Process: Practical Object- Oriented Analysis and Design," Addison Wesley, 2002, ISBN: Recommended textbook: Recommended textbook: [Norman’02] Donald Norman, The Design of Everyday Things, Basic Books, 2002, ISBN: [Norman’02] Donald Norman, "The Design of Everyday Things," Basic Books, 2002, ISBN:

10.The Texts Additional readings: Additional readings: For each individual project an additional 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. 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.

11 Initial WWW Pointers Course website: The Object Management Group: Several other addresses of websites that contain project-related resources will be indicated later

12 Grading Scheme. Tentative (subject to slight modifications): Project Deliverables [60%] Concept (P-I) 4% Concept (P-I) 4% Specification (P-II) 10% Specification (P-II) 10% Design (P-III) 11% Design (P-III) 11% Implementation, Integration, and Testing (P-IV) 35% Implementation, Integration, and Testing (P-IV) 35% Project Presentations and Publications [18%] Presentations (specs, design, workshop) (PRES-I, II, III) 8% Project website (PWEB) 6% Poster (POST) 4% Midterm examination (TEST) [15%] Class participation (classes & workshop, WS) [7%]

13.Grading Scheme Notes on grading: Notes on grading: For grade A: at least 90% overall, at least 85% in class participation and at least 60% in test For grade A: at least 90% overall, at least 85% in class participation and at least 60% in test 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: No late days for presentations, demos, posters 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)

16.Policies Legal notices on the world-wide web: Legal notices on the world-wide web: Read and comply with accompanying legal notices on websites accessed Specify references used 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: Do not plagiarize. Plagiarism and cheating will not be tolerated. Please read the policies of University of Nevada, Reno regarding academic dishonesty:

17 Tentative Schedule. Week #Dates (T, R)Contents 1Jan 24, 26Course syllabus & project organization 2Jan 31, Feb 2 Lectures on UML and UP: Analysis Definition of project topics, Teams set 2/2 3Feb 7, 9 Project group meetings P-I due 2/10 4Feb 14, 16 Lectures on UML and UP: Design. Draw. Project website set up (PWEB) 2/15 5Feb 21, 23 Lectures on UML and UP: Design. Project specification due (P-II) 2/22 6Feb 28, Mar 2Project specification presentations (PRES-I) 7Mar 7, 9 Invited talk, Lecture on UML and UP: Implementation, P-III due 3/8

18.Tentative Schedule 8Mar 14, 16Project group meetings 9Mar 21, 23Spring break, no classes 10Mar 28, 30 Lecture on UML and UP: Implementation Recap for midterm test 11Apr 4, 6Invited talk & Midterm Test (TEST) 4/6 12Apr 11, 13Project design presentations (PRES-II) 13Apr 18, 20Project pre-demos (Project group meetings) 14Apr 25, 27 Invited talk and Workshop preparation Project poster (POST) due 4/26 15May 1, 3 Project implementation, integration, and testing & internal project demos (P-IV) due 5/1 May 5 Workshop presentations, demos, posters (WS, PRES-III) 5/5