Teamwork Support in a Knowledge-Based Information Systems Environment
IEEE Transactions on Software Engineering
DAIDA: an environment for evolving information systems
ACM Transactions on Information Systems (TOIS)
Representing and using nonfunctional requirements: a process-oriented approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Interface support for data archeology
CIKM '93 Proceedings of the second international conference on Information and knowledge management
“…And nothing else changes”: the frame problem in procedure specifications
ICSE '93 Proceedings of the 15th international conference on Software Engineering
Managing performance requirements for information systems
Proceedings of the 1st international workshop on Software and performance
Specification and implementation of exceptions in workflow management systems
ACM Transactions on Database Systems (TODS)
Management of Performance Requirements for Information Systems
IEEE Transactions on Software Engineering
Representing Software Engineering Knowledge
Automated Software Engineering
Strategies for Integrating CASE Environments
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
On the Frame Problem in Procedure Specifications
IEEE Transactions on Software Engineering
Dynamic Constraints and Object Migration
VLDB '91 Proceedings of the 17th International Conference on Very Large Data Bases
| Hi-index | 0.00 |
In the process of developing an Information System, one passes through stages that include requirements gathering, design specification, and software implementation. The purpose of the TDL language is to express the conceptual design of an information system; it is the intermediate language in a triad that includes the language Telos, which captures an evolutionary view of the application domain and requirements, and DBPL, a procedural programming language that has persistent values and transactions supporting the development of databases. We consider TDL's features for specifying the data and eventual procedural components of the system, and discuss how these are related to its companions. We also survey several tools for manipulating TDL descriptions which are currently under development, and give a detailed example of the iterative refinement of TDL designs into DBPL programs.