Files
logseq/pages/GSSI - PhD Thesis proposal review.md
2025-06-05 22:07:12 +02:00

3.2 KiB

  • Invitation email


    • The email contains 2 attached file(s)

    • Dear Davide,
    • Thank you again for having accepted to provide your opinion on the
    • thesis proposal delivered by Jose Aleandro Concepcion Alvarez (see
    • attached PDF file).
    • Your report should simply consist of an evaluation of the following aspects of the thesis proposal as "good", "sufficient" or "insufficient".
      • Knowledge of the state of the art in the research field addressed in the proposal.
      • Novelty of the research proposal.
      • Feasibility of the research proposal.
      • Global evaluation of the thesis proposal (here "insufficient" means that you do not recommend that the student be admitted to the second year of his Ph.D. studies).
    • A few lines justifying your evaluation and possibly offering some suggestions that might be useful for the student in his/her future research (if the proposal is evaluated at least of sufficient quality to form the basis for a PhD thesis) are more than welcome.
    • If you want, you can (but you are not obliged to) use the attached LaTeX template.
    • We would need to receive your report by October 7, 2022.
    • I thank you again and I look forward to hearing from you.
    • All the best,
    • Gianlorenzo D'Angelo and Pierluigi Crescenzi
    • Coordinators of the PhD program in Computer Science at GSSI

    • File

      • Thesis_Proposal_Jose_Alvarez.pdf
        • tItle:: Recommender Systems for Reference Architectures author:: Jose Alejandro Concepcion supervisors:: #people/ludovico #people/mariani
  • Comments

    • The document is missing a conclusion section
    • ((633df160-52ba-4e3b-87b0-de325895edc1))
      • Interesting, even though it is not clear what you would like to recommend
    • ((633df1f2-53ed-4105-abed-ad47cc527574))
      • Instantiation process... this is important! #MAINGOAL
    • ((633df242-8b3d-4c2f-994b-68f7bef61b57))
      • That's crucial, how to address this?
    • ((633df5c4-3e3f-448f-877a-cb4320ad9747))
    • ((633ed873-be0c-4cd2-b0d5-b6ddefb0e6f4))
  • ((633ed9bc-bbab-4f58-bb01-dc66a3cad84d))
    • Qualche ref per #people/riccardo
  • ((633eda20-1dd6-4253-9996-31ff7bd47495))
    • Caratterizza cosa?
  • ((633edd00-5a84-450d-9878-7600c35bbb1e))
    • IMPORTANT
  • ((633edd38-5b7c-490e-b770-9d806802076d))
    • #MAINGOAL
  • ((633edd99-6dde-41bf-b886-bebc00f77893))
    • #MAINGOAL
  • ((633ee518-c325-4c14-86fb-492a67e7ed3a))
    • feedback mechanism. Useful for #people/riccardo
  • ((633eef2b-f0a1-4796-bc97-36efe446c972))
    • #MAINGOAL
  • ((633eef63-1d3d-47ea-88c5-540ca879340d))
    • The problem that I see it is related to the relation identifying the instance relation between Reference Architecture and Software Architecture
      • Appunto
        • ((633ef07a-daba-48c8-b053-4470f63d0146))
  • ((633ff5a3-5955-415c-8cbe-68ae0d3121b1))
    • This is risky in my opinion