Choosing the Right Demo for Requirements Validation

Correct Answers: A and C

Visual presentation of the requirements is a vital communication step between a Solution Architect and a customer.

There are several types of demos that you can use along with your story presentation to the stakeholders: Out-of-the-box - this demo presents the capabilities of the out-of-the-box solution without any customizations.

It provides information to the stakeholders about the system's current functionality.

The out-of-the-box demo does not illustrate the requirements but only familiarizes customers with the core features.

Prebuilt - this demo is tailored to the particular vertical and provides more specific to the stakeholders' business information than an out-of-the-box demo.

Prototype - this demo presents the minimally tailored out-of-the-box solution that reflects the customer's needs or requirements.

Proof of concept - this demo focuses on illustrating the implementation of the particular requirements, components, or technical solutions.

Option B is incorrect because an illustration of the implementation of the particular requirements is a Proof of concept demo but not a Prebuilt demo.

Option D is incorrect because customization of a standard solution for a particular vertical is a Prebuilt demo but not a Proof of concept demo.

For more information about the demo types, please visit the below URL:

When you need to validate requirements and want to make a presentation with a demo, the type of demo you choose depends on the purpose of the presentation and the level of customization required for the solution. Here are some guidelines that can help you choose the appropriate type of demo:

A. Prototype demo: If you are planning to present the minimally tailored standard solution that reflects the requirements, you need to prepare a Prototype demo. A prototype demo is a basic, functional representation of the solution that shows how it will work and how it will meet the requirements. A prototype demo is useful in the early stages of the project to validate requirements and to get feedback from stakeholders.

B. Prebuilt demo: If you want to illustrate the implementation of particular requirements, you need to prepare a Prebuilt demo. A prebuilt demo shows how a particular feature or requirement has been implemented in the solution. It is useful in demonstrating how the solution meets specific requirements or use cases.

C. Out-of-the-box demo: If you want to present the current functionality of the standard solution, you need to prepare an Out-of-the-box demo. An out-of-the-box demo is a demonstration of the solution's standard functionality without any customizations. It is useful in showing the capabilities of the standard solution and how it can meet common requirements.

D. Proof of concept demo: If you want to customize a standard solution for a particular vertical, you need to prepare a Proof of concept demo. A proof of concept demo is a demonstration of how the solution can be customized to meet specific requirements or use cases. It is useful in showing how the solution can be extended to meet unique business needs and in getting feedback from stakeholders.

In summary, the type of demo you choose depends on the purpose of the presentation, the level of customization required, and the audience's needs. Each type of demo has its own strengths and weaknesses, so it is important to choose the appropriate one for your situation.