FR2527808A1 - METHOD AND DEVICE FOR DOCUMENTATION IN A COMPUTER SYSTEM - Google Patents

Abstract

THE INVENTION CONCERNS COMPUTER SYSTEMS. USERS OF A DOCUMENTATION SERVICE IN CONNECTED MODE IN A COMPUTER SYSTEM HAVE THE POSSIBILITY TO SPECIFY CHANGES TO BE MADE TO THE NORMAL DOCUMENTATION THAT THE SYSTEM MAY ELSEWHERE PROVIDE. FOR THIS PURPOSE, IN RESPONSE TO A REQUEST FOR DOCUMENTATION ISSUED BY A USER, AN APPROPRIATE PROGRAM EXAMINES AND BREAKS UP A REGISTRATION OF THE CORRESPONDING SYSTEM 801, EXAMINES AND COMPOSES A CORRESPONDING RECORD PREVIOUSLY DEFINED BY THE USER 803, AND MAKES THE MODIFICATIONS 'SYSTEM REGISTRATION, TO PRESENT PERSONALIZED DOCUMENTATION TO THE USER. APPLICATION TO DATA BANKS.

Description

Computer systems often include a service program of

  connected-mode documentation, whereby users can have various kinds of information about the system, in response to the issuance of documentation or "support" commands. For example, a user could issue a documentation order such as that ASSISTANCE TERME = INVOICING IDENTIFIER, and the

  system would respond to that order by providing the user

  on its terminal, documentation concerning the meaning of the

  the term "billing identifier" as part of its use in the system The user could also issue a documentation order such as ASSISTANCE ORDER = CALL, and the system would provide in response documentation of how the order "call" must be used Another possibility is a documentation order such as ASSISTANCE ERROR = E NOT FOUND,

  the system responds by providing documentation

  surrounding the error whose mnemonic code is EPASTROUVE.

  In the past, this type of documentation has been

  nor entirely from the inside of the system, ie by

  the designers of the system However, in accordance with

  users of a computer system offering a

  documentation service in connected mode are given the possibility

  to define a specific documentation of the use of

  "for a particular documentation order, specifying changes to be made to the" system documentation "for that order, ie the documentation that would otherwise be provided by the system (The term" user "is used here in a sense that includes not only one person, but also a set of people, such as those who access the system under a particular account number) It is obviously necessary that the documentation

  the system remains intact, so that it can be communicated

  other users, either in its original form,

  in a form modified by such other users.

  In preferred embodiments, this is achieved by maintaining one or more documentation files of the

  system and, in addition, one or more document

  user for each user who wishes to

  the possibility of specific documentation of the use

  In particular, the system files contain

  the system documentation The user files

  keep documentation texts provided by the user.

  with instructions on how to use

  these texts to modify the documentation of the system Other-

  In other words, the user files contain

  the difference between the specific documentation of the user and the documentation of the system

  are associated with one or more orders of documentation.

  When the user issues a particular documentation order

  link, the system accesses the system documentation files.

  and the user documentation files, depending on the

  requirements, and provides the specific documentation of

the appropriate user.

  The invention will be better understood on reading the

  description that follows of an embodiment and in

  with reference to the accompanying drawings, in which: FIG. 1 is a block diagram of a data processing / transmission system in which the invention

is used; -

  Figure 2 is a block diagram of a node

  with several computers, in the system of FIG.

  FIG. 3 shows a software package which is executed in the node of FIG. 2 and which comprises a connected mode documentation service implementing the principles of the invention. FIG. 4 shows parts of the memory areas.

  of the user database and the system that are

  served in the node of Figure 2; Figure 5 shows the format of system documentation records that are stored in the system memory area; Figure 6 shows the format of user documentation records that are kept in the user memory area

  Figures 7 to 9 are flow diagrams of the program

  nie of documentation service on connected mode; and

  Figure 10 shows lists of records from

  system, user and output that are produced by the

  connected Inode documentation service program,

execution.

  Table I below shows the documentation of the

  system which is returned to a user of the computer system.

  Figure 1 in response to the order of documentation

ASSISTANCE ORDER = CALL.

Table I

CALL

USE*

PSGP PROGRAM

call (asr =) / asr / (mode = / mode /)

EXPLANATION

  The "call" command causes the named program to run.

ARGUMENTS

ASR:

  The program installed at the given ASR is executed.

