Software Documentation

This software details the theory of time, history and the end of history, as described in The Invisible Landscape by Terence and Dennis McKenna. After an extraordinary psychedelic experiment deep inside Columbia's Amazon jungle in 1971, as Terrence McKenna mentioned in his book True Hallucinations. The theory of zero time zero revealed to him that this instructed him to perform a specific digital conversion. From the "Easy of King Li Jingjun" including the occurrence of time phenomenon. This eventually resulted in a mathematical description of the "time wave". It is said to be related to the tide and flow of something called novelty, which claims to be the intrinsic quality of the space time structure.

One of the characteristics of this correlation is that it reaches a singular point at a certain point in this at the end of history, or at least a transition to the hyper-historical order where the fundamental occurrence of our general reality concept occurs. Gender transformation. This date was chosen by McKenna as the date of the winter solstice on 21 December 2012, and the end of the current 13 bacton of the Mayan calendar (by Goodman-Martinez-Thompson correlation) 584283)

An important feature of the time waveform is that it is fractal (although it was not completely disclosed until the late 1980s). After displaying a part of the waveform, you can use software to expand smaller parts. Although this usually reveals the complexity of the structure, the waves are greatly expanded. This is a typical feature of a fractal. Terence McKenna first proposed the idea that time has a fractal structure (pure, unstructured, as opposed to Newton time period). This is, of course, an interesting idea worthy of further study by physicists.

An interesting part of the Time Wave zero theory is the concept of "resonance" with each other in a historical period in which early events are repeated in a certain way in a certain way. The software makes it possible to resonate the graphic displays of different regions of the time waves with each other and includes the ability to draw so-called triangular resonances in addition to the first resonance. Therefore, this fractal time software can correctly check that Terrence McKenna claims to have discovered a time attribute that can even explain or even predict historical phenomena.

Class UML diagrams are the most common type of chart for software documentation. Recording software using class diagrams is a commonsense solution, as most of the software that is currently being created is still based on the object-oriented programming paradigm. This is because the OOP is based on the class and the relationship between them. That is, the class diagram contains the class, its properties (also called data fields), and its behavior (also called member functions). Specifically, each class has three fields. There is a class name at the top, a class attribute under the name, and a class action / action at the bottom. Relationships between different classes (represented by connecting lines) constitute a class diagram

Software engineering documentation is a comprehensive term covering all documented documentation and materials related to the development and use of software products. Regardless of whether it is a small team or a large company, all the software development products require some relevant documents. Also, various kinds of documents were created through the software development life cycle (SDLC). There is a document that explains the function of the product, integrates the project related information, and enables discussion on all important issues occurring between the stakeholder and the developer.

Excellent software manuals, such as specifications for programmers and testers, technical documents for internal users, software manuals and help files for end users, will help people using the software to understand their functions. A good software document provides concrete, concise, relevant and all essential information necessary for using the software. The following is a description of how to write software document for technical users and end users.