System Transparency
[Version 0.9 - alpha]
Mastering Complex Systems
- Nontransparent [closed source projects]
- Difficult Barrier Identification
- Difficult Efficiency Management
- Inpossible Public System Analysis
- Reduced System Evolution Rate
- Difficult Barrier Identification
- Transparent [open source projects]
- Simple Barrier Identification
- Simplified Efficiency Management
- Possible Public System Analysis
- Increased System Evolution Rate
The Lost Open Source Benefit
- Open Source is theoretically transparent
- This is could be abenefit
- Practice is different
- The Open Source Contradiction
- Practice is different
- This is could be abenefit
Example
| Manual Process | Automated Process | SW Functionality |
| 1st.txt | prepare.py | egg-extension metadata |
| include note about prepare.py | include note about need to move to functionality | patch/alteration |
| point to prepare.py | point to functionality extension | point back to automation |
Non provided transparency is a barrier to evolution
Action
- Action, applied base on
- Rule, defined based on
- Cause, detected based on
- Trigger, activated based on
- Facts