1987
DOI: 10.1016/0166-3615(87)90037-6
|View full text |Cite
|
Sign up to set email alerts
|

Information system analysis and conceptual database design in production environments with M∗

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

1988
1988
1997
1997

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(7 citation statements)
references
References 11 publications
0
7
0
Order By: Relevance
“…The M* methodology (Di Leva et al, 1987, 1988) was originally developed for design and analysis of information systems of CIM environments. It has now been extended to the analysis and design of reactive systems, such as design and manufacturing systems.…”
Section: The M *-Object Methodologymentioning
confidence: 99%
See 1 more Smart Citation
“…The M* methodology (Di Leva et al, 1987, 1988) was originally developed for design and analysis of information systems of CIM environments. It has now been extended to the analysis and design of reactive systems, such as design and manufacturing systems.…”
Section: The M *-Object Methodologymentioning
confidence: 99%
“…Process integration requires a sound and open information system but also relies on a common shared vision of the project provided by the &dquo;business process map&dquo; that is an organisation model. Some specific models and methodologies have been proposed in the literature for modelling engineering information systems such as SAM*- (Su, 1986), M* (Di Leva et al, 1987), or TSER (Hsu and Rattner, 1990). …”
Section: Technical Issues Concernmentioning
confidence: 99%
“…At the design-specification level, the AMICE project has selected the entity relationship attribute (ERA) approach first proposed by Chen (1976) and later extended in the M* methodology (Di Leva et al 1986). The ERA methodology adopted is used to transform the object-oriented information description obtained at the requirements-definition level into an unambiguous semantic data-oriented model at the design-specification level.…”
Section: Information Modelling At the Design-specification Levelmentioning
confidence: 99%
“…The internal schema is concerned with definition of the storage structures of files and databases to be implemented, storage tuning for performance considerations, and final specifications of external schemata and database transaction definitions using data languages of the target implementation systems. The information modelling and analysis methodology being defined for CIM -OSA is largely based on recent work concerning the SAM' model (Su 1986) and the M' methodology for CIM information system modelling and analysis (Di Leva et al 1986, Vernadat et at. 1989.…”
Section: Information Viewmentioning
confidence: 99%
“…Requirements for CIM applications are now usually modelled using classical approaches based on SADT/IDEF0 (see, e.g., the ICAM project [HDM88]) or MERISE (see, e.g., the M* project [LVB87]) or a combination of these approaches. New approaches are now emerging with the objectives of (i) increasing the degree of expressiveness, i.e.…”
Section: Introductionmentioning
confidence: 99%