System level testing is done usually by the testing team and test cases revolve around field level validations and the functional aspects of the application.
In acceptance level testing the test case revolve around the business perspective and usually done by business users
example : you would be testing a transaction flow end to end and would try to simulate transaction in customer's perspective.
TesterDays described difference between USER acceptance tests and system tests on v-model. The terms system and acceptance tests may be used different in different organizations however. Sometimes they even describe different categories: purpose and level. So you could have an testing of acceptance purpose at a system level (sorry for my poor English).
?:the art of a constructive conflict perceived as a destructive diagnose.
I'll answer shortly:
System testing is performed to ensure that application meets system specification (which can be written by tech writer or team leader or PM or someone else [depending of the company]).
Acceptance testing is performed to ensure that application meets all the requirements (which is written by the customer).
Look into V-model and you'll easily understand the difference
I find your comments very useful but still i have a confusion.
A requirements document (SRS)is written for all stakeholders including technical people and customers. If we are to create tests from SRS than how we can differentate system and acceptance tests.