Security System Development Life Cycle

Running head: SECSDLC METHODOLOGIES
SECSDLC METHODOLOGIES
Name of student
Name of university
Author’s note:

1SECSDLC METHODOLOGIES
Table of Contents
Introduction....................................................................................................................2
Discussion......................................................................................................................2
Methodologies............................................................................................................2
Comparison of the models.........................................................................................4
Advantages of waterfall model..................................................................................5
Disadvantages of waterfall model..............................................................................5
Advantages of agile model.........................................................................................6
Disadvantages of agile model....................................................................................6
Advantages of lean model..........................................................................................7
Disadvantages of lean model.....................................................................................7
Role of security blueprint in planning, maintenance and change management.............8
SecSDLC directed and managed....................................................................................9
Conclusion....................................................................................................................11
References....................................................................................................................12

2SECSDLC METHODOLOGIES
Introduction
The secure software development lifecycle could be described as the processes that
allow any organisation in completely integrating the security aspects in the prevailing SDLC
from the initial development with the help of obsolescence and the maintenance. SecSDLC
refers to the process that includes distinct phases requires to complete a project in a step-by-
step format. SecSDLC helps to acquire required number of resources in a secured way and at
the same time predicts risks that are encountered in a project (1). This comprises of six
distinct steps including investigation, analysis, logical design, physical design,
implementation and maintenance. It is the primary objective of SecSDLC to predict risks and
threats that are linked to a specific project. It helps the software development teams to reduce
the security related risks while creating software and different applications. There are mainly
three SecSDLC methodologies that are used in the present times.
This report intends to analyse the three SecSDLC methodologies and compare the
various features of the methodologies. The secure software development life cycle efficiently
follows the similar methodology as most commonly referred as the software development life
cycle, but they are different in some aspects which creates one method mainly preferred than
the other one in the software development.
Discussion
Methodologies
Agile: The agile planning could be described as the kind of planning for software
development that effectively estimates the work with the help of the self-contained units of
work that are referred as the iterations or the sprints. With the help of the agile model in the
software maintenance the developers could effectively estimate the issues that could be faced.
The bugs could be easily prioritised by the customers, the company could gain the common

3SECSDLC METHODOLOGIES
database of bug tracking and failing unit tests could be created by the developers (2). With
the introduction of the agile methodology, the change management could be effectively
handled. The change managers could be engaged in the earlier stages of the project, constant
communication would be established and engagement of the senior leaders would be allowed.
The principles of agile software development consist of the following:
1) Satisfaction of the customers by delivery of software in a proactive and continuous
way. When customers receive services in terms of working software at proper
intervals of time.
2) The changes in requirement are accommodated and delays in delivery are avoided.
3) There is a collaboration built between the shareholders and developers.
4) The involved people are motivated and thus they deliver their best work.
5) Technical detailing and design helps in the enhancement of agility.
6) Development process is just enough for completion of the task.
Lean: Unlike any other software development methodology, there are no strict plans
for the lean projects. It is due to the fact that the elements might change effectively in process
of the project realisation. The lean teams mainly improves the plans consistently. In the
maintenance phase, the lean model mainly reduces requirement of multitasking by the
emphasis on working at one aspect at one time. This model mainly comes with major benefits
to any organisation where the agile iterations eradicate the long pre-planned specifications.
At the stage of planning of a project, the lean life cycle starts and this has lenient
methodologies (3). The elements change in the project realization process. After the
completion of project planning the iteration planning process starts and every iteration has its
specific plan. When the plan is deployed, team starts the process of testing which are very