Archived
This forum has been archived. Please start a new discussion on GitHub.
Middleware Services - feature comparison
Ice team,
We are in the process of doing requirements capture, and we are going to go about it by:
1) Putting together a list; to capture the (common) middleware, and the “services” they provide.
2) Internally we are going to ask different development team to see which “middleware services” they are required, and ask them to provide their "wish list".
3) Based on this wish list we will define our project middleware requirements, and find a middleware. It would hopefully be a COTS based.
I have put together the attached table which lists the features and I appreciate if the experts out there could verify the “ICE” related entries in the table.
Cheers
Amir Sadrossadat (PM)
Australian Centre for Filed Robotics,
University of Sydney
We are in the process of doing requirements capture, and we are going to go about it by:
1) Putting together a list; to capture the (common) middleware, and the “services” they provide.
2) Internally we are going to ask different development team to see which “middleware services” they are required, and ask them to provide their "wish list".
3) Based on this wish list we will define our project middleware requirements, and find a middleware. It would hopefully be a COTS based.
I have put together the attached table which lists the features and I appreciate if the experts out there could verify the “ICE” related entries in the table.
Cheers
Amir Sadrossadat (PM)
Australian Centre for Filed Robotics,
University of Sydney
0