| R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993. |
....sends reminder user returns book user returns pass (a) borrow book request return book return pass ask pass give pass give book send reminder user library (b) Fig. 1. Rumbaughs Event Trace (a) and Event Flow (b) Exactly at this point, we disagree with the common opinion (e.g. RBP 91] Wie93] FW93] to focus on individual objects and their behaviour without getting a real grip on the system dynamics. Up to now, the events, the scenarios, the traces and the event flow, are created and specified in an informal way, and hence missing any meaning and semantics, which makes working with ....
....object oriented programming code automatically. The actual code generation is still a topic of research. Among the representations generated are State Transition Diagrams [RBP 91, BR95a] Jacksons Entity Life Cycles [Jac83] Wieringa s Object Life Cycles and Wieringa s Communication Diagrams [Wie93] Both Jackson and Wieringa distinguish between modeling the UoD and modeling the database itself. According to Wieringa: A life cycle is the dialog, a process involving a system and some systems in its environment that has a logical completion, that an object in the UoD has with its surrogate in ....
[Article contains additional citation context not shown here]
R.J. Wieringa. A Method for Building and Evaluating Formal Specifications of Object-Oriented Conceptual Models and Database Systems. Technical Report IR-340, Vrije Universiteit, Amsterdam, 1993.
....objects automatically from a Cem expressing the system dynamics. Among the representations generated are State Transition Diagrams [ Rumbaugh et al. 1991, Burg Riet, 1995b ] Jacksons Entity Life Cycles [ Jackson, 1983 ] Wieringa s Object Life Cycles and Wieringa s Communication Diagrams [ Wieringa, 1993b ] Both Jackson and Wieringa distinguish between modeling the UoD and modeling the database itself. According to Wieringa: A life cycle is the dialog, i.e. a process involving a system and some systems in its environment that has a logical completion, that an object in the UoD has with its ....
....limited to describe behavioural evolution of objects when considered in isolation. 5. 2 Life Cycles Another representation for object dynamics are life cycles, which are used by [ Jackson, 1983 ] Wieringa, 1993b ] and [ Shlaer Mellor, 1992 ] The representations of [ Jackson, 1983 ] and [ Wieringa, 1993b ] contain almost the same information, and hence we will focus on Jsd life cycles in the next discussion, but we will show Wieringa s models as well, Figure 5.4. For every function a certain active object performs, a branch in the entity life cycle is created. Figure 5.3 shows one of the branches ....
[Article contains additional citation context not shown here]
R.J. Wieringa. A method for building and evaluating formal specifications of objectoriented conceptual models and database systems. Technical Report IR-340, Vrije Universiteit, Amsterdam, 1993.
....A good example of such a toolkit for industrial product design (which is external design) is the collection of design methods described by Jones [30] in 1970. In a similar way, toolkits for software product specification are defined by Jensen and Tonies [29] Birrel and Ould [3] and Wieringa [54, 52]. The tools that we have in mind are conceptual. They are used to reduce uncertainty about the final product by giving heuristics for making an (external) design decision and by representing the result of this decision. It is possible to supplement them with software tools such as diagram editors ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....a need for conceptual modeling methods that adopt the best elements of modern object oriented methods and traditional functional methods, as well as bridges the gap between informal domain understanding and formal system specification. The Method for Conceptual Modeling (MCM) reported elsewhere [6, 5] is composed from elements of traditional and modern methods and tries to bridge the gap between formal and informal understanding. It can be used in conjunction with a formal specification language such as LCM [3] Troll [4] Oblog [1] or Albert [2] MCM takes a simple view of observable system ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
.... X cannot be represented in TCM, extend TCM with a notation to represent this part, subject to the following constraints: The added notation should resemble as much as possible some existing and widely used notation and TCM is a further development of MCM (Method for Conceptual Modeling) [44]. The motivation for this change in name is that MCM is built from elements taken from existing methods, possibly after simplifying these elements. It is not intended to be a method but a toolkit of methods and techniques that can be used as needed by the development situation. The tools and ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....borrow and memb borrow always occur synchronously. The two local actions only update the local state of two entities but the synchronous occurrence results in a simultaneous update of the state of several objects. This solution is followed in several algebraic and logical specification formalisms [11, 50, 18, 35, 46, 48]. It resembles specification of object interaction at the programming language level by means of contracts [20] We now returning to the guidelines of the JSD ER approach. ffl Allocate an action to an entity to enforce a sequencing of actions in the life of this entity. Allocate it to several ....
....15 is preferable to use a declarative way of specifying the effect of transactions, because this leads to a higher level of implementation independence. This approach is taken in Fusion [10] and in a number of formal methods that are currently under development, such as Troll [25, 18, 36] and MCM [50, 48]. 6 Discussion: Function Decomposition The transaction decomposition table allows us to pinpoint a common core of superficially very different methods, such as JSD, ER modelling, DF modelling, and OMT. It is easy to show that other object oriented methods, such as Shlaer Mellor [39] and Fusion ....
[Article contains additional citation context not shown here]
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993. 18
....at least two different states of the system. Dynamic integrity constraints of objects can at least partly be represented by object life cycle diagrams. There are several diagram techniques in use to represent life cycles, such as state charts [52] finite state machines [58] and process graphs [72]. Among the non object oriented methods, Jackson System Development represents entity life cycles by entity structure diagrams [31] In what follows, we will use a simple finite state machine representation of life cycles. What concerns us here is the way in which we can represent constraints on ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
.... a Kripke structure combined with a process algebra is described in a number of papers [14, 19, 17] First steps towards an operational semantics are taken by Spruit [12, 11] The method used to analyze the case study is called MCM (Conceptual Modeling Method) described in another companion report [16]. This name is chosen to bring out the connection with LCM. MCM leads to two models, an informal and formal one. The informal model is meant as interface between the formal model on the one hand and the intuitive understanding of analysts and domain specialists on the other. The formal model is ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....other notational issues. This revision process included changing the name of the language from CMSL to LCM, because the abbreviation CMSL proved to be unpronouncable to most people. Besides, it suggests its relation to MCM (Method for Conceptual Modeling) which is described in a companion report[13]. A second companion report describes the application of MCM to a case study, in which a LCM specification is developed[14] This document intends to serve as a reference for the specifier in the area of syntactic issues of LCM 3.0. Although the text and examples in this document suggest ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....in order to make the language more useful for the specification of control intensive systems. The solution was found by using elements of the method MCM (Method for Conceptual Modeling) which is intended to be used together with LCM if it is applied to the specification of data intensive systems [9, 10]. In addition to testing the extent to which LCM 3.0 can be used for the specification of control intensive systems, the purpose of this report is also to test the extent to which MCM can be extended to a method for the specification of conceptual models of such systems. One feature of MCM that ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....unary functions and predicates in order sorted logic Figure 1: Integration of semi formal and formal techniques in MCM. been less well studied. In MCM (Method for Conceptual Modeling) this has been done by combining existing formal and semi formal specification techniques as shown in figure 1 [14]. Unifying idea behind this integration is that a data manipulation system can be modeled as manipulating a set of surrogates, each of which represents a UoD object. Objects (an therefore surrogates) have a local state and behavior, and are subject to local and global constraints on permissible ....
....scenarios, and are evaluated with respect to this structure. The functions of knowledge based systems will also fall under one of these categories. This simple picture allows us to represent much of what is common to a wide variety of semi formal modeling techniques. Details are given elsewhere [14, 15, 16, 17, 18]. The question arises when it is cost effective to apply the machinery of some formal specification technique. From an engineering point of view, the role of formal specification with respect to requirements engineering is to facilitate simulation of the behavior of a product before the product ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....product engineering [31] Obviously, defining a set of coherent and well integrated tools for behavior specification alone is still a research topic. It would go beyond the bounds of this report to discuss in detail what how this can be done. A preliminary version of such a toolkit is given in [41]. A detailed analysis of some existing methods in search of useful tools is given in [45, 43, 46, 44, 40] The results of this search will be used to define a second version of the toolkit. The two taxonomies defined in this report play the following role in the definition of this toolkit: ffl ....
R.J. Wieringa. A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM). Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit, December 1993.
....system decomposition, as a later stage, following a TRADE specification. TRADE is based upon an analysis of structured and object oriented software specification methods (Wieringa 1995, Wieringa Saake 1996, Wieringa 1996, Wieringa 1997a, Wieringa 1997b) An earlier version was known as MCM (Wieringa 1993). The current version has a preliminary definition (Wieringa 1997c) but will be defined more elaborately after a number of case studies, including this one, are finished. The rest of the paper is structured as follows. In Section 2, a short introduction is given to the two basic policies for lamp ....
Wieringa, R. (1993), A method for building and evaluating formal specifications of object-oriented conceptual models of database systems (MCM), Technical Report IR-340, Faculty of Mathematics and Computer Science, Vrije Universiteit.
No context found.
R.J. Wieringa. A Method for Building and Evaluating Formal Specifications of Object-Oriented Conceptual Models and Database Systems. Technical Report IR-340, Vrije Universiteit, Amsterdam, 1993.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC