Document history

Date Version Description Author

1.0 BRD Draft You

Document Approvals:

Name Position Date of approval

Stake holder Name

Impacted Business and Tech Users

Open Questions:

1)

In Scope:

1) Person

Out Of scope:

1)

Technology stack

1) UI------ Which plat form( Angular/.net/java)

2) Data base----Sql server 2016
3) API------------ How we are loading data (Get/post)

Assumption:

1) Alexa is HIPPA Compliant.

Constraints:
Blocker?

Risks:

Timelines/Resources/Customers

Architecture Diagram

Customer Table Security

PK User1 PK User1 User ID

PK User2 PK User2

PKUser3 PK User3

PK User4 PK User4

IDR Process :

Use Case: Provider will raise the concern on the payment

We need a portal where the concern can be raised.

Independent IDR bodies need to be appoinmented.

The Date rule(Days to discuss and negotiation). Its there in BRD

What are the details we need to consider for IDR process ? Eg any form or details fill up .

Do we need any new table for IDR ?

Do we need any claims data for the IDR process ?

Data Dictionary:

Customer Information

Customer Name Char (100)

Customer ID Integer (20)

Customer user Id

Customer DOB

Customer mail

Customer Phone

Customer Health Id

Customer Interactions

Customer claims

Customer wellness

Customer Health information’s

Customer Appointments

Security Validation

User id

Password

MFA

Login Time

Modification of the resource

Speech recognition

User id

Speech details

Command for speech

SPEECH Let- real-time API recognition

Front End - Security Validation -> Customer information -Speech recognition  Customer Info
database

System/Functional Overview.

Requirements:
Requirements.

BR # 1 The system should have the ability to import data from Optum EDW and pacific east/eliza.

BR # 2 The system should have the ability to import operational team data.

BR # 3 The system should have the ability to import RA new member data.

BR # 4 The DB should be updated to add the field second email data field , including email type

BR #5 The DB should be updated to add the following flag fields Do not call,Do not visit, Do not contact,
Active/inactive .

BR# 6 The DB should be updated to Capture date and time when the data is added/ modified.

BR #6 The DB should be updated to add status and status disposition fields.

BR #7 The DB should have timestamp so that historical view of address and phone number data that is
effective dated.

BR #8 The UI should be enhanced to Add a button in each sub page that allows user to toggle between
each sub page and back to member general screen.

BR #9 The UI should be enhanced to Add a second email field and dropdown details of email type.

BR#10 The UI fields need to be updated from “permission to test” to “received verbal agreement to
text” and “ Lost Souls” to “care check”.
BR#11 The UI fields “data capture” and update data need to be removed from the page.

BR #12 The UI should be enhanced to add the following fields Do not call,Do not visit,do not contact.

BR # 13 The UI should be enhanced to add drop down status and status disposition.

BR#14 The system should be updated to extract data for Optum Best,EDW, EDW and pacific east/eliza.

BR# 15 The system should have the ability to maintain historical details of data (address , phone nuber)
with effective dated.

BR #16 The system should have the ability to capture date and time when the data is added/modified.

BR # 17 The system should have the ability for data Linking with CMR.

BR # 18 The system should have the ability to add athd display the following flag fields Do not call,Do
not visit ,Do not contact ,Active/inactive.

BR # 19 The UI should have the Reporting tab/Link so the user can generate report.

BR # 20 The system should have the ability to create reports that lists all members with contact
information updated as of given date and Produce report by market with all care check members which
includes status.

Impacted Use cases:

No of user and Flow

GLOSSARY:

VA- Virtual Assistant

Appendix:

Stake Holder Info

1)

2)

3)

Approval
Waterfall –Gathering the REQ->Design->Development->Testing->UAT->Release

Agile- Incremental -> Requirements ->Smaller parts ->Develop those->test those

Scrum – Scrum master – Manager team- Team people

Developer

Testers

10-6 Dev 3 Qas and 1 BA- SM

1) Refinement
2) Grooming- user stori- 1 week prior to sprint - Ready
3) Sprint Planning-1 day prior –Story points – Starting the sprit
4) Daily Stand up-Day1-
5) Dev- comp- Qa testing
6) Demo-Day 10
7) Retrospective
8) UAT-
9) Release-relase manager
10)

