Skip navigation
Full metadata record
DC FieldValueLanguage
dc.contributor.authorTuzhilin, Alexander-
dc.date.accessioned2006-06-21T17:52:34Z-
dc.date.available2006-06-21T17:52:34Z-
dc.date.issued1993-
dc.identifier.urihttp://hdl.handle.net/2451/14765-
dc.description.abstractA 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.en
dc.format.extent2541713 bytes-
dc.format.mimetypeapplication/pdf-
dc.languageEnglishEN
dc.language.isoen
dc.publisherStern School of Business, New York Universityen
dc.relation.ispartofseriesIS-93-033en
dc.subjectDesignen
dc.subjectLanguagesen
dc.subjectActivitiesen
dc.subjecteventsen
dc.subjectrule-based systemsen
dc.subjectspecification languagesen
dc.subjecttemporal logicen
dc.subjecttimeen
dc.titleTemplar: A Knowledge-Based Language for Software Specifications Using Temporal Logicen
dc.typeWorking Paperen
dc.description.seriesInformation Systems Working Papers SeriesEN
Appears in Collections:IOMS: Information Systems Working Papers

Files in This Item:
File Description SizeFormat 
IS-93-033.pdf2.48 MBAdobe PDFView/Open


Items in FDA are protected by copyright, with all rights reserved, unless otherwise indicated.