FASHION:

  The terminal mode is changed to the

  before the program is run The mode can be one of the following: common, transparent, or class-specific. According to the invention, the users of the

  system have the possibility of defining a specific documentation

  for a documentation order, specify modifications to be made to the system documentation, that is, to the documentation that would otherwise be provided by the system in response to the documentation order considered, for example Table II shows a version of the system documentation presented in Table I, as modified by a user to provide "user-specific" documentation for the calling order.

Table II

** CALL **

* USE *

  call <Network Standard Address> (mode = common or specific to a class>)

* EXPLANATION *

  Programs are "named" by a Standard Address of

  Network (ASR) with 10 digits The "call" command causes the execution

the named program.

* ARGUMENTS *

ASR:

  The program installed at the given ASR is executed.

  MODE: The terminal mode is changed to match the specified value, before running the program. The mode can be one of the following: common, transparent, or class-specific The "transparent" mode is not supported

  currently and should not be used.

* EXAMPLE *

  call 0451271234 mode = class-specific This command would call the Standard Control Program by the User and place your terminal in the mode

"class specific".

  It should be noted that the heading "use" has been replaced

  placed, a sentence has been added at the beginning of the section

  "explanation", a sentence was added at the end of the

  as "arguments", and a new topic, "example", has been added. Figure 1 illustrates a system in which the invention is used. The system provides an integrated data processing / transmission service to a set of clients and includes a number of nodes that are located in the premises of the service provider. the heart of each node are one or more computers, as described

  hereinafter A set of data terminals 10a and computers

  main drivers, lob, are connected to the nodes 10 by

  appropriate data lines Most terminals and main computers belong to

  customers are on their premises.

  some belong to the supplier and are used by

  example, for the management of the system The nodes 10 communicating

  The nodes are connected to the network by respective links 11 which carry data at 56 kbit / s, using a protocol conforming to the X.25 standard of the CCITT. Various nodes can be specialized for

  specific functions, such as billing,

  service, maintenance, etc. The transmission service provides customers with a number of possibilities These include running time-sharing application programs

  provided by the supplier and by the customers and recorded

  very in the knots; the recording of customer data in databases stored in the nodes

  support for "functional blocks" of software

  to be called by client programs, which provide

  services such as publishing, order interpretation, print generation, etc .; a possibility of distributed treatment according to which treatments in progress

  execution at various nodes can communicate, respecting

  critical weather conditions, with

  running at other nodes; and a service

  recording and routing of messages.

  Figure 2 is a block diagram of the one

  The node includes as an example two node processors, 20, and a database processor 26. As an example, each of these processors is

  a VAX 11/780 computer from Digital Equipment Corp.

  (DEC) operating under the control of the VMS operating system, provided by DEC The node includes in

  in addition to a spare VAX 11/780 processor,

  28, which can take the place of the database processor or one of the node processors. Other nodes

  (Figure 1) may have more or less than two processes

  nodes, depending on the demand for pre-treatment

  The communication between the processors is provided by a bus 25 which, by way of example, is a PCL bus (link

  parallel communication), provided by DEC.

  Mass memory units 21, for example with disks, are associated with each node processor and mass memory units 27 are associated with the database processor 26 The accesses of the mass memory units 27 are doubled, allowing the spare processor 28 to access these units Universal input-output (I / O) devices 29, for example with a CRT, are

  associated with each of the four processors.

  There is also at least one management processor

  lines 22 associated with each node processor, which establishes an interface between the node processor on the one hand,

  and the terminals Oa and the main computers.

  on the other hand The line management processors 22

  examples of this are IBM Series / i-based computers.

  under the control of RPS operating system, provided by IBM Each line management processor communicates

  with the respective node processor using a protocol

  The microprograms supplied by DEC, controlling a microprocessor 23 provided by DEC, perform the DTE function in the level 2 (the "link" level) of the protocol. Another microprocessor 24 associated with each node processor

  fulfills a similar function with regard to trans-

  missions with the protocol X 25 on the link 11.

  The node processors 20 have the function of executing programs on behalf of the clients and the provider. For this purpose, the mass memory units 21 associated with each processor are used essentially, if not exclusively, to assist the processing in progress in the considered processor Almost all the data,

  programs and other files, both those

  to the customer that those belonging to the supplier, are

  recorded in a database contained in the provisions of

  The purpose of the latter is to manage the database and to allow access to it.

