|
Size: 528
Comment:
|
Size: 1741
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| Line 12: | Line 13: |
== Association Model == Association components: * Development * Operation * Support * Maintenance LibIndSys should be centred around development of systems, mostly systems that integrates with third-part. These systems may be taken into operation, be maintained, and support for further development given. Typically development should lead quickly to an operational prototype or pilot system, for which support and development will evolve it into an integral system at the industrial partner site. Gradually, responsability for the system will be offloaded to the industrial partner. Especially the responsability for operation and maintenance should be entirely offloaded during a limited period of time. Whether responsability for support and further development may be offloaded entirely, or to what degree and over how long a period it may be offloaded, depends highly on the commitment of and develpment of skills at the industrial partner in relation to the complexity of the system. All engagements must take its offspring from some development and some code base manifested in LibIndSys. LibIndSys should not purely deliver or operate third-part systems. == Ownership == |
Purpose
- Development of industrial software systems based on libre and free 3rd party software
- Operating and further developing such running systems
- Helping local companies in achieving the skill and experience to run and further develop such systems
DevOps
A modern and reliable paradigm for LibIndSys to succeed would be DevOps: https://en.wikipedia.org/wiki/DevOps
This may ensure that the personnel operations are also involved with development of the system and routines, and vice versa.
Association Model
Association components:
- Development
- Operation
- Support
- Maintenance
LibIndSys should be centred around development of systems, mostly systems that integrates with third-part. These systems may be taken into operation, be maintained, and support for further development given. Typically development should lead quickly to an operational prototype or pilot system, for which support and development will evolve it into an integral system at the industrial partner site.
Gradually, responsability for the system will be offloaded to the industrial partner. Especially the responsability for operation and maintenance should be entirely offloaded during a limited period of time. Whether responsability for support and further development may be offloaded entirely, or to what degree and over how long a period it may be offloaded, depends highly on the commitment of and develpment of skills at the industrial partner in relation to the complexity of the system.
All engagements must take its offspring from some development and some code base manifested in LibIndSys. LibIndSys should not purely deliver or operate third-part systems.