Sei sulla pagina 1di 2

One page SDLC

1. Feasibility Study: a) Technical b) Schedule c) Financial.


2. Requirement Collection: a) Functional b) Environmental c) UI
3. System Requirement Specification/BRD/SRA (contains all the requirements,
spec, scheduled, price estimates etc.)
4. Preparation of master project plan: - A blue print to follow contains, detail plans,
product mgmt, plan mgmt, tests, logistics etc.
5. Designing- UI, DB, Application-a) HLD b) LLD
6. Coding- the actual dev. Process based on LL Design.
7. Testing- executing a programmer under control condition with intent to find an
error/fault.
a) BVT- (BUILD is a former release of code, encapsulated together and given
a name) To conduct a test on all major functionalities, based on BVT
checklist is BVT.
b) HOT-FIX- A quick fix by developers during testing phase.
c) Acceptance testing- by the client 1) Alpha: In house 2) Beta: at customer
Premises.
8. Test cases: Procedural guidelines for conducting a test.
A) T C Template: TC ID, TC Description, I/p, Expect Value, Actual Value,
Status (P/F), Module, Environment.
B) Tech for writing TC’s-
I) Boundary value Analysis
J) Negative value analysis
K) Positive value
L) Equivalence Portioning approach
M) Wild character

C) Test Case classification: UI (look & feel), Usability (Tab,


Cursor), Functionality (Save, insert, updating buttons),
Validation (-ve, +ve value)
D) Bug report: Bug is an error/malfunction noticed during testing.
Bug Template

Bug ID. Test case ID Bug Input Expected Actual Status (Pass/Fail)
Description

Seviourity Priority Detected Assigned to Module Environment


by
Resolutio New / Open Bug
n Differed
(Reason for
Won’t Fix/Can’t delay (low
Fix

Fixed /
Reope
Resolved
n

Closed

9. Software Life cycle models:


A} Waterfall: - Adv, simple & easy, good for small projects, easy to manage, clear
deliverables. Dies Adv, for long/ongoing projects, rigid, high risk, no S/w till end.

B} V-shape

C} Incremental: Keep adding the units/module for additional functions.


Adv; early working S/w, more flexible, easy to test, easy to manage.
Dis; each iteration/module is rigid, architectural problems.
D} Spiral: Adv; high amount of risk analysis, good for large projects, high success rate.
Dis; Costly, need specific expertise, success dependencies on risk analysis.

10. Miscellaneous terms: - CMM> Capability maturity model (Integration)


Scrum meeting> daily meeting to discuss the project status.