Intro To Se Week4
Intro To Se Week4
Process
Training Team
What Happened?
• NASA’s spacecraft crashed into Mars because one engineering team used metric units,
while another used imperial units.
Impact:
Root Cause:
What Happened?
Knight Capital, a major financial services firm, deployed a new software update to its
high-frequency trading system. However, due to miscommunication between teams, a
crucial part of the old code was left running.
Impact:
• The system started making unintended trades, causing Knight Capital to lose $440
million in 45 minutes.
Root Cause:
• Poor internal communication between the deployment team and the development
team.
Causes:
Solution:
Causes:
Solution:
Causes:
Solution:
• pip (Python)
1.Requirement Validation
1. Ensure that business and technical teams have agreed on the scope.
2.Code Review
1. Peer review by developers to check for coding standards & security issues.
2. Example: Google uses Gerrit for code reviews to maintain high coding
standards in Android and Search projects.
IT Mustakbil Training Program 18
Approval Process Before Final Deployment
Standard Approval Process
1. Requirement Validation
1. Ensure that business and technical teams have agreed on the scope.
2. Code Review
1. Peer review by developers to check for coding standards & security issues.
2. Example: Google uses Gerrit for code reviews to maintain high coding
standards in Android and Search projects.
IT Mustakbil Training Program 19
Approval Process Before Final Deployment
Before deploying software to production, it must go through:
3. Testing Stages
4. Example: Financial apps like PayPal undergo strict PCI DSS audits before
deployment.
IT Mustakbil Training Program 20
Approval Process Before Final Deployment
Before deploying software to production, it must go through:
2. Example: Apple beta releases iOS updates to a small group of users before the final launch.
4. Example: Netflix has "war rooms" where teams assess potential risks before deploying
major changes.
7. Deployment in Production
5. Deployment strategies:
1.Black box Testing: Testing in which the tester doesn’t have access to the source
code of the software and is conducted at the software interface without any concern
with the internal logical structure of the software known as black-box testing.
2.White box Testing: Testing in which the tester is aware of the internal workings of
the product, has access to its source code, and is conducted by making sure that all
internal operations are performed according to the specifications is known as white
box testing.
3.Grey Box Testing: Testing in which the testers should have knowledge of
implementation, however, they need not be experts.
2.Integration Testing: It is a level of the software testing process where individual units are combined and
tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated
units.
3.System Testing: It is a level of the software testing process where a complete, integrated system/software
is tested. The purpose of this test is to evaluate the system’s compliance with the specified requirements.
4.Acceptance Testing: It is a level of the software testing process where a system is tested for acceptability.
The purpose of this test is to evaluate the system’s compliance with the business requirements and assess
whether it is acceptable for delivery.
Unit Testing
•Responsibility: Developers.
Integration Testing
✅ Tests the complete, integrated system to verify if it meets functional and non-functional
requirements.
✅ Includes UI testing, security testing, performance testing, and end-to-end user flow
verification.
Example:
•Tests the entire ride-booking flow from searching for a ride to payment confirmation.
•System Test: Ensures that location services, driver allocation, fare calculation, and push
notifications work seamlessly.
•.