Session 6 At SOAR By Avembsys

    The day started out late, with the one of our batch mates taking the stage to explain to us, the concepts of C programming namely, bugs. We had a few debatable discussions on some of the programs that he put forth in front of us and we did learn quite a few things on, structurally small but logically huge mistakes that commonly occur during programming.
    As our guide entered we started out by discussing the progress of the project and whether anyone had any new ideas which can be explored, after which we went on discussing about the Software Development Life Cycle (SDLC), its stages, the time allocated to each stage and why that much time has to be allocated to each one of them.
    Firstly, we discussed about the analysis phase which has three steps, i.e. finding problems, feasibility and requirements. This is the phase in which there is an interaction between the customers and the project handlers. This phase usually involve the domain experts or business analysts who are familiar with both the domains that the customer and the handlers are involved in. Once the need of the customer is understood, then the technical and commercial feasibility is verified and the requirements are put forth. the output of this phase is the SRSD or Software Requirement Specification Document which is given back to the customer for verification of his needs and approval and the customer either responds with a nod for proceeding ahead or with a RFC or Request For Change.
    The next step is the design phase which, as the analysis takes up 10% of the total project time. The design phase involves Top level or high level design and Low Level design. The top level design is responsible for giving a clear overview of the project through algorithm, flowcharts and Block diagrams. The output of which yields a HDD or high level Design Document and the LLD is simply a translation of this document to codes in a relevant language. The  Low level design's output is the Low Level Design Document ( LDD) or Detailed design document (DDD). It is to be kept in mind that the design should be flexible enough to incorporate any changes if necessary and also the codes are to be reusable. So that, if necessary, they can be used for any future projects or for the same project's development.
     The next is the implementation phase which takes up 20% of the total time allocated. This phase involves finding the right hardware (if present) and interfacing the different blocks to yield the complete project. Once the project is done, it moves onto the testing phase which takes up majority of the time span of the project thus to ensure its proper working and hence ready for deployment.
     After the discussion of the SDLC, we again backtracked to our project's progress and discussed about its development. Personally, I feel that we will be able to finish this by the end of next week. Hence another session came to an end with a better understanding of how things work in a corporate world.