Hi Glenn,

 
Good evening. Please see BA tasks that you will take over after you received the SLF laptop:
 
·         Follow up with Pat on the Entity business rules. Confirmation in what should be the
level of checking if an application is Entity or not.
o    Current checking is based on the flag retrieved from Document Corner
o    Looking at checking the ePDF Form as well by verifying if the Business Applicant
section has data or none (Project to be park shift to SLGFI auto encoder, shift our
efforts)
·         Scenarios for follow up depending on the level of checking: (Project to be park
shift to SLGFI auto encoder, shift our efforts)

§  If flag from Document Corner shall be the sole basis if an application is
Entity or not:
·         If an application is Entity and there are no data in the Business
Applicant section. How will we handle the application? Will it be
considered as failed?
o    Once finalized, Data Mapping document should be updated. Version use for these
changes is 6.2
o    Once finalized, create new User Stories for both RU and GIO
·         Current user stories were created based on the following assumptions (and
was the agreement with the devs):
§  Flag from Document Corner will only be the basis for checking if the
application is Entity or not
§  If application is flagged as Entity and Business Applicant section is not
filled out or incomplete then mapping of application shall fail
·           Based on the previous meeting: eApp onboarding and addition of new documents
requirement discussion with interfacing systems (January 15), there will be new required
documents when submitting an application (Updated Data Dictionary in CPR) Technical
Dictionary
o    AutoEncoder shall be able to handle the new required documents.
o    Last discussion with Pat is to cascade this new requirement to dev team. However,
no meeting has been setup yet since the team has been busy with UAT
o    Follow up with Pat on when to cascade
o    There should be an update in the Requirements Document both RU and GIO/SIO
·         RU, this should be a Non-Day 1 requirement
·         GIO and SIO, Day 1 requirement
o    Create User Story for this requirement (both RU and GIO/SIO) but there should be
discussion of the technical implementation first since changes might be code level
·         RD updates
o    Non-Functional
·         Performance (RU, GIO and SIO)
§  How fast the application are parsed by the AutoEncoder
·         To determine this, compare the result of performance testing
against the number of applications processed everyday by BU
 ·         Retrieve the result of performance testing from TCOE by
coordinating with Mitzi – Data provided by Mitzi
·         Retrieve the number of applications processed everyday by
BU from BU
·         Responsiveness and Technology (RU, GIO and SIO)
§  Follow up the ASGP specs from Jenmart
·         Email already sent to Jenmart last December 11
·          
o    Functional
·         Requirement 4.6 (GIO and SIO)
§  Retrieve the details from Chin (Cristina Marie Samson)
§  Send heads up using Workplace Chat then email to formalize request
o    Out of Scope (GIO and SIO)
·         List of Accepted items, issues, workarounds by Business
§  Follow up with Pat on the new list for GIO and SIO
§  Note that some items from the RU list may still be used for GIO and
SIO. Goal of the new list is to have a separate one for GIO and SIO to
avoid confusion
·           HLR updates
o    In Scope
·         Requirement 11 (GIO and SIO)
§  Pat to update this requirement once RD for eAppEntry - AutoEncoder is
done
o    Out of Scope
·         Requirement 5 (GIO and SIO)
§  Pat to update this requirement once RD for eAppEntry - AutoEncoder is
done
·           Requirement 6 (GIO and SIO)
§  List of Accepted items, issues, workarounds by Business
·         Follow up with Pat on the new list for GIO and SIO
·         Note that some items from the RU list may still be used for GIO
and SIO. Goal of the new list is to have a separate one for GIO and
SIO to avoid confusion
·         Based on the GIO and SIO RD presentation with BU (January 28), there will be new
document types accepted in Document Corner for required attachments
o    AutoEncoder shall be able to handle these new document types during conversion
to TIFF
o    Last discussion with Pat: waiting for BU's email for the list of updated accepted
document types in Document Corner
o    There should be an update in the Requirements Document both RU and GIO/SIO
·         Ask Pat if this is a Non-Day 1 requirement for RU
·         For GIO/SIO, Day 1 requirement
o    Create User Story for this requirement (both RU and GIO/SIO) but there should be
discussion of the technical implementation first since changes might be code level
 Send email to BU for HLR and RD sign-off both RU and GIO/SIO
 o For RU, meeting with Ms. Gena Gaspar is a prerequisite since the
change in the RD concerns her team
Coordinate with Mark on setting up the meeting with Ms. Gena
o For GIO and SIO, finalizing all the updates from the above tasks is a
prerequisite
 Once all documents have been finalized, before sending an email to BUs, please make sure that
you have uploaded the latest versions of the documents to CPR
 o   Please update the version number in the CPR document named: Consolidated Reference
Documents for Auto PDF Encoder
 o   Use the link of the CPR documents in your email to the BUs so they can access the CPR files
easily
 ·         You also need to get a sign-off for the Data Mapping document
 o   Get Pat and Mark’s help on coordinating the walkthrough for the BUs
 o   Once you get the go signal from the BU that the Data Mapping document is good to go, then
you can also send them an email for their sign-off