Introduction to the ISO specification language LOTOS
Computer Networks and ISDN Systems - Special Issue: Protocol Specification and Testing
ACM Transactions on Programming Languages and Systems (TOPLAS)
CORBA distributed objects: using Orbix
CORBA distributed objects: using Orbix
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Open Distributed Processing and Multimedia
Open Distributed Processing and Multimedia
Can Behavioral Requirements Be Executed? (And Why Would We Want to Do So?)
EMSOFT '02 Proceedings of the Second International Conference on Embedded Software
ICENI: an open grid service architecture implemented with Jini
Proceedings of the 2002 ACM/IEEE conference on Supercomputing
| Hi-index | 0.00 |
Component-based software architecture is very important for current software engineering practice because (a) it is the basis for re-use of software at the component level, and (b) in distributed systems, the physical distribution of an application over separate computers represents a decomposition of the application. Typical e-commerce applications consist of various components sometimes belonging to different organizations, and presenting different user interfaces to various categories of users. We review in this paper the current trend in standards for inter-component communication in distributed systems, including various forms of remote procedure calls (RPC) and message passing, and paradigms for describing and implementing user interfaces in the Web environment. We discuss whether the user interface can also be described, at an abstract level, by RPC primitives. In the second part of the paper, we discuss the importance of indicating which party is responsible for making certain decisions for selecting control flow alternatives and certain parameter values. This leads to some guidelines for describing system behavior scenarios at the requirements level. We also discuss how this approach can be integrated with screen-oriented behavior definitions.