Your ultimate guide

Manual_SDLC

Software Development Life Cycle
    
    A method that is adopted by the organisation to develop the application(product/project) for improving the quality of software and also within the budget and time range.

Phases Involved in SDLC:
Requirement Gathering
Requirement Analysis
Designing
Coding/implementing
Testing
Release & Maintenance

    BA team (Business Analyst) will collect the requirement of the project from the client and document them. That document is called a Business Requirement Document/Business Requirement Specification Document(BRS)/User Requirement Specification(URS)/Customer Requirement Specification(CRS)
    BRS Document is the first document prepared in the SDLC phase. This document will be quoted with a brief description of client business needs likes - Users, Types of Users, Users permissions, Services, ---
    After the preparation of the BRS document, Business Analyst will do/make a Feasibility study in order to check whether the project can be developed or not, whether we have a sufficient team or not, or whether we need to recruit people, budget, resources everything will check in the feasibility study in order to check whether the project is Acceptable.
     If the project is Accepted Business Analyst will provide Intimation to the client and an Agreement will be made SLA(Service Level Agreement). Basically, SLA will be made between the Company and Client.


    The System Analyst team can based on the Business requirement they can develop a Functionality document. That document is called the Functional Requirement Specification document/Functional Requirement Document/System Requirement Document.
     FRS document plays a very important role in the software development process. The FRS document contains all the specifications and functionalities of the project.


    Technical Architect/Design Architect(Senior Developer) can make GUI documents, HLD(High-Level Document), LLD(Low-Level Document), Database documents.


    Depending on the Design Architect documents Developers write code.
    After coding programs, Applications are available for Dynamic testing Initial stage of testing is performed by Developers through Unit Testing, Component Testing, Integration Testing by using WBT(White Box Testing).
    If the code is all clear and executable then the developer will give the executable program to the Tester.


    The tester team can test the software/project based on their written Test cases using BBT(Black Box Testing) they are tested like an end user.
    Based on the FRS document testers can test every user-stories.


    After BBT client will test the application this testing is called UAT(User Acceptance Test).
    This UST are two types:
        1. Alpha Testing:
                It is done within the organization, and the client will come and test the application.
        2. Beta Testing:
                The organization will give the application to the client. The client runs the application itself.


Release the software then maintenance

No comments:

Post a Comment