Templar

  • Tuzhilin A
N/ACitations
Citations of this article
6Readers
Mendeley users who have this article in their library.

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.

Cite

CITATION STYLE

APA

Tuzhilin, A. (1995). Templar. ACM Transactions on Information Systems, 13(3), 269–304. https://doi.org/10.1145/203052.203061

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free