What is a organization?

group of units or sets of varios units

there will be vertical heads and horizantal heads
vertical heads- top to bottom. There will be unit heads and teams under it. Its like a water fall. Vertical structure allows for a c
horizantal- Instead, in a horizontal organization, communication is encouraged between teams and departments. there may b

What is a Stakeholders-

Stakeholders are those with any interest in your project's outcome. They are typically the members of a project team, project
Stakeholders are people who are invested in the project and who will be affected by your project at any point along the way, a
It's a good idea to practice good stakeholder management and constantly communicate with them in order to collaborate on t
clients, project manager, project team, sponser, executives

What is SOW?

The SoW is the document that captures and defines all aspects of your project. You’ll note the activities, deliverables and the ti

What is Scope of work document?

A sow is a agreement documen on the work which needs to be performed. It includes who will perform the task, the timelines
Product bases - your own organization system- deign and devolpment
outsource- your organization looks for other vendor to build your product
What is Functional and Nonfunctional document?

The Functional Requirements Document (FRD) is a formal statement of an application’s functional requirements.
agrees to find the product satisfactory if it provides the capabilities specified in the FRD.
Functional requirements capture the intended behavior of the system. This behavior may be expressed as services
They define things such as system calculations, data manipulation and processing, user interface and interaction wi
The Functional Requirements Document (FRD) has the following characteristics −
It demonstrates that the application provides value in terms of the business objectives and business processes in th
It contains a complete set of requirements for the application. It leaves no room for anyone to assume anything whic
It is solution independent. The ERD is a statement of what the application is to do— not of how it works. The FRD d
inappropriate in an FRD.

The functional requirement should include the following −

Descriptions of data to be entered into the system
Descriptions of operations performed by each screen
Descriptions of work-flows performed by the system
Descriptions of system reports or other outputs
Who can enter the data into the system?
How the system meets applicable regulatory requirements?

The functional specification is designed to be read by a general audience. Readers should understand the system, b

Functional Requirements Deliverables

A Business Requirements Document (BRD) consists of −

Functional Requirements − A document containing detailed requirements for the system being developed. These r
and constraints identified during the Business Case are still accurate and up to date.
Business Process Model − A model of the current state of the process ("as is" model) or a concept of what the proce
System Context Diagram − A Context Diagram shows the system boundaries, external and internal entities that inte
Flow Diagrams (as-is or to-be) − Diagrams graphically depict the sequence of operations or the movement of data fo
Business Rules and Data Requirements − Business rules define or constrain some aspects of the business and are
elements and the relational integrity of the data.
Data Models − Entity Relationship Diagrams, Entity Descriptions, Class Diagrams
Conceptual Model − High level display of different entities for a business function and how they relate to one anothe
Logical Model − Illustrates the specific entities, attributes and relationships involved in a business function and repre
Data Dictionary and Glossary − A collection of detailed information on the data elements, fields, tables and other en
Stakeholder Map − Identifies all stakeholders who are affected by the proposed change and their influence/authorit
(PMM) and is owned by the Project Manager but needs to be updated by the project team as new/changed Stakeho
Requirements Traceability Matrix − A table that illustrates logical links between individual functional requirements a
Design Elements, Code Modules, Test Cases, and Business Rules.

In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies c

Mitigation Plan-
Risk mitigation planning is the process of developing options and actions to enhance opportunities and reduce threa
Risk mitigation implementation is the process of executing risk mitigation actions. Risk mitigation progress monito
project [1].
Risk mitigation handling options include:

Assume/Accept: Acknowledge the existence of a particular risk, and make a deliberate decision to accept it without engaging in special
Avoid: Adjust program requirements or constraints to eliminate or reduce the risk. This adjustment could be accommodated by a change
Control: Implement actions to minimize the impact or likelihood of the risk.
Transfer: Reassign organizational accountability, responsibility, and authority to another stakeholder willing to accept the risk.
Watch/Monitor: Monitor the environment for changes that affect the nature and/or the impact of the risk.

Phase 1 - project manager decide the project of scope and then the BA comes in the role -> BA just give a high level ideas how
analysis- entire team or feasibility study- discussion / high level
business case
scope of the project
vertical or horizantal

Precise
Phase-2 - Main BA roles start in the secobd phase , from eliciating requirements, documenting them
phase 3-no BA needed- Archeciture duty -conceptual design- high level and low level document
phase 4- devolper work
Phase 5- UAT- BA works with the client and gives the demostration. giving demo
Phase 6- Production
unit tesing is done by- devolpers
UAT- done by BA

