| Both sides previous revision Previous revision | |
| report:eth [2026/05/20 03:01] – [6.1 Engineering Ethics] team1 | report:eth [2026/05/20 03:12] (current) – [6.5 Summary] team1 |
|---|
| ==== 6.5 Summary ==== | ==== 6.5 Summary ==== |
| |
| This chapter looked at the main ethical and deontological issues related to Screen2Green, such as safety, user privacy, behaviour design, environmental impact, plant welfare, and liability. Through this analysis, the team understood that the system should not only work properly, but also be safe, clear to users, and responsible in the way it affects both people and plants. | This chapter looked at the main ethical and deontological issues related to Screen2Green, such as safety, user privacy, behavior design, environmental impact, plant welfare, and liability. Through this analysis, the team understood that the system should not only work properly, but also be safe, clear to users, and responsible in the way it affects both people and plants. |
| |
| Based on this ethical and deontological analysis, the team chose a modular design with simple monitoring components, a soil moisture sensor, an ESP32 microcontroller, a controlled watering system, waterproof protection, and low-cost recyclable materials. These choices were made to reduce possible risks, protect plant health, support responsible data use, and make the product easier to maintain. | Based on this ethical and deontological analysis, the team chose a modular design with simple monitoring components, a soil moisture sensor, an ESP32 microcontroller, a controlled watering system, waterproof protection, and low-cost recyclable materials. These choices were made to reduce possible risks, protect plant health, support responsible data use, and make the product easier to maintain. |
| |
| Consequently, the team decided to include features such as safe watering limits, basic fail-safe protection, clear user information, modular parts, and behaviour feedback that supports users without creating pressure. These features help make the system safer, easier to use, and more suitable for daily use. | Consequently, the team decided to include features such as safe watering limits, basic fail-safe protection, clear user information, modular parts, and behavior feedback that supports users without creating pressure. These features help make the system safer, easier to use, and more suitable for daily use. |
| |
| This chapter also helped guide the team’s technical decisions and gives a clear basis for the next chapter, which explains how these ideas were applied in the system design and development process. | This chapter also helped guide the team’s technical decisions and gives a clear basis for the next chapter, which explains how these ideas were applied in the system design and development process. |
| |
| |