Specification
The project consists of designing and implementing a dynamic coalition system. Some
times organizations have to come together in an arbitrary fashion for limited time to do a
project. We call that a coalition. The membership of the coalition may not be known at
the time of the formation of the coalition. Members may join or leave a coalition any
time.
Each member of the coalition may offer one or more services that it wishes to share with
other members of the coalition. It registers these services (with parameters, proxy. etc.)
with a coalition service registry (CSR).
Each coalition member organization may have one or more users.
?
? A user may execute its
own organization’s services or execute a non-local service. In the case of a non-local
service, it invokes this service at CSR. CSR itself invokes the service at the provider, gets
the results, and returns to the requester. In other words, the requesting user is unaware of
the actual service provider. Only CSR knows it.
The coalition members execute on different machines. CSR itself is executing on 2
machines for increased availability. It may be accessed from any of the two, and it makes
no difference which one of the CSR’s they contact.
Develop a good graphical interface for CSR to help users register their services as well
as request execution of the services.
What to submit? (i) Project report including the design document and the
implementation details including snapshots of your screens explaining the options.(ii)
Source code (iii) Object code (if applicable) (iii) Make files (if any) (iv) Test output
(showing that your program works as specified) (v) README file