node processors.

  Figure 3 shows the structure of a typical application package provided by the vendor, which

  calls the Message Application Package (PAM) This program

  software provides the user with services such as

  text, the possibility of creating and

  and various services related to the database.

  The MAP includes a main program 31 which is linked to a number of utilities which are called by the main program in the form of these subprograms.

  Utilities include Publisher 32, which provides the possibility

  text editing facility; The utility of obtaining / fixing

  parameter setting, 33, which allows the user to obtain

  nir and fix various parameters associated with its terminal the command parsing utility, 34, which accepts a command line from the user, identifies the

  order (eg "call" or "assistance"), the conversion

  in an internal form, and presents the arguments in a form suitable for the utility to which the order

  to be transmitted; the menu service program 35, which pre-

  various selection menus to the user and, depending on the

  selection or selections of the user, pre-

  feels additional menus or produces some action on behalf of the user; and the Connected Mode Documentation Service Program 36, which

  implement the principles of the invention.

  Among other software packages provided by the provider and made available to users (but not shown in the drawing), include, as an example, a Standard Software Package by the User (PSCU) that provides the user a means to perform such functions

  that the validation and invalidation of programs and

  your; and a Standard Settings Management Software Package

  (PSGP), which provides a function similar to that of using

  of obtaining / setting parameters for a position, 33. Each of these packages is linked to a respective set of

  utilities including, in each case, a form of

  documentation service gram in online mode, 36.

  The registration area in the database is of two types: the system registration area and the

  user registration area As shown in the figure

  re 4, the system registration area, 40, includes

  For example, a number of documentary files

  400 files are represented explicitly

  These are 401, 402 and 403 documentation files, 404 glossary file and 405 error documentation file. Files 401, 402 and 403 consist of records and each of them contains a documentation of the system regarding a particular order

  recognized respectively by PAM, PSCU and PSGP.

  Each of the records constituting the glossary file

  re 404 contains the definition of a particular term used in the system Each of the records constituting the error file 405 contains information concerning a particular error or warning condition detected by the system and reported back to the user while

  the execution of any of the packages.

  A different registration area is established for each user in the database, and Figure 4 shows a user registration area 45 which is

  associated with a particular user In accordance with the

  the user registration area 45 includes user documentation files 450, the

  records contain documentation texts

  by the user, along with instructions on how these texts should be used to modify the system documentation, for one or more orders of documentation. In other words, the user documentation files contain information indicating how the specific documentation of a user and the documentation of the system associated with one or more orders of documentation differ As an example, the files

  correspondents contained in the registration area of

  were created using the 32 editor.

  In this example, the user has chosen to provide

  documentation information for (a) orders

  in the PAM package, and (b) errors. For this purpose,

  two user files, namely the document file

  order for PAM, 451, and error documentation file 452, have been set in the user registration area. For example, the names of these files are identical to the system documentation files. 401 and 405 Thus, once the documentation service program 36 has

  obtained the name of the appropriate system documentation file

  prompted to open, as discussed below, it also has the name of the user documentation file

  appropriate to open (if one exists).

  Each of the packages includes a structure of

  respective data which is called an "environment" The envi-

  for each software package contains the file names for the system documentation files associated with this particular software package. In particular, the environment 310 associated with the PAM software package (shown in FIG. 3) may contain error file names, of glossary and order, such doc Error, doc Term and doc PAM, which are the

  names of the respective files 405, 404 and 401.

  documentation service gram 36 needs to collect,

  For example, the order documentation associated with PAM

  uses the environment 310 to determine the name of the system documentation file to which it must access Each of the environments associated with PSCU and PSGP contains the

  the same error and glossary file names as the envi-

  the fact that uniform sets of error mnemonics and uniform terminology are used throughout the system. However, the commands used in each package vary. Thus, the PSCU and PSGP environments may contain respective names of error codes. order documentation files, for example doc PSCU and doc PSGP, which

  are respectively the names of files 402 and 403.

  Each record in the document files

  the system and user documentation is inde-

  xed by a "key" whose value is the mnemonic

  of order, term or error to which the registration relates

  For example, a record in a system or user file that contains documentation for a particular order, for example, is retrieved by specifying that order as an index key in the read operation of the

database.

  Figure 5 shows the format for a system documentation record, i.e. a record

  in one of the 400 system documentation files.

  Registration starts with a zone separator, representing

  example by the # # characters, followed by a

  optional primary registration indicator and a separate

  associated header, at least one first section header and, for each section header, a section text, all