Requirement traceablity matrix-

It is used to track the requirements and to check the current project requirements are met.

product based company-devolped and sale to many vendors- you are the owner of that product. marketing
What is SDLC?
The 7 phases of Software Development Life Cycle are planning, requirements, design, development, testing, deployment, an
Software Development Life Cycle consists of a complete plan explaining the way to develop, maintain and replace specific soft
Phase 1- Planning- Phase 1 - project manager decide the project of scope and then the BA comes in the role ->BA-enterprise a
business case
scope of the project. Estimate time requirement plan

Phase2- Requirement gathering -The main responsible person here is BA, who gathere the requirement

Requirement elicition techniques?

1. Brainstroming-
a group problem-solving technique that involves the spontaneous contribution of ideas from all members of the group. It’s al
that are generated, the better.
https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2067/Using-the-Brainstorming-Technique-in-Business-Ana
2. Document Analysis-
The document analysis technique is one of the most effective ways of kick-starting the requirements elicitation phase. It is the
project background and identifying requirements or opportunities for improvement.

It’s a means of gathering information before scheduling interviews or other elicitation sessions with stakeholders. It can comp
To perform document analysis effectively, the analyst should always check the source of documents for possible bias.  
Document Analysis is performed in 3 stages:

1. Prepare Stage – this involves identifying which materials are suitable and relevant for analysis
2. Review Stage – this involves studying the material, taking note of relevant information and listing follow-up questions for the stakeholders
3. Wrap up Stage – this stage involves reviewing notes with stakeholders, organising requirements and seeking answers to follow-up questions
https://businessanalystlearnings.com/ba-techniques/2013/5/17/understanding-the-document-analysis-technique
3. Focus Group
Focus Group is use to gather subjective information
The focus group technique is one example of a qualitative research methodology used to explore the opinions, knowledge, perceptions, and c
The focus group typically involves six to ten individuals who have some knowledge of or experience with the topic.
The group discussion is led by a moderator who guides participants through a series of open-ended questions. The in
The technique can also be used successfully in conjunction with other research tools, such as surveys, either to help develop a questionnaire
4. Interface Analysis
requirements that define how human beings interact with the system; how applications link to other applications and how ha
the requirements needed to integrate software into its new environment.
https://businessanalystlearnings.com/ba-techniques/2014/5/31/interface-analysis
5. Interview
Ways of gathering req- Interview, observation, visualization
Interview- interview in a systemantic approach for elicating infrmation person or group of people in a informal or formal way o
interactions with SME can be through Skype, in meeting as person. Discussion about the process
types of Interview-
Structured(formal) Interview- once the discussuion has happended->analysis-> Visualize it-> sequence of actions->series of ev
questions. drafting the requirements
Unstructured(informal) Interview- on fly, the question you are just on discussion going on right now but have no idea about th
before interview a SME- you should research about the client's business, google the comaprative options, client expactions, re
terms, documentation. discussion will be high level, and you have to put thought process. what will happend more whay and w
6 .Observation- Observation is nothing but asking client to demostrate the cureent process. You have to monitored the proces
how are the process is going on, start to end steps. Sequence of steps
where you can't observation?

observation without interaction- just observe and take notes

observation with interaction- self explainary
business rules- identify the things which are needed the process
external agents- people helping to complete the task, helping in the exsisting process. Third party API- external device or agen

7. Prototype technique-
helps us to validate the requirement in the presence of client. Start preparing the mockup- how the screen looks like, images,
. With prototypes, stakeholders can easily get a feel for what is required and what is superfluous. Prototypes also allow analys
The main value of using a prototype is to convey to stakeholders how the solution should work and what it should do.
 the main purpose of prototypes is to always help stakeholders visualize the requirements & gain quick feedback to eventually
where there is no user interface- in prototype when there clients need to build a project and when they have no exsisting soft
with the feed back and sign off we can move forward
mock up- an arrangement of text and pictures to be printed. a model or replica of a machine or structure, used for instruction

8. Process Modelling-
https://www.interfacett.com/blogs/three-steps-to-conducting-requirements-workshops/

https://businessanalystlearnings.com/ba-techniques/2013/2/28/requirements-workshop-technique-exploring-the-power-of-c

A requirements workshop can be defined as a structured and facilitated event for

getting carefully selected stakeholders together to discover, refine, prioritize, validate and discuss requirements.
A skilled facilitator usually manages workshop sessions. It is designed to be collaborative and has its roots embedded in Joint A

