ACM Home Page
Please provide us with feedback. Feedback
Templar: a knowledge-based language for software specifications using temporal logic
Full text PdfPdf (2.54 MB)
Source ACM Transactions on Information Systems (TOIS) archive
Volume 13 ,  Issue 3  (July 1995) table of contents
Pages: 269 - 304  
Year of Publication: 1995
ISSN:1046-8188
Author
Alexander Tuzhilin  New York Univ., New York, NY
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 20,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/203052.203061
What is a 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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
BORGIDA, A., GREENSPAN, S., AND MYLOPOULOS, J. 1985. Knowledge representation as the basis for requirements specifications. IEEE Comput. I8, 4 (Apr.), 82-91.
 
3
BORGIDA, A., MYLOPOULOS, J., AND SCHMIDT, J. W. 1993. The TaxisDL software description language. In Database Application Engineering with DAIDA. Springer-Verlag, Berlin.
 
4
CASANOVA, M. A. AND FURTADO, A. L. 1984. On the description of database transition constraints using temporal languages. In Advances in Database Theory. Vol. 2. Plenum Press, New York, 211-236.
 
5
 
6
 
7
 
8
 
9
 
10
 
11
GEORGErF, M. P. AND LANSKY, A. L. 1986. Procedural knowledge. Proc. IEEE 74, 10, 1383-1398.
 
12
 
13
 
14
 
15
H~EL, D. 1985. Recurring dominoes: Making the highly undecidable highly understandable. Ann. Discr. Math. 24, 51-71.
16
 
17
 
18
 
19
JEREMAES, P., KHOSLA, S., AND MAIBAUM, T. S.E. 1986. A modal (action) logic for requirements specifications. In Software Engineering '86, P. J. Brown and D. J. Barnes, Eds. Peter Peregrinus, 278-294.
 
20
 
21
 
22
 
23
LOUCOPOULOS, P., McBRIEN, P., PERSSON, U., SCHUMACKER, F., AND VASEY, P. 1990. TEMPORA --Integrating database technology, rule based systems and temporal reasoning for effective software. In Esprit '90 Conference Proceedings. Kluwer Academic, Dordrecht, Holland.
 
24
 
25
26
 
27
MEYER, B. 1985. On formalism in specification. IEEE Softw. (Jan.), 6-26.
28
 
29
NICOLAS, J.-M. 1982. Logic for improving integrity checking in relational data bases. Acta Informatica 18, 227-253.
 
30
 
31
Olle, H. G. Sol, and A. A. Verrijn-Stuart, Eds. North-Holland, Amsterdam, 1-14.
 
32
PRIOR, A. 1967. Past, Present, and Future. Clarendon Press, Oxford.
 
33
 
34
SPWEY, J.M. 1988. Understanding Z. Cambridge Tracts in Theoretical Computer Science, vol. 3. Cambridge University Press, Cambridge, U.K.
 
35
36
 
37
 
38
TUZHILIN, A. 1991. Temporally active databases .= Active databases + Time. Working Paper IS-91-43, Stern School of Business, New York, Univ., New York.
 
39
 
40
TUZmLIN, A. 1993. 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.
 
41
42



REVIEW

"Mauro Pezze : Reviewer"

Tuzhilin describes Templar, a formal language for requirement specifications. Its new features are “specifier and end-user friendliness.” Specifiers can quickly develop conceptual models (“specifier friendliness”), whil  more...