isaqb-org / glossary Goto Github PK

• Dropbox: done
• Github: ID fehlt
• Leanpub: ID fehlt

Carola, your bio is still missing...

To give more structure to the terms, add categories, for example:

• design-principle
• design-pattern
• architecture-pattern
• ddd (for advanced-level module)
• improve (for advanced-level module "improve")
• foundation
• advanced (generic for CPSA-Advanced modules)
  • advanced-improve
  • advanced-ddd
• advanced...
• ...

These are "leftovers" from the previous esa42 version of this glossary

the docu in the github readme is sufficient, but should be referenced from within the book...

• split the file into some smaller units...
• add those to Book.txt

the current leanpub markdown does not support that - therefore we might need to switch to Markua dialect... somebody should try that...

the JSON format is not interesting for glossary readers, only for authors...

therefore it should not be moved from book to readme.md ...

Phillip, your profile has only a title...

to have a dummy, I added the German version of our mutual OOP presentation...

add the central definitions from ADOK, such as: documentation, document, notation, artifact, view, technical concept, modeling tool, drawing tool, documentation repository, document generator, tool chain, review, checklist, catalog of questions, author, reviewer, moderator.

many terms from the advanced-curricula should be included -
eventually with back-references to the modules...

Hello everybody – there is a strange warning caused by my latest edits which I can't really understand.

Do you have any pointers on what might have gone wrong? Or where I could find warning messages from the lean-pub build?

Translator needs to redirect to distinct output files instead of stdout...

Kanban is not an agile method that requires an iterative incremental approach – it is a process optimization method wich can be used in iterative and incremental approachess.

e.g.: If term has multiple meanings, those shall be representat as a list (not just comma-separated strings)

Bettina Tacke advised to include:
https://intern.isaqb.org/index.php/%C3%9Cbersetzung

im github /marketing/pressemitteilung liegt ein Entwurf, den Frau Marx als docx zurück benötigt.

Term "round trip engineering":

In my personal opinion, it does not work in practical situations, only in hello-world-like scenarios.

As the book has multiple authors, it should be made clear whose opinion it is. (A few years ago, I was of the same opinion. Recently I have seen code that originated from DDD where reverse engineering did indeed work).

rev history is already in git... imho only interesting for authors

ensure that the keywords (highlighted in pdf) are included in translation table

especially the contributors of the (original, early...) iSAQB glossary, Uli Becker and Phillip Ghadir (and whoever contributed there)

https://leanpub.com/isaqbglossary/read shows the glossary terms in VERY small font...

Uli - please add some lines about yourself...

in file appendix/2-about-the-authors...

you might add an image too...

in directory hierarchy, so gradle-run becomes startable from root directory.

Terms from the IMPROVE module should also be included in the glossary IMHO

mit grammarly.com...

for example:

https://leanpub.com/isaqbglossary/read#term-context

to enable such links, a
{#term-XYZ}
needs to be included in the line above the term...

so we have an iSAQB-wide reference translation

Currently, only German (DE) and English (EN) should be neccessary -
and not for every glossary entry...

including image and short text.

so the EN-terms become links to their descriptions ...

Even though it is the glossary for the terms used in context with the isaqb, isaqb itself should also have an entry in the glossary itself so it can be found there

how can potential contributors open issues or improvements?