|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Bo I. Sand?, "Entity-Life Modeling: Modeling a Thread Architecture on the Problem Environment," IEEE Software, vol. 20, no. 4, pp. 70-78, July/August, 2003. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2003.1207459, author = {Bo I. Sand?}, title = {Entity-Life Modeling: Modeling a Thread Architecture on the Problem Environment}, journal ={IEEE Software}, volume = {20}, number = {4}, issn = {0740-7459}, year = {2003}, pages = {70-78}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1207459}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Entity-Life Modeling: Modeling a Thread Architecture on the Problem Environment IS - 4 SN - 0740-7459 SP70 EP78 EPD - 70-78 A1 - Bo I. Sand?, PY - 2003 KW - concurrency KW - multithreading KW - resource sharing KW - software design KW - entity-life modeling (ELM) VL - 20 JA - IEEE Software ER - | |||
Object-oriented development identifies classes and relationships in the problem domain and carries them seamlessly into design and implementation. Entity-life modeling extends this modeling idea into the time domain. ELM identifies sequences of event occurrences in the problem space called event threads, which form the basis for threads in software. ELM offers two modeling techniques. The basic technique mechanically finds event threads in the problem, while the pattern technique deals with concurrency patterns in the problem, such as users contending for resources. Such patterns are modeled by means of threads and synchronized objects in software. ELM supports the notion of a concurrency level, which indicates the number of threads that is, in a certain sense, optimal for a given problem.