1. SEG4910 – Projet génie logiciel en fin détudes / Software Engineering Capstone Project Syllabus, Rules, Process and Deliverables Timothy C. Lethbridge Derived from notes by Liam Peyton

2. 2 Tim Lethbridge, Ph.D., P.Eng. Professor at UOttawa since 1994 Software Engineering Usability, software tools, knowledge engineering Software developer at Nortel and the Government Researcher with GM, IBM, Boeing, Ericsson and smaller companies Current research focus: Umple

3. 3 Cours Bilingue …. Sort of les instructions pour le projet et les lectures, sont disponibles en anglais seulement MAIS, Vous pouvez travailler en français vous pouvez faire des présentations et les documents pour le projet en français Prières de venir me rencontrer, pour obtenir des instructions en français (orale)

4. 4 Everythings online See Course Website http://www.site.uottawa.ca/~tcl/seg4910-11/ Rules Class schedule Lecture Notes – to be updated I have simplified deliverables from last year

5. 5 One Project – 2 Courses 1 Project 1 customer (meet regular, once every week or two) 1 group: 2-6 students 1 group leader (can take turns) Workload: 3-4 weeks per person per semester (12-15h/wk) UCOSP students have slightly different rules Start in 4910, finish in 4911 Must have same project, same customer, same group for both courses, otherwise you have to retake the entire sequence 4910 / 4911=

6. 6 You will be attending class in the same time slot as SEG4911 They are finishing their project You will learn from their presentations You will not come to class every lecture Some are just for SEG4911 See the schedule to know when to come

7. 7 Project Teams of 2-6 students who may take leadroles Project Manager Business Analyst QA manager Architect Build Manager Lead Developers But everybody does some design and coding

8. 8 Project Real Customer From concept to deployment over 2 semesters An agile approach with the customer seeing your work every week or so and being on site virtually

9. 9 Project Grading Scheme See http://www.site.uottawa.ca/~tcl/seg4910- 11/rules-e/ for detailshttp://www.site.uottawa.ca/~tcl/seg4910- 11/rules-e/ Grades for the following Customer satisfaction (20%) Project management and professionalism (20%) Presentations (10%) Design (20%) Writing (20%) Complexity/Difficulty (10%) 5% zero-sum adjustment among team members You decide if some team members should get more or less

10. 10 Agile work Use a GIT or SVN repository Do Test-Driven Development where possible Use issue tracking for all user stories, features and bugs Use a Wiki for requirements etc., Put meeting minutes, progress logs here Have a group mailing list Set up automated building where possible Give the prof access to see the above. Deliver in increments at intervals of no more than a month, starting in October at the earliest Continuous development Each person commits their changes and the build runs

11. 11 Legal Issues Academic Fraud Using others work without acknowledgement Misrepresenting results, participation Grades group mark, EXCEPT: all agree and inform me zero-sum redistribution of up to 5 marks IP You own your work but can relinquish your ownership (big companies will insist on this) Non-Disclosure Agreements I wont sign one, but you can Paid For Work I do NOT recommend it. You must inform me. All team members must be equal

12. Work schedule Schedule times each week to work with your team Can use unused class timeslots Can use project room on 2 nd floor I will need to sign a form to get you access 12

13. 13 Proposal Must be finalized by next week – on your wiki Outline Team members and their roles Objectives (benefit to customer, key things to accomplish, criteria for success) Expected/anticipated architecture (e.g. web-based in PHP, Android App, C++ embedded system on Arduino etc.) Anticipated risks (engineering challenges, etc.) Legal and social issues. Initial plans for first release, tool setup, etc. Put the above on the Wiki and privately send me your customers name, title and contact info