Scribd Logo
Upload

Welcome to Scribd!

  • Release Mangement Process

    Uploaded by

    api-3756186
    16 views1 page
    The document outlines the release process for a software project. It involves development, testing, and deployment stages. In development, code is written, checked in, and built. Testing then executes test cases on the build to certify it. If bugs are found, they are logged and prioritized. The certified build is then deployed to development, system integration, and user acceptance testing environments. Once user acceptance testing is complete and any final bugs addressed, the build is deployed to production.

    Original Description:

    Original Title

    ReleaseMangementProcess

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document outlines the release process for a software project. It involves development, testing, and deployment stages. In development, code is written, checked in, and built. Testing then executes test cases on the build to certify it. If bugs are found, they are logged and prioritized. The certified build is then deployed to development, system integration, and user acceptance testing environments. Once user acceptance testing is complete and any final bugs addressed, the build is deployed to production.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    16 views1 page

    Release Mangement Process

    Uploaded by

    api-3756186
    The document outlines the release process for a software project. It involves development, testing, and deployment stages. In development, code is written, checked in, and built. Testing then executes test cases on the build to certify it. If bugs are found, they are logged and prioritized. The certified build is then deployed to development, system integration, and user acceptance testing environments. Once user acceptance testing is complete and any final bugs addressed, the build is deployed to production.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Release

    Check Priority
    Development Manager Testing Manager
    Check
    Severity

    DEVELOPER TESTER

    Release Plan & Release Notes Release Plan & Release Notes

    Check Out
    Planning & Estimation Planning & Estimation

    Design In Requirement Tracker, using


    Req. ID, trace requirement
    details in Release Notes
    Code Cut Date
    (Coding & Check in)

    Code Freeze Date Preparing Test Cases &


    (Reviewed & Generate Build) Reviewing Test Cases

    Build Generation &


    Certified by DEVELOPER

    Deployed in DIT Servers DIT Start Date

    Execute Test Cases & Certify Build


    (Smoke, Functionality, Retesting,
    BUG TRACKING TOOL and Regression)
    (PRIORITY BY TESTING)
    Bug Identified/Not Certified
    Test
    Case
    Bug Not Identified or
    Certified

    DIT Close Date

    SIT Start Date


    Certified Build Deployed in SIT Servers

    Identifying & Testing Missed Bugs


    Using Build Notes & Whole

    Bug Identified/Not Certified


    Test
    Case
    Bug Not Identified or
    Certified

    SIT Close Date

    UAT Start Date (CLIENT)


    Certified Build Deployed in UAT Servers

    Bug Identified/Not Certified


    UATesti
    ng
    UAT CertifiedBug Not Identified or
    Build
    Deployed in ProductionDate
    UAT (Client) Close
    Certified
    Unit

    You might also like