1 / 45

Software Quality Engineering: Functional Requirements & Release Management

Learn the differences between Software RE and QE, manage changing requirements, and understand the process of building and managing software releases. Explore examples, templates, impact analysis, and more.

carolee
Download Presentation

Software Quality Engineering: Functional Requirements & Release Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Quality Engineering Functional Requirements

  2. Software RE vs Software QE Functional Requirements Functional requirements define what system should do. Define particular behavior of the system when conditions are true.

  3. Software RE vs Software QE Functional Requirements May be calculations, technical details to achieve desired functionality. Functional requirements are captured using Use Cases.

  4. Software Quality Engineering Template for Functional Requirements

  5. Software RE vs Software QE

  6. Software RE vs Software QE Template for Functional Requirements Use cases serve as basis as connector between different phases of SDLC

  7. Software Quality Engineering Example-I: Filled Functional Requirements

  8. Software RE vs Software QE

  9. Software RE vs Software QE

  10. Software RE vs Software QE Example – I: Filled Functional Requirement Use Case # is used to make the requirements traceable

  11. Software Quality Engineering Example-II: Filled Functional Requirements

  12. Software RE vs Software QE

  13. Software RE vs Software QE

  14. Software RE vs Software QE Example – II: Filled Functional Requirement Use Case Templates are used to generate use case diagrams

  15. Software Quality Engineering Changing Requirements

  16. Software RE vs Software QE Changing Requirements Demoable software leads to WishLists or Change Requests Change Request Templates is used as appendix to manage it. Functional requirements as CR

  17. Software RE vs Software QE Changing Requirements Functional requirements as Change request have extra effort. Impact analysis is performed and to be communicated to client

  18. Software Quality Engineering What is Software Release

  19. Software RE vs Software QE What is Software Release Product development is achieved via Release. Release includes set of features, environment variables and backlog Features are divided into doable releases

  20. Software Quality Engineering How Release is build

  21. Software RE vs Software QE How Release is build Features are provided by Sales Team Environment Variable majorly includes next software version to be compatiable with product Environment variable are provided by technical team

  22. Software RE vs Software QE How Release is build Backlogs are discussed and finalized between Sales and Technical Team Each Release is a Project Each Release have tangible deadlines

  23. Software Quality Engineering Release Management

  24. Software RE vs Software QE Release Management Features are provided by Sales Team Environment Variable majorly includes next software version to be compatiable with product Environment variable are provided by technical team

  25. Software Quality Engineering What are Release Notes in General

  26. Software RE vs Software QE What are Release Notes in General Release notes are part of final build that contain of scope of particular release. Usually these are part and parcel of Software Products

  27. Software RE vs Software QE What are Release Notes in General Release notes are part of final build that contain of scope of particular release. Usually include known-issues, features-delivered and performance benchmarks QA is owner

  28. Software Quality Engineering What is Software Quality Assurance

  29. Software RE vs Software QE What is Software Quality Assurance SQA ensure that software developed is meeting the requirements with Quality SQA is on-going process SQA is part of every phase of SDLC

  30. Software Quality Engineering What is Software Requirements vs Software Quality Assurance

  31. Software RE vs Software QE What is Software Requirements vs Software Quality Assurance Requirements have to be QA approved. Test cases are written against Use Cases QA close Test case as per Use Case

  32. Software Quality Engineering Verifying Requirements

  33. Software RE vs Software QE Verifying Requirements Requirement verifications are formally , structurally achieved thorough Quality Assurance. Verification ensure a planned and documented Procedure to identify defects.

  34. Software RE vs Software QE Verifying Requirements Software Quality Assurance is not one-go process

  35. Software Quality Engineering People Expectation from Quality Engineering

  36. Software RE vs Software QE People Expectation from Quality Engineering Quality Engineering should ensure reliability and stable product. In context of software there should be no bugs or defects.

  37. Software RE vs Software QE People Expectation from Quality Engineering Software with Zero-bug count is practically not possible Expectation mismatch open lead to financial loss, clientage loss, law suits.

  38. Software Quality Engineering Quality Assurance Basics

  39. BG # 1 Quality Assurance Basics Correctness centric activities are the basis of QA. Objective is to reduce defects to minimum to ensure minimum disruption. High Priority areas should be defect free. Software Quality Assurance

  40. Software Quality Engineering QA and Defect

  41. BG # 1 QA and Defect QA and Defect are always head-to-head. Different strategies are adopted to ensure minimum damage to software system. Critical functionality should work atleast. Software Quality Assurance

  42. BG # 1 QA and Defect Defect should not impact critical working Software Quality Assurance

  43. Software Quality Engineering QA and Defect: Classification Scheme

  44. BG # 1 QA and Defect: Classification Scheme Defects can be classified into 3-Categories. Defect Prevention through Error Source Removal. Software Quality Assurance

  45. BG # 1 QA and Defect: Classification Scheme Defect Detection through fault detection removal Defect Containment Software Quality Assurance

More Related