| 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 |
// MADS4Engineering as a project-based learning programme; the real-world challenge; the composition of the team; the relevance of multidisciplinary and intercultural collaboration.//
Describe very briefly the challenge addressed; main project objective; key expected outcome.
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.
| Chapter | Description |
|---|---|
| 1 | … |
| 2 | … |
| 3 | … |
| 4 | … |
| 5 | … |
| 6 | … |
| 7 | … |
| 8 | … |
Provide here an overview of the contents (structure) of this chapter.
Provide here an overview of the contents (structure) of this chapter.
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.
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)].
Commercial solutions
Open-source solutions
Research prototypes
Compare selected solutions considering the requirements of your own solution
Data sources and acquisition
Data analysis and modelling techniques
Data visualisation techniques
UI/UX approaches
Development technologies
Summary of limitations of existing solutions
Identified opportunity
Positioning of the proposed solution
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?
Provide here an overview of the contents (structure) of this chapter.
Identification of affected stakeholders
Expected benefits
Potential risks
Ethical issues
Privacy and security issues
Bias and fairness issues
Sustainability issues and SDG alignment
Applicable regulations
How the identified concerns influenced the design
Requirements derived from ethical and critical thinking considerations
Provide here the conclusions of this chapter and make the bridge to the next chapter.
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.
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.
Explain how you managed the schedule of your project. Document the key milestones of your project, mapping key phases to reference deadlines.
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.
Document quality metrics that will apply to your project deliverables, associated thresholds and how they should be reviewed.
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.
Document how your team will manage communications, describing communication channels, meetings, etc.
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.
Document your procurement management strategy including make vs buy decisions, materials/services to be acquired, sources, costs, timings, etc.
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.
Include the outcomes of all sprint reviews (what was the sprint backlog, completion status, planned capacity vs. achieved velocity).
Include the summary of all the sprint retrospectives, including any actions implemented as part of the team’s continuous improvement strategy.
Provide here the conclusions of this chapter and make the bridge to the next chapter.
Provide here an overview of the contents (structure) of this chapter.
Provide here the conclusions of this chapter and make the bridge to the next chapter.
Discuss here what was achieved (wrt the initial objectives) and what is missing (wrt the initial objectives) of the project.
Identify here the limitations of the solution and prototype.
Provide here your recommendations for future work.
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.