Method for reusing definitions in documents and monitoring thereof

• US 20060184867A1
• Filed: 02/16/2006
• Published: 08/17/2006
• Est. Priority Date: 02/17/2005
• Status: Abandoned Application

• Current Assignee: Avraham Shpigel
• Original Assignee: Avraham Shpigel
• Inventors: Shpigel, Avraham
• Application Number:
  US11/355,849
• Publication Number:
  US 20060184867A1
• Time in Patent Office: Days
• US Class Current: 715/206
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
• CPC Class Codes: G06F 40/169 Annotation, e.g. comment data or footnotes
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A method for reusing, managing and monitoring definitions in documents. The new method suggests using a dedicated process that manages the ‘life cycle’ of the definitions called ‘the definition transitional states process’. This process keeps track of each definition version in a dedicated versions tree, state transition process and history/log files functioned to track the changes. The method further suggests a systematic way to monitor the process of updating all the relevant documents whenever a definition in one of the hierarchical documents is created or modified.

Claims

1. A method for definitions reuse in documents, wherein the documents have common context relating to at least one project, said method comprising the steps of:

(a) enabling a user to set a definition for the use in at least one document;

(b) keeping track of said definition'"'"'s qualitative and quantitative parameters along the life cycle of said definition relating to at least one project.

2. The method according to claim 1, wherein said definition comprises a title and a description corresponding to said title.

3. The method according to claim 1, wherein the definition is any component of a document that may be a part of the conceptual world of an organization.

4. The method according to claim 1, wherein the definition may be any of the following:

data, table, text, equation, figure, picture, any combination and formats and any component that may be reused.

5. The method according to claim 1, wherein said life cycle of said definitions in step (b) may include at least one of the following:

definition creation, examination, approving, reusing and modification thereof.

6. The method according to claim 1, wherein step (b) further comprises enabling said user to modify said definition.

7. The method according to claim 1, wherein said document is linked to a list of at least one library, and wherein said library contains at least one definition that must be reused in said document.

8. The method according to claim 1, wherein said document is linked to a list containing all the definitions used in said document with their corresponding data.

9. The method according to claim 8,wherein said list is updated as soon as a new definition is used in said document.

10. The method according to claim 1, wherein step (b) further comprises monitoring error definition by updating all the documents containing said error definition.

11. The method according to claim 1, wherein step (b) further comprises monitoring error definition by enabling users to perform any of the following actions regarding said error definition:

modifying and approving.

12. The method according to claim 1, wherein step (b) further comprises monitoring error definition by automatically sending a message to each user using said error definition.

13. The method according to claim 1, wherein step (b) further comprises allowing a user to set a definition to an error status wherein said status is automatically being updated in all definitions related documents.

14. The method according to claim 1, wherein step (b) further comprises presenting the definition title to the user in a graphically distinctive manner, providing information regarding at least one parameter relating to said definition.

15. The method according to claim 1, wherein step (b) further comprises notifying said user of any change in any definition'"'"'s parameters.

16. The method according to claim 1, wherein said keeping track in step (b) is performed in real-time and a user that is linked electronically may see any changes made on definition'"'"'s data as they happen.

17. The method according to claim 1, wherein step (b) further comprises enabling the user to work offline, wherein the user'"'"'s changes when working offline are not seen by external users.

18. The method according to claim 1, wherein step (b) further comprises enabling a super user to approve a change made to a definition and wherein said change may be in any part of the definition'"'"'s life cycle database.

19. The method according to claim 1, wherein the method operate within the scope of at least one of the following databases:

a. A database on the definition level;

b. a database on the document level; and

c. a database on the project level.

20. The method according to claim 1, wherein said keeping track in step (b) is done by holding the history information for any definition in a dedicated log file, and wherein any action performed on any definition is recorded on said log file.

21. The method according to claim 1, wherein said keep tracking in step (b) is done by building a versions tree data structure and wherein said versions tree contains information regarding each version and links between each version to another.

22. The method according to claim 1, wherein said keep tracking in step (b) further allows a user to define a section definition and wherein a section definition is a variant of definition.

23. The method according to claim 1, wherein the user is provided with tools monitoring the usage of said definitions along their life cycle.

24. The method according to claim 23, wherein said tools may include tools for searching appropriate candidates for definitions.

25. The method according to claim 23, wherein said tools may include tools for performing queries relating to definitions and their life cycle.

26. The method according to claim 23, wherein the user is a super user, and wherein a super user is a user who is entitled to performs activities beyond the user'"'"'s entitlements.

27. The method according to claim 23, wherein said tools may include measuring of at least one parameter relating to a definition.

28. The method according to claim 27, wherein said parameter is the number of occurrences of said definition in a document.

29. The method according to claim 27, wherein said parameter is the writing efficiency, and wherein said efficiency relates to the ratio between the number of words in said document containing at least one reused definition and the number of words in a document wherein the said definition'"'"'s title is replaced with the corresponding definition'"'"'s description.

30. The method according to claim 27, wherein said parameter is the writing consistency, and wherein said consistency relates to the number of documents reusing the same definition in said project.

31. The method according to claim 27, wherein said parameter is the writing complexity, and wherein said complexity relates to the number of versions of said definition that do not derive directly from main definition and document life-cycle.