Wednesday, August 19, 2015

High Level Design Documentation Template



Document Revision History


Version
Date
Description
Requested By
Created By
1.0
09/13/2011
High Level design document draft
XYZ Inc
Your Name





































Revision Level
Revision Date
Description of Revision
Revision
Author
1.00
24/09/2012
First Draft



 abc kumar





























Disclaimers
NewLease® is a trademark of XYZ, Inc.
Proprietary and Confidential Information/Copyright Notice. This work contains valuable, proprietary, and confidential information of XYZ, Inc. Disclosure, use, or reproduction outside of International Decision Systems, Inc. is prohibited except as authorized in writing. This unpublished work is protected by the laws of the United States and other countries. The work was created in 2011.
Permitted Uses. This documentation may be reproduced, duplicated, and distributed in electronic and/or printed format by any licensee of XYZ, Inc. or licensee or sub-licensee of an Affiliated Corporation of XYZ, Inc. (collectively "XYZ"), provided, however, that the following conditions are fulfilled:  (i) all copyright and other proprietary notices included in this documentation appear clearly and distinctively on all reproduced, duplicated, and distributed copies; (ii) this documentation is kept in its entirety and without modification or/and alteration; and (iii) this documentation is distributed only to officers, directors, or employees of an XYZlicensee or sub-licensee, or an XYZ licensee or sub-licensee's affiliated corporation. For any other use, authorization must be requested and obtained from XYZ.
Third Party Trademark Acknowledgments. Products and services that are referred to in this documentation may be either trademarks and/or registered trademarks of their respective owners. Neither XYZ, Inc. nor any of its Affiliated Corporations make claim to these trademarks.
Table of Contents
Introduction........................................................................................................ 6
High Level Design Document Overview.................................................................... 6
Audience........................................................................................................... 6
HDD (High Level Design document) Update Policy...................................................... 6
HDD.1      Availability Trigger Process Overview...................................................... 7
1.1         Availability Trigger Process Overview & Scope of the work................................ 7
HDD.2      Availability Trigger Design Details............................................................ 8
2.1         Windows Service Trigger............................................................................ 8
2.1.1     Fetch the Active Facility Data & Form the request....................................... 8
2.1.2     Actuate the existing web service & Transform the Response......................... 8
2.1.3     Database Insertion................................................................................ 8
2.2         Database Objects...................................................................................... 9

High Level Design Document Overview


This business has an approval rate between 30-50% and as such the goal of the scorecard is to allow the SFSI Credit team to make the quickest, most accurate credit decision possible on the non-Financial Statement transactions.  These are transactions which are under $250K or $350K in exposure (based on business line).  SFSI on the whole gains from an operational and cost perspective when they can make the quickest, lowest touch decision on whether to extend credit to these applicants.

Conceptually, the process overview is as follows

This document will cover the high level technical solution to create a custom web service to achieve the scorecard functionality being requested by XYZ inc.

·         The scorecard must provide a recommended decision on each application that falls into one of three categories:  Recommended Approval, Recommended Decline, Manual Review.
·         Any exposure amounts above the business line thresholds (aka Financial Statement transactions) will automatically qualify for “Manual Review” status. We would like the transaction to still go through the rate card.
·         Any transactions not meeting the Credit Filters recommended decision of “Recommended Approval” or “Recommended Decline” will automatically qualify for the “Manual Review” recommendation. With “recommend decline” can data that caused recommendation be highlighted in some fashion?

In Scope

Not In Scope

Flow Charts


Need
Comments
Internal test environment details:
NA
Customer test environment details (DEV/UAT):
These three interfaces should be setup on the following internal server:
-       Database server:
-       Database Name :
-       App and Web server:
-       On the application server, XYZ URL:

Note: XYZ will share later.

Test account credentials for bureau interfaces:
Details have been provided for configuring bureau test environment connectivity in the prior “Bureau Connectivity Details” section.

Prod account credentials for bureau interfaces:
This information has been requested from XYZ along with test accounts for their own use.
All deliverables are SMART: specific, measurable, achievable, realistic, and time-oriented.

Owner
Acceptance Criteria
Due Date
Reviewer/ Approver
An interface to be able to successfully pull a D&B BIR report.
Consultant
 users will review and accept

Lead/Tech Consultant
Ability to successfully pull a PayNet Direct report.
Consultant
users will review and accept

Lead/Tech Consultant
Ability to successfully pull an Experian Personal Credit Report
Consultant
 users will review and accept

Lead/Tech Consultant

No comments:

Post a Comment