Enhancing Wireless Charging Architecture: QA Considerations for Safety and Performance
In our analysis of wireless charging architecture, we highlight two fundamental structures: the feedback control loop and dynamic service discovery. We aim to revisit the QA decisions for these elements, emphasizing QA priorities including safety, availability, and performance. A significant safety risk is overheating of the coil, potentially leading to fire. We propose a feedback control loop to monitor electricity flow and mitigate overheating risks. Additionally, while service-oriented architecture (SOA) enables flexibility, dynamic discovery poses safety challenges, advocating for a local registry approach to enhance security.
Enhancing Wireless Charging Architecture: QA Considerations for Safety and Performance
E N D
Presentation Transcript
CPSC 875 John D. McGregor Quality Attribute Design
We have identified 2 major structures in the wireless charging architecture. • We skipped over the QA reasons for these structures so I want to revisit those decisions.
2 major elements • Feedback control loop • Dynamic service discovery
QA priorities for wireless charging • Safety • Availability • Efficient (performance) • Flexibility • Modifiable • Security
Major risk • Overheating of the coil is a major risk to safety. • If not regulated there is a high probability of overheating. • If it overheats, the consequences are a fire which destroys the vehicle. • We can’t reduce the fire risk so we try to reduce the probability by controlling the flow of electricity.
Feedback Control loop • The feedback control loop style monitors the flow of electricity and can keep it within range. • This style reduces the probability of overheating. • Must be able to adjust System faster than the System can change its output Monitor Control System
Service Oriented • The service oriented style provides flexibility due to the ease with which a new service can replace an existing one. • However, dynamic discovery is too error prone for a real-time system. • This is a safety concern and an availability concern. • Use SOA but not dynamic discovery; have a local registry
What’s next • Security