i hope, this paper can serve your purpose..

http://homepages.cs.ncl.ac.uk/graham.morgan/22_Morgan_SLA.pdf

http://www.cloudbus.org/reports/SLA-UtilityComputing2010.pdf

I think cloud computing infrastructure needs to pass through SLAs as applicable any other generic ICT infrastructure related SLA. Quality standards on services can be followed.

There are many software tools to monitor Cloud Computing performance for SLA purpose, some of them include in the following links:

http://talkincloud.com/cloud-computing-management/20-cloud-monitoring-and-management-tools-which-are-best

https://blog.profitbricks.com/top-47-cloud-server-monitoring-sysadmin-tools/

http://www8.hp.com/us/en/software-solutions/sitescope-application-monitoring/

http://www8.hp.com/us/en/software-solutions/operations-manager-infrastructure-monitoring/

http://www-03.ibm.com/software/products/en/ibmsmarmoni

Some of them do allow you to perform a Proof of Concept (PoC) for free evaluation.

Suggesting to consider the following before selecting & implementing a monitoring software tool:

1) what cloud workload performance needs to monitor for SLA generation - e.g. IaaS compute, memory, storage, I/O throughput, PaaS & SaaS software application types of SLA (availability, utilization, performance etc).

2) whether the software tool can monitor cloud computing performance based on multi-tenancy (if you are a public cloud service provider) or various-business units (even in a private cloud environment).

3) whether to acquire a monitoring software tool as 1-off purchase (capex), pay-per-use (opex) or cloud based SaaS etc (if via cloud based SaaS, need to clarify clearly the data & apps ownership when contract is terminated & location where the collected data is stored e.g. some companies / countries prohibit monitored data store outside the country).

4) how the SLA report being generated e.g. canned report, customizable report, required API integration with SLA Management Software / module from ITIL / ITSM Service Desk systems, required integration with other module for penalty / rebate credits calculation etc.

5) whether the software tool needs agent planted in the monitored nodes or is agentless (agent-based software tool needs additional effort to deploy the agent automatically or manually but can collect more information for detailed SLA calculation)

6) ease & completeness of training provided, design (HA or without HA), implementation, post-implementation support e.g. only 24 x 7 remote call support or onsite support within certain response time committed etc.

Maybe these papers are useful for your Research

http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=6927082

http://www.buyya.com/papers/SLA-CloudMan2015.pdf