NFR attributes to be identified for the system from integration perspective

	Attribute	Description	Required
1	Message Transformation	Message Transformation is the ability to transform the message into different forms and support for XML-java serialization.
2	Multi Channel/protocol Support	The system can use multiple transport channels to communicate between different systems. Ex: Http/Https/JMS/FTP/SMTP etc
3	Attachment Handling	Support for attachments across soap calls.
4	Multi channel/protocol support	The system can use multiple transport channels to communicate between different systems. Ex: Http/Https/JMS/FTP/SMTP etc
5	Attachment Handling	Support for attachments across soap calls.
6	Reliability	The reliable delivery of messages ensures the delivery of messages by supporting multiple retries both is synch and asynch mode and correlating messages once response is received.
7	Once and Only Once delivery	This ensures that the message is not redelivered again based on the uniqueness attributes of the message
8	Security	The need for WS-Security and support for XML signatures and XML-encryption
9	Auditing	The synchronous auditing if required within the scope of the transaction
10	Routing	The ability of the integration layer to route the message to the appropriate endpoint based on the rules or availability.
11	Transactions support	Transaction co-ordination that needs to be propagated and coordinated between multiple systems.
12	Mediations	Mediations to be supported if there any business/interaction specific pre or post processing required. Such as adding application specific headers which will be used for integration.
13	Versioning	Versioning will be used when there are multiple versions of the same service may be to address certain regulatory change in progress.
14	Sequencing	Sequencing will be used when we are to split a batch message and send the split message along with sequence so the aggregator to aggregate the batch based on the sequence.
15	Splitting	Splitting will be required if the batch sizes or message size is going beyond the message limits defined.
16	Business Rules	Business rules will be applied at the integration layer for reasons such as message validation.
17	Asynchronous Invocation	Asynchronous invocations would be required when we have batch uploads and nightly jobs.
18	Event Handling	Event handling can be used for event based processing. Event handling can be used to handle specific events such as permanent failure of delivery and to notify back office of the same.
19	Content Based Logic	Content based logic can used to validate and execute the business process based on the value contents of the message.
20	Store and Forward	Store and Forward can be a mechanism for non-repudiation or for reliability at the process level.
21	Intermediaries	Intermediaries will be used when there are interactions that will require the pre-post processing of the request or response by the other service. The intermediaries can be systems such as payment gateways and so on.
22	Policy management	Policies that define the interaction patterns between systems and services. The policy management provides repositories and interfaces to save and retrieve the policies.
23	Logging	Logging will be required in the on the integration points to monitor the behavior of the invocation process.
24	Metering	Metering will provide mechanisms to meter the invocations, response times and other behaviors of the invocation.
25	Monitoring	Monitoring provides a mechanism to monitor the invocations and the component behavior at the runtime.
26	Correlations	Correlations will be used to manage the relationships between 2 messages with different contexts but that would belong to the process.