DEPARTMENT OF COMPUTER SCIENCE
ACADEMICS
GRADUATE INFORMATION
DOCTORAL DEGREE
|
DEPARTMENT OF COMPUTER SCIENCE ACADEMICS GRADUATE INFORMATION DOCTORAL DEGREE |
The portfolio is the principal artifact used by the department to monitor progress of doctoral students, and successful defense of the portfolio is a required component of admission to candidacy. This document is intended as a guide to the portfolio component of these requirements. Adhering to these guidelines is a requirement for continuing in the doctoral program.
Every Computer Science doctoral student is required to assemble and submit a portfolio for review no later than the date specified under Portfolio Calendar below.
New portfolios should be submitted to the student's academic advisor for preliminary revew. The advisor may suggest that the student make modifications. When the advisor is satisfied, the advisor will sign the cover page form and transmit the portfolio on the the PRC.
Portfolios are reviewed on a regular basis (generally once a year, during the Spring term) by the Portfolio Review Committee (PRC), a faculty committee appointed by the department chair. Feedback to the student on portfolio contents and on progress towards admission to candidacy is provided as a result of these reviews.
Admission to candidacy for the PhD degree consists of two milestones:
Every student in the FSU Computer Science doctoral program is required to prepare a three-ring binder containing as much as possible of the information described below. For each major section, please begin the corresponding section in your binder with a tabbed separator labeled so as to identify the section heading.
Summary Data
| Personal Information | |
| Your Name: | |
| Your SSN: | |
| Date entered program (semester/year): | |
| Full or part time student? | |
| Principal source of support: | |
| Doctoral Committee | |
| Major Professor / Advisor | |
| Committee Member | |
| Committee Member | |
| Committee Member | |
| External Committee Member | |
| GRE Scores | |||
| Exam | Date exam was taken | Location where exam was taken | Score |
| GRE Verbal | |||
| GRE Math | |||
| GRE CS Area * | |||
| TOEFL | |||
* The Verbal and Math exams are required for admission to the graduate program. All Ph.D. students should be able to provide these scores, their first semester. The Computer Science area GRE exam is not required for admission to the graduate program, but is required before for admission to Ph.D. candidacy of all students who entered the Ph.D. program starting Fall 2003. Ph.D. students who did not take the exam before admission to the program are expected to take the exam before the portfolio defense.
| Core Graduate Courses and Grades | Core Area | Core Course | Semester Taken or Planned | Name of Instructor | Grade Received |
| Software | ||||
| Systems | ||||
| Theory | ||||
| GPA for core courses: | ||||
If you are requesting that courses taken at another institution be counted toward the core, please provide supporting documentation for the equivalence. If our department's Director of Graduate Studies or another qualified graduate faculty member has made an examination and determined that the course is equivalent, obtain a letter or memo signed by this person and put a copy in the portfolio. In any case, include in your portfolio a copy of the course syllabus, including at least the information about the prerequisites, topics, and textbook or other references used, and copies of whatever graded work (examinations, projects, etc.) you have retained from the course.
In general, to be equivalent a course must be a graduate course, with similar prerequisites, a similar list of topics, and similar performance expectations. For example, a course in operating systems will not be considered equivalent to COP 5611 unless it is a "second semester" course, i.e. one for which there is another operating systems course like COP 4610 as prerequisite. For the theory area, the course grade must be based on the ability to do mathematical proofs. For the software area, the course must involve substantial hands-on software development, with a mature level of documentation and testing.
| Elective Courses and Grades | Elective Course | Semester Taken or Planned | Name of Instructor | Grade Received |
| GPA for elective courses: | |||
| Area Exams | ||
| Exam Coverage Area | Date of Exam (semester/year) | Result of Exam |
The CV should contain the following information:
Research Publications and Writing
Begin this section by repeating the publication list cited in your CV.
Place a reprint or photocopy of one research publication of which you were a contributing author. State the role you played in this publication, i.e., what was your role in the research and in the writing of the paper.
If you were not the person primarily responsible for writing this paper, or if you have no publications, then contribute a work of a research nature which you personally created. This should be your Masters Thesis, or if you have not written a thesis, then some other research oriented writing. If you are the sole author of the paper contributed above, there is no need to place any further writing samples in the portfolio.
A person holding the PhD in Computer Science is expected to have the ability to contribute substantially to significant software artifacts. As such, one such artifact is a required component of the doctoral portfolio. Include a copy of ONE such artifact, including design, engineering, and certification reports, software documentation, and actual code.
A listing of unidentified uncommented code is not sufficient. The portfolio must include enough external documentation and internal comments for the reviewers to read and evaluate the scope and quality of the software. Some indication must be included of how the quality of the software was tested. If the software is something submitted for grade in a course, you should include the instructor's statement of the assignment as external documentation, but that is not sufficient; the code must at least include internal comments. Similarly, for a course assignment you may provide the grade you received, and any comments the instructor made, as part of the "certification report", but you also should explain how you tested it.
For large projects, only indicative samples of the actual code need be included, but the full code should be available either on-line or as a separate document. If lengthy, these items may be submitted in a separate binder. If you include a CD containing materials, please include printed copy of at least some overview material, with pointers to the CD for the rest.
If any of the software or documentation components are the work of more than one author, you must indicate what parts of these components you contributed to and estimate the percent of your personal contribution to each part. Moreover, it is best that you also include some examples of your individual work.
Write a 1-2 page abstract describing your intended area of dissertation research. Include indications of progress you have made.
List all employment you have had while a graduate student in the department along with the begin/end dates of that employment. Include TA/RA positions, other work within FSU, as well as outside employment. We are interested in some detail, for example, if you are research assistant, describe the position, work requirements (in terms of both effort and outcome), and who the employer/supervisor is. This information is relevant both for the extent to which your activities support your educational objectives and the extent to which they may occupy your time in activities not related to your degree program.
With each RA and TA position you have held at FSU, include here photocopies of your semesterly evaluation of performance in those positions.
List all fellowship support you have while a student in our program. List the granting agency, the academic and ancillary requirements, and the amount of funding for each fellowship.
As discussed above, doctoral student portfolios will be reviewed regularly by the Portfolio Review Committee, and each student will be sent a letter indicating the committee's evaluation of the student's progress toward the degree. Photocopies of all such letters to date are to appear in this section of the portfolio.
To the extent these are available, include copies of your transcripts from prior institutions, i.e., universities or colleges you attended prior to your beginning as a graduate student in Computer Science at FSU. If you submitted transcripts with your application to our graduate program, the departmental staff can make photocopies of these for you from your application file, if you so request.
In this section, place photocopies of the official reporting forms of your GRE and TOEFL scores reported in section 1 above.
In this section place photocopies of the result reports from all area exams you have taken.
The PhD Portfolio is intended to provide the department with a complete view of the student's accomplishments and abilities that relate to likelihood of success as a PhD professional. The portfolio is reviewed regularly by the Portfolio Review Committee to determine whether the student is making suitable progress towards the degree, and then again for a final time when the student makes the portfolio defense to the committee. The portfolio defense is held in conjunction with this final portfolio review. Successful defense of the portfolio (grade of "P" in CIS 8962 Doctoral Qualifying Exam (see note)) is one of the two required components of admission to candidacy.
The portfolio defense should be made soon after the core course requirements have been met, and core courses should be taken as soon as practical. The PRC will monitor progress taking core courses and may suggest a date for the portfolio defense.
The student should enroll in CIS 8962 Doctoral Qualifying Exam (see note) when he or she has completed the core courses and the student and major professor agree that the student is ready to defend the portfolio. (Portfolio defenses may be scheduled for Fall or Spring semester, but not Summer semester.) The PRC will schedule and conduct the portfolio defense during the semester. The defense will be oral and will cover any parts of the portfolio that the committee deems appropriate, including the course work itemized, publications, software artifacts, and the ongoing research of the student.
In evaluating the portfolio, no one aspect of the portfolio is taken as a determining factor, but rather an attempt is made to consider all strengths and weaknesses and to determine whether, overall, the student may reasonably be expected to succeed and become a credit to the department. Components of such success generally are as follows:
In order to demonstrate adequate mastery of the breadth of Computer Science, we ordinarily expect a successful candidate to maintain a GPA of at least 3.5 in the core courses required for the degree. Candidates may refer to the grading scale for PhD students in graduate courses that has been adopted by the department. The Portfolio Review Committee may make exceptions to this GPA rule if it finds compelling evidence of exceptional strength in research. For example, a slightly lower GPA might be offset by published papers in reputable journals or conference proceedings.
The portfolio defense will include a review of the candidate's competency in the core courses taken. Currently this is done via an oral examination on the contents of the courses. (The student would be wise to review the contents of these courses and their prerequisites prior to the examination.)
Research is a critical component of the PhD degree process and is a fundamental part of most professional positions that require a PhD as credentials. The department would like to admit to candidacy individuals who have demonstrated the ability, or aptitude, for research in the field.
The portfolio defense may assess this competency through oral examination. Such questions will test the ability of the student to reason through answers
The creation of computer software is a fundamental part of computer science, and the department generally expects that its graduates possess the skills and training necessary to contribute to such endeavors.
The department also wishes to see that the student has a capacity to express his or her thoughts in publication quality English. Thus there is a requirement that the Portfolio contain some writing sample that demonstrates written communication skills, and the portfolio defense serves to evaluate spoken communication skills. The writing requirement may be met by a professional publication, masters thesis, a masters degree project report, or any other writing that the student may have produced as part of his or her course work. Note that an ability to present one's ideas in written English is considered as separate from an ability to conduct research, and that both abilities are deemed necessary.
The department also wishes to see that the student is capable of responding extemporaneously to oral questions, as a researcher is required to do when presenting a paper at a conference and a professor is required to do when teaching. The portfolio defense is a test of these oral communication skills. The student will be expected to be able to understand the questions presented by the examiners, and to answer them on the spot. The questions may relate to contents of the core courses, their prerequisites, and the contents of the portfolio.
Q: Can I defend the Portfolio this term if I am registered in one of the six required core courses this term?
A: No. The Portfolio Defense is the point at which the Department checks for completion of the required core courses and the quality of work in those courses. Until the end of the term we have no way to tell how well you will have done in the course.
However, we have agreed in some cases to allow a student who has received high grades in all but one of the core courses to take the oral defense in the Spring term in which the last core course is being taken, since we do not ordinarily give portfolio defenses during the summer. In that case, the student is expected to still be able answer questions about all the core courses. If the student passes the oral, the exam is not recorded as passed untl after then end of the term, and the chair of the Portfolio Review Committee has verified that the remaining core course has been passed with an acceptable grade.
Q: Can I subsitute another course for one of the six required core courses? How about doing it just for the Portfolio Review, if I promise to take the course later?
A: No. The Portfolio Defense is the point at which the Department checks for completion of the required core courses and the quality of work in those courses. Until you take the course we have no way to tell how well you will have done in the course.
Of course, with adequate justification, departments at FSU are permitted to approve course substitutions in degree requirements. The PRC will only consider a subsituttion if the Portfolio contains a copy of a letter approving a course substitution for the degree requirements, signed by Director of Graduate Studies and the Department Chair.
Q: What kind of oral questions can I expect at the Portfolio Defense?
A: That will be up to the individual members of the PRC. You can expect questions asking for clarification of information that is in the Portfolio (especially any aspects of the portfolio that might appear weak), and questions about information that is missing from the portfolio. You should also expect questions on the four areas covered by the defense: (a) general competency in CS; (b) research aptitude; (c) software skills; (d) communication skills. If the portfolio itself is strong, all or most of the questions are likely to be on (a).
In area (a) the intent of the questions will be to gauge your understanding and retention of material covered in the six core courses and their undergraduate prerequisites. For example, if you have taken Automata and Formal Languages as part of your core requirement, you should not be take by surprise if you are asked to explain what is a finite state machine, what is the difference between a deterministic and a nondeterministic finite state machine, what it means for a gramar to be ambiguous, how that compares to a language being inherently ambiguous, etc..
Be sure to have your major professor, and possiby others, help you prepare for such questions. Minimal preparation would include reviewing your notes from the core courses, and then answering some oral questions from each of the areas they cover.
A big part preparing for the exam is learning to be comfortable listening to questions, making sure you understand (by asking for clarification if necessary), and then expressing yourself clearly. You will have an easel and pen to write on. Plan to use it appropriately, to help with your answer. A "mock" oral examination is a good way to practice.
Students who have not taken the core courses recently, or who have transferred credit for a core course from another institution, should expect to be asked more questions on the core courses, to verify that the knowledge has not become stale, and that the material learned is similar in scope and depth to what is covered in the corresponding course here at FSU. Similarly, if you took the course at FSU but your grade was not A or A-, you may expect more questions on that course.
In area (b) you might expect questions concerning your research experience, your contributions to any research papers in your portfolio, your research plans, and the membership of your supervisory committee. If your portfolio contains
In area (c) you might expect questions on what software you wrote, and the examples of software you included in your portfolio.
In area (d) you might expect questions on the technical writing samples you included in your portfolio, but mainly the committee will be judging your communication skills by the manner in which you answer the questions about (a). That is: Can you understand the question? Can you ask appropriate questions for clarification? Can you give a clear answer? Howe well you do these things in the exam will be viewed as indication of your ability to function in a classroom, and as a speaker at a research conference.
These are just my examples, not intended to limit the options of individual committee members.
Along with the questions, if the questions do not take up all of the available time, you can expect some encouraging words about the strong points of your portfolio, and some constructive advice as to how to proceed.
Q: Can I defend my portfolio during the summer term?
A: Don't count on it. Very few of the faculty are paid to teach during the summer, and many members leave town. If there happen to be enough members of the PRC in town, a defense may be held, but that cannot be predicted.
Q: Can I do my Area Examination before my Portfolio Defense?
A: Not officially. The course number for the Area Examination is listed as the Ph.D. Preliminary Examination, and the FSU Graduate Bulletin says that a student is admitted to Ph.D. candidacy by passing the Preliminary Examination. Our department's faculty has set up the admission to candidacy as a two-step process. The necessary first step is the Portfolio Defense (Qualifying Examination). In a few cases, for scheduling reasons, a student may go through the Area Examination process, but a passing grade for the Area Examination cannot be turned in until the student has completed the Portfolio Defense. If the are done the same term, this can work out. Students and advisors should take care about this. If, by some oversight, a passing grade for the Area Examination were to be turned in before the student passes the Portfolio Defense, the Department would need to revoke the passing grade on the Area Examination untl the Portfolio Defense is passed.
Q: What if I took courses at another institution, that I want to count toward my core requirement?
A: First, you should have obtained some clearance for transfer credit when you were admitted, and you should put a copy of a letter or memo to this effect in your portfolio. Second, you should include in your portfolio the name of the textbook you used in the course, a copy of the course syllabus, and examples of graded exams and projects form the course. This will enable the PRC to gauge whether the course seems equivalent, and to know what sort of questions to ask during your oral examination on that area.
Q: When will I know whether I passed?
A: The PRC will probably wait to tell anyone until all of the students taking the exam that term have completed the oral defense.
Q: Can I talk with other students about the exam, after I take it?
A: You are asked not to discuss questions you were asked on the oral exam with anyone, until you are told the result of the exam. This allows us to be fairer to all students. For example, suppose you have trouble on a question. It may be that all students have trouble with that question, and the committee decides to disregard it. Howver, if you tell another student who is due to take the exam later in the same term, and the other student then looks up the answer and so answers better than you did, the committee may conclude that the question was not hard, and that you have no excuse for answering poorly.
Q: Do I need to form my entire Ph.D. supervisory committee before I do the Portfolio Defense?
A: This is not a requirement, but if you do not yet have your supervisory committee formed you need to do it right away, because you need the full supervisory commmittee before you can move on to the next step, which is the Area Examination.
Q: Do I need to choose my research area before I do the Portfolio Defense?
A: This is not a requirement, but if you do not yet have your area chosen you need to do it right away, since you can't prepare for the Area Examination until you have chosen an area.