1. COMP4710 Senior Design Richard Chapman

2. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End of Cycle Binder Upcoming Lectures Upcoming Lectures Projects Projects Project Team Selection Project Team Selection

3. What is Senior Design?  A project course where you apply the engineering practices and principles you’ve learned during your undergraduate careers.  The capstone design class for software engineers and wireless engineers  A course in which you build a production-quality software system

4. Course Objectives Ability to do software design Ability to do software design Ability to work as a member of a development team Ability to work as a member of a development team Ability to communicate technical information in oral and written form Ability to communicate technical information in oral and written form Ability to learn independently Ability to learn independently

5. Course Structure Roles Roles Course Instructor: teacher,upper management, customer Course Instructor: teacher,upper management, customer Teaching Assistant: technical consultant, manager, customer Teaching Assistant: technical consultant, manager, customer Students: project team members, technical leads Students: project team members, technical leads Course Phases Course Phases Architectural Spike, Cycle 1, Cycle 2, Cycle 3, Wrap-up Architectural Spike, Cycle 1, Cycle 2, Cycle 3, Wrap-up

6. Architectural Spike (15%) A project cycle where teams attempt to complete the entire project by whatever means available A project cycle where teams attempt to complete the entire project by whatever means available 4 Week Duration 4 Week Duration Team Status Days: Tuesday each week Team Status Days: Tuesday each week Lectures: Thursday each week Lectures: Thursday each week Deliverables – dates indicated on syllabus Deliverables – dates indicated on syllabus Presentation -- printed copy for instructor, TA, soft copy on CD Presentation -- printed copy for instructor, TA, soft copy on CD Source Code – soft copy on CD Source Code – soft copy on CD Peer Evaluations -- email submissions only Peer Evaluations -- email submissions only Written Report -- describe your design Written Report -- describe your design

7. Cycle 1 (20%) The first iteration of the development process. This cycle will produce a minimally viable product. The first iteration of the development process. This cycle will produce a minimally viable product. 4 Week Duration – see syllabus for dates 4 Week Duration – see syllabus for dates Team Status Days – Tuesdays, with whole class Team Status Days – Tuesdays, with whole class Customer Meetings -- Thursdays, each team with TA Customer Meetings -- Thursdays, each team with TA Deliverables – Deliverables – Management Schedule – due with 2nd status report Management Schedule – due with 2nd status report Status Reports – Every Monday 5pm, submitted via email, printed copy in cycle binder Status Reports – Every Monday 5pm, submitted via email, printed copy in cycle binder Presentation -- End of cycle, 2 Hard copies, Cycle Binder, including demonstration Presentation -- End of cycle, 2 Hard copies, Cycle Binder, including demonstration Peer Evaluations – due at time of presentation, on paper Peer Evaluations – due at time of presentation, on paper Cycle Binder – due day of presentation Cycle Binder – due day of presentation Source code on CD -- due day of presentation Source code on CD -- due day of presentation

8. Cycles 2, 3 (20% each) Each cycle is an iteration of the development cycle. Each cycle is an iteration of the development cycle. At the end of each cycle the teams will produce viable products building on the previous cycle’s product At the end of each cycle the teams will produce viable products building on the previous cycle’s product 4 Week duration – see syllabus for dates 4 Week duration – see syllabus for dates Team status days and customer meetings -- same schedule as cycle 1 Team status days and customer meetings -- same schedule as cycle 1 Deliverables – same as cycle 1 Deliverables – same as cycle 1

9. Wrap-up Each team will be responsible for two additional deliverables. Each team will be responsible for two additional deliverables. Installation/Build (10%) –Hardcopy of instructions, CD submission Installation/Build (10%) –Hardcopy of instructions, CD submission Final Presentation – Each team will prepare a short, 7 minute presentation evaluating their experience in the course. (2 Hardcopies for instructor, TA) Final Presentation – Each team will prepare a short, 7 minute presentation evaluating their experience in the course. (2 Hardcopies for instructor, TA)

10. End of Cycle Binder For each production cycle (1,2,3), a documentation binder will be prepared and submitted (hard and softcopies). The contents are as follows; For each production cycle (1,2,3), a documentation binder will be prepared and submitted (hard and softcopies). The contents are as follows; Cycle Presentation (copy of slides) Cycle Presentation (copy of slides) Management Schedule (GANTT chart or similar) Management Schedule (GANTT chart or similar) Status Reports (for all weeks of the cycle) Status Reports (for all weeks of the cycle) Lessons Learned Lessons Learned Meeting Minutes/Memoranda Meeting Minutes/Memoranda Version Description (features since last version) Version Description (features since last version) Architecture Documentation Architecture Documentation User Story Documentation User Story Documentation Design Documentation Design Documentation Testing Documentation Testing Documentation Source Code Source Code

11. Upcoming Lectures The Senior Design Process The Senior Design Process Project Documentation Project Documentation Introduction to Refactoring Introduction to Refactoring

12. Projects

13. Project/Team Selection