Documentation_full_en.example.asciidoc 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138
  1. = MYMODULE =
  2. :subtitle: MYMODULE DOCUMENTATION
  3. :source-highlighter: rouge
  4. :companyname: __MYCOMPANY_NAME__
  5. :corpname: __MYCOMPANY_NAME__
  6. :orgname: __MYCOMPANY_NAME__
  7. :creator: __USER_FULLNAME__
  8. :title: Documentation of module MyModule
  9. :subject: This document is the document of module MyModule.
  10. :keywords: __KEYWORDS__
  11. // Date du document :
  12. :docdate: __YYYY-MM-DD__
  13. :toc: manual
  14. :toc-placement: preamble
  15. == TOPIC OF DOCUMENT
  16. This document was build from following input:
  17. * Date 1
  18. ...
  19. * Date 2
  20. ...
  21. The document includes an introductory chapter of functional specifications, presenting the different actors involved in the rebuild of the definitions
  22. of business terms that will be used (some of which may be new or different).
  23. The main following chapter will present the entire process, also known as *uses cases*, according to a principle of a description, in chronological sequence if possible,
  24. to present the actor and the action performed, as in the following example:
  25. * *X* Actor realizes Action A.
  26. * *Y* Actor communicates Info B to Actor *Z*
  27. * *Automaton* performs update of data for...
  28. * Etc ...
  29. Functional requirements are complemented by a chapter of technical requirements.
  30. The chapter on data lists key information specific to Presto that were identified at the time of writing specification. It will be enriched as
  31. iterations occurs.
  32. Finally, in the Appendix, the documents known when writing this document are centralized to illustrate the existing document or inspire the new expected one.
  33. These documents have their content directly integrated in this specification or have a reference to
  34. external documents stored in the *Appendices* directory accompanying this document.
  35. *Log of versions*
  36. [options="header",format="csv"]
  37. |===
  38. Author, Date, Version
  39. --- __USER_FULLNAME__ __USER_EMAIL__ ---, __YYYY-MM-DD__, Version 1.0
  40. |===
  41. <<<
  42. == BUSINESS SPECIFICATIONS - INTRODUCTION
  43. === List of actors [[actors]]
  44. Actors are physical people or moral entities working on at least one process.
  45. The following chart prensts list of actors or partners identified by the project for the defined scope of project. We will use then the name defined into first column to speak about roles in the rest of documents.
  46. [options="header",format="csv"]
  47. |===
  48. Actor/profil/role, Description of role, Access to system or not, Example of actor
  49. Customer Service, Receive and create Sales orders (SO), Yes, Mr Smith
  50. Purchase, Make puchase order (PO), Yes, 5 people
  51. Administrator - IT, Administration of users/groups and IT services, Yes, John Doe
  52. Automaton, Execute automatic data processing, Yes, NA
  53. |===
  54. === Definitions [[definitions]]
  55. To understand the descriptions of the target process, it was necessary to define or redefine some vocabulary concepts. We must see these definitions as defined in the
  56. new system. Indeed, some terms are already being used but have either not a definition in line with standards, or even differs between services. To bring everyone,
  57. and to consolidate the process, these terms are redefined here, and with their definition in the target objective.
  58. *Definition ABC*
  59. ...
  60. *Definition DEF*
  61. ...
  62. [NOTE]
  63. ==============
  64. Important information will be noticed with a notice like this one.
  65. * Main information 1
  66. * Main information 2
  67. ==============
  68. == BUSINESS SPECIFICATION - PROCESS
  69. Specifications were cut into different business process. We call a business process a workflow with a starting situation and ending situation. Between start and end, we will find actions
  70. done by actors to bring the value of the company. This actions are described using the syntax rule:
  71. *Actor X* do action Y, *Actor Z* do action W.
  72. _Each process/use case is described into a separate chapter._
  73. === Use case / Process 1 [[process_1]]
  74. ==== Title and goals
  75. ...
  76. ==== Actors or roles
  77. * Members of group *...*
  78. ==== Standard flow
  79. * Members of Groupe *...*: Do ...
  80. * Members of Groupe *...*: Do ...
  81. * Members of Groupe *...*: Do ...
  82. ==== Alternative flow
  83. * A user without role *...*: Can't do ...
  84. ==== Business rules
  85. * Business rule 1
  86. * Business rule 2