software engineering Mid-2 assignment quetions with Answers

1.  explain strategies approach to software testing?

• STRATEGIC APPROACH

• Testing is a set of activities that can be planned in advance and conducted systematically.

• Many strategies exist, all follow these generic characteristics:

• To perform testing, a software team should conduct effective formal technical reviews. This eliminates errors before testing commences.

• Testing begins at the component level and works outward toward the integration of the entire computer-based system.

• Different testing techniques are appropriate at different points of time.

• Testing is conducted by the developer of the software and (for large projects) an independent test group.

• Testing and debugging are different activities, but debugging must be accommodated in any testing strategy.

2. VERIFICATION VS. VALIDATION

Verification refers to the set of activities the ensures that software correctly implements a specific function. Validation refers to a different set of activities that ensures that the software that has been built is traceable to customer requirements.

 3.  ORGANIZING TESTING

 “ Optimism is the occupational hazard of programming; testing is the treatment.” Kent Beck “ The first mistake that people make is thinking that the testing team is responsible for assuring quality”

2. Describe the test strategies of conventional software?

•Unit testing

–Exercises specific paths in a component's control structure to

 ensure complete coverage and maximum error detection

–Components are then assembled and integrated

•Integration testing

–Focuses on inputs and outputs, and how well the components

 fit together and work together

•Validation testing

–Provides final assurance that

 the software meets all

 functional, behavioral, and 

performance requirements

•System testing

–Verifies that all system 

elements (software, 

hardware,

 people, databases) mesh properly and that overall system

 function and performance is achieved.

3.Define Smoke Testing?

Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing.

The term ‘Smoke Testing’ is came from the hardware testing, in the hardware testing initial pass is done to check if it did not catch the fire or smoked in the initial switch on.

Prior to start Smoke testing few test cases need to created once to use for smoke testing. These test cases are executed prior to start actual testing to check critical functionalities of the program is working fine. This set of test cases written such a way that all functionality is verified but not in deep.

Advantages of Smoke testing: 

It helps to find issues introduced in integration of modules. It helps to find issues in the early phase of testing. It helps to get confidence to tester that fixes in the previous builds not breaking major features (off course, only features exercised by smoke testing).

4.Design evaluation Process ?

Refer Unit-4 All In one

5.Explain various Product Metrics?

1. ‰ Software quality
2. ‰ Metrics for the analysis model
3. ‰ Metrics Metrics for the design model
4. ‰ Metrics for source code
5. ‰ Metrics for testing
6. ‰ Metrics for maintenance

What is Product Metrics?

Ans: They focus on the quality of deliverables. Product metrics are combined across several projects to produce process metrics.
Metrics for the product: