Solution Design

When NICE engages with the Customer/Partner, the Solution Design Document (SDD) is used to provide:

The Customer with a document that clearly defines the automated solution, providing the required level of detail for approval.

The Developer with a document that clearly defines how the process should be configured within the automation tool, including inputs, outputs, applications used and the various scenarios the automated process needs to cater for.

The level of detail in a Solution Design Document varies according to whether:

The individual who is designing the solution is the same person that is developing it.

The delivery methodology is waterfall or agile.

The process requires a high/low level of redesign.

The process development is complex/simple.

Level of detail required by the Customer to approve design.

The SDD includes the following:

Overview

Introduction

Version Control

Distribution List

Glossary

References

Solution Overview

Project Objectives

Process Background

Application 1

Application 2

Business Value

Naming Conventions and Standards

SQL Table List

Credentials Management

Volumes

Assumptions

Limitations

Application Requirements and Structure

Solution Files Architecture

APA High-Level Architecture

Attended Robotic Automation <Process Name>

Unattended/Attended Invoker Automation

Unattended Robot Automation

Solution Design

Part 1 – Solution Input/Output Parameters

Part 2 – Solution Public Business Entities (BEs) & Data Collections Business Entities

Part 3 – Solutions

Solution 1 – Main Flow

Solution 2 – Modules Library

Module N – Template

Solution 3 – Sub-Flow Library

Sub-Flow N – Template

Error Handling

Error Handling – System Errors

Exception Handling – Business Errors

Real Time Client Display

Deployment Methodology

Approval

Appendix