I had a bit of an epiphany today. What I realized is that by structuring Structured Thinking Language as I have, everything can evolve as lists. Each VERB is simply the addition of another list to the NOUN you are working with.
Six Verbs: CREATE, RELATE, REPORT, RECORD, AFFORD, ENGAGE
Six Nouns: MOTIVE, LOCALE, OBJECT, METHOD, PERSON, MOMENT
Four Adjectives: INDUCED, DEDUCED and IMPLICIT, EXPLICIT
CREATE INDUCED|DEDUCED IMPLICIT|EXPLICIT NOUN ( nounname_1, ..., nounname_n ); RELATE INDUCED|DEDUCED IMPLICIT|EXPLICIT NOUN.nounname TO ( NOUN_1.nounname_1, ..., NOUN_n.nounname_n ); REPORT INDUCED|DEDUCED IMPLICIT|EXPLICIT NOUN.nounname ( attributename_1, ..., attributename_n ); RECORD INDUCED|DEDUCED IMPLICIT|EXPLICIT NOUN.nounname.attributename ( constraintname_1, ..., constraintname_n ); AFFORD INDUCED|DEDUCED IMPLICIT|EXPLICIT NOUN.nounname ( SELECT INSERT, UPDATE, DELETE ) ON ( NOUN_1.nounname_1, ..., NOUN_n.nounname_n ); ENGAGE INDUCED|DEDUCED IMPLICIT|EXPLICIT SELECT|INSERT|UPDATE|DELETE
Obviously, it still needs work, but we can see where the Structured Thinking Language adds value to the design process. SQL does have it’s place in data manipulation. However, STL has a place in data definition. See the related posts for background information on this syntax.
- Structured Thinking Language R0.1
- Structured Thinking Language R0.2
- Implicity and Explicity
- Listening is Inductive; Speaking is Deductive
- The Six Hats, Six Coats Framework