100% found this document useful (1 vote)
66 views20 pages

System Development Life Cycle Methodology

The document discusses various methodologies in software development life cycles including waterfall, prototyping, RAD, and spiral methodologies. It then summarizes the key elements of analysis models like data dictionaries, entity relationship diagrams, data flow diagrams, and state transition diagrams. Finally, it briefly covers software design concepts, testing approaches, risk management in software development, and metrics for ensuring software quality.

Uploaded by

swap_benq7436
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
66 views20 pages

System Development Life Cycle Methodology

The document discusses various methodologies in software development life cycles including waterfall, prototyping, RAD, and spiral methodologies. It then summarizes the key elements of analysis models like data dictionaries, entity relationship diagrams, data flow diagrams, and state transition diagrams. Finally, it briefly covers software design concepts, testing approaches, risk management in software development, and metrics for ensuring software quality.

Uploaded by

swap_benq7436
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 20

SYSTEM DEVELOPMENT

LIFE CYCLE

•Methodology
OBJECTIVE
• To understand various
methodology.
• To learn software analysis
modeling and their elements.
• To learn software design
concept
• Understand software testing
• Understand Risk Management
WATERFALL METHODOLOGY
PROTOTYPING METHODOLOGY
RAD [Rapid Application Development]
Spiral METHODOLOGY
Strength and Weaknesses of SDLC
Strength Weakness
Control. Increased development time.
Monitor Large projects. Increased development cost.
Detailed steps. Systems must be defined up front.

Evaluate costs and completion Rigidity.


targets.
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.
SOFTWRAE ANALYSIS
MODELING
Pr
n
io oc
es
t
rip

Data s
sc
De

Spe
Entity
Flow
Object

cifi
Relationship
Diagram

c
atio
Diagram Data
Dictionary
Data

n
State- Transition
Diagram
Co
n tro at ion
l p ecific
S
ELEMENTS OF ANALYSIS
MODEL
• DATA DICTIONARY: It is the core of
analysis model. It is a repository of data
objects consumed or produced by the
software.
ELEMENT OF ANALYSIS
MODEL…….
• ENTITY RELATIONSHIP DIAGRAM: It
depicts the relationship between data
objects. It is the notation used for conducting
data modeling
ELEMENT OF ANALYSIS
MODEL…….
• DATA FLOW DIAGRAM: It provides an
indication of data transformation as they move
through the system. It depicts the function of data
transformation
ELEMENTS OF ANALYSIS
MODEL…….
• STATE TRANSECTION DIAGRAM: It indicates
the system behavior as a consequences of external
events. It represents the various modes of behavior
known as states of the system.
ELEMENT OF ANALYSIS
MODEL…….
• DATA OBJECT DESCRIPTION: The attributes of
each object given in ERD cab be described using a
data object description.

• PROCESS SPECIFICATION: The description


of the DFD function is contained in
process description.

• CONTROL SPECIFICATION: Extra


information about the control aspect
of the software is contained in the
control specification.
SOFTWARE DESIGN CONCEPT
Translation of Analysis Model
into a Software Design

Component
Level
Design

Interface
Design

Architectural
Design

Data
Design
SOFTWARE TESTING
• It indicate the ultimate review of specification ,design
and code generation.

• Software must be tested to uncover and correct


maximum possible errors,
before been delivered.

• In order to find highest possible no.


of errors, test must be conducted systematically and test
cause must
be designed using disciplined technique.
APPROACHES OF TESTING
Functional Testing Structural Testing
(Black Box Testing) (White Box Testing)

• Equivalence Partitioning • Basic Path Testing

•Boundary Value Analysis • Condition Testing

•Orthogonal Array Testing •Data Flow Testing

•Cause-Effect Graphing •Loop Testing


SOFTWARE TESTING
STRATEGY
SOFTWARE PROCESS MATRICS
Determinants for Software Quality and Organizational
Effectiveness
Product

Business
Customer
Conditions
Characteristics

Process

People Technology
Development Environment
RISK MANAGMENT Checklists
Decision Drive Analysis
Assumption Analysis
Risk Identification Performance Module decomposition
Cost Models

Risk Network Analysis


Analysis Decision Analysis Risk Exposure
Quality Factor Analysis Risk Leverage
Risk
Risk Avoidance Compound Risk Reduction
Polarization
Risk Transfer

Risk Risk Reduction


Risk Management Risk Element Planning
Management Planning Risk Plan Integration
Prototypes
Simulation
Benchmark
Risk Analysis
Resolution Staffing
Milestone Tracking
Top-10 Tracking
Risk
Risk Reassessment
Monitoring
Corrective Action
THANK YOU………….

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