Session 6 at SOAR by Avembsys

                    Hello everyone, session 6 at SOAR kickstarted with a brief knowledge of identifying bugs in a program. Our techlead then took over the session. The topic of discussion was about the software  development life cycle(SDLC). The SDLC has the following four phases:
       1. Analysis(10%)
       2. Design(20%)
       3. Development(20%)
       4. Testing(50%)
The percentage in the brackets is an average amount of time required for each phase of the cycle. It may vary from one software to another, i.e., depending on the type of software we are developing.
                   
                    Analysis is the first phase of the SDLC. In this phase it is the job of the developer to identify any problem that coulb be encountered by the software, the feasibility and the requirements.
                    To understand this let us consider the following example. The client who is a banker wants a software for an ATM machine and the developer is required to fulfill his requirement. A business analyst mediates between the two and explains exactly to the developer what he has to do. The developer prepares a questionaire for his client to understand the exact requirement. The developer also has to make sure of the technical, financial and commercial feasibilty of the software. The requirement is a collection of problems and sub-problems. The document of the analysis is sent to the client for approval. Once approved, the next phase of the SDLC is the design.
                 
                     In the design phase, we need to have design goals i.e., what we want to achieve with this design is very essential to have in mind. The first part of the design consists of the high level design. The high level design includes the following; algorithms, flowchart and blocl diagram. The output of a high level design is the high level design document. After this we have the low level design which includes the following; data structure, logic and function. More thought process goes into the design phase, because any flaws here could lead to the failure of the software.
                   
                      The next phase is the development. Here we translate the english language or in other words the design into a C language or any programming language. The code should follow the coding standards and the code should be re-usable i.e., it should be flexible and not rigid. Finally we come to the testing phase which tests the software. If there are any flaws we must go back to the design phase and correct it.With this, the sixth session at SOAR came to a close.