Scribd Logo
Upload

Welcome to Scribd!

  • 18 views

    Group 10 Testing 4th Presentation

    Uploaded by

    mahfuzkanon8

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Group 10 Testing 4th Presentation

    Uploaded by

    mahfuzkanon8
    18 views19 pages

    Original Title

    Group 10 Testing 4th Presentation(2)

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    18 views19 pages

    Group 10 Testing 4th Presentation

    Uploaded by

    mahfuzkanon8

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 19

    Presentation Title

    Sofware Requriments Specification

    Project Name
    Inventory Management System
    Proffessor : Xiaoqiang Yan ( 闫小强）
    Our Team Name
    Blueberry Pi

    Group Members :
    1. Md.Mahafuz Rahman Kutial 马夫子 117
    2. Litunjera Lima 丽马 128
    3. Rahim Shah 127
    Table of Contents
    1. Introduction
    2. Overview
    3. White Box Testing
    4. Black Box Testing
    5. Basis Path Testing
    6. Use case Testing
    7.Security Testing
    8. User Acceptance Testing (UAT)
    9. Conclusion
    1.Introduction
    Software testing is a crucial phase in the development lifecycle of any
    software, including an Inventory Management System (IMS). The
    primary purpose of testing is to ensure that the IMS functions as
    intended, meets the specified requirements, and is free of defects or
    errors that could compromise its performance. A well-executed testing
    process helps identify and rectify issues before the system is deployed,
    ensuring a reliable and efficient solution for managing inventory.
    2.Overview
    Software testing for an Inventory Management System (IMS) is crucial
    to ensure that the system functions as intended, meets user
    requirements, and is free from critical defects. Here is an overview of
    the key aspects of software testing for an Inventory Management
    System.
    3.White Box Testing
    White box testing is a method of testing software that examines the
    internal structure and workings of an application, as opposed to its
    functionality. The primary goal of white box testing is to focus on the
    flow of inputs and outputs through the software and strengthening the
    security of the software.

    Input Output
    4.Black Box Testing
    Black box testing is a method of software testing in which the internal
    structure, design, or implementation details of the system being tested
    are not known to the tester. Instead, the tester focuses on testing the
    functionality of the system based on its specifications.

    Input Output
    5.Basis Path Testing
    Basis Path Testing is a white box testing technique based on the control structure
    of a program or a module. To apply basis path testing to an Inventory
    Management System (IMS), you'll need to follow these steps:

    1.Understand the Control Flow Graph


    2. Identify Independent Paths
    3. Define Test Cases
    4. Execute Test Cases
    5. Analyze Results
    6.Use Case Testing
    Authentication testing
    ○ Required field.
    ○ Input type should be email and password type.
    ○ Should be a valid email, otherwise
    a validation message will be shown.
    Daseboard
    After successfully signing in, users will see their dashboard. In the dashboard, some basic
    information will be shown here like Total Brand, Total Products, Total Purchase (Current
    Month), Total Sales (Current Month) etc.
    Assign Role Testing
    We can assign users multiple roles. To assign roles, click the Roles button of the
    corresponding user row. A popup window will show all roles with a checkbox. Select
    roles which you want to assign the user and click on the Update button.
    Creat New Role Testing
    Page will be redirected to create page. Enter the role name and click on the submit button.
    Assign Access Testing
    Select the checkboxes which you want to give access to and click on the Update button.
    Selected accesses will be assigned to the role.
    Category Summary Testing
    ● Code ● Description
    ○ Required Field. ○ Optional Field.
    ○ Unique Field.
    ○ Must be 4 characters. ● Activity Status
    ● Name ○ Toggle Switch (Active/Inactive)
    ○ Required Field.
    ○ Unique Field.
    ○ Minimum length 2 and
    maximum length 50.
    Product Management Testing
    Page will be redirected to create page. Select category, brand, name and description click
    on the submit button.
    7.Security Testing
    Validate the security mechanisms in place to protect sensitive inventory
    data.

    Test user authentication and authorization processes to ensure that only


    authorized personnel can access and modify data.

    Identify and address potential vulnerabilities that could lead to data


    breaches or unauthorized access.
    8.User Acceptance Testing (UAT)
    User Acceptance Testing (UAT) is a crucial phase in the development
    and implementation of any software system, including an inventory
    management system.
    Summary of Test Results:
    9.Conclusion
    The “Inventory Management System” on General Store will help the store
    owner to keep a record of all the sale-purchase related activities in the shop .

    This shall also be beneficial to the customers as it shall provide them with
    the best service possible .

    The store employees will be benefited by its accuracy and stock details.
    Thank you

    You might also like