Homework Title / No.

: _________________1________________Course Code : ____CAP609 Course Instructor : _____Supreet Kaur______ Course Tutor (if applicable) : ____________ Date of Allotment : ______31/01/2012______ Date of submission : _____9/02/2012_____ Students Roll No.______RD1004A06______ Section No. : __________D1004_________ Declaration: I declare that this assignment is my individual work. I have not copied from any other students work or from any other source except where due acknowledgment is made explicitly in the text, nor has any part been written for me by another person. Students Signature : Sarbjit Kaur Evaluators comments: _____________________________________________________________________ Marks obtained : ___________ out of ______________________ Content of Homework should start from this page only:

Q.1) How product specification helps in finding the bugs? Ans: A product specification document (PSD) is a document written by a company that defines a product they are making, or the requirements for one or more new features for a new or an existing product. A product specification document generally define the problems(Bugs/Errors) that a product (or product feature) must solve, but should avoid defining the technical solution to those problems. This distinction allows engineers to use their expertise to provide the optimal solution to the requirements defined in the product specification document. Features of Product Specification: 1)Establish the basis for agreement between the customers and the suppliers on what the software product is to do. 2)Reduce the development effort. 3)Provide a basis for estimating costs and schedules. The description of the product to be developed as given in it is a realistic basis for estimating project costs and can be used to obtain approval for or price estimates. 4)Facilitate transfer: It makes it easier to transfer the software product to new users or new machines.

5)Serve as a basis for enhancement. Because the it discusses the product. A Product Specification helps to find out the bugs. As it provides a baseline for validation and verification. Organizations can develop their validation and Verification plans much more productively from a good Product Specification. Product Specification can also be define as the software testing. Because it helps to create an analyzer techniques for the software testing. It defines the requirements, objectvies of the company, cost for the software etc. Through Product Specification the reasons behind the bugs can be solved easily, which are as: Specification of software, Design, code and other external errors. Product Specification helps to reduces the cost of bugs by finding the errors. Because in Product Specification, there requirements are defined and if the software is not fulfilling the requirements or much satisfying/providing extra features which are not defined in Product Specification then these norms can be define as bugs and Product Specification works as the great analyzer. Q.2) Waterfall model is also called as the one shot or once through model. Discuss the statement. Ans: The waterfall model is the development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential. IEEE: Standards Collection, Software Engineering, 1994 Edition, published by the Institute of Electrical and Electronic Engineers Inc.) A model of the software development process in which the constituent activities, typically a concept phase, requirements phase, design phase, implementation phase, test phase, installation and checkout phase, and operation and maintenance, are performed in that order, possibly with overlap but with little or no iteration. There are mainly five steps of water fall model which are as:

Waterfall model is also called as the one shot or once through model because when the software developers starts to develop the software it is mandatory for them to first to complete the one step then they can move to another steps and if they find some bugs after the completion of the step then they can't access or move to backward. Because Water fall model follows the joint application development (JAD) which emphasis on that once the step has been completed then there is no backward option to fix the bugs. Then they have only one option that they have to re-start from the very first step which may cause more cost. Thus Waterfall model is also called as the one shot or once through model. 3) Ques:The more you test the software more immune it becomes to your test. Justify using example. Ans: The more software testing will be done the more it immune because there are curtain testing axioms which may fulfill or not. Such as the s/w can never test completely and there is no surety that all the bugs will be fixed after testing. There is only need to test the software once a while after the development because when the s/w will be tested again and again then there is possibility that more and more bugs will be accomplished then it will increase the cost to fix the bugs. There is an example that while testing the Software for Mobile, there may occur that the s/w is fulfilling the desired needs but at some phases it may causing the low speed or low battery backup. So if the software testing will be done again and again then it will immune more. And offcourse the cost of the bug will be increases. It will also increase the work load. Q: 4. Difference between static black box testing and dynamic black box testing.

Ans: Static static black box testing: Static testing is a form of software testing where the software isn't actually used.It is generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code and/or manually reviewing the code or document to find errors. This type of testing can be used by the developer who wrote the code, in isolation. Code reviews, inspections and walkthroughs are also used. Even static testing can be automated. A static testing test suite consists of programs to be analyzed by an interpreter or a compiler that asserts the programs syntactic validity. static testing involves reviewing requirements and specifications. This is done with an eye toward completeness or appropriateness for the task at hand. This is the verification portion of Verification and Validation. Dynamic black box testing: Testing software without having an insight into the details of underlying code is dynamic black-box testing. It's dynamic because the program is runningyou're using it as a customer would. And, it's black-box because you're testing it without knowing exactly how it workswith blinders on. Once you know the ins and outs of the software you're about to test, your next step is to start defining the test cases. Test cases are the specific inputs that you'll try and the procedures that you'll follow when you test the software. Q: 5). What do you mean by equivalence partitioning? Why is it important? Ans: Equivalence partitioning is a software testing technique that divides the input data of a software unit into partitions of data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once. This technique tries to define test cases that uncover classes of errors, thereby reducing the total number of test cases that must be developed. The testing theory related to equivalence partitioning says that only one test case of each partition is needed to evaluate the behaviour of the program for the related partition. In other words it is sufficient to select one test case out of each partition to check the behaviour of the program. To use more or even all test cases of a partition will not find new faults in the program. The values within one partition are considered to be "equivalent". Thus the number of test cases can be reduced considerably. Equivalence partitioning is not a stand alone method to determine test cases. It has to be supplemented by boundary value analysis.