Programming in Prolog (2nd ed.)
Programming in Prolog (2nd ed.)
A 15 Year Perspective on Automatic Programming
IEEE Transactions on Software Engineering - Special issue on artificial intelligence and software engineering
Research on Knowledge-Based Software Environments at Kestrel Institute
IEEE Transactions on Software Engineering - Special issue on artificial intelligence and software engineering
IEEE Transactions on Software Engineering
Salient features of and executable specification language and its environment
IEEE Transactions on Software Engineering
A Distributed Specification Model and its Prototyping
IEEE Transactions on Software Engineering
Statemate: a working environment for the development of complex reactive systems
ICSE '88 Proceedings of the 10th international conference on Software engineering
On executable models for rule-based prototyping
ICSE '85 Proceedings of the 8th international conference on Software engineering
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Time, clocks, and the ordering of events in a distributed system
Communications of the ACM
Specification and verification of distributed systems using prolog interpreted petri nets.
ICSE '84 Proceedings of the 7th international conference on Software engineering
Prototyping as a tool in the specification of user requirements
ICSE '81 Proceedings of the 5th international conference on Software engineering
Principles of Program Design
A Hybrid Knowledge Representation as a Basis of Requirement Specification and Specification Analysis
IEEE Transactions on Software Engineering - Special issue on software maintenance
A Real-Time Discrete Event System Specification Formalismfor Seamless Real-Time Software Development
Discrete Event Dynamic Systems
| Hi-index | 0.00 |
SXL, a modeling language that describes system behavior rather that software structure, is discussed. Using a conventional state-transition framework, model behavior is determined by rules that define pre- and postconditions for each transition. Behavior is also specified by constraints (logical invariants) that are automatically enforced during the execution of the model. Rules and constraints are expressed solely in terms of entity-relationship structure and declarative logic; the language lacks machine-oriented data or control structures, and has no facilities for specifying or implementing software. Application of SXL is demonstrated by its translation of a simple behavioral description (a scenario from an actual requirements document) into an executable model. Comparisons are made to software- and specification-oriented methods to illustrate the tradeoffs resulting from SXL's restriction to simple behavioral modeling. A brief account is given of one software development group's experience with SXL.