LimeSurvey architecture: Difference between revisions
From LimeSurvey Manual
Line 27: | Line 27: | ||
todo | todo | ||
* Communication | |||
=== Business risk === | === Business risk === |
Revision as of 12:38, 25 August 2021
This is the main public document for LimeSurvey's architecture
Overview
todo, constraints
Vision
todo
Risks
As defined in the code quality guide.
Risk identification, analysis, mitigation, monitor.
Product risk
todo
- Data loss (known or unknown)
- Unauthorized data access
- Blocking bugs (that leads to data loss)
Project risk
todo
- Communication
Business risk
Internal
Quality attributes
Maintainability, easy to deploy, testability
Technology stack
Dependency management, packaging, plugin
todo
Views
4+1 view model?
Domain
A simple domain diagram over LimeSurvey:
Modules
main arch
Flow and state
automata between states
admin flow diagram? what makes sense to document? create survey process?
API design
todo
Security
todo