CSC 590 Lecture Notes Week 6
Overview of Assignments 3, 4, and 5
Discussing Related Work in a Thesis



  1. Go over Assignments 3, 4, and 5 (see the handouts ).

  2. Where does related work go in a thesis?

    1. As seen in several examples, it goes in one or more chapters.

    2. A background chapter can come early.

    3. A detailed compare-and-contrast can come early or later.

    4. The discussion may go in several chapters, none titled "Background" or "Related Work".


  3. A "Background" chapter.

    1. Such a chapter is typically necessary if thesis subject matter is not "mainstream" for the intended audience.

    2. The "intended audience" consists of any computer scientist with a BS+ degree, i.e, a BS plus some grad work.

    3. Such a chapter provides tutorial-style intro for readers who's field is not that of thesis.


  4. An explicit "Related Work" chapter.

    1. This is the heart of the matter.

    2. The key aspects are these:

      1. Must cover all of the important related work.

      2. Must do a detailed compare-and-contrast style treatment of directly related work.

      3. Typical in MS, state limited focus vis a vis related work.

      4. Running comparative example may be appropriate.

      5. By end, reader should be fully clear where your work fits in state of the art.


  5. Cannon's type inference experimental project.

    1. Related work covered in three chapters, they each include some other technical content.

    2. No single chapter entitled "Background" or "Related Work".

    3. Chapter on type inference algorithms.

      1. This is essentially background.

      2. Covers key algorithms.

      3. Discusses them thoroughly.

      4. Good for readers who's field is not PLs or compilers.

    4. Chapter on type inference in python.

      1. Another background chapter, intermixed with discussion of technical problems.

      2. Good for readers who are not intimately familiar with Python.

    5. Ch on previous attempts at Python type inf.

      1. This is a focused "related work" chapter.

      2. It compares and contrasts the thesis work to two other attempts at Python type inf.

      3. These are the only known works in this particular area.


  6. Wirick's Lojban project.

    1. This thesis has two archetypal chapters.

    2. Chapter 2 is entitled "Background"

    3. Chapter 3 is entitled "Literature Review"

    4. Background chapter covers:

      1. The semantic web.

      2. Ontologies in OWL.

      3. Lojban.
      -- it could have done more on ontologies.

    5. Literature review chapter covers several approaches to NL translation into ontologies.

      1. A weakness of this chapter is that it does not compare and contrast in detail thesis work to others.

      2. This is potential problem with any related work chapter that comes early in thesis.

      3. Later chapter 7 on results analysis could have done compare and contrast, but it does not (in this particularly thesis).

      4. This is a weakness; cf. Cannon's comparison to "all known attempts".


  7. Smith's statistical survey.

    1. Here again, two archetypal chapters.

    2. Chapter 2 entitled "Background".

    3. Chapter 3 entitled "Previous Work".

    4. Background chapter covers:

      1. Survey theory.

      2. Phases of SE.

      3. Prototyping.
      -- organization is fine; thesis weakness is not here, but in definitional focus.

    5. Previous work chapter covers seven previous studies.

      1. Provides good coverage of other work.

      2. Compares and contrasts other work to each other.

      3. Some but not thorough compare and contrast to work of thesis.

      4. As with Wirick's, not comparison in later results chapter either.


  8. Skovil's codec survey.

    1. Give pure survey nature of thesis, it's essentially one big "related work" treatment.

    2. There is an initial chapter on digital audio fundamentals.

    3. Four tutorial style technical chapters follow..

    4. Chapter 7 on "Codec Criteria" is a good model for a compare/contrast methodology.

      1. It presents a specific set of criteria by which related work can be compared and contrasted.

      2. Such a methodology can be used on any thesis.


  9. Summary observations.

    1. Having a common example as basis of comparison.

      1. E.g., the common benchmark that Cannon uses.

      2. Or the common audio transmission problem that Scovil presents.

    2. Developing rigorous evaluation criteria.

      1. E.g., the codec criteria that Scovil presents.

      2. Not always necessary, but can greatly strengthen results.

    3. The critical importance of clarifying your contributions.

      1. Discussion of related work plays a key role in explaining why your work is worthwhile.

      2. The reader should be left with the distinct impression that your thesis contributed something new in the world, compared to what came before.




index | lectures | handouts | examples | reference