SDLC (Software Development Life Cycle) Tutorial

SDLC stands for SOFTWARE DEVLOPMENT LIFE CYCLE

GENERAL DEFINITION-

It is different phases of life through with a software undergoes during its development. Main propose of SDLC is to ensure that the software which is being developed should be of high quality and should meet customer expectation.

SPECIFIC DEFINITION 

It is a systematic process for building software that ensures the quality and correctness of the software built. SDLC process aims to produce high-quality software that meets customer expectations. The system development should be complete in the pre-defined time frame and cost. SDLC consists of a detailed plan which explains how to plan, build, and maintain specific software. Every phase of the SDLC life cycle has its own process and deliverables that feed into the next phase. SDLC stands for Software Development Lifecycle.

LIFE CYCLE:

There are 6 phases in life of Software



Phase 1: Requirement analysis:

The requirement is the first stage in the SDLC process. It is conducted by the senior team members with inputs from all the stakeholders and domain experts in the industry. Planning for the quality assurance requirements and recognization of the risks involved is also done at this stage. 

This stage gives a clearer picture of the scope of the entire project and the anticipated issues, opportunities, and directives which triggered the project.

Requirements Gathering stage need teams to get detailed and precise requirements. This helps companies to finalize the necessary timeline to finish the work of that system.


Phase 2: Defining:

Once the requirement analysis phase is completed the next step is to define and document software needs. This process conducted with the help of 'Software Requirement Specification' document also known as 'SRS' document. It includes everything which should be designed and developed during the project life cycle.

There are mainly five types of feasibilities checks:

  • Economic: Can we complete the project within the budget or not?
  • Legal: Can we handle this project as cyber law and other regulatory framework/compliances.
  • Operation feasibility: Can we create operations which is expected by the client?
  • Technical: Need to check whether the current computer system can support the software
  • Schedule: Decide that the project can be completed within the given schedule or not.

Phase 3: Designing:

In this third phase, the system and software design documents are prepared as per the requirement specification document. This helps define overall system architecture.

This design phase serves as input for the next phase of the model.

There are two kinds of design documents developed in this phase:

High-Level Design (HLD)

  • Brief description and name of each module
  • An outline about the functionality of every module
  • Interface relationship and dependencies between modules
  • Database tables identified along with their key elements
  • Complete architecture diagrams along with technology details

Low-Level Design(LLD)

  • Functional logic of the modules
  • Database tables, which include type and size
  • Complete detail of the interface
  • Addresses all types of dependency issues
  • Listing of error messages
  • Complete input and outputs for every module

Phase 4: Coding:

Once the system design phase is over, the next phase is coding. In this phase, developers start build the entire system by writing code using the chosen programming language. In the coding phase, tasks are divided into units or modules and assigned to the various developers. It is the longest phase of the Software Development Life Cycle process.

In this phase, Developer needs to follow certain predefined coding guidelines. They also need to use programming tools like compiler, interpreters, debugger to generate and implement the code.

Phase 5: Testing:

Once the software is complete, and it is deployed in the testing environment. The testing team starts testing the functionality of the entire system. This is done to verify that the entire application works according to the customer requirement.

During this phase, QA and testing team may find some bugs/defects which they communicate to developers. The development team fixes the bug and send back to QA for a re-test. This process continues until the software is bug-free, stable, and working according to the business needs of that system.

Phase 6: Installation/Deployment:

Once the software testing phase is over and no bugs or errors left in the system then the final deployment process starts. Based on the feedback given by the project manager, the final software is released and checked for deployment issues if any.

Phase 7: Maintenance:

Once the system is deployed, and customers start using the developed system, following 3 activities occur

  • Bug fixing - bugs are reported because of some scenarios which are not tested at all
  • Upgrade - Upgrading the application to the newer versions of the Software
  • Enhancement - Adding some new features into the existing software

The main focus of this SDLC phase is to ensure that needs continue to be met and that the system continues to perform as per the specification mentioned in the first phase.


Comments

Post a Comment

Popular posts from this blog

DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE

Image
DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE  DEFECT: If  difference exist  between actual result and expected result  and that difference is found by developer and  corrected by himself in the development phase then it’s called a defect.   Example if developer  has developed  a code  and while performing (Unit Testing) developed  found that the code is not functioning  as per requirement  then in tat case the issue occurred  is known as DEFECT. BUG: If testers find any mismatch in the application/system in testing phase then they call it as Bug. Example if the developer has done the development  and performed Unit testing of a login form then the module is sent to Tester for performing testing. In this phase if tester found that the client requirement is not matching with the  result of application then tester report it as Bug.  NOTE:  there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect. ERROR If we can’t compile
Read more

Software Testing Life Cycle (STLC)?

Image
STLC(SOFTWARE TESTING LIFE CYCLE) It is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. PHASES OF STLC : Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure What is Entry and Exit Criteria? Entry Criteria:  Entry Criteria gives the prerequisite items that must be completed before testing can begin. Exit Criteria:  Exit Criteria defines the items that must be completed before testing can be concluded. Requirement Analysis During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may in
Read more

SOFTWARE DEVELOPMENT LIFE CYCLE MODELS (SDLC MODEL)

Image
A software life cycle model is a descriptive representation of the software development cycle. SDLC models might have a different approach but the basic phases and activity remain the same for all the models. 1) Waterfall Model 2) V-Shaped Model 3) Prototype Model 4) Spiral Model 5) Iterative Incremental Model  6) Big Bang Model 7) Agile Model Waterfall Model The  Waterfall Model  was the first Process Model to be introduced. It is very simple to understand and use it. In a  Waterfall  model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.  The waterfall  model is the earliest  SDLC   approach that was used for software development. n “ The Waterfall ” approach, the whole process of  software development  is divided into separate phases. The outcome of one phase acts as the input for the next phase sequentially. This means that any phase in the development process begins only if the previous phase is complete. The waterfall model
Read more