LimeSurvey architecture: Difference between revisions
From LimeSurvey Manual
(→Views) |
|||
| Line 11: | Line 11: | ||
== Domain model == | == Domain model == | ||
A simple domain diagram over LimeSurvey: | |||
[[File:ls_domain.png]] | |||
[https://drive.google.com/file/d/0B2zfh04EPg7FWkpnRk1qNXZYRVk/view?usp=sharing Source]. | |||
== Risks == | == Risks == | ||
Revision as of 12:35, 25 August 2021
This is the main public document for LimeSurvey's architecture
Overview
todo, constraints
Vision
todo
Domain model
A simple domain diagram over LimeSurvey:
Risks
As defined in the code quality guide.
Risk identification, analysis, mitigation, monitor.
Product risk
todo
Project risk
todo
Business risk
Internal
Quality attributes
Maintainability, easy to deploy, testability
Technology stack
Dependency management, packaging, plugin
todo
Views
4+1 view model?
Domain
todo
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