PBT 2019-2020

PBT – retake session – check the rules [here]

PBT seminar 931 online [here]

PBT evaluation [931]

The methodology for the third seminar (March 30, 2020):

  • live session using the above stream
  • the presence must be notified, by each student, in the chat associated with the above stream (Surname, First Name)
  • each student must prepare a pdf that contains:
    • the title of the thesis and the student’s name (e.g. usage of a header will emphasise this info on every page)
    • the table of content of his/her thesis
    • a theoretical chapter or a consistent part of it – please insert before this chapter a preamble with a short description and informal specification of the approached problem (in this way, is more evident why you must present some theoretical elements, methods, models, etc.)
  • please follow the suggestions regarding the document formatting
    • read more details [here]
    • optional, you can check a latex model [here]
  • if you have questions about the deliverables, they will be discussed during the live session
    • for an efficient communication, each student must prepare an open-access (for professor) document and inform the professor about it
  • each student must load the prepared pdf in [cs server] until the end of the day

 

The methodology for the fourth seminar (April 13, 2020):

  • live session using the above stream
  • the presence must be notified, by each student, in the chat associated with the above stream (Surname, First Name)
  • each student must prepare a pdf that contains:
    • another [part of the] theoretical chapter  – please add a section/sub-chapter dedicated to related work/state of the art regarding the approached problem (other methods or models from the literature used to solve the considered problem)
    • [optional: a chapter dedicated to the proposed approach where:
      • all the theoretical elements, described in the theoretical chapter, could be adapted to the proposed application
      • the relations between the developed model and each related work could be emphasised
      • the advantages and disadvantages of the advanced  model could be analysed]
    • the first part of the practical chapter that must contain all the application requirements and the informal and formal specifications of the tackled problem
  •  please follow the suggestions regarding the document formatting
    • read more details [here]
    • optional, you can check a latex model [here]
  • if you have questions about the deliverables, they will be discussed during the live session
    • for an efficient communication, each student must prepare an open-access (for professor) document and inform the professor about it
  • each student must load the prepared pdf in [cs server] until the end of the day

 

For the next seminar (the fifth one) you have to prepare:

  • new parts of the practical chapter
    • one that describes the design of the application (a general flowchart, conceptual model, use cases, class diagrams, sequence diagrams, etc.)
    • one that is dedicated to the implementation details (language, libraries, frameworks, other technological aspects, etc.)
    • one that is dedicated to the validation and testing of the developed application
  • one functionality of the proposed application
    • the corresponding specification [already shown in the previous assignment]
    • the dedicated use case(s)
    • the corresponding code / implementation
    • the validation and testing associated with this functionality
    • the real working (live running of the functionality)

 

For the next next seminar (the sixth one) you have to prepare:

  • the thesis’s Abstract that must emphasise:
    • a short description of the thesis (motivation, the main idea of the proposed solution and short analysis of it)
    • the structure of the thesis (short description of each thesis’s chapter)
    • last paragraph of the abstract must be: “This work is the result of my own activity. I have neither given nor received unauthorized assistance on this work.
  • the thesis’s Introduction – in this chapter several elements must be present (in a non-technical style)
    • the [theoretical and practical] context of the solved problem – why is important to solve this problem
    • the proposed solution for the considered problem [and its strengths and, maybe, weaknesses]
    • the student’s/thesis’s original contributions
    • the structure of the thesis
  • [optional: the thesis’s Conclusions  – in this chapter several elements must be present
    • on short, the tackled problem and the proposed solution
    • the outcomes of the performed analysis
    • possible future work and improvements to be done [maybe in a master program 🙂 ]
  • [optional: the structure of the final presentation – a maximum of 10 slides dedicated to:
    • author identification (name, specialisation, faculty, university)
    • contents
    • the considered problem and the proposed solution
    • theoretical elements required by the proposed solution
    • application presentation (design, implementation, validation)
    • conclusions and further work]
  • k (k>=2) new functionalities of the proposed application
    • the corresponding specification [already shown in the previous assignment]
    • the dedicated use case(s)
    • the corresponding code / implementation
    • the validation and testing associated with each functionality
    • the real working (live running of each functionality)