1. Make an executive summary for the information provided

OVERVIEW

The address verification service provides customers with the ability to verify and correct addresses based on an address database. There are three scenarios:

Recommended Address Scenario: Customers enter their address, which is then cross-checked in the address database. If a match is found, a corrected address with full details, including zip code and geographic direction, is recommended. This ensures accuracy for shipping purposes.

Invalid Address Scenario: If the customer's address is not found in the database, the system informs the customer that the address is invalid. Customers have the option to request the addition of the address to the database for admin approval.

Users View Scenario: Customers who log in with the correct credentials see their address entered in the "address" section and a suggested address in the "recommended address" section. Changes can be confirmed using the select and apply function before proceeding.

Address Verification System Interface: An interface is introduced to verify customer-entered addresses. The payload includes fields like RequestType (indicating recommended, invalid, or new address), AuthenticationType (to verify user credentials), and more. Extended Attributes: A Customer entity includes the field NewAddress to allow the addition of addresses not present in the database. The provided data flow diagram illustrates the various steps and interactions within the system, such as user login, address entry, database authorization, address verification, response handling, and address management.

2.1 ASSUMPTIONS

Authentication Process: Users need to authenticate using the correct credentials to access the service.

Recommended Address Reason Code: Configured codes to explain why a recommended address is provided.

Invalid Address Reason Code: Configured codes for reasons when a similar address isn't found in the database

New Address Reason Code: Configured codes for reasons when users can request to enter a new address in the database.

2.2 GLOSSARY

Term	Description
Authentication	Process of authenticating user entered credentials
Recommended address reason code	Configured reason codes that are applied when address is found in database with proper recommendation.
Invalid address reason code	Configured reason codes that are applied when similar address not found in database
New address reason code	Configured reason codes that are applied when user is allowed to request to enter a new address in database.

3 FUNCTIONALITY

Scenario 1: Customers get recommended address based on address database.

The functionality allows customers to review and modify addresses based on address database. When a customer puts their address, it will be cross-checked in our address database, and it will recommend the corrected address that will include full zip code and geographic direction, for example NW or SE. This functionality will help customers to put the most corrected address so that in case of shipping, there is no confusion.

Scenario 2: Customer gets no recommended address or invalid address based on address database.

This functionality will allow customers to re-check and re-verify the address they are putting. If a customer puts their address, it will be cross-checked in our address database. If the address is not in the database, it will tell customers that the address is invalid. Customers, however, can request the address to add in the database and they can request admin approval.

4 USER INTERFACE CHANGES

When customers log in using the right credentials, the customer entered address is displayed in address section and suggested address is displayed in recommended address section. There is a select and apply function used to confirm the changes before the customer proceeds.

5 INTERFACE CHANGES

5.1 ADDRESS VERIFICATION SERVICE INTERFACE

A new interface is introduced to support verification of an address entered by the customer.

Sample payload

{

RequestType:null,

AuthenticationType:null,

RequestType:null

}

Sl. No	Field	Description	Values
1	RequestType	To indicate if there is a recommended address that a customer should use.	User input Recommended address
2	RequestType	To indicate that the input address is not a valid address.	Invalid address Add new address
3	AuthenticationType	To make sure if the user put the correct credentials	True False

6 CONFIGURATION

6.1 EXTRENDED ATTRIBUTES

Entity	Field name	Data type	Description
Customer	NewAddress	VarChar	To add new address if the address is not in address database.

7 REFERENCES

GROIJP 10 : DATA FI OW DIAGRAM