| CRP&UAT [message #261137] |
Tue, 21 August 2007 23:43  |
tsm.apps
Messages: 22
Registered: August 2007
Location: Bangalore
|
Junior Member |
|
|
Hi
This is mahesh, could you pls tell me what is the difference between CRP testing and UAT testing. whaen UAT will occur and when CRP will occur.
Mahesh
|
|
|
|
| Re: CRP&UAT [message #261174 is a reply to message #261137] |
Wed, 22 August 2007 01:47  |
arunkp76
Messages: 16
Registered: August 2007
Location: Chennai
|
Junior Member |
|
|
Mahesh,
CRP - Conference Room Pilot
CRP is meant for the core users and sterring committe members to have a look and feel of the application and see how the current processes will be mapped in Oracle apps
UAT - User acceptance testing
User accepatance testing will be the last step before the go-live where the actual end users will be trained in application/mapped processes and given a chance to check all the processes.
Regards ... Arun
|
|
|
|
| Re: CRP&UAT [message #261245 is a reply to message #261137] |
Wed, 22 August 2007 03:48 |
arunkp76
Messages: 16
Registered: August 2007
Location: Chennai
|
Junior Member |
|
|
Mahesh,
CRP :
Purpose of Conference room Pilot
> To see that the computer software can support all the things we need to do. (And many of the things that can go wrong in the business.)
> To identify operational responsibilities. To identify new procedures needed, and to test draft procedures and policies.
> To identify training needs.
> To identify implementation method and issues to be resolved.
> To test problem management procedures.
> To confirm data definitions (will the system interpret the data codes devised and be able to use them)
> To confirm data conversion rules (will the new system use the data converted from the old system properly)
> To confirm the system testing already carried out, for batch processes and job streams and interfaces, will work in a repetitive production environment
UAT:
The purpose of User Acceptance Testing
The explanation of UAT is actually in its name. Taking each part separately explains what it is about.
User
Users means the real business users, who will have to operate the system; normally the staff of an organisation, but it could be your suppliers or customers. They are the only people who understand exactly what the business is, and how it operates. Therefore they are the only people qualified to check a system to see if it will deliver any benefit to the business or organisation.
System developers cannot do it, as although they are expert in writing software, they are unlikely to know anything about the realities of running the organisation, other then what they have acquired from requirements specifications, and similar documents. In addition they have been closely involved in the design compromises that always take place when a system is being developed, and so have a commitment to the system as it is.
Acceptance
The acceptance of a system means you are confident it will give benefit to the organisation. It does not mean that it only meets the original specification as requested. A system may very well meet all the specifications asked of it, but when trying to see how it will work in the business it is realised that it will not give anything positive to the organisation, or may even damage the organisation. This may be for a number of reasons such as a change in the business or business environment, such as a takeover.
The point is that a system may not be acceptable, even if it meets specification. You may still have to pay the supplier, but you will not incur any costs to implement it. Of course it may not even work to specification, which makes the question of acceptance even harder to answer. There are cases where it is worth implementing and paying for systems, which are imperfect, but that deliver real business value.
Testing
Whenever people are asked what testing is, many of them say it is to prove the system works. This is the key problem with the way UAT is employed in many organisations, as it is impossible to prove any system is correct. In fact a lot of effort is expended, and wasted, in trying to get right answers.
There is much literature on the subject of testing, and most writers agree that all you can prove is if a system is wrong. Therefore a good test is one that is designed to try and make a system fail, so as to expose its faults before it goes live. This type of testing is the only type worth doing.
UAT
Bringing the three words together shows that the point of UAT is for business users to try and make a system fail, taking into account the real organisation it will be working in. It is checking the system in the context of the business environment it will operate in.
Regards,
B.T.S.Ananth
|
|
|
|
| Re: CRP&UAT [message #261536 is a reply to message #261245] |
Thu, 23 August 2007 00:04 |
tsm.apps
Messages: 22
Registered: August 2007
Location: Bangalore
|
Junior Member |
|
|
Hi Arun & B.T.S.Ananth
Thanks a lot for giving the solution which is so useful for me past 5 days onwards im searching for this answer but i did't get exact solution. today i got this thank you
thanks®ards
Mahesh
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
