Integrating database technology, rule‐based systems and temporal reasoning for effective information systems: the TEMPORA paradigm

Loucopoulos, Pericles; McBrien, Peter; Schumacker, F.; Theodoulidis, Babis; Kopanas, Vassilis; Wangler, Benkt

doi:10.1111/j.1365-2575.1991.tb00032.x

Cited by 28 publications

(15 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As in object-oriented models, data objects have been classified into types-structured objects such as forms, memos, financial worksheets etc and unstructured objects which have free form text and graphics. Some models such as Minstrel-ODM [43] and TEMPORA [45] allow for non-exclusivity in the classifications, resulting in a network structure of object types (rather than a hierarchy). The definitions of object types make use of such well known mechanisms as abstraction, reference, object composition, object instances, derivation, time-stamping etc.…”

Section: Documentsmentioning

confidence: 99%

See 1 more Smart Citation

Office Information Systems: A Retrospective and a Call to Arms

Amaravadi¹

2014

JSEA

View full text Add to dashboard Cite

Office Information Systems is a field of computer science concerned with studying offices and developing technologies to support office workers. The field initiated in 1982 suffered a gradual demise by 2004. However, many of the themes and issues that motivated the discipline continue to exist today. Office workers continue to struggle with routine tasks that do not have adequate IT support and the problem is worse for mobile employees. In this paper we provide a retrospective on OIS technologies with the hope of stimulating interest in the discipline and addressing the needs of office workers worldwide. The evolution of office technologies and a detailed discussion of past research are provided. The discussion shows that technology support for office workers is still inadequate. The paper suggests a technology vision and architecture to motivate researchers and identifies challenges for future research.

show abstract

Section: Documentsmentioning

confidence: 99%

“…Dependent objects for instance, are objects whose existence depends on other objects. Thus a "car engine" is a dependent object of "car" [45]. The activities performed with objects usually include storage, presentation, retrieval, deletion and update [48].…”

Section: Documentsmentioning

confidence: 99%

Office Information Systems: A Retrospective and a Call to Arms

Amaravadi¹

2014

JSEA

View full text Add to dashboard Cite

show abstract

“…There are many examples of the use of the object-oriented approach in systems analysis and development in Van Baelen et al (1992), Booch (1991), Coad & Yourdon (1991), Coleman et al (1992), Rumbaugh et al (1991). Furthermore, examples of the use of rules in requirements specifications may be found in DHaenens et al (1991) and Loucopoulos et al (1991). The VENUS environment combines both the object-oriented and rule-based approaches within a uniform modelling framework for all system aspects.…”

Section: Related Workmentioning

confidence: 99%

Towards the Development of Effective and Flexible Information Systems

Tsalgatidou

Gouscos

Halatsis

1994

AJIS

View full text Add to dashboard Cite

The development of Information Systems which are effective (i.e. satisfy users' needs) and flexible enough to incorporate future changes of user requirements basically depends on the importance given to the requirements analysis stage and to the techniques employed for their development This paper presents a new approach to requirements analysis through an environment called VENUS. The VENUS environment provides a set of tools to support the requirements capture and analysis process so that design and development is more effective and flexible. The construction of user requirements starts by first constructing an Entity-Relationship Model which is then transformed to an Object-oriented Rule-based Model (ORM) where rules are used for the definition of the behaviour of each object class. ORM is then mapped to a graphical Petri-net based model and is validated by employing graphical animation and exploiting formal properties of the underlying Petri-net formalism. INTRODUCTIONTwo desirable characteristics of Information Systems are effectiveness and flexibility. Effectiveness refers to the satisfaction of users' needs and is primarily related to the production of valid and complete requirements specifications. Flexibility refers to the ability of Information Systems to easily incorporate any future changes of user requirements; flexibility depends on the techniques employed for the development of information systems starting from the initial requirements analysis phase to the final implementation and integration stage. The importance of requirements specifications in the information systems development process is not a recently identified need (Endres, 1975). Boehm (1975) has denoted that incorrect requirements specifications result in serious errors in the information system development process, where the cost to fix them increases as the development process progresses. However, there is still a lack of methodologies and tools which would focus on the capture and validation of requirements specifications and the work reported by Reubenstein and Waters (1991), Zave (1991) and Fickas and Finkelstein (1993) are among the few examples that can be found in this area. The large number of existing methodologies for systems analysis and design produce specifications which are inherently static. Furthermore, CASE tools play a passive rather than active role in requirements specifications. A developer, in order to validate the captured requirements, tries to derive a system's behaviour from a static description. What is needed is an approach and a set of tools that enables a developer to obtain a 'working' model of a system at the early requirements phase, so that the system's behaviour can be better understood and appreciated by end users. This may be achieved if the produced requirements specifications are executable. An executable specification is a formal model of the system with the ability to simulate the system's behaviour when executed by a suitable interpreter, thus, such a specification can be thought of ...

show abstract

“…Model validation could be further facilitated by inspecting the dynamic aspects of the system in different levels of abstraction. For these purposes, we are using Petri nets [9] as the underlying formalism for graphically representing the rule-based behaviour model in a number of abstraction levels and for validating it by employing graphical animation or even using formal validation tools. T o this end, this paper introduces the Rule Based Net model which is subsequently mapped to a specialised Predicate Transition (PrT) net model.…”

Section: Inheritance and Redefinition Of Behaviour Unitsmentioning

confidence: 99%

Rule-based behavioural modelling of information systems

Tsalgatidou

Gouscos

Halatsis

[1993] Proceedings of the Twenty-Sixth Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

This paper introduces a rule-based object-oriented model and a new graphical formalism capable of representing the behaviour of information systems at the desired level of abstraction. The graphical model, called Rule-Based Net (RBN), is based on Petri nets and it can be considered as an abstraction of Predicate Transition nets (PTT nets). The formality of the RBN model and its graphical and executable nature provide a very good basis for its analysis and validation. RBNs provide a simple net representation of information systems dynamic behaviour showing flow of control. If information flow is desired too, RBNs are mapped to specialised P r T nets. In this way, all the well developed techniques on P r T nets could be exploited for an-alytically deriving general properties of an information system.

show abstract

Integrating database technology, rule‐based systems and temporal reasoning for effective information systems: the TEMPORA paradigm

Cited by 28 publications

References 11 publications

Office Information Systems: A Retrospective and a Call to Arms

Office Information Systems: A Retrospective and a Call to Arms

Towards the Development of Effective and Flexible Information Systems

Rule-based behavioural modelling of information systems

Contact Info

Product

Resources

About