Question

What are the primary differences between a traditional SDLC approach and each of the following development methods.

• Secure SDLC (SSDLC)
• Software Testing Life Cycle (STLC)
• Secure Agile
• Secure RAD

Answer 1

1) Requirement Gathering and Analysis
During this part, all the relevant info is collected from the client to develop a product as per their expectation. Any ambiguities should be resolved during this part solely.

Business analyst and Project Manager originated a gathering with the client to collect all the data like what the client needs to make, World Health Organization are going to be the end-user, what's the aim of the merchandise. Before building a product a core understanding or information of the merchandise is extremely vital.

For Example, A client needs to possess associate application that involves cash transactions. during this case, the necessity should be clear like what reasonably transactions are going to be done, however it'll be done, during which currency it'll be done, etc.

Once the necessity gathering is completed, associate analysis is completed to examine the feasibleness of the event of a product. just in case of any ambiguity, a decision is ready up for any discussion.

Once the necessity is clearly understood, the SRS (Software demand Specification) document is formed. This document ought to be completely understood by the developers and conjointly ought to be reviewed by the client for future reference.

2) Design
In this part, the necessity gathered within the SRS document is employed as associate input and package design that's used for implementing system development springs.

3) Implementation
Implementation/Coding starts once the developer gets the planning document. The package style is translated into ASCII text file. All the parts of the package ar enforced during this part.

4) Testing
Testing starts once the cryptography is complete and also the modules ar discharged for testing. during this part, the developed package is tested completely and any defects found ar allotted to developers to induce them fastened.

Retesting, regression testing is completed till the purpose at that the package is as per the customer’s expectation. Testers refer SRS document to create certain that the package is as per the customer’s customary.

5) Deployment
Once the merchandise is tested, it's deployed within the production atmosphere or 1st UAT (User Acceptance testing) is completed betting on the client expectation.

In the case of UAT, a reproduction of the assembly atmosphere is formed and also the client along side the developers will the testing. If the client finds the applying obviously, then log off is provided by the client to travel live.

6) Maintenance
After the readying of a product on the assembly atmosphere, maintenance of the merchandise i.e. if any issue comes up and desires to be fastened or any sweetening is to be done is taken care by the developers.