10.LOVEVOL - add own plugins,modules, architecture, ... Example in the Description

1. download: https://workupload.com/file/tsCMJgNXbXa
2. unzip
3. open and start
login: human
password: human

*****************************************************************************************
see example(plugin wrote in c# but You can write in all managed code languages eg. c++,VisualBAsic, c# , ... ):
https://workupload.com/file/pPPkRzN7WUM
*****************************************************************************************

The architecture is enabled ... YOU CAN BUILD OWN APPLICATIONS using it everything is replacable logo, colors, information about , ... EVERYTHING . With the architecture You can build exactly the same modules, plugins You see in the LOVEVOL.

Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.[1][2]

The architecture of a software system is a metaphor, analogous to the architecture of a building.[3] It functions as the blueprints for the system and the development project, which project management can later use to extrapolate the tasks necessary to be executed by the teams and people involved.

Software architecture is about making fundamental structural choices that are costly to change once implemented. Software architecture choices include specific structural options from possibilities in the design of the software.

For example, the systems that controlled the Space Shuttle launch vehicle had the requirement of being very fast and very reliable. Therefore, an appropriate real-time computing language would need to be chosen. Additionally, to satisfy the need for reliability the choice could be made to have multiple redundant and independently produced copies of the program, and to run these copies on independent hardware while cross-checking results.

Documenting software architecture facilitates communication between stakeholders, captures early decisions about the high-level design, and allows reuse of design components between projects.[4]: 29–35 

Software architecture activities
Scope
Opinions vary as to the scope of software architectures:[5]

Macroscopic system structure: this refers to architecture as a higher-level abstraction of a software system that consists of a collection of computational components together with connectors that describe the interaction between these components.[6]
The important stuff—whatever that is: this refers to the fact that software architects should concern themselves with those decisions that have high impact on the system and its stakeholders.[7]
That which is fundamental to understanding a system in its environment[8]
Things that people perceive as hard to change: since designing the architecture takes place at the beginning of a software system's lifecycle, the architect should focus on decisions that "have to" be right the first time. Following this line of thought, architectural design issues may become non-architectural once their irreversibility can be overcome.[7]
A set of architectural design decisions: software architecture should not be considered merely a set of models or structures, but should include the decisions that lead to these particular structures, and the rationale behind them.[9] This insight has led to substantial research into software architecture knowledge management.[10]
There is no sharp distinction between software architecture versus design and requirements engineering (see Related fields below). They are all part of a "chain of intentionality" from high-level intentions to low-level details.[11]: 18