Implicit Invocation Architecture

Advantages

· This system supports functionality enhancement by addition of new components and interfaces. (enhanceabiliby (+))

· Insulate computations from changes in data representation. This will bring easy modification of individual modules without changing entire system. (modification (+))

· The system evolves easily: Components may be replaced or added by other newly designed components without affecting existing system or by establishing new interfaces for new components with current system. (evolution (+))

· It usually provides a user-friendly interface. (user-friendliness (+))

· If some components malfunction, the system might still perform some functions. (robustness (+))

Disadvantages

· Difficult to control the processing order of the implicitly invoked modules because components relinquish control over the computation performed by the system. (time performance (-))

· It usually requires more space due to transaction data/files creating. (space performance (-))

· Most of the system components have to be used in similar system due to data sharing. The reusability is low. (reusability (-))

· Reasoning about correctness can be problematic, since the meaning of a procedure that announces events will depend o the context of bindings in which it is invoked. (understandability (-))

· Low portability: some modules can be implemented in same architecture designs as a whole. (portability (-))