What is SDLC cycle

(RDIVM)
Requirement
Design
Implementation
Verification 
Maintenance

Planning/Inception/Kickoff
Two docs

1. Scope and Vision -PM or BA- signoff(this is only looked by BA from planning and inspection point of view).
2. Project Charter -PM (cost/Time/Resources)
3. SOW -statement of work-done by technical leads for external vendors

budget/Cost-400M

size -2800

Time-8 months

NOTE-if we doing waterfall. IIt has a signoff in every phase. BRD/FRD/Scope and vision/ almost everything has a sign off (in traditional water fall).
Allmost all project done in waterfall.

1) BRD-/BRS Business requirement doc/Specs-
2) FRD/FRS- Functional Requirement Document /spec

3) Design (creating a blue print)
a) UID- User interface Design-Mocks of actual user screen UX/UI
user experience
b) TDD-/TSD-Technical design doc/Technical specification doc

What BA role in design?

1. Transiting requirement to designers.
2. Along with this, if designers have any questions, then BA have to run back and get back with requirements. Working with CR (change requirement). 
3. In this phase, BA start testing. You writing your test cases.
4. When PM /Manger comes and ask 'how development looking, closing is coming our first drop1 /drop 2 or drop3.
1. BA will say ya its progressing.. But how to show..QA will start in drop 1... delivering code to QA.so for this, we have to show test cases. 
2. We won't be doing testing at the level of testing team, but we will be able to do basic testing. We might not do data verification but we will check to see that data is coming.  All this happen in build and construction phase (called DIT and UIT (dev integrated testing and Unit integrated testing)
3. you will click on links. might and check print button /etc and check data if matches but atlest you will high level functions.
4. when you find problems, you report these problems to development team (not QA team) as QA not started yet. You will do initial testing in development phase itself and you will give stamp of approval to PM itself. (like major testing and all seems good and so now QA have to find indepth bugs).
5. So as BA you do DIT/UIT and internal verification  and BA (Functional Testing )
6. All these errors, we document
7. Test case is verifying the requirement.
8. DIT is done by both (development and 
9. UIT (unit testing by develeopemt team)
10. BA does functional testing

Function testing usually done manually and as BA, you will always do manual testing.

3) Build phase
4) Testing Phase
QA/Verification/Testing-Functional Testing -
UAT User acceptance Testing /Verification/Testing-Customer walk-through

Note-BA could be asked  -show me test results.
PTS (project tracking system )
we upload all docs. All gets uploaded. Thats how we internal and external audit.
like lawyer will ensure

5) Deployment phase/Release
The Verified Code is released into production.
The UAT teeam will perform production checkout
Customer gets the key of project

6) Post Production Support OR Maintenance
House is supported by the users and support team

Support has
L1-help desk (assigning incident tickets/Answering phone calls):
Level 2-Production support team (technical team). Moniter the app and debug the code and look into App Logs).
( Exception -if system b dont' come when rquired, so all application errors are written in application log and reviewed by level 2 team.
Last is Level 3-L3-Actual application development team (the developers ) who created the code)..
Those are your

Role of BA in SDLC
BA will coordinate between L2 and L3. (you might talk to L1 to get feedback).
You are a BA started by gathering requirement and now you have gathered all requirement and technilogy team built it and now its released but its not right so its yours..