Proof of a Business:

Use Architecture
Deep Dive

Why the need to do a Proof of Business Use Case Architecture Deep Dive?

The target audience of this ‘Proof of Business: Use Case Architecture Deep Dive’ are companies that have already started to discover the possibilities and have created either in code or on paper their use case. The ‘Proof of Business: Use Case Architecture Deep Dive’ goes deeper in the assessment of a Use Case than the ‘Proof of Business Assessment in a week’

A Proof of Concept is a technical exercise to demonstrate that your idea is operationally feasible is mostly used to garner support from internal stakeholders however will in most cases not be seen by potential customers. A Proof of Business goes deeper and further than a proof of concept (PoC), it focuses on the business value including possible external stakeholders and enterprise fabric of a company.

If you already have a Use Case and have done development activities (maybe even done a PoC), however you remain unsure about your overall architecture, created codes (smart contracts) and the business landscape you want your Use Case to operate in, another few steps are required.

This is why Fujitsu recommends doing a ‘Proof of Business: Use Case Architecture Deep Dive’. This service covers the overall architecture, the business and legal context, identified risks, the code and is conducted Fujitsu experts who have significant experience in the different projects in the market.

The ‘Proof of Business: Use Case Architecture Deep Dive’ is therefore best suited to validate whether your Use Case is an appropriate solution and is production-ready.

The Assessment:

The final goal of the assessment is to gather insights on the created and developed Use Case (in the various stages) and give customers the confidence to take the next steps, possibly in co-creation with a company like Fujitsu.

The base service ‘Proof of Business: Use Case Architecture Deep Dive’ has typically an assumed lead time of (10) days organized in a ‘sprint’.

The Approach in Practice

In practice, the ‘Proof of Business: Use Case Architecture Deep Dive’ includes four key steps:

  1. 1. The Workshop
  2. 2. The Research and Assessment Phase
  3. 3. The Report Preparation
  4. 4. The Result Presentation

The Workshop

The goal of the workshop is to understand the Use Case in detail and confirm the next steps conducted during the Research and Assessment Phase.

It is imperative that all information related to the selected Use Case are collected in an orderly and transparent fashion, summarized and given to the person leading the Assessment. Full access to the Architects, Business Owner, Application Developer(s) or the Application Administrator is considered a critical success factor for this workshop. The document stack of the ‘Proof of Business: Use Case Architecture Deep Dive’ includes a Non-disclosure Agreement (NDA) protecting both the customer and Fujitsu. If required, after the assessment the base data can be destroyed on request with a formal confirmation by Fujitsu of the destruction of the data.

The Research and Assessment Phase

After collecting all possible information about the Use Case and conducting the Workshop that has enabled the Fujitsu experts to understand the Use Case. The following assessments are included:

  • Application Architecture Assessment;
  • Business Architecture Assessment;
  • Smart Contract and Frontend Code Assessment.

The following assessments are not included by default:

  • Accelerator Advisory Services.

Unless the complexity has forced a different direction, these assessments are conducted in two five-day sprints. The work is done based on the collected information and the analysis of the evidence.

The Report Preparation

The findings of all the assessments are consolidated into a Management Report, which contains high-level design and sizing recommendations for the Use Case. The report is presented back to you to ensure all aspects of the report are fully understood during the last step.

The Assessment report is typically available two weeks after the last day in the aforementioned sprint.

The Result Presentation

The Result Presentation is conducted remotely unless otherwise agreed on a mutually agreed data after the publication of the report.

You need more info? Do you have doubts? Download our “Proof of Business: Use Case Architecture Deep Dive” brochure and find your answers

Download here(pdf file 796kb)