SDLC vs STLC: The Main Points of Comparison - PowerPoint PPT Presentation

About This Presentation
Title:

SDLC vs STLC: The Main Points of Comparison

Description:

The SDLC is a process that we use to produce quality software application while STLC refers to a series of tasks that are performed to ensure the software meets definite quality standards. – PowerPoint PPT presentation

Number of Views:12
Slides: 7
Provided by: oodlesERPsolutions
Tags:

less

Transcript and Presenter's Notes

Title: SDLC vs STLC: The Main Points of Comparison


1
SDLC vs STLC The Main Points of Comparison
2
  • The Software Development Life Cycle (SDLC) is a
    process that the teams use to produce quality
    software in the application. The purpose of SDLC
    is to meet customer expectations by a certain
    time by utilizing a cost-effective approach. SDLC
    was designed to handle complex businesses that
    require processing and analyzing data.

3
  • 1. Plan / Gather Requirements
  • The first phase plans and gathers the significant
    requirements from different stakeholders. The
    stakeholders can include customers, team members,
    and subject matter experts (SMEs). Generally, the
    information is evaluated to determine what is
    most practical for the software project.
  • In addition, the risks and opportunities are
    discussed during this phase. All the requirements
    gathered are used to plan a feasible approach. A
    couple of approaches are
  • Technical Approach All the expected services
    that will meet the stated technical scope of work
    (SOW)
  • Operational Approach All the steps taken for
    the transition from a softwares current
    condition to an end-result condition

4
  • 2. Design Software
  • In the design software phase, the team moves with
    every requirement and creates a design document
    specification (DDS). The main question from the
    DDS perspective answers, How are we actually
    going to build the software?.
  • With all the approved requirements, the
    comprehensive software architecture defines
    processes and approaches for each module.
    Individual processes and modules represent the
    data flows and the communication. Usually, the
    DDS designer uses pseudo-code, business rules,
    screenshots, and diagrams (hierarchy, detailed
    logic, entity-relationship, business processes)
    to outline many different functionalities.
  • 3. Develop Software
  • The development of software begins when the
    developer receives the design document
    specification (DDS). All the components are
    transformed from a high-level overview into the
    source code. The previous planning and
    specifications operate as a guide for
    implementing the required functionality.

5
  • 4. Test Software
  • Testing of the software affirms its quality. The
    QA team refers to the system requirements
    document (SRD) or the user stories to verify each
    of the functionality. Therefore, in this phase,
    the goal is to ensure a quality product and
    confirm every functionality working as expected.
  • If a bug is discovered, then the QAs reproduce
    the steps, note them, and then assign them to the
    development team. A developer fixes the bugs and
    sends them back to QA. Generally, the QA tester
    who discovered the bug also retests and verifies
    that it no longer exists. Testing is performed by
    the QAs until the software operates according to
    the business requirements and customers
    standards.
  • 5. Deploy Software
  • In the deployment phase, the team has already
    resolved all the bugs and satisfied the agreed
    specifications. Finally, the software is released
    to the production environment. It is available
    for the market so customers can use the software.
  • 6. Maintain Software
  • The software maintenance phase is the most vital
    for SDLC. It safeguards the software and
    continues to perform as per the requirements. The
    team gradually transitions from developing and
    testing the software to maintaining the software.
    Based on the different feedback from the
    development team and the end-users/customers, the
    following actions are taken

6
  • Conclusion SDLC STLC Comparison
  • SDLC and STLC have phases that extend each other.
    For example, the SDLC encompasses gathering
    requirements and testing software. The STLC
    incorporates analyzing requirements before
    creating a test plan.
  • When it comes to setting up the test environment,
    this activity can be carried out in the SDLC or
    STLC. Although essential, the QA team is not
    responsible for constructing the test
    environment. Developers generally set it up so
    testers can start execution. The following is a
    breakdown of each phase for SDLC and STLC
  • We, at Oodles, specialize in building custom
    enterprise solutions for the diverse
    industry-specific needs of our clients. Our
    development team is skilled at using open-source
    software platforms for custom ERP development
    from scratch. To learn more about our custom ERP
    development services, contact us at erp_at_oodles.io.
Write a Comment
User Comments (0)
About PowerShow.com