Scribd
Upload
25 views16 pages

IT314 - Software Engineering: Asim Banerjee 20 January 2011 Soft - Engg@daiict - Ac.in

The document outlines the schedule and topics for an IT314 Software Engineering course. It discusses the following: 1. The course schedule, which includes lab hours for project teams on specific days of the week. 2. Types of integration testing like top-down, bottom-up, regression, and smoke testing. 3. Types of validation testing like configuration review, alpha testing, and beta testing. 4. The objectives and types of system testing and acceptance testing. 5. Activities in the software maintenance phase like corrective and adaptive maintenance.

Uploaded by

Abhijeet
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
25 views16 pages

IT314 - Software Engineering: Asim Banerjee 20 January 2011 Soft - Engg@daiict - Ac.in

The document outlines the schedule and topics for an IT314 Software Engineering course. It discusses the following: 1. The course schedule, which includes lab hours for project teams on specific days of the week. 2. Types of integration testing like top-down, bottom-up, regression, and smoke testing. 3. Types of validation testing like configuration review, alpha testing, and beta testing. 4. The objectives and types of system testing and acceptance testing. 5. Activities in the software maintenance phase like corrective and adaptive maintenance.

Uploaded by

Abhijeet
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 16

IT314 - Software Engineering

Asim Banerjee

20th January 2011

[email protected]
Course Schedule (Existing)
• 3 lab hours per week 14:00 to 17:00 Lab004
on Monday, Tuesday, Thursday & Friday
Project Teams 1 to 5 - Thursday
Project Teams 6 to 10 - Friday
Project Teams 11 to 15 - Monday
Project Teams 16 to 19 - Tuesday

IT314 - Software Engineering 2


Integration Testing
• Modules are integrated in planned manner
• During each integration step, partially
integrated system is tested
• When ALL modules are integrated (and tested),
the system is ready for system testing
• Types of Integration testing
– Top-down integration
– Bottom-up integration
– Regression Testing
– Smoke Testing
IT314 - Software Engineering 4
Reading Assignment
• Read up on the various types of integration
testing viz.
– Top-down integration testing
– Bottom-up integration testing
– Regression Testing
– Smoke Testing
To be completed before 17:00 hrs. on
Monday, 24th January 2011.
IT314 - Software Engineering 5
Any Questions?

IT314 - Software Engineering 6


Validation Testing (1/2)
• Objective of Validation testing
– To confirm that the developed system meets the
requirements (as specified in SRS document in the
section called validation criteria)
• Both plan and procedure are designed to ensure that
– all functional requirements are satisfied.
– all behavioral characteristics are achieved
– all performance requirements are attained
– documentation is correct
– Human-engineered and other requirements are met (e.g.
transportability, compatibility error recovery,
maintainability)

IT314 - Software Engineering 7


Validation Testing (2/2)
• Types of validation testing
– Configuration review
– Alpha testing
– Beta testing

IT314 - Software Engineering 8


Reading Assignment
• Types of validation testing
– Configuration review
– Alpha testing
– Beta testing
To be completed before 17:00 hrs. on
Monday, 24th January 2011.

IT314 - Software Engineering 9


Any Questions?

IT314 - Software Engineering 10


System Testing(1/2)
• Objective of System Testing
– To confirm that the developed system meets the
requirements (as specified in SRS document)
• Carried out according to the system test plan
NOTE: System test plan is prepared during
requirements phase (include test cases and expected
results)
• Types of System testing
– Recovery testing
– Security testing
– Stress testing
– Performance testing

IT314 - Software Engineering 11


System Testing (2/2)
• Final output of the test phase:
1. Test report and
2. Tested (all test cases passed successfully) System

IT314 - Software Engineering 12


Any Questions?

IT314 - Software Engineering 13


Acceptance Testing
• Objective of Acceptance Testing
– To confirm that the developed system is
acceptable by the client as meeting his/her
requirements (as specified through the
acceptance criteria)
• Carried out according to the Acceptance test
plan using the acceptance criteria specified or
agreed upon by the client
NOTE: Acceptance criteria has also to be
signed off by the client
• Final output of the test phase:
– The client accepts the product and pays up!!!
IT314 - Software Engineering 14
Any Questions?

IT314 - Software Engineering 15


Maintenance Phase
• Maintenance phase involves performing one or more
of the following activities:
1. Corrective maintenance:
– Fixing errors not detected during the development phase
2. Adaptive maintenance:
– Improving implemented system e.g. performance
– Enhancing functionalities e.g. new requirements
– Porting software to new environment (as needed)
• Maintenance phase consumes far more effort than the
development phases (40:60)

IT314 - Software Engineering 16


Any Questions?

IT314 - Software Engineering 17

You might also like