1 – Audits -

What is your knowledge on how these Audits will happen for a BA?
•  Leveraging data visualization tools in the planning, execution and reporting phases to drive
• efficiencies and effectiveness
•  Participating in planning activities to develop audit scopes
•  Designing audit programs and test plans to determine the adequacy and effectiveness of
internal
• controls and compliance
•  Interviewing select personnel and documenting and assessing business processes and
• information systems to determine the adequacy of the control environment
•  Testing information technology application and system processes and controls
•  Understanding financial, operational and compliance risks which impact information systems
•  Identifying value-added recommendations and aligning with management on corrective
actions
• to address identified risks
•  Presenting audit results to management
•  Preparing audit reports detailing recommendations to strengthen and improve the control
• environment
•  Maintaining work papers and participate in department projects
•  Provide advice and training to IT application owners on implementation of Computer and
• Interface controls • Perform design effectiveness testing (DET) and detailed operational
• effectiveness testing (OET) of IT controls.
•  Perform Quality Assurance Reviews of control documentation and testing
•  Perform risk analysis for control matters/issues identified during testing

2 – BA Approach Strategy

 What Elicitation Techniques to apply- I would be using the Brainstorming Technique

In Brainstorming elicitation technique where a problem or topic is presented to the group, and
participants are asked to produce as many ideas to solve/address the topic as possible. As ideas are
presented, a scribe documents the ideas and ensures the participants can see what is being captured.

Stakeholder Analysis RACI/ILS

Below is the list of Stakeholders.

Project Stakeholders
 Business Analyst – Rohini
 Delivery Head – Mr Karthik
 Project Manager – Mr Vanadanam
 Development Team – MS Juhi , Mr. Teyson, Ms Lucie, Mr. Tucker, Mr. Bravo
 Testing Team – Mr. Jason and Ms Alekya
 Network Admin – Mr. Mike and DB Admin is John.

Business Stakeholders
 Business Sponcer - Mr. Henry
 Influencers - Peter, Kevin and Ben.
 Finance team - Mr Pandu
 Project Team - Mr Dooku
 What Documents to Write –
1. Scope
2. In-Scope Features/Services
3. Out scope Features/Services
4. Solution Architecture Diagram
5. Technology Specifications
6. FRD – Functional and Non Functional
7. BRD
8. PROJECT TIMELINE
9. RISKS AND MITIGATION PLAN
10. CHANGE MANAGEMENT

Process to follow to Sign off on the Documents –

Project sign-off is typically executed during the contract closure phase – the company presents
the results of the work done to the client and then, after getting the necessary acceptance from
them, should get a client statement to verify that the job was completed.

• Name of the project.

• All relevant dates.
• Key roles in the project.
• Project deliverables.

How to take Approvals from the Client?

 Whenever we seek approval from a manager or a client, we will have to draft a request for an approval
letter.
•  Write email to addressing the relevant signing stakeholders and reviewers as per below format
Dear Henery,I am sending this request to seek your approval regarding the recent project proposal I
mentioned earlier at the meeting.
• The team and I have put together a detailed plan that can be found attached to this email.
Afterreceiving your approval, we will commence with the project immediately. You will find this
plan beneficial for several reasons for your Online Agriculture store.

What Communication Channels to establish and implement –

• Face-to-Face Communication/ In person meeting
• Video Conferencing.
• Phone Calls
• Emails
• Text Messages
• Online Messaging platforms. (Skype, teams etc.).

How to update the progress of the project to the Stakeholders, how t o take signoff on the
UATClient
Project Acceptance Form)

User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to
verify/accept the software system before moving the software application to the production
environment. UAT is done in the final phase of testing after functional, integration and system
testing is done. Deliverables for UAT testing are Test Plan, UAT Scenarios and Test Cases, Test
Results and Defect Log.
Once execution is over, and as many defects as possible are resolved, it is time to sign off on UAT
and go live.
The sign-off approval indicates that the change meets business requirements and is ready for
deployment.

Business Analysts or UAT Testers needs to send a sign off mail after the UAT testing. After sign off
from client.

3-Tier Architecture – Explain and illustrate 3-tier architecture?

• Each tier (Presentation, Logic, Data) should be independent and should not expose
dependencies related to the implementation.
• Presentation tier (front end) – The top most level of the application is the User interface (UI).
• The main function of the interface is to translate task and result to something that user can
understand -
•  Logic Tier – This layer coordinates the application process commands, makes logical decisions
and evaluations and perform calculations. It also moves and processes data between to 2
surrounding layer. A dynamic content processing and generation level application server, e.g.,
Java EE, ASP.NET, PHP, ColdFusion platform (middleware).

• Data Tier (Back end) – Here information is stored and retrieved from database or file system.
The information is passed back to the logic tier for processing and eventually back to the user.

4.
.Question 6 – This project Elicitation Techniques

Which Elicitation Techniques can be used in this Project and Justify your selection of Elicitation
Techniques? Prototyping / Use case Specs/ Document Analysis / Brainstorming.
I would be using Workshop and will invite all stakeholder and will set up agenda ; discussion ; req
gathering ; client expectation and out .
I would be using use case specs as it helps for early designs, mock-ups, prototypes with real users. User
testing helps us to find out if the potential design will be usable.

Question 7 – 10 Business Requirements

Make suitable Assumptions and identify at least 10 Business Requirements.
Platform for Buyers / Farmers
BR 001 - User registration and Login - Farmers should be able to Register as a first-time user and if
already registered then login on the application by using user name and password
BR002 - Farmers should be able to search the product category wise like pesticides; fertilizers; seeds;
crops etc
BR003 - Farmers should be able to add the items in the cart; also, at the same time delete the items from
the cart
BR004 - Payment Gateway – able to proceed for an order; make payment via. Net banking; UPI; wallet;
Coupons or COD
BR005 - Received shipping details & Invoice
Platform for sellers
BR006: - Login for Vendors – Vendors should be able to Register as a first-time user and if already
registered then login on the application by using user name and password
BR007: - Upload the product – Add product category vise also the product Videos; specification
BR008: - Vendor should be able to Change or revise the product, Product quality matrix; Farmers should
be able to upload the logo of the product
BR009: - Vendor should be able to Describe the product price
BR0010: - Vendor should be able to update the Inventory details / Stocks
BR0011: - Vendor should be able to float Discounts; festive & seasonal offers; Coupons
BR0012: - Vendor should be able to View; received order details and confirm once the order is correct
BR0013: - Payment gateway – Receive payment for the confirmed order; refund payment gateway
BR0014: - Refund /return policy.
BR0015: - Vendor should be able to view: update Dashboard

Platform for Admin

BR0016: - Admin login

BR0017: -- Supplier Infor Create / update / delete / display / search supplier details
BR0018: - Add / Edit Category – Change / Manage category
BR0019: - Add / Edit Items – Change product; price
BR0020: - Manage users – Active; inactive users
BR00:21- Manage Orders – Confirm / cancel orders
BR0022: - Purchase Module – Payment receivable; cash flow
BR0023: - Order Management – Invoicing ; Logistic & Supply chain
BR0024: - Language Preference – Add the regional language
BR0025: - Resolve customer Issues; Via. Call; tickets
BR0026: - View; update report

Platform for payments

Payment by Credit card; debit card; cash; UPI; wallet

Authorize; Capture; validate; approved
Return; Refund

Platform for customer support –

Customer should be able to raise the ticket

Platform for tracking –
Ask the expert / Chat Bot

lOMoARcPSD|38070307

lMoARcPSD|380