Difference between revisions of "Contensive Library Architecture"
From Contensive Wiki
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
* Separate design from code - so designers and UI/UX professionals can use native tools to create and modify. | * Separate design from code - so designers and UI/UX professionals can use native tools to create and modify. | ||
| − | * Isolate and abstract hardware services - To facilitate mocking for integration testing, to minimize infrastructure lock-in | + | * Isolate and abstract hardware services - To facilitate mocking for unit/integration testing, to minimize infrastructure lock-in. |
* To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence. | * To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence. | ||
* To encourage rapid development by isolating business logic layer | * To encourage rapid development by isolating business logic layer | ||
| Line 10: | Line 10: | ||
For developers, the following diagram outlines the underlying system architecture | For developers, the following diagram outlines the underlying system architecture | ||
| − | [[File: | + | [[File:ContensiveBlockDiagrams.png]] |
Latest revision as of 17:24, 21 December 2016
The Library has the following goals:
- Separate design from code - so designers and UI/UX professionals can use native tools to create and modify.
- Isolate and abstract hardware services - To facilitate mocking for unit/integration testing, to minimize infrastructure lock-in.
- To prevent lock-in to this library by focusing on replaceable modularity - low coupling and high coherence.
- To encourage rapid development by isolating business logic layer
- Facilitate content administration.
For developers, the following diagram outlines the underlying system architecture
