A pdf on software testing.

1. &
QUALITY MANAGEMENT
SOFTWARE TESTING
GROUP 8
SWAGAT GOGOI
ADITYA OJHA
UTPAL KHANAL
SHIVA SHARMA
ABHIPSHA NEOG
HIYASRI DAS

2. INTRODUCTION
Performance
Reliability
Security, or
Usability
Software testing is the process of evaluating a software application or
system to identify any potential defects or errors that could negatively
impact its:
Testing involves running the software under controlled conditions and
observing its behavior, comparing its actual results with the expected
ones.

3. INTRODUCTION
Planning
Controlling
Monitoring, and
Improving
Software quality management is a set of activities and processes that
aim to ensure that software products and services meet the desired
quality standards and requirements.
It involves:
the quality of software throughout its entire lifecycle, from
requirements gathering to deployment and maintenance.

4. TAXONOMY OF SOFTWARE TESTING
Depending on the Goal:
Taxonomy is a system for classifying and organising objects according
to their traits and attributes. Taxonomy is used in software testing to
categorise various testing types based on variables like purpose,
amount of testing, test design approaches, and more.
Tests the software application's functionality through functional testing.
Non-Functional Testing Examines the software application's
performance, security, usability, and other non-functional elements.

5. User acceptance testing (UAT) determines whether the application
satisfies the needs and expectations of the user.
Regression testing verifies that the application's existing functionality
have not been impacted by changes made after the first testing.
Acceptance testing tests the software application's compliance with the
acceptance criteria.

6. Gray Box Testing: Tests the software application with partial knowledge
of its internal structure or code.
White Box Testing: Tests the software application with knowledge of its
internal structure or code.
Based on techniques for test design:
Black Box Testing: Tests the software application without knowing its
internal structure or code.

7. SOFTWARE TESTING STRATEGIES

8. SOFTWARE TESTING STRATEGIES
Integration Testing
Unit Testing
Validation Testing
System Testing
Debugging

9. QUALITY CONCEPTS
Functional quality
Structural quality
In the context of software engineering, “software quality” is the
capability of a software product to conform to requirements. It refers to
two distinct yet interconnected concepts:

10. Software testing and quality management use a variety of ideas and tenets to make sure that the
software is of the highest standard and satisfies the demands of stakeholders. This is how software
quality is defined. The following are some major quality ideas in software testing and quality
management:
Defect Prevention
Risk Management
Cost Management

11. Adhering to and implementing these principles into the software development process can
help to ensure that software is of high quality, satisfies customer requirements, and gets
released on time and within budget.
Metrics and Measurements
Continuous Improvement
Testing Automation

12. SOFTWARE QUALITY ASSURANCE
A way to assure quality in the software.
It is done by software engineer group and SQA group
Set of activities which ensure processes , procedures as well as standards
suitable for the project and implemented correctly
It works parallel to development of a software
It is a kind of an umbrella activity that is applied through the software
process

13. Prepare a SQA plan for the project.
Participate in the development of the projects software process
description.
Review software engineering activities to verify compliance with the
defined software process.
Ensure that there are no deviations in software work
Audits designated software work products to verify compliance with
those defined as part of the software process.
SOFTWARE ASSURANCE ACTIVITIES
Records any non compliance and reports to senior manager.

14. High quality software Save time and cost
BENEFITS OF SOFTWARE ASSURANCE ACTIVITIES
Better reliability No maintenance
Increase market share Improves process creation
Required more resources Need more employees
DISADVANTAGE OF SOFTWARE ASSURANCE ACTIVITIES

15. SOFTWARE REVIEWS
A Software reviews is a systematic examination of a document by one or
more people.
Software review is necessary to find and remove errors early in the
software development life cycle.
Used to verify documents such as requirements, system designs, code,
test plans and test cases.

16. To improve the productivity of the development team.
To make the testing process time and cost effective.
To make the final software with fewer defects.
To eliminate the inadequacies.
OBJECTIVES
It meets the requirements stated by the client.

17. Software Peer Review
TYPES
Software Management Review
Software Audit Reviews

18. STATISTICAL QUALITY ASSURANCE
c: Trace out each defect.
Steps Involved to correct the defects:
d: Apply Pareto Principle to all the defects.
It involves finding each defect to its underlying cause and making moves
to correct them.
a: Collect the software defects.
b: Categorize the software defects.

19. Pareto Principle
Six Sigma

20. An AI-Based Traffic
Management Software
JORSMOOTH
GROUP 8

21. INTRODUCTION
Nowadays, traffic congestion has become a significant problem
in many cities around the world, leading to increased travel
times, reduced productivity, and increased air pollution.
To solve the problem, We , at JORSMOOTH are planning to
implement AI and 3D modeling which will lead to:
Improved traffic flow Better safety
Reduced emissions: Increased efficiency
Cost-effective

22. SOFTWARE MODEL
DTA (DYNAMIC TRAFFIC ASSIGNMENT) MODEL
We have decided to go with
Dynamic Traffic Assignment (DTA) is a traffic management
software model that uses real-time data to predict traffic
patterns and optimize traffic allocation on a network of roads. It
simulates driver behavior and assigns traffic to different routes
to minimize congestion and travel time. The DTA model is useful
in situations where traffic conditions are constantly changing,
and it is used by transportation planners and traffic management
systems to optimize network performance and make real-time
adjustments to traffic flow.

23. SOFTWARE DESIGN
User interface
Privacy & Security
Decision Making
Data Accuracy
Compliance with regulations
Integration with other systems
Data Analysis
Customer's POV

24. SOFTWARE DESIGN
Requirements gathering
Architecture design
Data collection and processing
Implementing Machine Learning models
Security Design
Testing and Deployment
User Interface Design
Developer's POV

25. SOFTWARE
ARCHITECTURE

26. USER INTERFACE

27. USER INTERFACE

28. USER INTERFACE

29. SOFTWARE REQUIREMENTS
Inaccuracy of Data
Cybersecurity
System failure
Human error
Privacy concerns

30. RISKS INVOLVED
Inaccuracy of Data
Cybersecurity
System failure
Human error
Privacy concerns

31. ADVANTAGES
Improved traffic flow
Increased safety
Better resource utilization
Enhanced decision-making
Improved customer satisfaction
Cost savings in the long run

32. DISADVANTAGES
Technical complexity
Dependence on technology
Privacy concerns
Unintended consequences
Customers' resistance to adapt
Higher initial cost

33. TACKLING THE DISADVANTAGES
Dividng the various technical tasks among specialized teams
Having very strong balance between the tech and non-tech teams
Having a very strict privacy policy
Collaborating with local authorities to avoid unintended consequences
Increasing awareness through campaigns
Lower costs in the longer run

34. THANK YOU
GROUP 8