A computer system for modeling is disclosed, where the computer system has a storage device, first and second platforms, a portable persistent model, and first and second platform-dependent computerized modeling systems (CMS). Each platform is interfaced to the storage device and provides system-dependent services. The first platform has a first type of operating system and a first type of computer hardware including a first memory, and the second platform has a second type of operating system and a second type of computer hardware including a second memory. The model resides in the storage device in a platform-independent format and includes persistent component objects. The first CMS resides in the first platform memory and the second platform-dependent CMS resides in the second platform memory. Each CMS provides CMS services including retrieving the model from the storage device, manipulating the model, changing the model by adding and removing persistent objects, and persistently saving the model to the storage device. Each CMS includes a static kernel and a dynamic framework. The kernel executes on the platform and interfaces to the operating system and the computer hardware, and provides services necessary to load and execute CMS services and to interface to the platform services. The framework executes on the platform and interfaces to the kernel, provides a platform-independent visual interface between the CMS and a CMS user, and employs the services of the kernel.

Object-oriented computerized modeling system

A system and method are presented in which the system manages the properties related to the architectural layers within the context of software development. It provides mechanisms to define the architectural layers and the additional information required by them. The method for specifying a software model comprises specifying at least one architectural layer for a software system; specifying at least one property and relating each the at least one property to one of the at least one architectural layer and to at least one model element type to which the at least one property is attached; and automatically providing assistance for specifying property contents of the at least one property using an architecture layer corresponding to the at least one property for each one of a plurality of model elements to be defined as part of a software model of the software system.

A system and method for managing architectural layers within a software model

A workflow model is useful for business process analysis. A well-built workflow can help a company streamline its internal processes by reducing overhead. The results of workflow modeling need to be managed as information assets in a systematic fashion. Reusing these results is likely to enhance the quality of the modeling. Therefore, this paper proposes a document-based workflow modeling mechanism, which employs a case-based reasoning (CBR) technique for the effective reuse of design outputs. A repository is proposed to support this CBR process. A real-life case is illustrated to demonstrate the usefulness of our approach.

Document-based workflow modeling: a case-based reasoning approach

Abstract A workflow model is useful for business process analysis. A well-built workflow can help a company streamline its internal processes by reducing overhead. The results of workflow modeling need to be managed as information assets in a systematic fashion. Reusing these results is likely to enhance the quality of the modeling. Therefore, this paper proposes a document-based workflow modeling mechanism, which employs a case-based reasoning (CBR) technique for the effective reuse of design outputs. A repository is proposed to support this CBR process. A real-life case is illustrated to demonstrate the usefulness of our approach.

Document-based workflow modeling : case-based reasoning approach = 문서기반 워크플로우 모델링 : 사례기반추론 접근법

We address a problem of reusing and customizing soft IP components by introducing a concept of design process - a series of common, well-defined and well-proven domain-specific actions and methods performed to achieve a certain design aim. We especially examine system-level design processes that are aimed at designing a hardware system by integrating soft IPs at a high level of abstraction. We combine this concept with object-oriented hardware design using UML and metaprogramming paradigm for describing generation of domain code.

Application of UML for hardware design based on design process model

This paper presents a hierarchical, object-oriented model as a basis for reuse of components in the design process of digital systems. The model forms a uniform knowledge base which consists of formal descriptions about functional, qualitative, and quantitative properties of systems and components. It supports the synthesis of systems from the described components. Starting at a system specification different models and descriptions are generated for simulation, prototyping, analysis and high level synthesis.

An object-oriented model for specification, prototyping, implementation and reuse

Thispaper describes a method for the design of digital systems that automatically derives an executable prototype of a system from an infornzal specification. Our method bases oy1 an object-oriented hierarchy of classes which describe the functions of components. A tree of instances of these classes representing a certain system is built depending on the specification. VHDL descriptions of all classes involved in this free are transformed into VHDL code for the complete system. Our approach emphasizes a bottom-up procedure arid reuse of existing components. Several different approaches towards the description of hardware at system level have been suggested [7], for example Speccharts [13], Statecharts 131, speedC€€ARTS [ll], SDL [4], Extended Sequence Charts [5]. Important models used as a basis by these approaches are communicating concurrent processes, extended finite state machines, and hierarchical descriptions. The methods for system level design with these concepts usually follow a top-down approach: Starting with an initial graphical representation, a sequence of refinement steps is executed. The intermediate representations are attributed by VHDL annotations. This refinement process lasts until a complete description of the system’s behavior is built that can be compiled into VHDL code which in turn serves as a foundation for a simulation or synthesis. Our method of designing digital systems uses a bottonup approach based on an objectqriented domain model. For every concept met in a certain domain this model includes a description of all variants of the type. In case of functional units this includes all information concerning its behavior as well as quantitative and qualitative properties. This includes the unit’s interface, descriptions of its behavior using different approaches (e. g. VHDL, Petri-nets, temporal logic), hierarchical structuring, specialization, attributes, and generic parameters. In order to build a complete hierarchy from this set of types, appropriate relations between them have to be defined. In our case, two relations were needed:

Level Modeling of System Components for the Generation of VHDL Code

This paper describes a method for the design of digital systems that automatically derives an executable prototype of a system from an informal specification. Our method bases on an object-oriented hierarchy of classes which describe the functions of components. A tree of instances of these classes representing a certain system is built depending on the specification. VHDL descriptions of all classes involved in this tree are transformed into VHDL code for the complete system. Our approach emphasizes a bottom-lip procedure and reuse of existing components.

/pdf/object-oriented-high-level-modeling-of-system-components-for-3zsfqv26mb.pdf

Object-oriented high-level modeling of system components for the generation of VHDL code

We present an object-oriented method to represent knowledge about a set of digital systems. Based on this representation, concrete systems can easily be specified, their implementations in various models such as VHDL or Petrinets can be derived automatically from a specification by a knowledge based configuration system. In this paper, we focus on the set-theoretic foundations of our model.

Object-Oriented High Level Modeling of Complex Systems

In this paper we present a new method to specify digital systems at the system level and to automatically transform a specification into a set of required system components from which in turn a complete system can be constructed using a knowledge-based configuration system. Our approach bases on an object-oriented domain model which captures all knowledge about a certain domain of systems. Throughout the paper we use the domain of RISC processors as an example. We show how the designer specifies systems based on a given domain model and how a specification is automatically mapped into a set of system functions.

Sören Schulze

Papers

An object-oriented model for specification, prototyping, implementation and reuse

Level Modeling of System Components for the Generation of VHDL Code

Object-oriented high-level modeling of system components for the generation of VHDL code

Object-Oriented High Level Modeling of Complex Systems

Automating system-level design: from specification to architecture