Tulis(21 7 11)
0 likes280 views
TULIS is a framework for analyzing any entity, whether conceptual or physical. It was originally conceived as a methodology for software programming, but was expanded to be a more fundamental tool. TULIS is based on several foundational concepts, including modeling an entity's essence, form, names, attributes, actions, and behavior. It can be used to analyze social structures, business models, and other domains.
![TULISTM
entity analysis framework
Background
TULIS is a Malay word for "write." As an acronym it stands for "Transformational Universal Language
- Intuitive Semantics."
Originally TULIS was conceived as a methodology and tool for software programming. Over the
months of development; I feel due to its nature, it ought
TULIS
to become more fundamental than that. So now, TULIS is
being proposed as a framework for understanding reality Transformational Universal
in a structured way. It is an entity analysis framework.
Language Intutive Semantics
My original motive was to develop a pseudo-
programming language so that I could write programs for Street University technologies such as
roboMu (a web crawler, indexer and storage agent for PostgreSQL database), uTV (course delivery
system), asuMu (a virtual AI-based personal tutor) and k-Framer (a knowledge parsing agent).
As I began to write the semantics, it dawns upon me that TULIS is more than a pseudo-programming
language. It is far more fundamental than that. It is a framework for understanding reality. As an
example, TULIS could be utilized for analysing social structures, problems and propose solutions
accordingly. TULIS could also be used to develop business cases for a particular model. The
applications are varied and enormous.
Foundation
TULIS is based on a number of fundamental concepts:
[1] Physical Entity-Conceptualization-Word Construct (PECWC - pronounced "PEKWEK")
[2] EFNAAB (Essence, Form, Names, Attributes, Actions, Behaviour - pronounced "EFNAAB")
model which predates OO methodology by a few hundred years.
[3] CASE (Core, Auxiliary, Supplementary and Exemplary) categorization for an entity.
[4] Obligation Parameters (ObliPar) which delineate boundaries between obligations and
avoidance.
[5] Conditional Parameters (ConPar) which define the conditions that modify the original
obligation boundaries (modifiers).
[6] Process Elements and Sequence (PE/S) that define the integrals for a particular entity and
its actions/behaviour and the proper sequence order of the process in question.](https://image.slidesharecdn.com/tulis21711-13112141499761-phpapp02-110720211119-phpapp02/85/Tulis-21-7-11-1-320.jpg)
![[7] Relationship by Covenant (RbC) that governs the dependencies and links (the flux)
between entities under studies.
What is the essence of TULIS?
TULIS is a tool (and framework) for
analyzing any entitiy, living or
otherwise; conceptual or physical.
How Do You Use TULISTM?
Depending on the complexity of the domain to be analysed, you may use TULISTM Component
Specifications above together or any combination.
For example, if you intend to develop a new business; then in all probability you would need to use
all of the Specifications. The use of the components does not, however, entail a sequential order. If
you belong to the type of those who like to experiment and develop your own semantics, you are
welcome to try. For those who want to follow TULISTM semantics. you may request the
Specifications by sending an e-mail to me at megatahmadsani@gmail.com. A more detailed
description may be found at http://www.streetuniversity.my.
A Simplified Example of Applications
TULISTM can be used in any language. The example below is a description of EFNAAB Specifications
(in Malay shortened to Spesifikasi ZaBeNa).
Semantics:
Entity:Essence{[Essence 1], // Write your comments here. Use of newline is for clarity.
[Essence 2]
[Essence n]}
Entity:Form{[Form 1],
[Form 2]
[Form n]}
Entity:Name{[Name 1], // An entity may have a few names. Name is any word to describe
[Name 2]} // a noun, verb, adjective anything. Name is not to be
// confused with name used in a grammatical sense.
Entity:Attribute{[Attribute 1], // Attribute is any feature or characteristic description of an entity.
[Attribute 2], // The attribute may be expanded to detail out certain value
[Attribute n]} // proposition as used in designing a new product (for example).
// uTV:Display:Search:Syntax_Errors{[Error Message No],
// [Point_to_Error]
// [Refer_to_Help_for_Details]
Entity:Action{[Action1]. // Action can be passive or active. The principles of action are:
[Action 2], // [a] Doer [b] Object of action [c] Types of action [d] Means of action
[Action n]} // [e] Enumeration and process. Action descriptors may be extended
// such as in the example:](https://image.slidesharecdn.com/tulis21711-13112141499761-phpapp02-110720211119-phpapp02/85/Tulis-21-7-11-2-320.jpg)
![// uTV:Search():Enter_Search_Words{[Select_from_List()].
// [Type_keywords(),
// [Use_kFramer()]}
Entity:Behaviour{[Behaviour 1], // Behaviour and action are tightly integrated. Using the same
[Behaviour 2], // example as above:
[Behaviour n]} // uTV:Search_Agent:When_connection_down(){[Display()],
// [Option()],
// [Check()],
// [Take_a_
// break()]
You may extend EFNAAB Specifications by adding the necessary element(s) as per your
requirements. The format for the extension may take the following:
Entity:Element{Element_Descriptors:Essence[..], // Notice the recursive nature of the
:Form[..], // Specifications. In other words you can
:Names[], // nest elements within the element.
:Attributes[],
:Action[],
:Behaviour[]}
EFNAAB Semantics
The example below is the semantic for EFNAAB written in
Malay for the purpose of developing a restaurant
You may use your own
business model.
semantics. Whatever you do,
make sure you write them
down. A short pencil is better
than a long memory!
Restoran:Zat{Tempat di mana berbagai makanan dan minuman disediakan,
terdapat tempat bersantai sambil menikmati sajian,
pelanggan dapat membuat pilihan mengikut citarasa tersendiri,
...}
:Bentuk{LayanDiri,atau
AmbilPesanan, atau
Gabungan,
KeterbukaanRuang,
SudutSajianKhas,
Susun_Duduk_Ikut_Kumpulan,
...}
:Nama{SeniRasa, // Nama yang dicadangkan bagi restoran.
sampaian_mesej-->kesenian gastronomi, // untuk memberi nilai berbeza dari
...} // pesaing.
// --> digunakan untuk maksud
// sasaran, objektif.
:Sifat{Layan_Dari_Masuk_Hingga_Keluar, // Model nilai untuk restoran
MesraDuduk,
Pilih_dan_Gabung_MenuUtama,
MesraPoket}](https://image.slidesharecdn.com/tulis21711-13112141499761-phpapp02-110720211119-phpapp02/85/Tulis-21-7-11-3-320.jpg)
Tulis(21 7 11)
- 1. TULISTM entity analysis framework Background TULIS is a Malay word for "write." As an acronym it stands for "Transformational Universal Language - Intuitive Semantics." Originally TULIS was conceived as a methodology and tool for software programming. Over the months of development; I feel due to its nature, it ought TULIS to become more fundamental than that. So now, TULIS is being proposed as a framework for understanding reality Transformational Universal in a structured way. It is an entity analysis framework. Language Intutive Semantics My original motive was to develop a pseudo- programming language so that I could write programs for Street University technologies such as roboMu (a web crawler, indexer and storage agent for PostgreSQL database), uTV (course delivery system), asuMu (a virtual AI-based personal tutor) and k-Framer (a knowledge parsing agent). As I began to write the semantics, it dawns upon me that TULIS is more than a pseudo-programming language. It is far more fundamental than that. It is a framework for understanding reality. As an example, TULIS could be utilized for analysing social structures, problems and propose solutions accordingly. TULIS could also be used to develop business cases for a particular model. The applications are varied and enormous. Foundation TULIS is based on a number of fundamental concepts: [1] Physical Entity-Conceptualization-Word Construct (PECWC - pronounced "PEKWEK") [2] EFNAAB (Essence, Form, Names, Attributes, Actions, Behaviour - pronounced "EFNAAB") model which predates OO methodology by a few hundred years. [3] CASE (Core, Auxiliary, Supplementary and Exemplary) categorization for an entity. [4] Obligation Parameters (ObliPar) which delineate boundaries between obligations and avoidance. [5] Conditional Parameters (ConPar) which define the conditions that modify the original obligation boundaries (modifiers). [6] Process Elements and Sequence (PE/S) that define the integrals for a particular entity and its actions/behaviour and the proper sequence order of the process in question.
- 2. [7] Relationship by Covenant (RbC) that governs the dependencies and links (the flux) between entities under studies. What is the essence of TULIS? TULIS is a tool (and framework) for analyzing any entitiy, living or otherwise; conceptual or physical. How Do You Use TULISTM? Depending on the complexity of the domain to be analysed, you may use TULISTM Component Specifications above together or any combination. For example, if you intend to develop a new business; then in all probability you would need to use all of the Specifications. The use of the components does not, however, entail a sequential order. If you belong to the type of those who like to experiment and develop your own semantics, you are welcome to try. For those who want to follow TULISTM semantics. you may request the Specifications by sending an e-mail to me at megatahmadsani@gmail.com. A more detailed description may be found at http://www.streetuniversity.my. A Simplified Example of Applications TULISTM can be used in any language. The example below is a description of EFNAAB Specifications (in Malay shortened to Spesifikasi ZaBeNa). Semantics: Entity:Essence{[Essence 1], // Write your comments here. Use of newline is for clarity. [Essence 2] [Essence n]} Entity:Form{[Form 1], [Form 2] [Form n]} Entity:Name{[Name 1], // An entity may have a few names. Name is any word to describe [Name 2]} // a noun, verb, adjective anything. Name is not to be // confused with name used in a grammatical sense. Entity:Attribute{[Attribute 1], // Attribute is any feature or characteristic description of an entity. [Attribute 2], // The attribute may be expanded to detail out certain value [Attribute n]} // proposition as used in designing a new product (for example). // uTV:Display:Search:Syntax_Errors{[Error Message No], // [Point_to_Error] // [Refer_to_Help_for_Details] Entity:Action{[Action1]. // Action can be passive or active. The principles of action are: [Action 2], // [a] Doer [b] Object of action [c] Types of action [d] Means of action [Action n]} // [e] Enumeration and process. Action descriptors may be extended // such as in the example:
- 3. // uTV:Search():Enter_Search_Words{[Select_from_List()]. // [Type_keywords(), // [Use_kFramer()]} Entity:Behaviour{[Behaviour 1], // Behaviour and action are tightly integrated. Using the same [Behaviour 2], // example as above: [Behaviour n]} // uTV:Search_Agent:When_connection_down(){[Display()], // [Option()], // [Check()], // [Take_a_ // break()] You may extend EFNAAB Specifications by adding the necessary element(s) as per your requirements. The format for the extension may take the following: Entity:Element{Element_Descriptors:Essence[..], // Notice the recursive nature of the :Form[..], // Specifications. In other words you can :Names[], // nest elements within the element. :Attributes[], :Action[], :Behaviour[]} EFNAAB Semantics The example below is the semantic for EFNAAB written in Malay for the purpose of developing a restaurant You may use your own business model. semantics. Whatever you do, make sure you write them down. A short pencil is better than a long memory! Restoran:Zat{Tempat di mana berbagai makanan dan minuman disediakan, terdapat tempat bersantai sambil menikmati sajian, pelanggan dapat membuat pilihan mengikut citarasa tersendiri, ...} :Bentuk{LayanDiri,atau AmbilPesanan, atau Gabungan, KeterbukaanRuang, SudutSajianKhas, Susun_Duduk_Ikut_Kumpulan, ...} :Nama{SeniRasa, // Nama yang dicadangkan bagi restoran. sampaian_mesej-->kesenian gastronomi, // untuk memberi nilai berbeza dari ...} // pesaing. // --> digunakan untuk maksud // sasaran, objektif. :Sifat{Layan_Dari_Masuk_Hingga_Keluar, // Model nilai untuk restoran MesraDuduk, Pilih_dan_Gabung_MenuUtama, MesraPoket}