• Journal of Internet Computing and Services
    ISSN 2287 - 1136(Online) / ISSN 1598 - 0170 (Print)
    http://jics.or.kr/

A Priority Process Based Connector's Interaction considering Component Processing Time


Jeong Hwa-Young, Journal of Internet Computing and Services, Vol. 6, No. 2, pp. 49-58, Apr. 2005
Full Text:
Keywords: Component composition, Connector interaction, Wright, ADL

Abstract

Connector's role between components is very important in the CBD(Component Based Development). The most connector has process ADL based rrethod was choosing FIFO method by component request. But in case many component's with various characteristics request It is difficult that this method operate efficiently, In this research, I did design and implement priority connector considering component's processing time, Also, I used Wright architecture for formal specification. Application result of proposed connector was spend more 388ms compares with existent FIFO method in total processing time. But this method could handle preferentially from components that have short processing time. Also, in case of component's waiting time in connector, existent FIFO method is 23323,1 ms and proposal method is 12731.27ms, So, proposal method could reduce waiting time for component process.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from November 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[APA Style]
Jeong Hwa-Young (2005). A Priority Process Based Connector's Interaction considering Component Processing Time. Journal of Internet Computing and Services, 6(2), 49-58.

[IEEE Style]
J. Hwa-Young, "A Priority Process Based Connector's Interaction considering Component Processing Time," Journal of Internet Computing and Services, vol. 6, no. 2, pp. 49-58, 2005.

[ACM Style]
Jeong Hwa-Young. 2005. A Priority Process Based Connector's Interaction considering Component Processing Time. Journal of Internet Computing and Services, 6, 2, (2005), 49-58.