Software Development Life Cycle(SDLC)

 Explain SDLC with an example?



Every organization will follow some standard models to implement/build a software. One of the most popular model is called SDLC. It contains different phases. In each phase different people will be involved and carried out different activities. Every phase will have some inputs and corresponding outputs.

 The below are the phases in SDLC model.

Planning and Analysis: Planning and Analysis is the most important and fundamental stage in SDLC. In this stage business analyst and project manager set up a meeting with customer and gather information about the product. Once the requirement is clearly defined, a SRS (Software Requirement Specification) document will be created. This document should be thoroughly understood by the developers and also should be reviewed by the customer for future reference.

Design: Once planning and analysis is done, the next action is, SRS document is used as an input and developer use it to design high level architecture.

Development: In this stage the actual development will be started. The software design is translated to code. Developers must follow some coding guide lines defined by the company.

Testing: Testing starts once the coding is complete and the modules are released for testing. In this phase, the developed software is tested thoroughly and any defects found are assigned to developers to get them fixed.

Deployment and Maintenance: After testing is done, code will be deployed to production environment and product will be available to end-user.

Example: Develop a e-commerce platform





Comments

Post a Comment

Popular posts from this blog

Design Phase (SDLC)

  What would you do during the design phase in SDLC? The Design Phase is an crucial phase of the  Software Development  Life Cycle. The list of requirements that you develop in the definition phase is used to make design choices. In the design phase, one or more designs are created to achieve the project result. Depending on the project subject, the design phase products includes flow-charts, sketches, site trees, HTML screen designs, photo impressions, prototypes, and UML schemas. The project supervisors use these designs to choose the definitive design that you can produce in the project. The development phase follows it. Once you have selected the design in the definition phase, you cannot make changes in the project’s later stage. The objectives of the SDLC Design Phase are as follows: Objectives Successful completion of the SDLC Design Phase comprises: Transformation of all the requirements into detailed specifications covering all the aspects of the system. Planning...
Read more

UseCase Vs TestCase

What is the difference between use case and test case? Use Cases  and  Test Cases  are two important terms in context of Software Testing. A use case tells how a System will behave or perform a certain task provided the given conditions and a test case contains the actual test data, set of instructions to system and expected result of the interaction with system. Following are the important difference between Use Case and Test Case. Sr. No. Key Use Case Test Case 1 Objective The objective of Use case is to ascertain a certain output after the set of operations. The objective of test case is to ensure that system is working fine for each given instruction and yields the required result. 2 Definition Use case is a representation of actions which describes the behaviour of system to do a particular task. Test case contains the test data, set of instructions to follow and a result(s) of following the instructions. 3 Source Use cases are prepared on requirements. Test cases ar...
Read more

TestCase Vs TestScenario

What is the difference between test case and test scenario? A test case is a set of criteria that a tester uses to verify whether or not a software application is meeting the customer's requirements. Preconditions, case name, input conditions, and intended outcome are all included in the test case design. A test case is a basic activity that is derived from test scenarios. It is a comprehensive document that comprises all potential inputs (both positive and negative) as well as navigation instructions for the test execution process. Writing test cases is a one-time effort that may be reused for regression testing in the future. The test case contains thorough information about the testing approach, procedure, preconditions, and expected results. These are used during the testing phase to see if the software program is capable of executing the purpose for which it was created. By associating a defect with a test case ID, test cases assist testers in defect reporting. The testing tea...
Read more