system development life cycle methodology

8/8/2019 System Development Life Cycle Methodology

1/20

SYSTEM DEVELOPMENT LIFECYCLE

Methodology


2/20

OBJECTIVE

To understand variousmethodology.

To learn software analysis

modeling and theirelements.

To learn software design

concept

Understand softwaretesting

Understand RiskManagement


3/20

WATERFALL METHODOLOGY


4/20

PROTOTYPING METHODOLOGY


5/20

RAD [Rapid Application Development]


6/20

Spiral METHODOLOGY


7/20

Strength andWeaknesses of SDLC

Strength WeaknessControl. Increased development time.

Monitor Large projects. Increased development cost.

Detailed steps. Systems must be defined up

front.

Evaluate costs andcompletion targets. Rigidity.

Documentation. Hard to estimate costs,

project overruns.

Well defined user input. User input is sometimes

limited.

Ease of maintenance.

Development and design

standards.

Tolerates changes in MIS

staffing.


8/20

SOFTWRAE ANALYSIS MODELING

Data

Dictionary

EntityRelationship

Diagram

Data

Flow

Diagram

State- Transition

Diagram


9/20

ELEMENTS OF ANALYSIS MODEL

DATA DICTIONARY: It is the coreof analysis model. It is a repositoryof data objects consumed or

produced by the software.


10/20

ELEMENT OF ANALYSIS MODEL.

ENTITY RELATIONSHIP DIAGRAM: Itdepicts the relationship betweendata objects. It is the notation used

for conducting data modeling


11/20


DATA FLOW DIAGRAM: It provides anindication of data transformation as theymove through the system. It depicts the

function of data transformation


12/20

ELEMENTS OF ANALYSIS MODEL.

STATE TRANSECTION DIAGRAM: It indicatesthe system behavior as a consequences ofexternal events. It represents the various

modes of behavior known as states of thesystem.


13/20


DATAOBJECT DESCRIPTION: Theattributes of each object given in ERDcab be described using a data objectdescription.

PROCESS SPECIFICATION: The descriptionof the DFD function is contained inprocess description.

CONTROL SPECIFICATION: Extrainformation about the control aspectof the software is contained in thecontrol specification.


14/20

SOFTWARE DESIGN CONCEPT

Component

LevelDesign

Interface

Design

Architectural

Design

Data

Design

Translation of Analysis Model

into a Software Design


15/20

SOFTWARE TESTING

It indicate the ultimate review of specification,design and code generation.

Software must be tested to uncover andcorrect maximum possible errors,

before been delivered.

In order to find highest possible no.of errors, test must be conductedsystematically and test cause must

be designed using disciplined technique.


16/20

APPROACHES OF TESTING

Functional Testing

(Black Box Testing)

Equivalence Partitioning

Boundary Value Analysis

Orthogonal Array Testing

Cause-Effect Graphing

Structural Testing

(White Box Testing)

Basic Path Testing

Condition Testing

Data Flow Testing

Loop Testing


17/20

SOFTWARE TESTING STRATEGY


18/20

SOFTWARE PROCESS MATRICS

People Technology

Product

Development Environment

Customer

Characteristics

Business

Conditions

Process

Determinants for Software Quality and Organizational

Effectiveness


19/20

RISK MANAGMENT

Milestone Tracking

Top-10 Tracking

Risk Reassessment

Corrective ActionMonitoring

Prototypes

Simulation

Benchmark

Analysis

Staffing

Checklists

Decision Drive Analysis

Assumption Analysis

decompositionPerformanceModule

CostModels

Network Analysis

Decision Analysis

Quality Factor Analysis

Risk Exposure

Risk Leverage

Compound Risk ReductionRisk Avoidance

Risk Transfer

Risk Reduction

Risk Element Planning

Risk Plan Integration

Risk

Management

Risk

RiskResolution

Risk Management

Planning

Risk

Risk

Risk Identification

Polarization

Analysis


20/20

THANK YOU.

system development life cycle methodology

Documents