Templar(ID:7113/tem011)

Software specification language based on temporal logic
References:
  • Tuzhilin, Alexander "Templar: A knowledge-based language for software specifications using temporal logic" Working Paper IS-93-33, Stern School of Business, New York Univ., New York 1993 view details
  • Tuzhilin, Alexander "Templar: a knowledge-based language for software specifications using temporal logic" ACM Transactions on Information Systems (TOIS) 13(03) July 1995 pp269-304 view details Abstract: A software specification language Templar is defined in this article. The development of the language was guided by the following objectives: requirements specifications written in Templar should have a clear syntax and formal semantics, should be easy for a systems analyst to develop and for an end-user to understand, and it should be easy to map them into a broad range of design specifications. Templar is based on temporal logic and on the Activity-Event-Condition-Activity model of a rule which is an extension of the Event-Condition-Activity model in active databases. The language supports a rich set of modeling primitives, including rules, procedures, temporal logic operators, events, activities, hierarchical decomposition of activities, parallelism, and decisions combined together into a cohesive system. DOI Abstract: A software specification language Templar is defined in this article. The development of the language was guided by the following objectives: requirements specifications written in Templar should have a clear syntax and formal semantics, should be easy for a systems analyst to develop and for an end-user to understand, and it should be easy to map them into a broad range of design specifications. Templar is based on temporal logic and on the Activity-Event-Condition- Activity model of a rule which is an extension of the Event-Condition-Activity model in active databases. The language supports a rich set of modeling primitives, including rules, procedures, temporal logic operators, events, activities, hierarchical decomposition of activities, parallelism, and decisions combined together into a cohesive system.