diff --git a/src/how-to-guides/ESL/pdf-generation.md b/src/how-to-guides/ESL/pdf-generation.md index bad374f9db4472b88307daab4438dbd83bac567f..81ed6153538d08f5492c4495af4561cd01006661 100644 --- a/src/how-to-guides/ESL/pdf-generation.md +++ b/src/how-to-guides/ESL/pdf-generation.md @@ -1,7 +1,8 @@ # PDF generation -!!! warning +As mentioned before, not every system engineer you come across will work with ESL. Moreover, establishing a culture change within a company from document-driven-engineering to model-drive-engineering is not a small feat. Therefore, ESL specifications can be converted into seemingly natural language PDF documents. - This content is not fully migrated, yet. Please hop over to this page on - [docs.ratio-case.nl](https://docs.ratio-case.nl/manuals/esl_manual/index.html#generated-documents) - for the source content. +For example, check out the generated PDF document +of the example pump specification. You can add epilogue and prologue chapters written in Markdown to provide additional context with the specification. In this case, an Introduction chapter and a Conclusion chapter is added. + +All other chapters are generated based on the ESL specification. At the start of each of these chapters one can find a component-function-spec multi-domain matrix that shows the dependencies between the components and function-specifications discussed within that chapter. The figures are by definition consistent with the written text. This eliminates inconsistencies between text and dependency figures as often encountered within manually written documents. \ No newline at end of file diff --git a/src/how-to-guides/assets/pump_specification.pdf b/src/how-to-guides/assets/pump_specification.pdf new file mode 100644 index 0000000000000000000000000000000000000000..0e9d8807b286bb84b43c375d38ca22fb139622ed Binary files /dev/null and b/src/how-to-guides/assets/pump_specification.pdf differ