Specification and design of transactions in information systems: a formal approach
- 1 January 1991
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 17 (8) , 814-829
- https://doi.org/10.1109/32.83916
Abstract
In conventional information systems development, consistency between requirements specifications and design is achieved by manual checking. The application of the transformational paradigm to the specification and design phases is proposed. Requirements are expressed in the ADISSA notation, using the ADISSA method, a transaction-oriented refinement of structured systems analysis. The control part of a transaction is transformed into a formal specification, the FSM (finite state machine) transaction, by applying a set of rules. The design stage is realized by an algorithm which compares the FSM transaction into simpler transactions and implements them with a hierarchical set of finite-state machines. Consistency between the formal specification and the result of the design is achieved by proving that the latter has the same behavior as the former.Keywords
This publication has 9 references indexed in Scilit:
- Software engineering tools supporting ADISSA methodology for systems analysis and designInformation and Software Technology, 1990
- ADISSA: Architectural Design of Information Systems based on Structured AnalysisInformation Systems, 1988
- On synchronization in hard-real-time systemsCommunications of the ACM, 1988
- ADDS: A system for automatic database schema design based on the binary-relationship modelData & Knowledge Engineering, 1987
- Structured Programming: Retrospect and ProspectIEEE Software, 1986
- A dialog-based architecture for interactive information systemsACM SIGMIS Database: the DATABASE for Advances in Information Systems, 1985
- Prototyping interactive information systemsCommunications of the ACM, 1983
- An Operational Approach to Requirements Specification for Embedded SystemsIEEE Transactions on Software Engineering, 1982
- Transformational Implementation: An ExampleIEEE Transactions on Software Engineering, 1981