University of London / MSc Computer Science: Project(13〜24 週目)
October 3, 2024
ロンドン大学で MSc Computer Science: Project モジュールを履修中。
講義内容に関して記録した個人的なスタディノートです。
全 24 週のうち 13〜24 週目の内容を記録します。(13 週目開始:2024 年 7 月 8 日 / 12 週目終了:2024 年 10 月 2 日)
Weeks
プロジェクトは他のモジュールの長さ(12 週間)とは異なり、24 週間にわたる内容となっている。
後半 12 週間の各パートの内容は以下の通り。
- Week 13: Starting the development phase
- Week 14: Starting your final report
- Week 15: Developing your analysis
- Week 16: Writing your methodology section
- Week 17: Reviewing your work
- Week 18: Writing up the results of your project
- Week 19: Writing the evaluation and critical evaluation
- Week 20: Writing the conclusion section of your report
- Week 21: Proof reading your project report
- Week 22: Wrapping up your project
- Week 23: Preparation for final project report submission
- Week 24: Preparation for final project report submission
後半 12 週間は自分のプロジェクトの開発と最終レポートの作成が中心となるため、各レクチャーで講義される内容量は控えめ。
Week 13: Starting the development phase #
自分のプロジェクトの実開発を始める、進める際に注意すべき点について一般的な内容の説明。
- Set up your development environment
- Divide and conquer
- Start coding
- Test early and often
- Iterate and improve
- Version control
- Document your work
- Regularly communicate and update
- Deploy and test in production-like environments
- Seek feedback and refine
Week 14: Starting your final report #
プロジェクトレポートを記述する上で、自分のプロジェクトの成果を求める際に、どのように基準をおいてどのようにそれを計測するのかについての説明。
- Define the test objectives
- Identify the testing scope
- Determine test methods
- Define test criteria
- Identify test environment and tools
- Develop test cases and test data
- Prioritrse and schedule test execution
- Execute test cases
- Monitor and track defects
- Analyse test results
- Review and update the test plan
Week 15: Developing your analysis #
前週に引き続き、プロジェクトの成果の分析と評価をレポートに書く際に留意すべき事項などの説明。
- Structure your write-up
- Describe your methodology
- Present your data
- Explain your experiments
- Present your results
- Discuss your findings
- Address limitations
- Relate back to the literary review
- Conclude with implications and future work
Week 16: Writing your methodology section #
Considering your approach
- Problem statement
- Data collection
- Experimental setup
- Algorithms or techniques
- Parameters and configuration
- Experimental design
- Evaluation metrics
- Ethical considerations
- Software and tools
- Validation and verification
- Limitations
Week 17: Reviewing your work #
Reviewing the work completed so far
- Actual versus planned progress
- Monitor time and effort
- Regularly review and reflect
- Test and validate
Looking at the structure of your report
- Structure and presentation of your report
- Core reading
- Advice from others
Week 18: Writing up the results of your project #
- Present your results
- Discuss your finding
- Address limitations
- Relate back to the literary review
- Conclude with implications and future work
Week 19: Writing the evaluation and critical evaluation #
- Evaluation
- Critical evaluation
Week 20: Writing the conclusion section of your report #
- Recap on the objectives
- Summarise the results
- Evaluate the success
- Discuss the contributions
- Limitations and future work
- Reflect on lessons learnt
- Emphasise the impact
- Strong statement
Week 21: Proof reading your project report #
Proof reading
- How clear and concise is each section of your report?
- It is well structured and presented?
- Spelling, grammar, and typos.
Week 22: Wrapping up your project #
Producing your demonstration video
- Plan and script
- Set up the environment
- Capture the screen
- Demonstrate key features
- Provide context and narration
- Edit the video
- Polish and finalise
Wrapping up your project
- Review and validate
- Documentation
- Clean up and refactoring
- Testing and bug fixing
- Finalise report
- Backup and version control
- Project handover
- Celebrate and recognise
- Future plans and dissemination
Week 23, 24 #
プロジェクト最終報告書を作成、提出する期間。5,000〜7,000 ワードで作成する。さらに、開発した成果物のデモ動画を目安3分ほど撮影して提出する。ただしデモ動画は採点対象外のため気軽に作れば良いとのこと。
About a demonstration video
It is not really an oral presentation as you would have with a viva, it really is just a case of demoing your software to show it working in the wild. It will not be graded, and can be as simple as pointing you mobile phone at the screen, or using desktop screen recording software.