Details
| Original language | English |
|---|---|
| Title of host publication | IFIP Transactions B |
| Subtitle of host publication | Computer Applications in Technology |
| Pages | 43-57 |
| Number of pages | 15 |
| Edition | B-10 |
| Publication status | Published - 1993 |
| Externally published | Yes |
| Event | IFIP TC5/WG5.10 Working Conference on Interfaces in Industrial Systems for Production and Engineering - Darmstadt, Ger Duration: 15 Mar 1993 → 17 Mar 1993 |
Abstract
Many engineering disciplines use graphical notations with defined semantic meaning, such as Petri nets, or structure charts. The diagrams drawn in these notations represent semantic models upon which application-specific operations may be performed. To handle this type of notations and their semantic models comfortably, a graphical editor can support them. As there are many different graphical notations in every discipline, reuse of general editor functionality should be supported and encouraged to save tool building effort. vis-A-vis is an object-oriented framework serving this purpose. However, instead of laying the burden of properly composing those classes on the tool builder's shoulders, vis-A-vis also contains a backbone architecture. In this paper we motivate the construction of vis-A-vis by listing the essential requirements that we had set out for a framework supporting in tool building. The scope of vis-A-vis based tools is defined, and a short survey of the main concepts of vis-A-vis is given. An example of a System Dynamics graphical notation editor which was built within vis-A-vis illustrates these concepts and shows how little effort a tool builder has to spend to implement an editor.
ASJC Scopus subject areas
- Engineering(all)
- General Engineering
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
IFIP Transactions B: Computer Applications in Technology. B-10. ed. 1993. p. 43-57.
Research output: Chapter in book/report/conference proceeding › Contribution to book/anthology › Research › peer review
}
TY - CHAP
T1 - vis-A-vis
T2 - IFIP TC5/WG5.10 Working Conference on Interfaces in Industrial Systems for Production and Engineering
AU - Lichter, Horst
AU - Schneider, Kurt
PY - 1993
Y1 - 1993
N2 - Many engineering disciplines use graphical notations with defined semantic meaning, such as Petri nets, or structure charts. The diagrams drawn in these notations represent semantic models upon which application-specific operations may be performed. To handle this type of notations and their semantic models comfortably, a graphical editor can support them. As there are many different graphical notations in every discipline, reuse of general editor functionality should be supported and encouraged to save tool building effort. vis-A-vis is an object-oriented framework serving this purpose. However, instead of laying the burden of properly composing those classes on the tool builder's shoulders, vis-A-vis also contains a backbone architecture. In this paper we motivate the construction of vis-A-vis by listing the essential requirements that we had set out for a framework supporting in tool building. The scope of vis-A-vis based tools is defined, and a short survey of the main concepts of vis-A-vis is given. An example of a System Dynamics graphical notation editor which was built within vis-A-vis illustrates these concepts and shows how little effort a tool builder has to spend to implement an editor.
AB - Many engineering disciplines use graphical notations with defined semantic meaning, such as Petri nets, or structure charts. The diagrams drawn in these notations represent semantic models upon which application-specific operations may be performed. To handle this type of notations and their semantic models comfortably, a graphical editor can support them. As there are many different graphical notations in every discipline, reuse of general editor functionality should be supported and encouraged to save tool building effort. vis-A-vis is an object-oriented framework serving this purpose. However, instead of laying the burden of properly composing those classes on the tool builder's shoulders, vis-A-vis also contains a backbone architecture. In this paper we motivate the construction of vis-A-vis by listing the essential requirements that we had set out for a framework supporting in tool building. The scope of vis-A-vis based tools is defined, and a short survey of the main concepts of vis-A-vis is given. An example of a System Dynamics graphical notation editor which was built within vis-A-vis illustrates these concepts and shows how little effort a tool builder has to spend to implement an editor.
UR - http://www.scopus.com/inward/record.url?scp=0027761525&partnerID=8YFLogxK
M3 - Contribution to book/anthology
AN - SCOPUS:0027761525
SN - 0444814965
SP - 43
EP - 57
BT - IFIP Transactions B
Y2 - 15 March 1993 through 17 March 1993
ER -