Skip to content

Latest commit

 

History

History
89 lines (48 loc) · 2.93 KB

ROADMAP.md

File metadata and controls

89 lines (48 loc) · 2.93 KB
Raw

SDEVEN Software Development & Engineering Methodology

Document control

  • updated at: 230810
  • updated by: Petre Iordanescu

Table of contents

[TOC]

ROADMAP

RMAP.004 - convert to Word (docx) format the full document - (temp closed @ 230810)

  • Objective: convert to Word (docx) format the full document
  • Recorded at: 230810
  • Updated at:
    • 230810 [Petre Iordanescu] tested locally, generated DOCX from HTML & PDF ok, resulted document has "protection" footers and banners (ie, undesired, unwanted text) that can be manually dropped or by using a paid license (price magnitude 1.5 - 3 kUSD), genration time ~10sec for source full SDEVEN HTML and ~1min for full SDEVEN PDF
    • 230810 [Petre Iordanescu] resolution: not to be used except a licence is paid by client, can be kept as optional feature included in site generation only with paid license
  • Recorded by: Petre Iordanescu (piu)
  • Detailed description:
    • convert to Word (docx) format the full document
    • Aspose offer multiple variants for output file (doc & docx) - choose the free commercially licensed one
  • Recommendations:
    • use Aspose tool (see refs)
    • make a Python script that is execute after mkdocs build finish execution (in order to have the full doc generated as HTML and PDF)
    • create a script (bash and cmd / bat types) that "integrates" final build (by running Word generator after mkdocs build)
  • Known dependencies: -
  • Assigned to: Petre Iordanescu
  • References & notes:
    • Aspose tool details @ https://pypi.org/project/aspose-words/

Closed and archived issues

Templates & other misc...


## RMAP.item_code - #NOTE...give a hort description name of item

* **Objective:** -#NOTE...the item objective...
* **Recorded at:** -#NOTE...date of recording this item...
* **Updated at**: n/a
* **Recorded by:** -#NOTE...who registered this item - this should identify that person as mail and phone, otherwise these should be written here...
* **Detailed  description:**
    * -#NOTE...here different items of description...
    * -#NOTE...here different items of description...
* **Recommendations:**
    * -#NOTE...here different items of hints / recommendations...
    * -#NOTE...here different items of hints / recommendations...
* **Known dependencies:** -#NOTE...if there are knwon dependencies of INTERNAL system components or other open / wip issues...
* **Assigned to:** -#NOTE...the person nominated to respond for this roadmap item...
* **References & notes:**
    * -#NOTE...more notes... (if use footnote like `[^xxx]: ...`, please do not mark as list entry because will appear at foonotes)