This is an old revision of the document!
PlayGround
Test stuff here.
Welcome to your new DokuWiki
Congratulations, your wiki is now up and running. Here are a few more tips to get you started.
Enjoy your work with DokuWiki,
– the developers
Create your first pages
Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: start.
Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the syntax page.
You might also want to use a sidebar. To create it, just edit the sidebar page. Everything in that page will be shown in a margin column on the side. Read our FAQ on sidebars to learn more.
Please be aware that not all templates support sidebars.
Customize your Wiki
Once you're comfortable with creating and editing pages you might want to have a look at the configuration settings (be sure to login as superuser first).
You may also want to see what plugins and templates are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.
Join the Community
DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the newsletter.
The DokuWiki User Forum is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get support.
Of course we'd be more than happy to have you getting involved with DokuWiki.
Title of the Report
- Author1
- Author2
- Author3
- Author4
Abstract
List of Acronyms
| Acronym | Description |
|---|---|
| CRISP-DM | Cross-Industry Standard Process for Data Mining |
| ISEP | Instituto Superior de Engenharia do Porto |
| MADS4Engineering | Minor in Applied Data Science to Engineering |
Introduction
Project Context
// MADS4Engineering as a project-based learning programme; the real-world challenge; the composition of the team; the relevance of multidisciplinary and intercultural collaboration.//
Challenge and Objectives
Describe very briefly the challenge addressed; main project objective; key expected outcome.
Methodological Overview
Just a paragraph explaining that: Design Thinking supported problem framing and user-centred design; CRISP-DM structured the data science activities; Scrum supported project execution. No methodological details.
Report Structure
| Chapter | Description |
|---|---|
| 1 | … |
| 2 | … |
| 3 | … |
| 4 | … |
| 5 | … |
| 6 | … |
| 7 | … |
| 8 | … |
Methodology
Introduction
Provide here an overview of the contents (structure) of this chapter.
Design Thinking
CRISP-DM
Scrum-Based Development
Summary
Problem Understanding
Introduction
Provide here an overview of the contents (structure) of this chapter.
Challenge Description
Stakeholder Analysis
User Analysis
Requirements
Objectives and Success Criteria
Summary
State of the Art
This chapter provides the reader with the relevant technical-scientific background as well as existing related products and research, also known as the state of the art, in the field(s) of the project.
Introduction
Provide here an overview of the contents (structure) of this chapter.
These are examples of citations to books [(Thapa2019)] and [(Obayashi2020)], a chapter on a smart companion [(Reis2020)], articles on IoT [(Hamza2023)], blimps [(Mahn2006)], cloud computing [(Llorente2009)], gas emissions [(Ranjith2020)], pedestrian crossing behaviour [(Sobhani2018)], smart bicycles [(Lee2018)] and diaper moisture [(Khan2018)], and to Web resources [(android41)], [(cloudexpo2008)] and [(gartner2021)].
Domain Overview
Existing Solutions
Commercial solutions
Open-source solutions
Research prototypes
Compare selected solutions considering the requirements of your own solution
Relevant Technologies and Approaches
Data sources and acquisition
Data analysis and modelling techniques
Data visualisation techniques
UI/UX approaches
Development technologies
Gap Analysis
Summary of limitations of existing solutions
Identified opportunity
Positioning of the proposed solution
Design Implications
Summary
Provide here the conclusions of this chapter and make the bridge to the next chapter.
What did the you learn from the state of the art and how did it influence the proposed solution?
Critical Thinking and Ethical Considerations
Introduction
Provide here an overview of the contents (structure) of this chapter.
Stakeholders and Impact
Identification of affected stakeholders
Expected benefits
Potential risks
Risks and Concerns
Ethical issues
Privacy and security issues
Bias and fairness issues
Sustainability issues and SDG alignment
Applicable regulations
Design Implications
How the identified concerns influenced the design
Requirements derived from ethical and critical thinking considerations
Summary
Provide here the conclusions of this chapter and make the bridge to the next chapter.
Data Understanding
Introduction
Data Sources
Data Quality Assessment
Exploratory Analysis
Data Limitations
Summary
Solution Design
Introduction
Solution Vision
Design Requirements
User Stories
Conceptual Data Model
Information Architecture
UX/UI Design
Summary
Project Management
Provide here an overview of the contents (structure) of this chapter. Explain the project management approach your group followed and justify why you think it is a good approach.
Scope
Document the boundaries of your project. Document the product scope (the extent of what your project will produce) and the project Scope (summary of the work needed to produce it). Make sure you clearly define what is part of the project and what is outside of its scope, justifying as needed.
Time
Explain how you managed the schedule of your project. Document the key milestones of your project, mapping key phases to reference deadlines.
Cost
Describe your project budget and its key components. Explain how your budget was managed throughout the project. Document the planned vs. effective costs of your project.
Quality
Document quality metrics that will apply to your project deliverables, associated thresholds and how they should be reviewed.
People & Stakeholder Management
Enumerate all people relevant to your project, including the project team and key stakeholders. Document their roles and responsibilities. Document your stakeholder management plan and strategy.
Communications
Document how your team will manage communications, describing communication channels, meetings, etc.
Risk
Identify key risks (product and project level), evaluate them and define how they should be handled (responses) and monitored. Perform quantitative and qualitative risk analysis and use the results to define the appropriate risk responses.
Procurement
Document your procurement management strategy including make vs buy decisions, materials/services to be acquired, sources, costs, timings, etc.
Project Plan
Document the project schedule, and the key project phases, using a Gantt Chart. Highlight the key project phases and milestones.
Describe how your plan was mapped to multiple iterative sprints.
Document how the sprint backlog was planned and managed for each of the sprints you have created in Planner.
Describe how prioritization was done.
Document how the estimation process was implemented, and any underlying challenges.
Provide a summary of the sprints that were executed, along with sprint goals.
Sprint Outcomes
Include the outcomes of all sprint reviews (what was the sprint backlog, completion status, planned capacity vs. achieved velocity).
Sprint Evaluations
Include the summary of all the sprint retrospectives, including any actions implemented as part of the team’s continuous improvement strategy.
Summary
Provide here the conclusions of this chapter and make the bridge to the next chapter.
Development
Introduction
Provide here an overview of the contents (structure) of this chapter.
System Architecture
Data Pipeline
Backend Development
Analytics Components
Front-End Development
Integration
Summary
Provide here the conclusions of this chapter and make the bridge to the next chapter.
Evaluation
Introduction
Functional Testing
Usability Testing
Validation Against Requirements
Discussion
Conclusions
Achievements
Discuss here what was achieved (wrt the initial objectives) and what is missing (wrt the initial objectives) of the project.
Limitations
Identify here the limitations of the solution and prototype.
Future Work
Provide here your recommendations for future work.
Acknowledgements
Bibliography
Will be added automatically by citing, in the body of the report, entries specified in BibTeX format and stored in the https://www.mads4e.dee.isep.ipp.pt/doku.php?id=refnotes:bib file
PS - If you have doubts on how to make citations, create captions, insert formulas, etc. visit this page with examples and select “Show pagesource” to see the source code.