Beyond Code: An Introduction to Model-Driven Software Development (CISC 836, Winter 2021)

Projects

Important note
These are the webpages for last term's version (Winter 2021) of the course. For this term's version (Fall 2021), go here.

Choosing a project

The projects for CISC836 can be worked on in groups of 1 or 2 students.

Proposal

The proposal should describe the problem to be solved or work to be carried out, material or software to be used, together with any challenges and results expected. The length should not exceed 2 pages.

Please use the ACM SIG Proceedings format when preparing your proposal. Templates for Word, Word Perfect, Latex are available here.

Final report

The report should describe the problem or issue that your project addresses and why it is important. It should describe the work that you have done, and any ideas or insights it is based on. Relevant observations and lessons learnt about the project or any part of it should be included. Finally, the work should be placed into the context of the course and any related work should be sketched briefly. The length should be at least 5 pages.

Please use the ACM SIG Proceedings format when preparing your proposal. Templates for Word, Word Perfect, Latex are available here.

Schedule

Proposals: Due around Week 7
Presentations: Will be held during the week of Monday, April 12, 2021.
Final report: Due on Wednesday, April 21, 2021.

Evaluation

The project is worth 40% of your overall mark in the course with the following breakdown:

Presentation: 14%
Proposal and final report: 13%
Evaluation (i.e., overall difficulity and quality of work carried out): 13%

Presentation schedule

Session 1: Fri, April 16, 10:00 to noon
1. ATM 2.0 (Steph)
2. Treasure hunt (Nisha)
3. Investment simulation with UML-R'Turn (Brennan)
4. What goes up, must come down: elevator simulation (Zitong)
5. Smart homes (Yihao and Yuhao)
6. Exploring the use of DSLs for machine learnnig for network security (Reetam)
Session 2: Fri, April 16, 13:00 to 15:00
1. The iterated prisoner's dilemma (Anthony)
2. Dynamic adaptation of DARTEmu (Kopi)
3. Behaviour Trees (Gabriele)
4. Papyrus-RT-to-RSARTE compatibility (Liam)
5. Validating ML pipelines (Aadi)

Presentation meetings will be held online using MS Teams. Links will be circulated.

Please note:

You are expected to attend the entire session that your presentation is scheduled in. Attendance of other sessions is welcome, but optional.
Please send me your presentation at least 2 hours before the start of the session that your presentation is scheduled in.
Each presentation has a 15 mins slot. Of these 15 mins, 10 mins should be used for the presentation itself, while the remaining 5 mins are for questions and discussion. Please ensure that your presentation does not take longer than 10 mins. If you do take longer, I will have to interrupt you. The 5 mins discussion period will also be used to allow the next speaker to get ready.
The content of each presentation should
- be understandable to the majority of the members in the class,
- explain any background or context information or material necessary to understand or appreciate what you have done,
- summarize what you have done and why it is interesting and worth doing,
- briefly describe how you have done it,
- mention which results you have obtained and what you have learned (e.g., what would you do differently next time?),
- share any additional observations that you feel are relevant or interesting.
The presentation slides should
- be correct, clear, readable and easy to navigate; typically, that means that slides should not contain a lot of text; highlighting of text can be very useful to emphasize key points; diagrams can be very useful to communicate concepts and relationships effectively, and
- support what you say.
The delivery of the presentation should be clear, engaging and easy-to-follow, i.e., try to speak clearly with appropriate pace (i.e., neither too fast, nor too slow).

Last modified: Fri Apr 09 2021 17:54:06