separated by separators e #.

  The value of the primary record flag may be the "C" character, for "continuation", which indicates that the documentation associated with the index key in question is too long to be contained in a single record, and is so continued in one or more records

  These additional recordings may

  are indexed by a key that is formed by adding a name

  to the key under which the first record is indexed, eg call, call 2, etc.)

  The primary registration indicator may also

  The indicator indicates that the record considered does not contain actual documentation, but the name of a menu, and that when the documentation service program 35 encounters such a record. he must call the menu service program 35 and specify this menu as the one to be presented to

  This type of recording is used, for example

  lolsque system provides documentation for a family of slogans such as "file-listing", "listing-orders", listing directories ", etc., and when providing the possibility for users to enter the order incomplete documentation ASSISTANCE LISTAGE In this case, the order documentation file will contain a record,

  indexed by the key "listing," containing an "M" as an indication

  main recorder, and containing the name of a menu that will ask the user for the order type "listing"

  for which he wishes to have documentation.

  In the system documentation record shown in Figure 5, the section headers are strings of characters, such as the USE and EXPLANATION headers in Table I. The section texts are

  strings constituting the texts that follow each

than section header.

  (Another type of recording used in

  system documentation files, which does not follow the

  FIG. 5, simply includes an index key, without initial separator The documentation service program 36 reacts to the encounter of such a record by immediately accessing the record which is indexed under this

  key This mechanism allows the system to automatically correct-

  some of the user's errors that are

  For example, a record constituted by the heading "Execu-

  program "could be indexed under the key" execution ",

  which is not a valid order Thus, if the user,

  documentation of the "programprogram" command, issues the documentation order by mistake ASSISTANCE ORDER EXECUTION, the documentation service program retrieved

  first the record indexed under the key "execution".

  By finding that this record simply contains the topic "program run", it immediately goes to

  extraction of the indexed record under "executionpro-

  gram ", which automatically corrects the error of the user.

  Figure 6 shows the format for a recording

  user documentation, that is, a record of

  450 It includes an initial separator, one or two optional main recording flags, at least a first

  section header and, following each section header,

  an optional section indicator and a text of sec-

  all separated by separators.

  The main recording indicator area

  may contain "C" which, as before, indicates "continuous"

  "It may also contain an" R "or" N "The" R "means" replacement "and the" N "means" new "These indicator values can be used interchangeably,

  and each of them is an instruction that the totality of

  This user documentation record must be used in place of the entire record of the

  documentation of the corresponding system.

  Section headers and section texts in user documentation records are similar to those in

* documentation of the system and it is not necessary to

to be more insidious.

  The section indicator can have one of four values: "A", "B", "R" or "N" "A" and "B" mean "after" and "before" and this is respective instructions indicating that the section text in the user record is to be added after or before the section text of the section carrying the corresponding header, in the corresponding system documentation record "R" and "N" are again interchangeable instructions that mean "replacement" and "new" each of which indicates that the section text in question should replace the section text

  of the section with the corresponding heading in the record

  documentation of the corresponding system.

  section is omitted, the section is treated as if the section flag value was "A" If the section header of the user documentation record

  is not identical to the section header in a record

  In any case, the value of the section indicator becomes meaningless, as will be seen. Before proceeding to the flowchart in Figures 7-9, the format should be considered here in more detail

  documentation orders As already indicated, the use of

  The user can issue commands such as ASSISTANCE ORDER CALL, ASSISTANCE TERM = IDENTIFIER_p_FACTURING and ERROR ASSISTANCE = EPASTROUVE, to which the system responds by supplying all available documentation for the order, term or error in question, modified

  (optionally) by the user As an option, the use of

  may delete "ORDER =" in a request for documenta-

  order, for example: ASSISTANCE CALL Another

  option is that the user can specify only

  the display of one or more specific sections of

  the documentation, for example ASSISTANCE CALL SECTION = UTILI-

  SATION SECTION = EXAMPLE Another option still allows the user to obtain documentation from the order documentation file associated with a software package other than

  the one he uses at the relevant moment, provided that the use

  For example, a user knows the name of this file.

  MAP user could issue the order:

  ASSISTANCE CALL FILE = doc PSCU SECTION = ARGU-

  And obtain documentation of the arguments

  for the "call" order as used in PSCU.

  Figures 7-9 provide a flowchart of the Connected Mode Documentation Service Program.

  which, as indicated above, is called as a sub-

  program, and hereinafter also referred to as "the program".

  FIG. 7, in particular, represents the recording extraction portion of the program. The program begins at step 701 by examining the arguments that are transmitted to it by the parsing program of order 34, to determine that she is exactly the documentation

  If, according to the determination made by the

  eg 703, the user issued a documentation order

  improper, for example ASSISTANCE ERREUR, the service program

  documentation defect calls the menu service program, 35, at step 704 By requesting responses from the

  user, the menu service program tends to

  will determine the documentation the user wants.

  Once this has been determined, the menu service program formats a request for documentation on behalf of the user and forwards it back to the documentation service program. It will be assumed, for example, that the user

  is running PAM and has issued a documentary order

  requesting documentation for the "call" order

  indicated in 706, the program now determines whether the

  The documentation requested by this user concerned the same order as the documentation he is now requesting.

  that is to say "call" (This documentation is always

  available in an Exit Record List 1050 (contemplated below)) If so, the order passes directly to the program marking / printing portion.

(Figure 9).

  Otherwise, the documentation service program now determines in step 709 the name of the system order documentation files, and therefore of use.

  the user, who intervene, in this example: doc PAM.

  In 711, the program consults a table that it keeps, giving the names of the open documentation files, to determine if one or more files called PAM doc are already open. If not, it tries in 714 to open a file at this time. name in the system registration areas

and user.

  At this point, it can be assumed that a system file

  the name in question is open, because a system file already exists However, a user file

  for the requested documentation may not exist.

  So, in step 717, it is determined whether there is indeed a

  open user file called doc PAM In the nega-

  tive, the program proceeds directly to step 732 in which the record or (in the case of continuations) records containing the documentation for the order

in question are extracted.

  If instead a user file called PAM doc is open, the program attempts in step 721 to extract from this file one or more user records constituting documentation for the "call" order If, as it is determined in step 724, there is no record of this type, which means that the user has not provided documentation for the "call" order, the program simply switches back to Step 732 However, if a user record actually exists, its main record indicator area (Figure 6) is checked to determine if it

  contains an "R" or an "N" This would indicate that the documentation

  The user command for the "call" command must replace the entire system documentation, in which case step 732 is skipped, because the registration of the system containing

  the documentation for the "call" order will not be necessary.

  If, on the other hand, the user record is not such a replacement record, the record of the system must also be retrieved and, as a precedent, the step

732 is executed.

  At this point, the control goes to the processing part.

  registration of the document service program.

  which corresponds to step 734 This part of the pro-

  gram, shown in Fig. 8, begins with step 801 in which the system documentation record

  previously extracted, if it exists, is examined and decomposed.

  This involves the establishment of headings in a

  list called the system registration list, 1010, representing

  Fig. 10 The system registration list is a predefined set of data structures (blocks of the system 1020), and each of them includes record positions intended to hold the following information from a section. of the registration of the

  system or concerning such a section: the header of sec-

  the nature of the information recorded at heading 1021, a pointer to the position of the section text, which is recorded at heading 1022, and a count of the number of characters in the text, which is recorded at heading 1023 .

  Returning to Figure 8, we note that the

  gram now proceeds to step 803 at which the record

  previously retrieved user documentation, if it exists, is similarly examined and decomposed into a user registration list 1030, also

  shown in Figure 10 The user registration list

  The user is formed by user blocks 1040 In addition to registration positions for a section header, a

  text pointer and a character count, which are respec-

  1041, 1042 and 1043, each user block has a record position 1045 for the section indicator value (A, B, R or N)

described above.

  System registration lists are used

  and user to create a list called register list.

  1050, described briefly below This list includes a set of output blocks 1060, each of which has a recording position for the following information: a section header, a pointer to a first text , a character count for the first text,

  a pointer to a second text, a character count

  for the second text and a print indicator,

  as respectively the references 1061 to 1066.

  In particular, the program fills the output record list 1050 by executing a loop which corresponds to step 808 of FIG. 8. At each pass in the loop, it examines a successive block among the blocks of the system 1020 and determines in step 811, if there is a corresponding section header in any of the user blocks 1040 If not, the program proceeds to step 814 at which the section header is copied from position 1021 in the system block to position 1061 in the immediately following available block among output blocks 1060 In addition, the text pointer and the character count are copied from positions 1022 and 1023 of the system block to positions 1062 and 1063 of the output block, respectively constituting the first text pointer and the first character count The second text pointer in the output block, stored at position 1064 is set to zero to denote an empty string The program then loops back to process the block

of the next system.

  If on the contrary, there exists in one of the user blocks 1040 a section header which corresponds to

  the section header in the current system block

  dere, the program copies this header to place it at the

  position 1061 of the output block available immediately following

  in step 816, then in step 819, it positions the text pointers (and the corresponding character counts) in the output block according to the value of the section indicator which is recorded at position 1045 in the user block In particular, if the section indicator value is "A" (for "after"), the first and second text pointers stored in the output block at positions 1062 and 1064 receive values from text pointers saved to positions

  respective 1022 and 1042 blocks of the system and of

  the program proceeds in a similar way for character counts. If the section indicator is "B"

  (for "before"), these same values are assigned to

  text and character accounts of the output block.

  In reverse order If the section indicator is "R" (for "replacement") or "N" (for "new"), the system documentation for the particular section should be

  be completely replaced by the user documentation.

  In this case, the first text pointer and the character count in the output block receive the values of the text pointer and the character count of the block.

  user, and the second text pointer of the output block.

  In step 821, the user block in question receives a mark indicating that it has been "used", which is done by way of example in

  transforming its section header into an empty string.

  Once all the blocks in the 1020 system have been processed this way, the program gets out of the loop

  and goes to step 824. Here he explores the recording list

  1030 to search for user blocks

  unmarked, ie blocks whose headers

  are not empty strings. Information from

  Any such user block is copied to a respective one of the output blocks in the same way that the information in a block of the system that does not have a corresponding user block is copied. to an output block, as described above in connection with step 814. The above shows that the value

  section indicator does not intervene in this case.

  In step 826, the program proceeds to its section marking / printing section, which is represented on the

  Fig. 9 If the order of documentation has specified that some

  only sections should be displayed, which is

  determined in step 901, the print indicator is posi-

  Lioned in the appropriate output block, which corresponds to

  step 903 Otherwise, the print indicators

  are positioned in all the output blocks, which

corresponds to step 904.

  The documentation is now ready to be

  "printed", that is to say presented to the user

  first, the registration key that was used for extracting the record is presented in capital letters and printed with double asterisks to form the main header at step 908 (e.g. CALL, from Tables I and II) Then, each block of the output list 1050 is examined in turn by means of a loop that begins in 911 In the loop, each block

  output is first checked at step 913 to see-

  if it was marked for the impression If not, the

  men passes to the next block However, if the block has been marked for printing, the program goes through steps 915, 916

  and 919 who respectively carry out the actions

  both to print in capital letters and to print the section header, to print the first text specified in the block

  output, and to print the second text, if it exists.

  Once all the output blocks have been exa-

  the program returns to the program that called it.

  It goes without saying that many modifications can be made to the described method and device and

  represented, without departing from the scope of the invention.

Claims (4)

  A method of documentation in connected mode for use in a computer system, characterized in that it comprises the following operations: it provides to individual users of the system, in response to the transmission by these users of an order particular documentation, documentation of the system associated with the particular order of documentation; and providing at least one other user of the system, in response to the issuance of the particular documentation order by that other user,   user-specific documentation, defined beforehand by this other user.   Apparatus for implementing the method of documentation in connected mode for use in a computer system according to claim 1, characterized in that it comprises: first means (36, 40, 1010, 1050) for provide to individual users of the system, in response to issuing a documentation order   particular by these users, a documentation of the system   associated with this particular order of documentation; and second means (36, 40, 45, 1030, 1050) for providing to at least one other user of the system, in response to the issuance of the particular documentation order by that   other user, specific documentation of the use   user, previously defined by this other user.   3 Device according to claim 2, characterized in that the first and second means comprise   means (40) which are common to them and are intended to record   the system documentation associated with the document order   particular, and to record the documentation of the   system associated with other orders of documentation which may   may be issued by the users of the system; and in that   the second means further comprise means (45) for   born to record one or more user documentation texts associated with at least the order of documentation   particular, and to record an instruction associated with each   as user documentation text, which indicates how this user documentation text is to be used to modify the registered system documentation that is associated with that particular order; and means (36, 1030, 1050, 1010) for creating the specific documentation of   the user in accordance with each instruction.   Device according to claim 2, characterized in that the first and second means comprise   means (40) which are common to them and are intended to be   the system documentation associated with the document order   particular, and to record the documentation of the   system associated with other orders of documentation which may   may be issued by the users of the system; in that the   documentation of the system associated with each document   tation consists of one or more sections of system documentation text; the second means further comprises means (45) for recording   one or more user documentation texts   at least in the order of particular documentation, and   record an instruction associated with each document text   User Agreement, which indicates whether this text of   the user must be added to a documentary text.   the corresponding system, used to replace a corresponding system documentation text, or used as a separate section in the user-specific documentation; and in that the second means (36, 1010, 1050, 1030) further comprises means for creating the user specific documentation in accordance with each instruction.