# Student Notes (Project) Few notes to help you get started with the project * On the project system put a starting title/description * Create a GitHub repository for your project * Add a readme to the repository * Keep a record of your weekly activities (log) on your repository * Invite your supervisor to the repository (e.g., bkenwright) * Include your project repository link at the end of the project description (project.hw.ac.uk) * Look into 'overleaf' - use to manage the report (easier to maintain a complex technical document vs using word) **Dissetation Template** > https://www.overleaf.com/read/tfpkgnzrfnpk # Planning (Weekly Meetings) * Try and organise your weekly tasks * Keep a record of what you did, what you're doing now and what you're going to do in the future (e.g., GitHub wiki) ## For example > *Week 2* Project Planning and Kickoff 1. Define outline for project objectives and goals. 2. Conduct initial research to understand the project topic. 3. Create a project timeline with milestones. 4. Identify the resources needed (books, software, equipment). 5. Meet with the project supervisor to discuss the plan. > *Week 3* * Review literature (take notes) * Update aims & objectives * Develop project questions (what questions will this project answer?) * Confirm meeting dates with supervisor * Send supervisor link to the details > *Week 4* * Expand literature review (not just gathering research papers and articles, but starting to explain/discuss/write). * Create a bibliography of the sources you plan to use. * Begin summarizing key findings from the literature (topic landscape). > *Week 5* * First draft of the project plan (rough ideas of the direction/focus) * Draft outline of the abstract (200ish words) - rough version to help clarify the project * Update title/abstract on the project system > If the project needs data - data collection * Begin data collection if your project involves experiments, surveys, or data analysis. * Review ethical considerations if applicable. * Analyzing collected data. * Visualize/verify the data is suitable? Such as graphs, charts, or tables to present preliminary results (suitable for this project). * Revise the literature review based on new findings. * Discuss initial findings with your supervisor. Week 6: Methodology and Design 1. Refine your research methodology if needed. 2. Update your project plan to reflect any changes. 3. Continue data analysis. 4. Identify any potential challenges or obstacles. > *Week 7* * Submit ethics form * Plan the structure of the literature review chapter * ... > *Week 8* * Organise the structure of the D1 report (get template and add chapters for each section) - start thinking about writing the report * ... etc ---------- Try and share an online link with your supervisor - easier to manage and helps us both see project details (past/current/future) - especially for the meetings. If you use hackmd.io, you can create seperate pages for different details (e.g., task page, draft notes, etc - easier to maintain and share) ---------- ## Common questions/things to think about: * Why is this project important? * What has been done before? * What gaps/limitations/challenges are there? * What method/tests/experiments will you do? * What data/tools/software/hardware will you need? * What results/data will you get/generate? * How will you analyse/present/evaluate your data/results? ---------- Setup other online systems to store/track your project resources (papers/code/data/results/....) [BK2021] ---------- ## Literature Some ideas to help you manage your background/literature review. Often it can be daunting reading/searching/understanding the vast volume of literature around any subject - there are often tens of thousands of articles - hence, you should try and break down the problem and use the various tools and resources available to you, to make the task more managable, such as: * Comparison grid * Timeline plot * Citation metrics (which papers have been mentioned/referred to the most) * Mind-maps (show overlap/connections) * Hierarchy diagram * ... Think critically when reviewing the literature, gaps or innovations, differences between techniques and so on. --------- First submission, you'll include: * Project details * Aims/Objectives * Gantt Chart (show project planning/management) * Literature Review * Ethics (PLES - Professional, Legal, Ethical and Social) * Method (details for any testing, results, evaluation) Remember, you should 'explain' information, that is, don't just put a chart and expect the reader to understand why/what. --------- Example of a GitHub repository structure for managing/tracking your project (regularly updated and maintained) project-name/ ├── README.md # Project README file ├── LICENSE # License information ├── .gitignore # Git ignore file ├── docs/ # Documentation directory │ └── wiki/ # Wiki section │ ├── Home.md # Home page for the wiki │ ├── Week2.md # Tasks/details for week 2 │ ├── Week3.md # ... │ ├── FAQ.md # Frequently Asked Questions │ └── ... # Additional wiki pages ├── data/ # Data directory │ ├── raw/ # Raw data files │ ├── processed/ # Processed data files │ ├── external/ # External data sources (optional) │ └── README.md # Data directory README ├── src/ # Source code directory │ ├── app/ # Application code │ ├── scripts/ # Utility scripts │ └── tests/ # Unit tests ├── requirements.txt # Python dependencies Weekly wiki/log: * Progress details * Tasks * Issues and challenges -------- ## Literature Review Techniques Developing the literature review chapter can be dauting, to help you on this journey, I've provides a list of techniques that you might use to develop and structure your chapter (depend on your topic/questions). - **Traditional Approaches** - Narrative Review - Systematic Review - Qualitative Systematic Review - Quantitative Systematic Review - Meta-Analysis - Fixed-Effect Meta-Analysis - Random-Effects Meta-Analysis - **Conceptual Frameworks** - Conceptual Synthesis - Concept Mapping - Spider Concept Mapping - Conceptual Diagram Mapping - Conceptual Framework Analysis - **Visualization Tools** - Mind Map - Tree Mind Map - Flowchart Mind Map - Concept Map - Spider Concept Map - Hierarchy Concept Map - Taxonomy - Hierarchical Taxonomy - Faceted Taxonomy - **Data Analysis Techniques** - Content Analysis - Deductive Content Analysis - Inductive Content Analysis - Thematic Analysis - Pattern-Based Thematic Analysis - Framework-Based Thematic Analysis - Discourse Analysis - Critical Discourse Analysis - Foucauldian Discourse Analysis - **Comparative Methods** - Comparison Grid - Comparative Framework - Qualitative Comparative Analysis (QCA) - Quantitative Comparative Analysis (QCA) - Comparative Analysis - **Bibliometric Analysis** - Citation Analysis - Co-citation Analysis - Bibliographic Coupling - Authorship Analysis - Collaboration Network Analysis - Author Impact Analysis - Scoping Review - Rapid Review - Integrative Review - Realist Review - Framework Synthesis --------- Keeping track of the references/details References [BK2021] Title, Conference, Year, Author, Link, ..