Tuesday, January 18, 2011

Session 6 at SOAR by AVEMBSYS

              Hello everyone, it was our 6th session and was a bit of short duration unlike the previous sessions. The session started as usual with one of our friend explaining about bugs and debugging with the help of a few sample codes. The session was mainly focussed in the discussion of the projects that were as a part of our assignment.
              However, in the later part of the session we discussed about SDLC (Software Development Life Cycle). Here we learnt about the software development process in industries. We learnt about the various phases that undergoes in the process of development of software. The various phases include Analysis, Design, Implementation/Development and Testing. The efforts and time spent in each phases are roughly estimated to be 10% (Analysis), 20% (Design), 20% (Development) and 50% (Testing).
               Analysis is the first step towards a software development process. Here the software developer (industrialist) tries to understand the various problems of the client. This is mainly handled by the domain experts or the business analyst. He has to look for the various requirements of the client considering the feasibility, both technical and commercial. The output of this stage is SRSD (Software Requirement Specific Document) which is then sent to the client for approval. The client may send RFC (Request for change) if any changes are required and the SRSD is changed accordingly and resend to client for further approval.
              Once a SRSD has been approved by the client, the second phase, i.e. Design, starts. This phase has two level designs, the top level and the low level. The top level design consists of algorithms, flow charts and block diagram. The low level design consists of data structure, logic and function. The output of top level design is HDD (High level Design Document) while that of low level design is LDD (Low level/Detailed Design Document).
              The third phase, development, deals with the transformation of the designed document into programming codes. The codes so developed must be efficient, flexible and reusable.
              After the development of the programming codes, they undergo testing process. Here the programme codes are checked for their efficiency and error free with their respective systems.
              At the mere end of the session, the discussion drifted once again to the projects. The session was very interesting and delightful as there was a lot to learn from it.

No comments:

Post a Comment