Defense Timeline

[samm82]

As mentioned in #88, there is some actual research I would like to finish up before defending, which would likely take my thesis into October. I thought that the seminar required for a SE MASc took place a week before the defense, but according to Section 7.1 of this Regulations for the Software Engineering M.A.Sc. Program document (which appears up-to-date), the seminar must take place at least four weeks before the defense.

I think this is reasonable, with me having the actual "structure" of my thesis (e.g., methods/ology, background, conclusions, research questions) fleshed out in time to have my seminar by late September. Then, I could finish up the research mentioned above before my defense by late October. Am I understanding things correctly? Just wanted to double check before I (finally 😬) reach out to the rest of my committee.

[smiths]

The regulations show a month, but it is usually done quicker than that. The committee wants the final version of your thesis in their hands when you do your seminar. We shouldn't have the seminar until your thesis is essentially in its final form. Correcting typos after the seminar is fine, but the version that the committee members receive before the seminar is the version they will read and review. Practically the seminar is usually 1 to 2 weeks before the defence.

[samm82]

OK that's what I thought; glad I checked before just running with the "on paper" process! 😅 I'll send out an email tomorrow (during business hours) about October availability ("ideally" with my seminar mid-October and defense late-October) and we can take it from there. Would it be good to keep this issue open for keeping track of our scheduling, or should I close this and we can discuss updates in the email chain?

[smiths]

Sounds good @samm82. Whether you wish to use this issue as a reminder or use an e-mail chain is up to you. Whatever helps you the most. :smile:

[samm82]

Was just about to draft an email and got overthinking again. 😔 The requirements doc seems to make a distinction between:

1. A Supervisor Committee:
   • consists of the student’s supervisor and at least one other member of the department
   • supervisory meetings must be scheduled once a year
2. The Examination Committee:
   • consists of the Supervisor(s) and at least two additional faculty members
   • the Supervisor verifies that the members proposed are willing and able to serve on the Examination Committee
   • the Software Engineering Graduate Advisor approves or modifies the composition of the Examination Committee and nominates the Chair of the Committee (who may not be the Supervisor)

This prompted some questions @smiths:

1. Do I need to schedule a supervisory meeting again before I defend, since this is my second year (technically into my third) of my Master's, or would the seminar be sufficient as a "meeting"?
2. Is it presumptuous to assume that my supervisor committee will also be my Examination Committee, or is that usually the case? Would these details just be hashed out by the scheduling process?

[JacquesCarette]

1. No need to have another supervisory meeting
2. No, that's the usual case.

[samm82]

Thanks; email going out now! 😅😩