The joys of reviewing papers

Reviewing papers that were submitted for journals is always a tedious thing. First of all, because the deadline for the review is so far away from the moment you receive the paper, you usually end up reviewing it in the last 20 minutes or so before the review is due. Secondly, it is so unbelievably BORING to read 30 pages or so about other people's work. We did this, bla bla bla and then we did this bla bla bla, not like that guy did it but like this bla bla bla. But not when you review papers that were written by authors (like myself) for whom English is a second language. Even more so if you read papers that were translated (using a translator) from Chinese to English, or papers whose authors are definitely Chinese (or german for that matter, or thai). You can tell by the way the phrases are constructed and so on :) A few examples, even though these are not by far the best :))

However, the separation also leads to much bewilderment in the process of assembling systems. (bewilderment? wtf?)

First, the composition of quality properties is even impossible or it is possible but not at the same phase as that of functionalities, which makes it difficult to reason ...

Second, it is a paradox that dealing with the functional and quality of requirements of components separately.

The approach allowed designing and developing a software tool for devs modeling and simulation.

... besides the underlying network connectivity, the causally entering or quit of autonomous software entities may dramatically impact on the availability of software systems as well since the availabilities of autonomous entities may change over time and they are even unpredictable to some extent.

An AC had better be reused and assembled like a traditional component and it implements a collection of interfaces as a traditional component so that users could invoke its services.