-
Notifications
You must be signed in to change notification settings - Fork 4
Risk
Charles Eimer edited this page Apr 10, 2025
·
44 revisions
Integration challenges upon integrating new system components to the existing Smartess mobile infrastructure and hardware
- In order to mitigate this, testing newly developed features early and regularly upon their integration mitigates potential integration conflicts.
- Mitigated through: Incremental development
- Mitigated through: Logging
- Mitigated through: Logging Library
- Mitigated through: Containerization
- Mitigated through: Vercel Integration for Continuous Deployment
- Mitigated through: CI Pipelines
User Data, authentification when handling sensitive user data.
- In order to mitigate this, implementing stringent security mechanism to ensure protection of user data
- In order to mitigate this, ensuring proper user authentication in determining user access to critical data.
- Mitigated through: User Authentification
- Mitigated through: local .envr file in which data is not directly embedded on codebase (version control)
Requirements misinterpretation with stakeholders leading to the development of features that don't agree with requirements.
- In order to mitigate this, regularly engaging with stakeholders in requirements gathering, validation, sprint planning and refinements.
- The initial scope for each feature will be smaller and increase as knowledge is gained on requirements and features delivery.
-
Mitigated through: Continuous stakeholder / team communication and feature planning
-
Mitigated through: [Continuous Testing Front-End and Back-end Testing with a goal of 50% coverage - Overall 90% achieved]
-
Front-end Testing Results
- Back-end Testing Results