Sprint 0 – Access

Write user stories – Grooming -1 weeek to Sprint 1

10 Req- 20 Smaller requirements

BRD/FRD

BRD- Sometimes

Epic/feature/Sto

1 epic- 10 features- 100 User stories *3= 300 story points

9 people – 6 hours per day- 1 story point

Fibonacci series- 1,2,3,5,13,21

13 pointer -13 *6 78

10*6= 60

SM- 9 *6 *10=540/6=90- Priority list

ries

UI-3 releated- EPIC- Features- UI1- User stories UI 1.1

UI-2

API-2 Req- EPIC

DB-5 Req- EPIC

Sprint- Time to deliver deliverable – 2 weeks 3weeks or 4 weeks

Requirement Gathering

Virtual assistant-> 3 to 6months

Module1 – 2weeks- Sprint

Module 2- 2 weeks
HIPAA Virtual assistant - Epic
 Front End – Feature 1
o Mobile App –
o Login Page
o Content Page
o Web UI – User story 3

Given The user is in the login page of the VA APP

When The user provides his user id and password
And the user clicks on the login button
Then The user can login to the app

 Algorithm For booking Movie ticket – Feature 2

o Bookmy my show integration
o Paytem Integration
 Appointment in caldener – Feature 3
o Calender Integrator
o Schedule of outlook or and calnder
o Sned a notication to the user
o Cancel the appoint ment
 Loging Page – Feature 4
o User Id
o Password
 Back End Feature 5
o Table 1
 Customers details
o Table 2
 Security
o Table 3
 Interaction
 Weather forecast Feature 6
o Tempreture -google integrator
o Rain and hzarads conditions
o Humid and Wid speed
 Quiz Feature 7
o Module for world,Animal,mamal,Forest
Mobile App- Sign up page- user id and password

Login page- user id and password

Customer can search the word and get the meanings

Customer can search the Grammar and he will get the grammar details

Table “ Customer table : Customer id

User Id

Password

Api Integration For searching the grammar and meaning of word

BRD- In scope

Out scope

Assumption

Mobile APP- Epic

Descriptions: As a User I should have the capability to search the words and grammars in the grammerly
app and use them.

Scope:

In scope:

Out scope:

Success Criteria :

1) The user can login with valid credentials.

2) The user can check the …………….

AC:

Given the user is in the App and logged in using valid credentials

When the user Wants to search the word

Then the user can get the word details.

Given the user is in the App and logged in using valid credentials

Ui- Feature

Description: As a user I should have the ability to sign up and login upon the successful sign up.

In scope: Ui changes

UI check using mock data

Mock ups

Out of scope:

Ac/Success criteria:

1) Login using valid credentials

2) Sign up for login

Given The user in the login page

When the user logs in

Then the user can see the detaisl

Api changes

DB changes

 Mobile Sign up
 Mobile login
 Error cases

API_feature

Description: As a user I should have the ability to get the grammar and word details using the APIs

In scope: Ui changes

UI check using mock data

Mock ups

Out of scope:

Ac/Success criteria:

1) Login using valid credentials

2) Sign up for login

Given The user in the login page

When the user logs in

Then the user can see the detaisl

 Grammar
 Meaning

DB- Feature

In scope: Ui changes

UI check using mock data

Mock ups

Out of scope:

Ac/Success criteria:

1) Login using valid credentials

2) Sign up for login

Given The user in the login page

When the user logs in

Then the user can see the detaisl

Description: As a user I should have the ability to store the information of the customer in the DB.

 Create the DB-Customer-

 Description: As a user I should have the ability to store the details in the DB
 In scop:
 DB changes
  Fileld:
 Customer name Char(20)
 Email Varchar(20)
 Password varchar(20)
 DOB Date(10)
 Details Blob/Json

 And DB load
 Out of scop:
 UI changes
 API changes

Given the user is in the DB

When the user provides his details using the App

Then the user details will be loaded to the DB.

 Loading the data to the DB

Epic- All Req

Feature- Part of Epic

User story –Part of feature

A- 10 *6=60 Capacity

B 9*6 = 54

C 8*6=48

=(48+54+60)/6

162/6 27