Software Quality Assurance

and
Security
 Principles used in Project scheduling

(1)Compartmentalization
(2)Interdependency
(3)Time allocation
(4)Effort Validation
(5)Defined Responsibilities
(6)Defined Outcomes
(7)Defined milestone
 Work Breakdown Structure
 Work breakdown structure (WBS) is a process of
dividing the complex projects to simpler and
manageable tasks .
 In WBS , the large tasks are broken down into
manageable chunks of work . These chunks can
be easily examied and analysis .
 The project manager is responsible for creation
of WBS .
Work breakdown structure in tree
form
Project

Task 1 Task 2 Task 3

Sub task 1.1 Sub task 1.2 Sub task 1.3

Work package Work package Work package

1.1.1 1.1.2 1.1.3
 Activity Network and critical path
method
Bar charts and activity networks are geographical
representation of project schedule . The beginning and end
of the activity , responsible staff for corresponding activity
is shown by chart .
Activity network shows dependencies between different
activites . There are some automating project management
tools using which bar chart and activites network can be
generated . These tools require database of project
information as an input .
 Task Duration dependencies

T1 10

T2 15 T1(MI)

T3 15 T1(M2)

T4 7 T1,T2(M3)

T5 20 T1(MI)

T6 5 T4,T5(M4)

T7 4 T6(M6)

T8 8 T7(M5)

T9 10 T6,T8(M7)

T10 12 T9(M8)
Activity network
 Example
Tasks T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12

Duration(in 8 15 15 10 10 5 20 25 15 15 7 10
days)
Dependencies - - T1 - T2,T4 T1,T2 T3 T4 T3,T6 T5,T7 T9 T11
 Scheduling Techniques
 There are 2 scheduling techniques -
PERT and CPM.
 PERT – Stands for project management and
review technique . This technique is used for the
project where time needed to complete different
activites are known .
 Scheduling Techniques

 CMP-
Stands for Critical Path Method . This
technique is used in conjunction with
PERT and is used for managing well
defined activites of the project .
 Scheduling Techniques
 The PERT and CPM technique is used for–
 Prediction of deliverables
 Planning recourse requirements
 Controlling recourse allocation
 Internal and external program review
 Performance evaluation
 Scheduling Techniques
 Various framework activites in PERT/CPM are –
 Define the project . The project should have single start
activity and single finish activity .
 Develop relationship among the activites.
 Draw the network diagram for connecting all the activites.
 Assign time and cost to each activity.
 Compute critical path.
 Use network to help plan , schedule , monitor and control the
project .
 Scheduling Techniques(PERT)

 Formula –
Optimistic time + 4 x Mostly likely time +
Pessimistic time
= 6
 Scheduling Techniques(PERT)
 Example –
Optimistic time = 6 days
Most likely time = 9 days
Pessimistic time = 12 days
Then ,
PERT weighted average = 6+(4x9)+12
6 =9
 Thus it would be 9 days using PERT .
 The main advantage of PERT is that it attempts to address the
risk associated with duration estimates
 Scheduling Techniques
 Various activites conducted during tracking of the project schedule –
1. Conduct periodic meetings. In this meetings various problems related to
the project get discussed . The progress of the project is repotted to the
project manager .
2. Evaluate results of all the project reviews .
3. Compare ‘actual start date’ and ‘schedule start date’ of each of the project
task .
4. Determine If the milestone of the project is achieved on schedule date .
5. Meet informally the software practioners . This will help the project
manager to solve many problems. This meeting will also be helpful for
assessing the project progress .
6. Assess the progress of the project quantitatively .
 Time line chart
 The purpose of timeline chart is to emphasize
the scope of individual task .
 The timeline chart is also called Gant chart .
 The timeline chart can be developed for entire
project or it can be developed for individual
functions .
 Time line chart
 In Time line chart
1. All the tasks are listened at the leftmost column .
2. The horizontal bars indicate the time required by the corresponding
task .
3. When multiple horizontal bars occur at the same time on the calendar ,
then that means concurrency can be applied for performing the task.
4. The diamonds indicate the milestone .
 In most of the projects , after generating of time line chart the project
table are prepared . In project tables all the task are listened along with
actual start and end dates and related information
 Earned value Analysis
 The earned value Analysis (EVA)takes into
consideration the project context for planned and
actual expenditure
 This analysis is made up to find out project scope ,
schedule and recourse characteristics .
 The EVA acts as a measure for software project
progress .
 Earned value Analysis
 Various measures are determined during EVA – These measures are –
1. Planned value (PV) : It denotes the planned cost of the work
2. Actual cost (AC) : It represents the actual amount that the business has to
expand on the project . (AC) = ∑ Effort expanded on the work tasks that
have been completed by time it .
3. Earned Value (EV) : It is project managers estimated of the amount of
originally budgeted work completed .
4. Budget at completion (BAC) It represents total budget for the project .
 Software Quality Management vs
Software Quality assurance
 Definition of Quantity : The international
organization for standardization (ISO) defines
quantity as the totality of characteristics of an
entity that bear on its ability to satisfy stated or
implied needs .
 The project quantity management is a process
which ensures that the project will satisfy the need
s for which it was undertaken .
 Software Quality Management vs
Software Quality assurance

Quality management

Planning Quality
Quality assurance Controlling Quality
Management
 Phases of Software Quality
Assurance
 Definition of Quality assurance : It is planned
and systematic pattern of activites necessary to
provide a high degree of confidence in the quality
of a product .
 The quality assurance consists of set of repotting
and auditing functions .
 SQA plan

1. Create a SQA plan

2. Participates in description of software process
3. Review software engineering activites
4. Authenticate designated software work products
5. Ensure The deviations in software work . Document
work products .
6. Identify any noncompliance and reports to senior
management .
 Six Sigma

 The word “six sigma” is derived from six

standard deviations . Six sigma
originated at Motorola in the early 1980.
 Six Sigma

Define Measure Analyze Improve Control

Six Sigma framework

 CMMI
 CMMI – The capability Maturity Model(CMM)
is used in assessing how well an organization
process allow to complete and manage new
software projects .
 CMMI

 Level 1 – Initial
 Level 2 - repeatable
 Level 3 - Defined
 Level 4 - Managed
 Level 5 - Optimization
 Software Security
 Software security is a concept which is
implemented to product software against
malicious attack and other hacker risk so that the
software continues the function correctly under
such potential risks.
 Software Security
 Basic principles of Software Security
1. Protection from disclose
2. Protection from alteration
3. Protection from destruction
4. Who is making the request
5. Ability to build historical evidence
 Introduction to DEVOPs
 The term DEVOP is derived from “Software
Development” and “information technology
operations “
 Definition – DEVOP is a practice in which
development and Operation engineers participle
together in entire lifecycle activites of system
development from design , implementation to
product support
DEVOPs
 Introduction to DEVOPs
 Goals –
1. To make simple process increasing programmable and dynamic .
2. Fast delivery of product .
3. Lower failure rate of new releases.
4. Shortened lead time between fixes.
5. Faster mean time to recovery .
6. Increases net profit of organizations.
7. To standardize development environment .
8. To reduce work in progress.
9. To reduce operating expenses.
10. To set up automated environment .
 Introduction to DEVOPs

 Benefits
1. Technical benefits
2. Cultural benefits
3. Business benefits