loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
What Models Mean
September/October 2003 (vol. 20 no. 5)
pp. 26-32
ASCII Text
x 
 
Ed Seidewitz, "What Models Mean," IEEE Software, vol. 20, no. 5, pp. 26-32, September/October, 2003.
 
 
BibTex
x
 
@article{ 10.1109/MS.2003.1231147,
author = {Ed Seidewitz},
title = {What Models Mean},
journal ={IEEE Software},
volume = {20},
number = {5},
issn = {0740-7459},
year = {2003},
pages = {26-32},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1231147},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - What Models Mean
IS - 5
SN - 0740-7459
SP26
EP32
EPD - 26-32
A1 - Ed Seidewitz,
PY - 2003
VL - 20
JA - IEEE Software
ER -
 
Ed Seidewitz, InteliData Technologies

Models must be more than informal pictures. By carefully considering a model?s relationship to the thing being modeled and to other models derivable from it, we can understand how to use models to reason about the systems we build and how to use metamodels to specify languages for expressing models.

Citation:
Ed Seidewitz, "What Models Mean," IEEE Software, vol. 20, no. 5, pp. 26-32, Sep./Oct. 2003, doi:10.1109/MS.2003.1231147
Usage of this product signifies your acceptance of the Terms of Use.