Requiremnt Workshop
when ever there is a Enhancemnet at that time we invites all the stakeholders to the workshop

9. Questionnaires/Surveys-
https://businessanalystlearnings.com/ba-techniques/2013/6/25/how-to-design-effective-questionnairessurveys
Questionnaires can be very useful in gathering opinions and information from multiple sources. The analyst may choose to dis
Using a questionnaire can go a long way in gauging user perceptions and gaining insight into pertinent issues. If questions are

When is it advisable to use a questionnaire?

1. When you need direct or specific responses
2. When there’s a large group of people you need data from. In this case, using a standard set of questions can provide respon
3. When you’re more interested in facts than details

when you have many solutions and not sure which will be the best fit for the product. So you will share with group of users an
feedback is survey, questionarie- list of sets of question and give choices,

Document analysis, interview and observation. You as BA will be using irrespective to every project. Elication technique

Focus Group- identify stakeholder who have domain knoweldge about that particular topic or feature. You will interview or
Focus Group- identify stakeholder who have domain knoweldge about that particular topic or feature. You will interview or ar
It is a gathering of delibrately selcted people who particpates in a facilated discussion to elict coustomer preceptions about a p
if it's a generic question then you can ask any group but if it's a related to a particular domain you will pick the group from tha

when do you use Focus group?

focus groupis used by BA remember- situation impletemnet for one particular domain and you don’t have any knowledge. Ha
inviting the team who a particular domain knowledge.
real time exam- sale team product is build so as a BA you don't have sales knowledge. So you will focus on the sale team wher
but you have to do your research and then start clarify the requirement.

LEGACY SOFTWARE TO NEW APPLICATION

Existiting product- analyze as is state of the product , identify the functional and non functional , business rules
To Be Product- expected product will be, expectation proceess and you will know the flaws on the exsisting product
reversible engineering- existing solution and try to update the system or you replace the product completely. Gap analysis wit
Methadology-There are different type of methadology
Waterfall-
V- type-
Prototype-
agile-

Waterfall methadology
t’s also a very straightforward approach: finish one phase, then move on to the next. No going back. Each stage relies on inform

The downside of Waterfall is its rigidity. Sure, it’s easy to understand and simple to manage. But early delays can throw off the
maintenance stage. This model doesn’t work well if flexibility is needed or if the project is long term and ongoing.
The waterfall model is a breakdown of project activities into linear sequential phases, where each phase depends on the deliverables of the previous one and
The approach is typical for certain areas of engineering design. In software development, it tends to be among the less iterative
as progress flows in largely one direction ("downwards" like a waterfall) through the phases of conception, initiation, analysis,
V Model- https://www.tutorialspoint.com/sdlc/sdlc_v_model.htm
This linear development methodology sprang from the Waterfall approach. It’s characterized by a corresponding testing phase
Under the V-Model, the corresponding testing phase of the development phase is planned in parallel. So, there are Verification

Prototype-
The Software Prototyping refers to building software application prototypes which displays the functionality of the product under
Software prototyping is becoming very popular as a software development model, as it enables to understand customer require

What is Software Prototyping?

Prototype is a working model of software with some limited functionality. The prototype does not always hold the exact logic use
Prototyping is used to allow the users evaluate developer proposals and try them out before implementation. It also helps unde
https://www.tutorialspoint.com/sdlc/sdlc_software_prototyping.htm
rs and developers understand about what exactly is expected from the product under development.
https://www.tutorialspoint.com/business_analysis/business_analysis_functional_requirements_document.htm

Balsamiq
email- [email protected]
password-k1Balsamiq

https://www.tutorialspoint.com/business_analysis/business_analysis_functional_requirements_document.htm

https://www.tutorialspoint.com/sdlc/sdlc_v_model.htm

https://www.mitre.org/publications/systems-engineering-guide/acquisition-systems-engineering/risk-management/risk-mitig

https://www.guru99.com/traceability-matrix.html
Tentative

itinerary

a la carte
Unusal
Worried
concise- giving a lot of information clearly and in a few words; brief but comprehensive.
channels
solicating
configured
on the pilot
geographically disapered
clarity
enhancement
How do you identify your stakeholders?
RACI- chart - the document is maintain by the Project manager, where the roles and their responsibilites are mentions.
responsible
Accountable
confirmed
informed
project manager
roles and responsibility to what extend

What is the role of BA in the intial stage?

identify the stalkholders