Life Cycle: Beginning and End: Birth Death

Birth of a S/W: Thought process to automate a system

Death: obsolete
SDLC will have different phases:
1.
2.
3.
4.
5.
6.
7.

Planning
Analysis (Requirement Gathering)
Design
Development
Testing
Deployment (installation)
Maintenance and Support
What is Software?
Ans: Set of instructions coded together to perform a task
Types of software:
1. Operating system S/W : Interface between the User and the
Hardware
On ur computer
What is a Computer?
Hardware
2. Application S/W: A s/w meant to perform a desired task Ex: Media
Player to play music
COTS : Commercial Off The Shelf s/w. (Ready to use)
Product based Companies: That makes the application s/w
MS Office
Owner: Microsoft (Client)
Developed: Microsoft
End users: Ppl using the application
3. Custom S/W: A s/w which is being designed as per the needs of
the client.
Service/ Project based Companies:
Company: Infosys
Client: BOFA (The owner of the product)
End user : BOFA Staff, Customers
Database:
Files Systems:
1. Flat Files : text docs, Text pad, Word Pad , ms word

2. Indexed Files: Spread Sheets, Xcel sheets

3. Hierarchal Data Base
Parents
Ch 1

Ch2

Ch3 ..

Chn

C1n1 C1n2 C1nn

4. DBMS(Data Base Mgmt Systems)

Table
Columns
Rows
Create Table transaction
{ date: date
Amtpaid: int},

Table: Transaction
date
Apr 3rd

Table: Orders
date

Amt Paid
$1000

OrderNum

Table: Line Item

Quantity

Delivery
address

Status

5. RDBMS (Relational DBMS)

Tables: Constraints, Dependencies, Normalization
http://www.w3schools.com/sql/default.asp
http://www.sqlcourse2.com/index.html

SDLC will have different phases:

I.T Management: One (INFOSYS)
Client: BOFA
Project Team: PM, BA, SA, Tech Arch, DB Arch , DB Dev,web designers,Dev/
programmers, Testers, Deployment/Installation associates, Support
associates
1. Planning
Role: Project Manager
Deliverable / Artifact: Vision and Scope Document
Define the project and schedule it.
Resource Analysis
Time
Cost
Risk
Procurement
Risk mitigation
Vision and Scope Document/ Project Charter / Project reqs
document/ Project Kick Start Doc./ Conceptual Design Doc./ Business
Reqs Doc/ Solution Scoping

2. Analysis (Requirement Gathering)

Role: Business Analyst
Deliverable: Business Reqs Doc (BRD), Functional Reqs Doc (FRD),
Use Cases(Narratives, Diagrams), User Stories, Wire Frames[User
Interface(UI), Screen Mockups], Activity Flow Diagrams,
BPM(Business Process Modeling), Traceability
Step 1: Perform Stake Holder Analysis: create a doc.
Point of Contact (POC)

Stakeholder
Analysis.xls
POC and SME

Requirements Process/ Requirements Design

S1: Investigation: Elicitation (Req Collection)
S2: Req Analysis (Use cases)
S3: Req Documentation (BRD, FRD, Activity flows)
S4: Req Verification
S5: Sign off with the client
3. Design
Role: System Arch,
Deliverable: Blue print of the system (Unified Modeling Language)
Role: DB Design by DB Arch,
Deliverable: Blue print DB
Role: Screen Design by Application/Web Designers
Deliverable: Screens
Tech Arch: define the system blue print using UML (Unified Modeling
Language- consists of diagrams)
DB Design:
Conceptual Model
Logical Model
Physical Model

Data Modeling
Concept to DBMS.pdf

Screen / Application design:

They design the application windows/screen
System Blue Print +Database Design +Screen Design =

Solution

Design
System Analysis: System Analyst will use the all the docs from
ANALYSIS phase and DESIGN phase and will SYSTEM REQ SPEC (SRS/
developers requirement)
4. Development
Role: Programmer
Deliverable: BUILD
They built the application
The build is tested for
a. Unit Tested (10) one after the other
b. Low Level system integration Testing

The testing performed by the Developers is referred to as WHITE

BOX Testing
Transition Phase from Dev to testing:
A Business Analyst will Test the build sent from Development Team
to check if the BUILD is TESTABLE and this testing is referred to as
SMOKE TESTING/ MONKEY TESTING/ ADHOC TESTING
5. Testing
Role: TESTER, Business Tester (BA/ Business User)
Deliverable: Test Plan, Test Strategy, Test Scenarios, Test Cases, Test
Scripts, Bug Report, Traceability Matrix (RTM)
Testing Phases
1. System Testing:
Tester perform system testing: Functional and NonFunctional
This could be performed manually or by using Tools
(Automation)
2. User Acceptance Testing :
Business Analyst performs the UAT
a. UAT Alpha : Test the application where it is
being developed
b. UAT Beta: Test the application at the
Clients premises (Pre-Production testing)
6. Deployment
Role: Deployment / Installation associates
Deliverable: Install
Install the application on the client server
7. Maintenance and Support
Role: Maintenance and Support Associates
Deliverable: Support and take care of the application

Day # 4

1 RUP Model (Rational Unified Process)

Frame work was proposed and developed by IBM. (Rational Corporation)
This model is based on Object Oriented Concepts (OOPs)

4 Phases
1
2
3
4

Inception
Elaboration
Construction
Transition

Planning: Inception
Analysis: Elaboration
Design: Construction
Development: Construction
Testing: Transition
Maintenance: Transition
RAD:
V1 v2 v3: Combine only when all the independent modules are
completed
V1+V2+V3 ::>IntegrationTesting, System Testing and UAT
respectively
RUP:
Modules:V1 :Jeff, V2: Abdul, V3: Dipak
Lets say that Modules being completed in the following order
1: Abdul, delivers V2
2: Jeff, delivers V1
3: Dipak Delivers V3
V2: System testing
V2+V1 = X (New Module) :> Integration Testing and System Testing
X+V3 = Y: CompleteProject ::> Integration Testing, System testing
and UAT