SDLC - A framework that describes the activities performed at each stage of a software development project. What is the relationship between SDLC and Quality Assurance? Example of the templates that support

3. 3

4. SDLC
A framework that describes
the activities performed at
each stage of a software
development project.
4

5. Verification
-Are we building the
System right?
-The process of
evaluating products
of a development
phase to find out
whether they meet
the specified
requirements.
-Reviews, Meetings
and Inspections.
Validation
-Are we building the
right System?
-the process of
evaluating software at
the end of the
development process
to determine whether
software meets the
customer expectations
and requirements.
-Testing like black box
testing, white box
testing, gray box
testing etc.
5

6. SDLC QA
Quality Assurance refers to the
planned and systematic way of
monitoring the quality of the process
which is followed to maintain the
quality of the product. QA is proactive
and plays important roles in each phase
of SDLC.
Quality Control finds the defects in the
product. The process set by QA is
followed by QC to meet the
expectation. QC also termed as a tester,
who find the bugs. They rely on the test
cases prepared by QA.
6

7. ▪ Requirements – defines needed
information, function, behavior,
performance and interfaces.
▪ Design – data structures,
software architecture, interface
representations, algorithmic
details.
▪ Implementation – source code,
database, user documentation,
testing.
7

8. Strengths
• Easy to understand, easy to use
• Provides structure to inexperienced
staff
• Milestones are well understood
• Sets requirements stability
• Good for management control (plan,
staff, track)
• Works well when quality is more
important than cost or schedule
Deficiencies
• All requirements must be known
upfront
• Deliverables created for each phase are
considered frozen – inhibits flexibility
• Can give a false impression of progress
• Does not reflect problem-solving
nature of software development –
iterations of phases
• Integration is one big bang at the end
• Little opportunity for customer to
preview the system (until it may be too
late)
8

9. When to use it?
▪ well known
▪ stable
▪ understood
▪ version of an existing product
▪ Porting an existing product
9

10. ▪
▪
▪
▪
10

11. ▪ major functions first
▪ operational
product
▪ respond to each build
▪ breakdown of
tasks
▪ initial delivery cost
▪ product delivery is faster
▪ important functionality
early
▪ changing requirements is reduced
▪ good planning and design
▪ Requires early definition of a
complete and fully functional system
▪ Well-defined module interfaces
▪
not lower
Strengths Weaknesses
11

12. ▪
early realization of benefits.
▪
evolve over time
▪ get basic functionality to the market
early
▪ lengthy development
schedules
▪ new technology
When to use it?
12

13. 13 13

14. ▪
▪
▪
▪
▪ Scrum
▪
▪
▪
▪
▪
▪
▪
14

15. Scrum is an iterative and incremental agile framework for a project and
product development
Product Owner
Defines the product features / stories. Responsible for prioritization of
stories, sprint ceremony schedules and project acceptance
Scrum Master
Scrum facilitator. Responsible for removing project impediments and
improving the team productivity
Development team
Cross functional team. Responsible for project estimation
Sprint
Sprint is time boxed unit of scrum development. It consists of various
ceremonies
Ceremony
Ceremony is similar to milestone, it consists of Planning, Daily stand up
scrum, Review and Retrospection
Product Backlog
It consists of user stories /features of entire product. Owned and prioritized
by the product owner
Sprint Backlog
List of user stories to be completed in the current sprint. Estimated by the
development team
Burndown Chart
Sprint progress chart. Displaying remaining work in the sprint backlog
Velocity
Long term measure of the amount of work completed per iteration
15

16. Project Concept / Initiation Phase
Project Charter
Business Case Document
Project Team Definition
Project Initiation Agenda
Project Resource Plan
Feasibility Study
Value Proposition Template
Project Or Issue Submission Form
Project Cost-Benefit Analysis
Stakeholder Identification List
Initiate Project Checklist
Concept of Operations
Project Schedule Template
Project Planning Phase
Project Plan
Roles And Responsibilities Matrix
Required Approvals Matrix
Project Approval Document
Development Estimating Worksheet
Statement Of Work
Activity Worksheet in Work Breakdown
Structure Doctionary Form
Work Breakdown Structure Resource
Planning Template
Work Breakdown Structure
Risk Information Data Collection Form
Risk Analysis Plan
Project Management Office (PMO)
Checklist
Project Capital vs. Expense Costs
Configuration Management Plan
Procurement Plan
Project Organization Chart
COBIT Checklist And Review
Request For Information
Root Cause Analysis
List Of Opportunities Summary
Requirements Definition Phase
Business Requirements Document
Functional Requirements Document
Requirements Traceability Matrix
Requirements Inspection Checklist
Use Case Template
Software Architecture Plan
Managing Scope and Requirements
Requirements Changes Impact Analysis
Training Plan
Service Level Agreement Template
System Design Phase
System Requirements Specifications
Technical Requirements Document
Analysis and Design Document
Website Planning Checklist
User Interface Design Template
Report Design Template
Conversion Plan
Code Review Checklist
Database Design Document
Application Development Project List
Testing Phase
User Acceptance Test Plan
Testing Bug List
System Test Plan
Test Plan
Documentation QA Checklist Template
Building Test Scenarios
System Quality Assurance Checklist
Testing Bug Report
Regression Testing Plan
Project Acceptance Document
Website Testing Summary Template
Project Monitoring and Control Phase
Project Status Report
Meeting Summary
Action Item Status
Issue Identification and Resolution
Change Management Log
Risk Management Log
Issues Management Log
Project Milestone Status Form
COBIT Objectives and Audit Activity
Report
Production Turnover / Deployment Phase
Production Implementation Plan
Production Turnover Approval
Installation Planning Guide
Software User Guide
System Administration Guide
Process Guide
Operations Guide
Project Closure / Maintenance Phase
Lessons Learned Template
Modification / Change Control Request
Disaster Recovery Plan Information
Product Retirement Plan
Transition Out Plan
Post Project Review
Request For New Application / Enhancement
Developer Knowledge Transfer Report
Post Project Survey Questionnaire
Certificate of Compliance and Acceptance of Deliverable
Global Application Support Summary
16

17. 17

18. ▪
▪
▪
▪
▪
18