项目实施中CRP的含义，以及各个阶段

项目实施中CRP的含义，以及各个阶段

CRP (Confrence Room Pilot) 会议室模拟，模拟运行及用户化。在基本掌握软件功能的基础上，选择代表产品，将各种必要的数据录入系统，带着企业日常工作中经常遇到的问题，组织项目小组进行实战性模拟，提出解决方案。模拟可集中在机房进行，也称之为会议室模拟（conference room pilot）。

我们看看维基百科对CRP的解释。

Concept from Wiki 维基上的概念
Conference room pilot (CRP) is a term used in software procurement and software acceptance testing. A CRP may be used during the selection and implementation of a software application in an organisation or company.
CRP是在软件购买和软件接受度测试时用到的词汇。组织或者公司中软件应用的选型和实施的时候可能会用到。

The purpose of the conference room pilot is to validate a software application against the business processes of end-users of the software, by allowing end-users to use the software to carry out typical or key business processes using the new software. A commercial advantage of a conference room pilot is that it may allow the customer to prove that the new software will do the job (meets business requirements and expectations) before committing to buying the software, thus avoiding buying an inappropriate application. The term is most commonly used in the context of 'out of the box' (OOTB) or 'commercial off-the-shelf' software (COTS).
CRP的目的是，通过使用软件允许最终用户执行典型地或者关键业务流程，来验证软件应用和软件最终用户的业务流程。CRP的商业优势是它允许客户在承诺购买软件之前，去证明这款新软件能够胜任工作（满足业务需求和期望），来避免购买一款不合适的应用。这个词汇经常应用在“开箱即用”或者“商用现成品”软件情形中。

CRP and UAT CRP和UAT
Conference room pilot is kind of a software acceptance testing. It is kind of UAT. But UAT will do a functional testing and see if the solution is suitable as per the business requirements. However, conference room pilot tests the software to check whether its suitable for the business or not.

CRP是一种软件接受度测试。它是UAT的一种。但是UAT将做一个功能测试，来查看解决方案对于每个业务需求是否合适。然而，CRP测试软件来检查它是否适合这个业务。
Although a conference room pilot shares some features of user acceptance testing (UAT), it should not be considered a testing process – it validates design or solution fit for purpose at a higher level than functional testing.

尽管CRP和UAT某些功能共通，但是它不应该被认为是测试过程----它在比功能测试更高层次上验证了设计或者解决方案是否合适。
Shared features of CRP and UAT include: CRP和UAT相同的功能有

• End-to-end business processes are used as a "business input" for both 端到端业务流程被作为“业务输入”
• Functionality demonstrations  功能展示
• Non-functional validation(e.g. performance testing) 非功能性验证（如性能测试） 

Differences between a conference room pilot and a formal UAT: CRP和正式的UAT不同的是

• It is attempting to identify how well the application meets business needs, and identify gaps, whilst still in the design phase of the project  它在项目还在设计阶段时，尝试着鉴定应用程序满足业务需求的程度，以及差距
• There is an expectation that changes will be required before acceptance of the solution 在解决方案接受前，需要修改
• The software is ‘on trial’ and may be rejected completely in favour of another solution.软件还在试用阶段，可能因为另一个解决方案而被拒绝

CRP-1: Discrete transactional activities 离散的事务活动
CRP-2: Proposed business processes (No RICE – custom Reports, Interfaces, Conversions, Enhancements / Extensions) 推荐的业务流程（没有RICE----自定义报表、接口、转换和增强/拓展）
CRP-3: End to end business scenarios. Processes with converted data and some RICE components 端到端的业务情形。带有转换数据和一些RICE部分的业务
UAT: Test 100% of functionality and end-to-end integration testing including all RICE components 测试百分百功能，以及端到端集成测试（包括所有RICE部分）