A lap 2025. április 2., 10:29-kori változata

This discussion page helps to interpret what should be done in a particular chapter and why...
Final product: https://miau.my-x.hu/mediawiki/index.php/CT_00
History of the final product: https://miau.my-x.hu/mediawiki/index.php?title=CT_00&action=history
History of the discussion page: https://miau.my-x.hu/mediawiki/index.php?title=Vita:CT_00&action=history

Title

Optimization challenge: the better is a title the more is the number of keywords but the less is the length of the text

Subtitle

(a new aspect can be visualized based on the same principle as before in case of the title)

Authors

names (https://orcid.org/...),

Institutions

expected cover-sheet-elements incl. university, department, etc.

Abstract

One-pager-like chapter for conferences (c.f. IKSAD/Türkiye: https://miau.my-x.hu/miau2009/index_en.php3?x=e080). The abstract is not the summary, where citations might quasi only be listed about the most relevant statements of the publication. The abstract should deliver a kind of motivating information package - quasi without any citations: e.g. history of the project, descriptive core information about the problem, own steps and their results, future - maximal one single page.

Chapter#1. Introduction

Between to chapters (e.g. 1. and 1.1.), it is necessary to have explaining texts - mostly about a kind of detailed/specific table of content with argumentations...

Chapter#1.1. Aims/objectives

A final thesis (a publication in general) might not formulate more aims than being really covered through the publication. In order to avoide the suspicions about potential realistic, but not realized aims/objectives, each promise should have a "CHAPTER#..."-sign, where the Readers will be capable of checking the real performaces behind each promise - immediately. These chapter#-signs can be empty, if the whole structure (table of content) is still fluid. But each empty sing should be filled with the appropriate numbers, if the details behind a promise could be formulated as a finally existing subchapter (mostly in chapter#3 - own development).

The aims may only be listed, if the basic definitions are given. The keywords of the (sub)title and each further relevant term should always and immediately be defined after the first using.

It is not forbidden to work with arbitrary high complexity. In this case: the Readers have to understand the XLSX-files before going on...

Important and general rule: if a plural form is used, then it is necessary to present examples: e.g. phylosophycal challenges (e.g. automation, nature/level of vierification), or arbitrary systems (c.f. encryption/decryption tasks for unknown-cyphers) or relevant keywords ... (c.f. concepts, verification, partial log-data) or different steps (task1, task2, task3, task4:interpretation of the hidden file), etc.

Recommended literature about keyhole-challenges: https://miau.my-x.hu/myx-free/index_en.php3?x=fbl, https://miau.my-x.hu/myx-free/index_en.php3?x=iq

Chapter#1.2. Tasks

Rules: The list of the particular tasks should deliver a clear classification of steps without any overlapping effects and/or without any lacks. BTW: this expectation is valid for each lists in general. Tasks are also promises (as aims/objectives), therefore, it is also necessary to have a chapter#-sign for each task. Tasks are decisions of the Author(s), therefore, it is necessary to deliver argumentations for the rationality of these decisions.

Chapter#1.3. Targeted groups

Rules: each potential targeted groups should be listed (see without overlapping and lacks) - and the argumentations must be given: why is a listed element rational? Targeted groups are potential customers, who should be capable of paying for the results of this project based on a real information added-value estimated by the Authors themselfes.

Chapter#1.4. Utilities (estimation of informational added-values)

Rules: For each targeted group should be made an as far as exact estimation in USD or EUR about the information added-value. It is expected, that the estimations are positive values! Negative values means: parasitism through the IT-experts concerning their customers! Estimations have two layers: incomes and costs in the bechmark situation AND incomes and costs based on the results of the projects.

Chapter#1.5. Motivation

Chapter#1.6. About the structure of the publication

Chapter#2. Literature

Chapter#3. Own developments

Chapter#4. Discussions

Chapter#5. Conclusions

Chapter#6. Future

Chapter#7. Summary

Chapter#8. Annexes

Chapter#.8.1. Abbreviations

Chapter#.8.2. Figures

Chapter#.8.3. References

https://miau.my-x.hu/mediawiki/index.php/BPROF_Thesis_Structure / https://miau.my-x.hu/bprof/Deepl%20-%20Thesis%20specialities%20of%20the%20BPROF%20training%20at%20the%20KJE.docx / https://miau.my-x.hu/temp/2025tavasz/?C=M;O=D

@@ 36. sor: / 36. sor: @@
 ==Chapter#1.4. Utilities (estimation of informational added-values)==
-Rules: For each targeted group should be made an as far as exact estimation in USD or EUR about the information added-value. It is expected, that the estimations are positive values!
+Rules: For each targeted group should be made an as far as exact estimation in USD or EUR about the information added-value. It is expected, that the estimations are positive values! Negative values means: parasitism through the IT-experts concerning their customers! Estimations have two layers: incomes and costs in the bechmark situation AND incomes and costs based on the results of the projects.
 ==Chapter#1.5. Motivation==

„Vita:CT 00” változatai közötti eltérés