0% found this document useful (0 votes)
49 views1 page

SDLC (Software Development Life Cycle) : Terminology

The document discusses the software development life cycle (SDLC) and terminology used in the process. It describes the phases of the SDLC as including a proposal initiation phase and requirements gathering phase. In the requirements gathering phase, the business analyst and engagement manager interact with customers to collect requirements, with the business analyst filling out a template and producing a requirements document and the engagement manager validating any additional requirements.

Uploaded by

pathuri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
49 views1 page

SDLC (Software Development Life Cycle) : Terminology

The document discusses the software development life cycle (SDLC) and terminology used in the process. It describes the phases of the SDLC as including a proposal initiation phase and requirements gathering phase. In the requirements gathering phase, the business analyst and engagement manager interact with customers to collect requirements, with the business analyst filling out a template and producing a requirements document and the engagement manager validating any additional requirements.

Uploaded by

pathuri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Product: If a software is developed for a group of customers.

SDLC(SOFTWARE DEVELOPMENT LIFE CYCLE):


TERMINOLOGY:

KOM: KICK OF MEETING


PIN: PROJECT INITIATION NOTE
BA: BUSINESS ANALYST
SA: SYSTEM ANALYST
EM: ENGAGEMENT MANAGER
BRS: BUSINESS REQUIREMENT SPECIFICATIONS
SRS: SOFTWARE REQUIREMENT SPECIFICATIONS
CRS: CUSTOMER REQUIREMENT SPECIFICATIONS
FRS: FUNCTIONAL REQUIREMENT SPECIFICATIONS
URS: USER REQUIREMENT SPECIFICATIONS
BDD: BUSINESS DESIGN DOCUMENT
BD: BUSINESS DOCUMENT
PM: PROJECT MANAGER
HLD: HIGH LEVEL DESIGNING
LLD: LOW LEVEL DESIGNING
CA: CHEIF ARCHITECT
UML: UNIFIED MODELLING LANGUAGE
TDD: TECHNICAL DESIGN DOCUMENT
ASC: ACTUAL SOURCE CODE
RCN: REQUIREMENT CLARIFICATION NOTE

Phases of SDLC:
Proposal/Proposal initiation
Requirement gathering:
TASK: Interacting with the customer and gathering the requirements.
Roles: BA,EM
Process: first of all the BA will take an appointment from the customer,collect the
template from the company, meets the customer at appointment date and gathers the
requirements with the help of the template. Finally comes back to the company with
requirements document.
The EM will go through the requirements, if at all he finds any extra requirements then
he will ask the concerned team to develop a prototype, with that prototype go to the
customer and demonstrates the prototype gathers the clear requirements.
Proof: requirement document.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy