Scribd Logo
Upload

Welcome to Scribd!

  • Software Change Control

    Uploaded by

    Eric Wientzek
    29 views2 pages
    The document outlines the process for testing and managing changes in software development projects. It involves testing by various stakeholders including end users, QA testers, and developers. If issues are found, a change management process begins which includes a business review, feasibility study, and decision on whether to implement the change. If approved, development is impacted, issues are addressed, and additional testing is performed to manage the implementation.

    Original Description:

    my software develoement guidlines.

    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 process for testing and managing changes in software development projects. It involves testing by various stakeholders including end users, QA testers, and developers. If issues are found, a change management process begins which includes a business review, feasibility study, and decision on whether to implement the change. If approved, development is impacted, issues are addressed, and additional testing is performed to manage the implementation.

    Copyright:

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

    Software Change Control

    Uploaded by

    Eric Wientzek
    The document outlines the process for testing and managing changes in software development projects. It involves testing by various stakeholders including end users, QA testers, and developers. If issues are found, a change management process begins which includes a business review, feasibility study, and decision on whether to implement the change. If approved, development is impacted, issues are addressed, and additional testing is performed to manage the implementation.

    Copyright:

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

    Testing and Managing change in Software Development Projects

    Test and Change procedures are necessary for large projects. As required, involve all affected team
    members such as
    • Project Steering committee members or Upper Management
    • Project change board members
    • Business experts
    • End User testers
    • QA testers
    • Development team members
    • Project managers
    • Business Clients

    Developer Code
    Time Design
    Effort Impacted

    Chang Client Says Repercussion


    e YES s
    Other
    Features
    Impacted

    Test Stage
    1. UAT or QA testing
    2. Report issue
    3. Verify issue
    4. Document issue
    5. Manage change

    Manage Change Stage


    1. business review
    2. business adjustment
    3. feasibility study
    4. Decision to proceed.

    Implement Change Stage


    1. Development repercussions and feedback
    2. verify issues
    3. documents issues
    4. manage issues.

    Page 1 06/05/2010
    Testing and Managing change in Software Development Projects
    Manage implementation issues Stage
    1. Reduce functionality
    2. Add or remove features
    3. Add effort.
    4. Test

    Page 2 06/05/2010

    You might also like