Documentation is pain, but we need reference points and common grounds.
Historically Arrowhead had various types of documents - Definitions, Cookbook, then the types according to the documentations structure SoSD(D), SysD(D), SD, IDD, CP, SP. We had generic reference examples/descriptors to these.
The current common ground is the Generic SoSD (GSoSD), the Concepts Reference, and the Foundational Principles.
These are generic Arrowhead documents by Arrowhead Core Experts.
Domain engineers and experts still have to create SoSD, SysD, SD and IDD documents and grow the Arrowhead capable universe of SoSs, systems and services.
Beside the GSoSD, Concepts Reference, and the Foundational Principles, it makes sense to provide common, generic specs as:
- Example SoSD, SysD, SD and IDD documents
- A one-pager on how to make the (basic) Arrowhead Reference implementation run in a new environment is less than 30 minutes.
- Application System Skeleton
- Arrowhead Reference Implementation message sequences and APIs
- ... further ideas and detailed content is the discussion topic of this issue
Documentation is pain, but we need reference points and common grounds.
Historically Arrowhead had various types of documents - Definitions, Cookbook, then the types according to the documentations structure SoSD(D), SysD(D), SD, IDD, CP, SP. We had generic reference examples/descriptors to these.
The current common ground is the Generic SoSD (GSoSD), the Concepts Reference, and the Foundational Principles.
These are generic Arrowhead documents by Arrowhead Core Experts.
Domain engineers and experts still have to create SoSD, SysD, SD and IDD documents and grow the Arrowhead capable universe of SoSs, systems and services.
Beside the GSoSD, Concepts Reference, and the Foundational Principles, it makes sense to provide common, generic specs as: