100 Business and Technical Term for

Business Analysts working in IT Project

Created By – Diwakar Kumar Singh

Agile: A methodology for iterative and incremental project
management and software development.
API (Application Programming Interface): A set of
protocols and tools for building and interacting with
software applications.
Backlog: A list of tasks or features that are prioritized for
development in future sprints.
Benchmarking: Comparing business processes and
performance metrics to industry bests and best practices
from other companies.
BPMN (Business Process Model and Notation): A
graphical representation for specifying business processes
in a workflow.
BRD (Business Requirements Document): A document
that details the business solution for a project including the
needs and expectations of the customer.
Change Management: A systematic approach to dealing
with change both from the perspective of an organization
and the individual.
Cloud Computing: Delivery of different services through the
Internet including data storage, servers, databases,
networking, and software.
Data Migration: The process of moving data from one
system to another.
Data Modeling: The process of creating a data model for the
data to be stored in a database.
DevOps: A set of practices that combines software
development (Dev) and IT operations (Ops) to shorten the
development lifecycle.
DPI (Data Protection Impact): An assessment to identify
and minimize the data protection risks of a project.
ETL (Extract, Transform, Load): A process in database
usage and especially in data warehousing.
Gap Analysis: A method for comparing the current state
with a desired future state and identifying the gaps.
GUI (Graphical User Interface): A user interface that
includes graphical elements, like windows, icons, and
buttons.
Integration: The process of linking together different
computing systems and software applications physically or
functionally.
Iteration: A repetition of a process in order to generate a
sequence of outcomes.
JAD (Joint Application Development): A methodology that
involves the client or end user in the design and
development of an application.
Kanban: A visual method for managing and improving work
across human systems.
KPI (Key Performance Indicator): A measurable value that
demonstrates how effectively a company is achieving key
business objectives.
Lean: A methodology focused on minimizing waste within
manufacturing systems while simultaneously maximizing
productivity.
Legacy System: An old method, technology, computer
system, or application program that is still in use.
Middleware: Software that connects different applications
or systems.
Mock-Up: A static representation of a website or application
used to demonstrate and test design ideas.
MVP (Minimum Viable Product): A product with the
minimum features needed to satisfy early adopters.
Non-functional Requirements: Requirements that specify
criteria that can be used to judge the operation of a system,
rather than specific behaviors.
On-Premises: Software and technology that is hosted on
the physical premises of an organization.
Product Backlog: An ordered list of everything that is known
to be needed in the product.
Prototyping: The process of building an experimental model
of a proposed solution.
Regression Testing: A type of software testing to confirm
that a recent program or code change has not adversely
affected existing features.
RFP (Request for Proposal): A document that solicits
proposals, often made through a bidding process, by an
agency or company interested in procurement.
Risk Management: The forecasting and evaluation of
financial risks together with the identification of procedures
to avoid or minimize their impact.
Roadmap: A high-level, visual summary that maps out the
vision and direction of a product offering over time.
Scrum: A framework within which people can address
complex adaptive problems, while productively and
creatively delivering products of the highest possible value.
SDLC (Software Development Life Cycle): A process for
planning, creating, testing, and deploying an information
system.
SLA (Service Level Agreement): A commitment between a
service provider and a client.
Sprint: A set period of time during which specific work has
to be completed and made ready for review.
Stakeholder: An individual, group, or organization that has
an interest in the outcome of a project.
SWOT Analysis: A framework for identifying and analyzing
the internal and external factors that can have an impact on
the viability of a project.
SysML (Systems Modeling Language): A general-purpose
modeling language for systems engineering applications.
System Integration: The process of bringing together the
component subsystems into one system and ensuring that
the subsystems function together.
Test Plan: A document detailing the objectives, resources,
and processes for a specific test for a software or system.
Traceability Matrix: A document, usually in the form of a
table, used to track the requirements and their coverage in
the testing phase.
UI/UX (User Interface/User Experience): The design and
experience users have with a company’s products and
services.
Use Case: A list of actions or event steps typically defining
the interactions between a role and a system to achieve a
goal.
User Stories: A description of a software feature from an
end-user perspective.
UAT (User Acceptance Testing): The final phase of the
software testing process where actual software users test
the software to make sure it can handle required tasks in
real-world scenarios.
Version Control: A system that records changes to a file or
set of files over time so that you can recall specific versions
later.
Waterfall: A sequential design process, used in software
development processes, in which progress is seen as
flowing steadily downwards through phases.
Wireframe: A visual guide that represents the skeletal
framework of a website or application.
Acceptance Criteria: Conditions that a software product
must meet to be accepted by a user or stakeholder.
As-Is Process: The current state of a business process
before any changes or improvements are made.
Automation: The use of technology to perform tasks without
human intervention.
B2B (Business-to-Business): Transactions conducted
directly between companies.
B2C (Business-to-Consumer): Transactions conducted
directly between a company and consumers.
BPR (Business Process Reengineering): The analysis and
redesign of workflows within and between enterprises.
Business Case: A justification for a proposed project or
undertaking on the basis of its expected commercial benefit.
Business Rules: Specific rules that define or constrain
some aspects of the business.
CAB (Change Advisory Board): A group that supports the
assessment, prioritization, and scheduling of changes.
CRUD (Create, Read, Update, Delete): The four basic
functions of persistent storage.
Data Dictionary: A detailed description of all the data used
in the system.
Data Flow Diagram (DFD): A graphical representation of the
flow of data through a system.
Data Mining: The process of discovering patterns in large
data sets.
Data Warehouse: A central repository of integrated data
from one or more disparate sources.
Domain Model: A conceptual model of the domain that
incorporates both behavior and data.
ERP (Enterprise Resource Planning): Integrated
management of main business processes, often in real time
and mediated by software and technology.
Feasibility Study: An assessment of the practicality of a
proposed plan or method.
Functional Decomposition: The process of breaking down
a complex process into smaller, more manageable parts.
HLD (High-Level Design): A general system design in
architecture, components, and data flow.
Impact Analysis: The process of assessing the effects of a
proposed change.
Information Architecture: The structural design of shared
information environments.
IoT (Internet of Things): The interconnection via the Internet
of computing devices embedded in everyday objects.
ITIL (Information Technology Infrastructure Library): A set
of detailed practices for IT service management that focuses
on aligning IT services with the needs of business.
JIRA: A tool used for issue tracking and project
management.
Lean Six Sigma: A methodology that relies on a
collaborative team effort to improve performance by
systematically removing waste.
Metadata: Data that provides information about other data.
Mock Data: Artificially created data used for testing
purposes.
Modularization: The process of dividing a system into
modules.
Non-disclosure Agreement (NDA): A legal contract
establishing a confidential relationship.
Normalization: The process of organizing data to reduce
redundancy and improve data integrity.
OOP (Object-Oriented Programming): A programming
paradigm based on the concept of objects.
OTAP (Operation, Test, Acceptance, Production): A
strategy for the structured deployment of software.
Page Flow: The sequence of pages a user navigates through
in an application.
Parallel Testing: Running the same test simultaneously on
multiple environments to compare results.
PDM (Product Data Management): The use of software or
other tools to track and control data related to a particular
product.
PLM (Product Lifecycle Management): The process of
managing the entire lifecycle of a product from inception
through engineering design and manufacture to service and
disposal.
PMO (Project Management Office): A group or department
within a business that defines and maintains project
management standards.
Proof of Concept (POC): A realization of a certain method
or idea to demonstrate its feasibility.
Refactoring: The process of restructuring existing computer
code without changing its external behavior.
Requirements Traceability Matrix (RTM): A document that
links requirements throughout the validation process.
SaaS (Software as a Service): A software distribution
model in which applications are hosted by a vendor or
service provider and made available to customers over a
network, typically the Internet.
Scalability: The capability of a system, network, or process
to handle a growing amount of work, or its potential to be
enlarged to accommodate that growth.
Service-Oriented Architecture (SOA): A design pattern
where services are provided to the other components by
application components, through a communication
protocol over a network.
Sprint Retrospective: A meeting held at the end of a sprint
to discuss what went well, what didn't, and how to improve.
Stakeholder Analysis: The process of identifying and
analyzing stakeholders to understand their needs and
expectations.
System Context Diagram: A high-level diagram that defines
the boundary between the system, or part of a system, and
its environment, showing the entities that interact with it.
System of Record (SOR): The authoritative data source for a
given data element or piece of information.
Test Automation: The use of special software to control the
execution of tests and compare actual outcomes with
predicted outcomes.
User Persona: A fictional character created to represent a
user type that might use a site, brand, or product in a similar
way.