1.

_________ categories of data will be collected during testing. a. Two b. Three c. Four d. Five ANSWER : c 2. ______________ is normally a reverse of the test development process. In other words, it begins at the very lowest level and the results are rolled up to the highest levels. a. Conducting testing b. Resuming testing c. Acceptance testing d. None of the above ANSWER : a 3. Which one is called as most common test report ? a. Test Summary Report b. Check List c. Spreadsheet d. Cause-Effect Graphing ANSWER : c 4. Verification that the process deliverables/ phases are meeting the users true needs is called as a. Inspections b. Reviews c. Acceptance testing d. Acceptance criteria ANSWER : b 5. _____________ the reporting process is very important because software tools are being upgraded, and manual supporting activities sometimes break down. a. Analyzing b. Monitoring c. Both A & B d. None of the above ANSWER : b 6. _______________ report provides information related to a specific project component. a. Individual Project Status Report b. Major Project Status Report c. Both A & B d. None of the Above ANSWER : b 7. ________________ report provides general information about all projects. a. Individual Project Status Report b. Major Project Status Report c. Both A & B d. None of the Above

ANSWER : d 8. The Project Status Report contains the project activities information and give a history of the project over a 16-month period. a. True b. False ANSWER : a 9. The test reports are for use by the testers, the test manager, and the software development team. a. True b. False ANSWER : a 10. _________ is a risk-oriented activity in which resources should be expended to minimize the major risks. a. Testing b. Development c. Quality Control d. Quality Assurance ANSWER : a 12. _______________ measure the characteristics of the documentation and code. a. Process metric b. Product metric c. Software quality metric d. Software metric ANSWER : b 1. What is the meaning of COSO ? a. Common Sponsoring Organizations b. Committee Of Sponsoring Organizations c. Committee Of Standard Organizations d. Common Standard Organization e. None of the above ANSWER : b 2. Which one is not key term used in internal control and security a. Threat b. Risk Control c. Vulnerability d. Exposure e. None ANSWER : c 3. Management is not responsible for an organization internal control system a. True b. False ANSWER : b

2.

4. Who is ultimate responsible for the internal control system a. CEO b. Project Manager c. Technical Manager d. Developer e. Tester ANSWER : a 5. Who will provide important oversight to the internal control system a. Board of Directors b. Audit Committee c. Accounting Officers d. Financial Officers e. both a & b f. both c & d ANSWER : e 6. The sole purpose of the Risk Control is to avoid risk a. True b. False ANSWER : b 7. Management controls involves limiting access to computer resources a. True b. False ANSWER : a 8. Software developed by contractors who are not part of the organization is referred to as in sourcing organizations a. True b. False ANSWER : b 9. Which one is not tester responsibilities ? a. Assure the process for contracting software is adequate b. Review the adequacy of the contractors test plan c. Perform acceptance testing on the software d. Assure the ongoing operation and maintenance of the contracted software e. None of the above ANSWER : a 10. The software tester may or may not be involved in the actual acceptance testing a. True b. False ANSWER : a 11. In the client systems, testing should focus on performance and compatibility

a. True b. False ANSWER : b 12. A database access applications typically consists of following elements except a. User Interface code b. Business login code c. Data-access service code d. Data Driven code ANSWER : d 13. Wireless technologies represent a rapidly emerging area of growth and importance for providing everpresent access to the internet and email. a. True b. False ANSWER : a 14. Acceptance testing involves procedures for identifying acceptance criteria for interim life cycle products and for accepting them. a. True b. False ANSWER : a 15. Acceptance testing is designed whether or not the software is fit for the user to use. The concept of fit is important in both design and testing. There are four components of fit. a. True b. False ANSWER : a 16. Acceptance testing occurs only at the end point of the development process; it should be an ongoing activity that test both interim and final products. a. True b. False ANSWER : b 17. Acceptance requirement that a system must meet can be divided into ________ categories. a. Two b. Three c. Four d. Five ANSWER : c 18. _______ categories of testing techniques can be used in acceptance testing. a. Two b. Three c. Four d. Five

ANSWER : a 19. _____________ define the objectives of the acceptance activities and a plan for meeting them. a. Project Manager b. IT Manager c. Acceptance Manager d. ICO ANSWER : c 20. Software Acceptance testing is the last opportunity for the user to examine the software for functional, interface, performance, and quality features prior to the final acceptance review. a. True b. False ANSWER : a 1 : With thorough testing it is possible to remove all defects from a program prior to delivery to the customer. a. True b. False ANSWER : b 2 : Which of the following are characteristics of testable software ? a. observability b. simplicity c. stability d. all of the above ANSWER : d 3 : The testing technique that requires devising test cases to demonstrate that each program function is operational is called a. black-box testing b. glass-box testing c. grey-box testing d. white-box testing ANSWER : a 4 : The testing technique that requires devising test cases to exercise the internal logic of a software module is called a. behavioral testing b. black-box testing c. grey-box testing d. white-box testing ANSWER : d 5 : What types of errors are missed by black-box testing and can be uncovered by white-box testing ? a. behavioral errors b. logic errors c. performance errors d. typographical errors e. both b and d

3.

ANSWER : e 6 : Program flow graphs are identical to program flowcharts. a. True b. False ANSWER : b 7 : The cyclomatic complexity metric provides the designer with information regarding the number of a. cycles in the program b. errors in the program c. independent logic paths in the program d. statements in the program ANSWER : c 8 : The cyclomatic complexity of a program can be computed directly from a PDL representation of an algorithm without drawing a program flow graph. a. True b. False ANSWER : a 9 : Condition testing is a control structure testing technique where the criteria used to design test cases is that they a. rely on basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs ANSWER : b 10 : Data flow testing is a control structure testing technique where the criteria used to design test cases is that they a. rely on basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs ANSWER : c 11 : Loop testing is a control structure testing technique where the criteria used to design test cases is that they a. rely basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs ANSWER : d 12 : Black-box testing attempts to find errors in which of the following categories a. incorrect or missing functions b. interface errors c. performance errors d. all of the above e. none of the above

ANSWER : d 13 : Graph-based testing methods can only be used for object-oriented systems a. True b. False ANSWER : b 14 : Equivalence testing divides the input domain into classes of data from which test cases can be derived to reduce the total number of test cases that must be developed. a. True b. False ANSWER : a 15 : Boundary value analysis can only be used to do white-box testing. a. True b. False ANSWER : b 16 : Comparison testing is typically done to test two competing products as part of customer market analysis prior to product release. a. True b. False ANSWER : b 17 : Orthogonal array testing enables the test designer to maximize the coverage of the test cases devised for relatively small input domains. a. True b. False ANSWER : a 18 : Test case design "in the small" for OO software is driven by the algorithmic detail of the individual operations. a. True b. False ANSWER : a 19 : Encapsulation of attributes and operations inside objects makes it easy to obtain object state information during testing. a. True b. False ANSWER : b 20 : Use-cases can provide useful input into the design of black-box and state-based tests of OO software. a. True b. False

ANSWER : a 21 : Fault-based testing is best reserved for a. conventional software testing b. operations and classes that are critical or suspect c. use-case validation d. white-box testing of operator algorithms ANSWER : b 22 : Testing OO class operations is made more difficult by a. encapsulation b. inheritance c. polymorphism d. both b and c ANSWER : d 23 : Scenario-based testing a. concentrates on actor and software interaction b. misses errors in specifications c. misses errors in subsystem interactions d. both a and b ANSWER : a 24 : Deep structure testing is not designed to a. examine object behaviors b. exercise communication mechanisms c. exercise object dependencies d. exercise structure observable by the user ANSWER : d 25 : Random order tests are conducted to exercise different class instance life histories. a. True b. False ANSWER : a 26 : Which of these techniques is not useful for partition testing at the class level a. attribute-based partitioning b. category-based partitioning c. equivalence class partitioning d. state-based partitioning ANSWER : c 27 : Multiple class testing is too complex to be tested using random test cases. a. True b. False ANSWER : b 28 : Tests derived from behavioral class models should be based on the

a. data flowdiagram b. object-relation diagram c. state diagram d. use-case diagram ANSWER : c 29 : Client/server architectures cannot be properly tested because network load is highly variable. a. True b. False ANSWER : b 30 : Real-time applications add a new and potentially difficult element to the testing mix a. performance b. reliability c. security d. time ANSWER : d

In software quality assurance work there is no difference between software verification and software validation. True A) False B)

2
The best reason for using Independent software test teams is that software developers do not need to do any testing A) a test team will test the software more thoroughly B) testers do not get involved with the project until testing begins C) arguments between developers and testers are reduced D)

3
What is the normal order of activities in which traditional software testing is organized? a. integration testing b. system testing c. unit testing d.validation testing a, d, c, b A) b, d, a, c B) c, a, d, b C) d, b, c, a D)

4
Class testing of object-oriented software is equivalent to unit testing for traditional software. True A) False B)

5
By collecting software metrics and making use of existing software reliability models it is possible to develop meaningful guidelines for determining when software testing is finished. True A) False B)

6
Which of the following strategic issues needs to be addressed in a successful software testing process? conduct formal technical reviews prior to testing A) specify requirements in a quantifiable manner B) use independent test teams C) wait till code is written prior to writing the test plan D) both a and b E)

7
Which of the following need to be assessed during unit testing? algorithmic performance A) code stability B) error handling C) execution paths D) both c and d E)

8
Drivers and stubs are not needed for unit testing because the modules are tested independently of one another. True A) False B)

9
Top-down integration testing has as it's major advantage(s) that low level modules never need testing A) major decision points are tested early

B) no drivers need to be written C) no stubs need to be written D) both b and c E)

10
Bottom-up integration testing has as it's major advantage(s) that major decision points are tested early A) no drivers need to be written B) no stubs need to be written C) regression testing is not required D)

11
Regression testing should be a normal part of integration testing because as a new module is added to the system new control logic is invoked A) data flow paths are established B) drivers require testing C) all of the above D) both a and b E)

12
Smoke testing might best be described as bulletproofing shrink-wrapped software A) rolling integration testing B) testing that hides implementation errors C) unit testing for small programs D)

13
When testing object-oriented software it is important to test each class operation separately as part of the unit testing process. True A) False B)

14
The OO testing integration strategy involves testing

groups of classes that collaborate or communicate in some way A) single operations as they are added to the evolving class implementation B) operator programs derived from use-case scenarios C) none of the above D)

15
The focus of validation testing is to uncover places that a user will be able to observe failure of the software to conform to its requirements. True A) False B)

16
Software validation is achieved through a series of tests performed by the user once the software is deployed in his or her work environment. True A) False B)

17
Configuration reviews are not needed if regression testing has been rigorously applied during software integration. True A) False B)

18
Acceptance tests are normally conducted by the developer A) end users B) test team C) systems engineers D)

19
Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that software is able to continue execution without interruption. True A) False B)

20
Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration. True A)

False B)

21
Stress testing examines the pressures placed on the user during system use in extreme environments. True A) False B)

22
Performance testing is only important for real-time or embedded systems. True A) False B)

23
Debugging is not testing, but always occurs as a consequence of testing. True A) False B)

24
Which of the following is an approach to debugging? backtracking A) brute force B) cause elimination C) code restructuring D) a, b, and c E)

1. What is Software Testing? 2. Why is Software Testing Important? 3. Why start testing Early? 4. Test Design Techniques Black Box Testing Methods of Black box Testing Equivalence Class Partitioning Simplified

White Box Testing & its methods / techniques Gray Box testing

4.1 Software Testing Techniques

4.2 Test Design Techniques 5. Art of Test Case Writing 6. Fault, Error & Failure 7. Unscripted Testing Techniques/Approaches 8. V-model is the basis of structured testing 9.1 V Model to W Model | W Model in SDLC Simplified 10. The Testing Mindset 11. Practical interview questions on Software Testing 12. Concept of Complete Testing | Exhaustive testing i... 13. Testing Limitations 14. How and When Testing Starts

15. Requirement Specification document Review Guidelin... 16. Role of a tester in defect prevention and defect d... 17. How and When Testing Starts - A Complete Testing Process.
1. What is the MAIN benefit of designing tests early in the life cycle? It helps prevent defects from being introduced into the code. 2. What is risk-based testing? Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first. 3. A wholesaler sells printer cartridges. The minimum order quantity is 5. There is a 20% discount for orders of 100 or more printer cartridges. You have been asked to prepare test cases using various values for the number of printer cartridges ordered. Which of the following groups contain three test inputs that would be generated using Boundary Value Analysis? 4, 5, 99

4. What is the KEY difference between preventative and reactive approaches to testing? Preventative tests are designed early; reactive tests are designed after the software has been produced. 5. What is the purpose of exit criteria? To define when a test level is complete. 6. What determines the level of risk? The likelihood of an adverse event and the impact of the event 7. When is used Decision table testing? Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the

same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced. Learn More About Decision Table Testing Technique in the Video Tutorial here

8. What is the MAIN objective when reviewing a software deliverable? To identify defects in any software work product. 9. Which of the following defines the expected results of a test? Test case specification or test design specification. Test case specification. 10. Which is a benefit of test independence? It avoids author bias in defining effective tests. 11. As part of which test process do you determine the exit criteria? Test planning. 12. What is beta testing? Testing performed by potential customers at their own locations. 13. Given the following fragment of code, how many tests are required for 100% decision coverage? if width > length then biggest_dimension = width if height > width then biggest_dimension = height end_if else biggest_dimension = length if height > length then biggest_dimension = height end_if end_if

4 14. You have designed test cases to provide 100% statement and 100% decision coverage for the following fragment of code. if width > length then biggest_dimension = width else biggest_dimension =

length end_if The following has been added to the bottom of the code fragment above. print "Biggest dimension is " & biggest_dimension print "Width: " & width print "Length: " & length How many more test cases are required? None, existing test cases can be used. 15. Rapid Application Development ? Rapid Application Development (RAD) is formally a parallel development of functions and subsequent integration. Components/functions are developed in parallel as if they were mini projects, the developments are time-boxed, delivered, and then assembled into a working prototype. This can very quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements. Rapid change and development of the product is possible using this methodology. However the product specification will need to be developed for the product at some point, and the project will need to be placed under more formal controls prior to going into production. 16. What is the difference between Testing Techniques and Testing Tools? Testing technique: Is a process for ensuring that some aspects of the application system or unit functions properly there may be few techniques but many tools. Testing Tools: Is a vehicle for performing a test process. The tool is a resource to the tester, but itself is insufficient to conduct testing Learn More About Testing Tools here 17. We use the output of the requirement analysis, the requirement specification as the input for writing User Acceptance Test Cases 18. Repeated Testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component: Regression Testing 19. What is component testing ? Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are separately testable. Component testing may be done in isolation from the rest of the system depend-ing on the context of the development life cycle and the system. Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components in a simple manner. A stub is called from the software component to be tested; a driver calls a component to be tested. 20. What is functional system testing ? Testing the end to end functionality of the system as a whole. 21. What is the benefits of Independent Testing Independent testers see other and different defects and are unbiased.

22. In a REACTIVE approach to testing when would you expect the bulk of the test design work to be begun? After the software or system has been produced. 23. What are the different Methodologies in Agile Development Model? There are currently seven different Agile methodologies that I am aware of: Extreme Programming (XP) Scrum Lean Software Development Feature-Driven Development Agile Unified Process Crystal Dynamic Systems Development Model (DSDM) 24. Which activity in the fundamental test process includes evaluation of the testability of the requirements and system? A Test analysis and design. 25. What is typically the MOST important reason to use risk to drive testing efforts? Because testing everything is not feasible. 26. Which is the MOST important advantage of independence in testing? An independent tester may be more effective at finding defects missed by the person who wrote the software. 27. Which of the following are valid objectives for incident reports? i. Provide developers and other parties with feedback about the problem to enable identification, isolation and correction as necessary. ii. Provide ideas for test process improvement. iii. Provide a vehicle for assessing tester competence. iv. Provide testers with a means of tracking the quality of the system under test. i. Provide developers and other parties with feedback about the problem to enable identification, isolation and correction as necessary, ii.Provide ideas for test process improvement, iv.Provide testers with a means of tracking the quality of the system under test

28. Consider the following techniques. Which are static and which are dynamic techniques? i. Equivalence Partitioning. ii. Use Case Testing. iii.Data Flow Analysis. iv.Exploratory Testing. v. Decision Testing. vi. Inspections. Data Flow Analysis and Inspections are static, Equivalence Partitioning, Use Case Testing, Exploratory Testing and Decision Testing are dynamic. 29. Why are static testing and dynamic testing described as complementary? Because they share the aim of identifying defects but differ in the types of defect they find. 30. What are the phases of a formal review ? In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process consists of six main steps: Planning Kick-off Preparation Review meeting Rework Follow-up.

31. What is the role of moderator in review process? The moderator (or review leader) leads the review process. He or she deter-mines, in co-operation with the author, the type of review, approach and the composition of the review team. The moderator performs the entry check and the follow-up on the rework, in order to control the quality of the input and output of the review process. The moderator also schedules the meeting, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions and stores the data that is collected. Learn More About Review process in Video Tutorial here

32. What is an equivalence partition (also known as an equivalence class)? An input or output range of values such that only one value in the range becomes a test case. 33. When should configuration management procedures be implemented? During test planning. 34. A Type of functional Testing, which investigates the functions relating to detection of threats, such as virus from malicious outsiders. Security Testing 35. Testing where in we subject the target of the test , to varying workloads to measure and evaluate the performance behaviors and ability of the target and of the test to continue to function properly under these different workloads. Load Testing 36. Testing activity which is performed to expose defects in the interfaces and in the interaction between integrated components is: Integration Level Testing 37. What are the Structure-based (white-box) testing techniques ? Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases. They are com-monly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works. For example, a structural technique may be concerned with exercising loops in the software. Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the func-tionality of the software. 38. When should be performed Regression testing ? After the software has changed or when the environment has changed 39. When should testing be stopped? It depends on the risks for the system being tested 40. What is the purpose of a test completion criterion? To determine when to stop testing 41. What can static analysis NOT find? For example memory leaks 42. What is the difference between re-testing and regression testing? Re-testing ensures the original fault has been removed; regression testing looks for unexpected sideeffects 43. What are the Experience-based testing techniques ? In experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases. The experience of both technical and business people is important, as they

bring different perspectives to the test analysis and design process. Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing. 44. What type of review requires formal entry and exit criteria, including metrics? Inspection 45. Could reviews or inspections be considered part of testing? Yes, because both help detect faults and improve quality 46. An input field takes the year of birth between 1900 and 2004 What are the boundary values for testing this field ? 1899,1900,2004,2005 47. Which of the following tools would be involved in the automation of regression test? a. Data tester b. Boundary tester c. Capture/Playback d. Output comparator. d. Output comparator 48. To test a function,what has to write a programmer, which calls the function to be tested and passes it test data. Driver 49. What is the one Key reason why developers have difficulty testing their own work? Lack of Objectivity 50.How much testing is enough? The answer depends on the risk for your industry, contract and special requirements. 51. When should testing be stopped? It depends on the risks for the system being tested. 52. Which of the following is the main purpose of the integration strategy for integration testing in the small? To specify which modules to combine when, and how many at once. 53. What is the purpose of a test completion criterion? To determine when to stop testing 54. Given the following code, which statement is true about the minimum number of test cases required for full statement and branch coverage? Read p Read q IF p+q> 100 THEN Print "Large" ENDIF IF p > 50 THEN Print "p Large"

ENDIF 1 test for statement coverage, 2 for branch coverage 55. What is the difference between re-testing and regression testing? Re-testing ensures the original fault has been removed; regression testing looks for unexpected sideeffects. 56. Which review is normally used to evaluate a product to determine its suitability for intended use and to identify discrepancies? Technical Review. 57. Why we use decision tables?. The techniques of equivalence partitioning and boundary value analysis are often applied to specific situations or inputs. However, if different combinations of inputs result in different actions being taken, this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend to be more focused on the user interface. The other two specification-based tech-niques, decision tables and state transition testing are more focused on business logic or business rules. A decision table is a good way to deal with combinations of things (e.g. inputs). This technique is sometimes also referred to as a 'cause-effect' table. The reason for this is that there is an associated logic diagramming technique called 'cause-effect graphing' which was sometimes used to help derive the decision table 58. Faults found should be originally documented by who? By testers. 59. Which is the current formal world-wide recognized documentation standard? There isnt one. 60. Which of the following is the review participant who has created the item to be reviewed? Author 61. A number of critical bugs are fixed in software. All the bugs are in one module, related to reports. The test manager decides to do regression testing only on the reports module. Regression testing should be done on other modules as well because fixing one module may affect other modules. 62. Why does the boundary value analysis provide good test cases? Because errors are frequently made during programming of the different cases near the edges of the range of values. 63. What makes an inspection different from other review types? It is led by a trained leader, uses formal entry and exit criteria and checklists. 64. Why can be tester dependent on configuration management?

Because configuration management assures that we know the exact version of the testware and the test object. 65. What is a V-Model ? A software development model that illustrates how testing activities integrate with software development phases 66. What is maintenance testing? Triggered by modifications, migration or retirement of existing software 67. What is test coverage? Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in some other way, e.g. using specification-based techniques). Wherever we can count things and can tell whether or not each of those things has been tested by some test, then we can measure coverage. 68. Why is incremental integration preferred over big bang integration? Because incremental integration has better early defects screening and isolation ability 69. When do we prepare RTM (Requirement traceability matrix), is it before test case designing or after test case designing? The would be before. Requirements should already be traceable from Review activities since you should have traceability in the Test Plan already. This question also would depend on the organisation. If the organisation do test after development started then requirements must be already traceable to their source. To make life simpler use a tool to manage requirements. 70. What is called the process starting with the terminal modules ? Bottom-up integration 71. During which test activity could faults be found most cost effectively? During test planning 72. The purpose of requirement phase is To freeze requirements, to understand user needs, to define the scope of testing 73. How much testing is enough? The answer depends on the risks for your industry, contract and special requirements 74. Why we split testing into distinct stages? Each test stage has a different purpose. 75. Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities? a) Regression testing b) Integration testing c) System testing d) User acceptance testing Regression testing 76. How would you estimate the amount of re-testing likely to be required? Metrics from previous similar projects and discussions with the development team

77. What studies data flow analysis ? The use of data on paths through the code. 78. What is Alpha testing? Pre-release testing by end user representatives at the developers site. 79. What is a failure? Failure is a departure from specified behaviour. 80. What are Test comparators ? Is it really a test if you put some inputs into some software, but never look to see whether the software produces the correct result? The essence of testing is to check whether the software produces the correct result, and to do that, we must compare what the software produces to what it should produce. A test comparator helps to automate aspects of that comparison. 81. Who is responsible for document all the issues, problems and open point that were identified during the review meeting Scribe 82. What is the main purpose of Informal review Inexpensive way to get some benefit 83. What is the purpose of test design technique? Identifying test conditions and Identifying test cases 84. When testing a grade calculation system, a tester determines that all scores from 90 to 100 will yield a grade of A, but scores below 90 will not. This analysis is known as: Equivalence partitioning 85. A test manager wants to use the resources available for the automated testing of a web application. The best choice is Tester, test automater, web specialist, DBA 86. During the testing of a module tester X finds a bug and assigned it to developer. But developer rejects the same, saying that its not a bug. What X should do? Send to the detailed information of the bug encountered and check the reproducibility 87. A type of integration testing in which software elements, hardware elements, or both are combined all at once into a component or an overall system, rather than in stages. Big-Bang Testing 88. In practice, which Life Cycle model may have more, fewer or different levels of development and testing, depending on the project and the software product. For example, there may be component integration testing after component testing, and system integration testing after system testing. V-Model

89. Which technique can be used to achieve input and output coverage? It can be applied to human input, input via interfaces to a system, or interface parameters in integration testing. Equivalence partitioning 90. This life cycle model is basically driven by schedule and budget risks This statement is best suited for V-Model 91. In which order should tests be run? The most important tests first 92. The later in the development life cycle a fault is discovered, the more expensive it is to fix. why? The fault has been built into more documentation,code,tests, etc 93. What is Coverage measurement? It is a partial measure of test thoroughness. 94. What is Boundary value testing? Test boundary conditions on, below and above the edges of input and output equivalence classes. 95. What is Fault Masking ? Error condition hiding another error condition. 96. What does COTS represent? Commercial Off The Shelf. 97.The purpose of wich is allow specific tests to be carried out on a system or network that resembles as closely as possible the environment where the item under test will be used upon release? Test Environment 98. What can be though of as being based on the project plan, but with greater amounts of detail? Phase Test Plan 99. What is exploratory testing? Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the cre-ation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typi-cally without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. For example, the tester may decide to use boundary value analysis but will think through and test the most important boundary values without necessarily writing them down. Some notes will be written during the exploratory-testing session, so that a report can be produced afterwards.

100. What is failure? Deviation from expected result to actual result

1. Testing is a process of executing a program with the intent of finding an error. 2. A good test case is one that has a high probability of finding an as yet undiscovered error. 3. A successful test is one that uncovers an as yet undiscovered error. Testing should systematically uncover different classes of errors in a minimum amount of time and with a minimum amount of effort. A secondary benefit of testing is that it demonstrates that the software appears to be working as stated in the specifications. The data collected through testing can also provide an indication of the software's reliability and quality. But, testing cannot show the absence of defect -- it can only show that software defects are present.

1. a. b. c. d.

Acceptance testing will be done by User Quality control Quality assurance Senior management

1. a 2. a. b. c. Main objective of configuration management Maintain baseline for each version Build software libraries Get the right change installed at the right time

2.

3. Customers will be get supported from these people for their problems a. Helpdesk

4.

Unit testing is a

a. b. c.

White box testing Black box testing Stress testing

5. a 5. Before doing integration testing this testing must have been done

a. b. c.

Unit testing Systems testing Stress testing

6.a 6. Cost of quality

a.

Appraisal, failure and preventive

7.

4 types of testing

a. 8.

System, unit, integration, acceptance There are 7 problem analysis tools. Which of the following is not one

a. b. c.

Flow chart Scatter plot Variance analysis

11.

Given the following costs: Rework - $ 1000 Review of User Documents - $ 1000 Code review - $ 1000

User documentation - $ 1000 Design - $ 400

The cost of Quality is a. b. $3000 $4000

c.

$5000

12.

Metric to measure operational reliability

a. b.

MTBF Defect density

13. a. b. c. d.

The programmer writes a program step-by-step following this: Procedure Checklist Process Check sheet

14.Testing (including fixing the problem) is app. 50% of total product development cost

a. b.

True False

15. JIT is used only for inventory control by toyota

a. b.

True False

16. What is 6 sigma a. b. c. d. 34 per 1,000 34 per 1,00,000 34 per 1,000,000 34 per 10,000,000 (its 34 not 3.4 :-P )

17. Mean and median are

a. b.

Central tendency Variation

18. An example of deployment of a quality approach is: a. b. c. d. e. The degree to which the approach embodies effective evaluation cycles The appropriate and effective application to all product and service characteristics The effectiveness of the use of tools, techniques, and methods The contribution of outcomes and effects to quality improvement The significance of improvement to the companys business

19.The concept of continuous improvement as applied to quality means a. b. c. d. Employees will continue to get better Processes will be improved by a lot of small improvements Processes will be improved through a few large improvements Improved technology will be added to the process, such as acquiring CASE tools

d. The functionality of the products will be enhanced

20. Quality is

a. b. c. d. a.

Meeting requirements Zero defects Customer satisfaction All of the above a & c only

SQA
2 Marks & 16 Marks Unit 1 1.Define a software engineering. Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software 2.what are all the different software engineering paradigms?

waterfall model prototyping model object oriented model spiral model WINWIN spiral model incremental model evolutionary model

3. what is meant by software Verification and Validation ?

In software project management, software testing, and software engineering, Verification and Validation (V&V) is the process of checking that a software system meets specifications and that it fulfils its intended purpose. It is normally part of the software testing process of a project.

4. what is meant by Independent Verification and Validation?

Verification and validation often is carried out by a separate group from the development team; in this case, the process is called \"Independent Verification and Validation\", or IV&V.

5. define Dynamic verification .

Dynamic verification is performed during the execution of software, and dynamically checks its behaviour; it is commonly known as the Test phase. Verification is a Review Process. Depending on the scope of tests, we can categorize them in three families:

Test in the small: a test that checks a single function or class (Unit test) Test in the large: a test that checks a group of classes, such as o Module test (a single module) o Integration test (more than one module) o System test (the entire system) Acceptance test: a formal test defined to check acceptance criteria for a software o Functional test o Non functional test (performance, stress test)

6. define Static verification .

Static verification is the process of checking that software meets requirements by doing a physical inspection of it. For example:

Code conventions verification Bad practices detection Software metrics calculation Formal verification

7. define a software life cycle. The software life cycle is a general model of the software development process, including all the activities and work products required to develop a software system. A software life cycle model is a particular abstraction representing a software life cycle. Such a model may be:

activity-centered -- focusing on the activities of software development entity-centered -- focusing on the work products created by these activities

8. define a Waterfall Model.

The waterfall model prescribes a sequential execution of a set of development and management processes, with no return to an earlier activity once it is completed. Some variants of the waterfall model allow revisiting the immediately preceding activity (\"feedback loops\") if inconsistencies or new problems are encountered during the current activity.

9.what is meant by RAD? Rapid application development (RAD) is an approach rather than a model. Its proponents view formal life cycle models as inherently inefficient, due to the large amount of documentation and the number of reviews required. The formality of such models is seen as interfering with customer communication. Instead, RAD focuses on developing a sequence of evolutionary prototypes which are reviewed with the customer, both to ensure that the system is developing toward the user\'s requirements and to discover further requirements. 10.define a system engineering concept. Systems engineering (also known as Systems design engineering) is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals

with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering and project management.

11.what is computer based system? A System is a collection of interrelated componets that work together to achieve some objective.systems and their environment Two reasons why system engineers must understand the environment of a system : (1) The reason for the existence of a system is to make some changes in its environment. (2) The functioning of a system can be very difficult to predict. 12.define BPE. The BPR involves significant organisational change and that managing the change process must therefore be critical to the success of such undertakings with all its major ramifications. In particular the role of organisational culture within the change process is explored. These explorations are initially conducted using a search of the literature and this is followed by a small primary research exercise into a particular hypothesis and issue arising.

13.what is meant by BPR? Structures StaffSkillsStrategyStyleShared Values Reengineering is the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical, contemporary measures of performance, such as cost, quality, service, and speed. 14.what are all the 7s models that can impact on the organization?

System Structures StaffSkills Strategy Style Shared Values

15. what are all the Problems that can arise during system installation? (1) Proposed changes have to be analysed very carefully both from a business and a technical perspective.

(2) Because sub-systems are never independent, changes to one sub-system may adversely affect the performance of another sub-system. (3) (4) The reasons for original design decisions are often unrecorded. As systems age, their structure typically becomes corrupted by change so the costs of additional changes increase.

16.define a V-Model

Another variant of the waterfall model -- the V-model -- associates each development activity with a test or validation at the same level of abstraction. Each development activity builds a more detailed model of the system than the one before it, and each validation tests a higher abstraction than its predecessor

17.what is meant by Project Management

The project manager initiates, monitors and controls the project throughout the software life cycle. The project management plan is documented in the Software Project Management Plan (SPMP) during the Project Initiation process, and the plan is updated to reflect changes throughout the project.

18.what is meant by product engineering?

In the final phase a product X is being engineered. This product X uses the commonalities and variability from the Domain Engineering phase, so product X is being derived from the platform established in the Domain Engineering phase. It basically takes all common requirements and similarities from the preceding phase plus its own variable requirements. Using the base from the Domain Engineering phase and the individual requirements of the Product Engineering phase a complete and new product can be built. After that the product has been fully tested and approved, the product X can be delivered. 19. define aTest product During this step the product is verified and validated against its specifications. A test report gives information about all tests that were carried out, this gives an overview of possible errors in the product. If the product in the next step is not accepted, the process will loop back to Build Product,

20.what is meant by Deliver and Support of Product The final step is the acceptance of the final product. If it has been successfully tested and approved to be complete, it can be delivered. If the product does not satisfy to the specifications, it has to be rebuilt and tested again. The next figure shows the overall process of product family/line engineering as described above. It is a full process overview with all concepts attached to the different steps.

PART-B (16 MARKS)

1. Explain the linear software life cycle model with suitable illustration. Bring out the demerits of this model. 2. (a) How do you differentiate software engineering from system engineering? (b) For each of the types of process models, identify the types of project suitable to Implement. (c) Distinguish between verification and validation process. 3. (a) What is meant by generic view of software engineering? Brief it. (b) Explain the process model, which is useful when staffing, is unavailable for Complete implementation. 4. (a) what is the difference between system and computer based system? (b)What is prototyping? Mention its types. Also explain this model with advantages and disadvantages. 5. Define Software process model? Explain any one of it with a neat diagram 6. Explain the hierarchy of Business process Engineering. 7. Explain Software Life cycle process 8. Explain Evolutionary process model 9. Explain the different layers of Software Engineering? 10. (a) Describe the process model which defines a network of activities? (b) Why the first systems throw away system? Explain the concept with advantages and disadvantages. 11.(a) Draw a system engineering hierarchy diagram and explain the concept? (b) Explain the process model that combines the elements of waterfall and iterative fashion.

2 Marks & 16 Marks Unit-IV

1.Define black box testing strategy. Black box testing focuses on the functional requirements of the software. Test cases are decided on the basis of the requirements or specifications of the program and internals of program are not considered. Test cases are generated based on program code.

2.What is meant by software change? Software change is defined as the change in nature of software as the requirements of software changes.

3. Why testing is important with respect to software? A testing process focuses on logical internals of software ensuring that all statements have been tested and all are functional externals. While testing, we execute the entire program before it gets to the customer with specific indent of finding and removing all errors. In order to find the highest number of errors, test must be conducted systematically and test cases must be designed using disciplined techniques.

4. Write short notes on empirical estimation models. Estimation model for computer software uses empirically derived formulas to predict effort as a function of line of codes (LOC) and function points (FP). The values of LOC and FP estimated are plugged into estimation model. The empirical data that support most estimation models are derived from a limited sample of projects. So, results obtained from models should be used judiciously. The model must be tested and compared with actual and predicted data.

5. Justify the term Software is engineered Software is engineered not manufactured. Although some similarities exit between software development and hardware manufacture, the two activities are fundamentally different. Both activities are dependent on people, but the relationship between people applied and work accomplished is entirely different. Both activities require the construction of a Product but the approaches are different.

6. State Lehmans Fifth law. Over the lifetime of a system, the incremental change in each release is approximately constant.

7. Define software scope. The first software project management activity is the determination of software scope. Scope is defined answering the following questions. Context: What constraints are imposed as a result of the context. Information objectives: What data objects are required for input? Function and performance: Are any special performance characteristics to be addressed?

8. Define process maturity. In recent years there has been a significant emphasis on process maturity. The Software Engineering Institute. (SEI) has developed a comprehensive model predicated on a set of software engineering capabilities that should be present as organizations reach different levels of process maturity .The grading schema determines compliance with a capability maturity model (CMM) that defines key activities required at different levels of process maturity.

9.Distinguish between alpha testing and beta testing. The alpha test is conducted at the developer site. The software is used in a natural setting with the developer looking over the shoulder of the user and recording The beta test is conducted at one or more customer sites by the end user of the software. The beta test is a Live application of the software in an environment that problems. cannot be controlled by the developer.

10. What is software architecture. The software architecture of a program or computing system is the structure or structures of the system, which comprises software components, the externally visible

properties of those components and the relationships among them.

11. What is meant by software change? Once software is put into use, new requirement emerge and existing requirements change as the business running that software changes parts of the software may have to be modified to correct errors that are found in operation, improve its performance or other non functional characteristics. This entire means that ,after delivery ,software system always evolve in response to demands for changes.

12. define Performance Testing. This type of testing checks whether the system is performing properly, according to the user\'s requirements. Performance testing depends upon the Load and Stress Testing, that is internally or externally applied to the system.

Load Testing : In this type of performance testing, the system is raised beyond the limits in order to check the performance of the system when higher loads are applied. Stress Testing : In this type of performance testing, the system is tested beyond the normal expectations or operational capacity

13.what is meat by Regression Testing? Regression Testing: Regression testing is one of the most important types of testing, in which it checks whether a small change in any component of the application does not affect the unchanged components. Testing is done by re-executing the previous versions of the application. 14. what is meant by Boundary value analysis?

Boundary value analysis is a software testing design technique in which tests are designed to include representatives of boundary values. Values on the edge of an equivalence partition or at the smallest value on either side of an edge. The values could be either input or output ranges of a software component. Since these boundaries are common locations for errors that result in software faults they are frequently exercised in test cases.

15.define White box testing .

White box testing (a.k.a. clear box testing, glass box testing, transparent box testing, translucent box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

16. what is meant by unit testing? unit testing is a software verification and validation method in which a programmer tests if individual units of source code are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. 17. what is the goal of unit testing?

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. Unit tests find problems early in the development cycle.

18.what is meant by Integration testing

Integration testing is the activity of software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. 19.list out the types of validation testing.

Content Validation Concurrent Validation Predictive Validation

20. lis tout the types of system testing. The following examples are different types of testing that should be considered during System testing:

GUI software testing Usability testing Performance testing Compatibility testing Error handling testing Load testing Volume testing Stress testing

21.define debugging. Debugging is a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware thus making it behave as expected. Debugging tends to be harder when various subsystems are tightly coupled, as changes in one may cause bugs to emerge in another.

22.define Anti-debugging. Anti-debugging is \"the implementation of one or more techniques within computer code that hinders attempts at reverse engineering or debugging a target process\"

Part -B(16 marks)

1. (a) How to derive test cases for the given project? Explain with detail. (b) How the RST (Reflexive, Symmetric and Transitivity) condition is verified in black box testing? Explain with example. 2. (a) Why unit testing is so important? Explain the concept of unit testing in detail. (b) Write a note on regression testing. 3. (a) Explain the testing procedure for boundary conditions. (b) Describe verification and validation criteria for software. 4. (a) Describe unit testing and integration testing. How test plans are generated. (b) Suggest software testing sequence for 100% bug free software explains. 5. (a) Why is testing important? (b) Narrate the path testing procedure in detail with a sample code. 6. (a) Distinguish between black box and white box testing.

(b) Explain the different integration testing approaches. 7. Explain in detail Black box testing in detail . 8. How Boundary test conditions are achieved? 9. Explain in detail Structural testing? 10. Explain in detail Software Testing Strategies. 11. Explain the test coverage criteria based on Data flow mechanisms. 12. (a) What are all the formulas for cyclomatic complexity? Calculate cyclomatic Complexity for greatest of three numbers. (b) Explain about system testing. 13. Explain different types of software measures .

2 Marks & 16 Marks Unit 3

1.define a system engineering. Systems engineering (also known as Systems design engineering) is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more difficult when dealing with large, complex projects. Systems engineering deals with work-processes and tools to handle such projects, and it overlaps with both technical and human-centered disciplines such as control engineering and project management. 2. What is the use of Architectural design? Architecture is both the process and the product of designing and constructing spaces that reflect and functional, aesthetic and environmental considerations. Architecture requires the use of materials, technology, textures, light, and shadow. As a process, architecture also includes the pragmatic elements of design, such as planning, cost and construction. A wider definition may comprise all design activity from the macro-level (urban design, landscape architecture) to the micro-level (construction details and furniture). In fact, architecture today may refer to the activity of designing any kind of system.

2. Define Software design. Software design is a process of problem-solving and planning for a software solution. After the purpose and specifications of software are determined, software developers will design or employ designers to develop a plan for a solution. It includes lowlevel component and algorithm implementation issues as well as the architectural view.

3. Mention some of the Design concepts.

1.Abstraction - Abstraction is the process or result of generalization by reducing the information content of a concept or an observable phenomenon, typically in order to retain only information which is relevant for a particular purpose. 2.Refinement - It is the process of elaboration. A hierarchy is developed by decomposing a macroscopic statement of function in a stepwise fashion until programming language statements are reached. In each step, one or several instructions of a given program are decomposed into more detailed instructions. Abstraction and Refinement are complementary concepts. 3.Modularity - Software architecture is divided into components called modules. 4.Software Architecture - It refers to the overall structure of the software and the ways in which that structure provides conceptual integrity for a system. A software architecture is the development work product that gives the highest return on investment with respect to quality, schedule and cost. 5.Control Hierarchy - A program structure that represent the organization of a program components and implies a hierarchy of control. 6.Structural Partitioning - The program structure can be divided both horizontally and vertically. Horizontal partitions define separate branches of modular hierarchy for each major program function. Vertical partitioning suggests that control and work should be distributed top down in the program structure. 7.Data Structure - It is a representation of the logical relationship among individual elements of data. 8.Software Procedure - It focuses on the processing of each modules individually 9.Information Hiding - Modules should be specified and designed so that information contained within a module is inaccessible to other modules that have no need for such information.

4. State Procedural abstraction. procedural abstraction The principle that any operation that achieves a well-defined effect can be treated by its users as a single entity, despite the fact that the operation may actually be achieved by some sequence of lower-level operations (see also

abstraction). Procedural abstraction has been extensively employed since the early days of computing, and virtually all programming languages provide support for the concept (e.g. the SUBROUTINE of Fortran, the procedure of Algol, Pascal, Ada, etc.). 5. What does Data abstraction contains? Data abstraction enforces a clear separation between the abstract properties of a data type and the concrete details of its implementation. The abstract properties are those that are visible to client code that makes use of the data typethe interface to the data typewhile the concrete implementation is kept entirely private, and indeed can change, for example to incorporate efficiency improvements over time. The idea is that such changes are not supposed to have any impact on client code, since they involve no difference in the abstract behaviour

6. What does Modularity concept mean? In systems engineering, modular design or \"modularity in design\" is an approach that subdivides a system into smaller parts (modules) that can be independently created and then used in different systems to drive multiple functionalities. Besides reduction in cost (due to lesser customization, and less learning time), and flexibility in design, modularity offers other benefits such as augmentation (adding new solution by merely plugging in a new module), and exclusion.

7.what is meant by heuristic evaluation?

The main goal of heuristic evaluations is to identify any problems associated with the design of user interfaces. Usability consultant Jakob Nielsen developed this method on the basis of several years of experience in teaching and consulting about usability engineering. Heuristic evaluations are one of the most informal methods[1] of usability inspection in the field of human-computer interaction. There are many sets of usability design heuristics; they are not mutually exclusive and cover many of the same aspects of interface design.

8. define CASE. Computer-Aided Software Engineering (CASE), in the field of Software Engineering is the scientific application of a set of tools and methods to a software system which is meant to result in high-quality, defect-free, and maintainable software products.[1] It also refers to methods for the development of information systems together with automated tools that can be used in the software development process. 9.list out the various systems analysis and design techniques.

data flow diagram entity relationship diagram logical schema Program specification SSADM. User documentation

10. define a User interface design.

User interface design or user interface engineering is the design of computers, appliances, machines, mobile communication devices, software applications, and websites with the focus on the user\'s experience and interaction. The goal of user interface design is to make the user\'s interaction as simple and efficient as possible, in terms of accomplishing user goalswhat is often called user-centered design. Good user interface design facilitates finishing the task at hand without drawing unnecessary attention to itself. 11.what are all the processes available in User interface design?

Functionality requirements gathering User analysis Information architecture Prototyping Usability testing Graphic Interface design

12.list out the steps involved in real time software design. Designing Realtime software involves several steps. The basic steps are listed below:

Software Architecture Definition Co-Design Defining Software Subsystems Feature Design Task Design

13. define a Software Architecture Definition.

This is the first stage of Realtime Software design. Here the software team understands the system that is being designed. The team also reviews at the proposed hardware architecture and develops a very basic software architecture. This architecture definition will be further refined in Co-Design. Use Cases are also used in this stage to analyze the system. Use cases are used to understand the interactions between the system and its users. For example, use cases for a telephone exchange would specify the interactions between the telephone exchange, its subscribers and the operators which maintain the exchange.

14.define task design.

Designing a task requires that all the interfaces that the task needs to support should be very well defined. Make sure all the message parameters and timer values have been finalized.

15.list out the types of task.

Single State Machine

Multiple State Machines Multiple Tasks Complex Task

16. define Systems design.

Systems design is the process or art of defining the architecture, components, modules, interfaces, and data for a system to satisfy specified requirements. One could see it as the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering

17.what are all the Alternative design methodologies?

Rapid Action Development (RAD) Joint Action Development (JAD)

18.define JAD. JAD is a methodology which evolved from RAD, in which a systems designer consults with a group consisting of the following parties:

Executive sponsor Systems Designer Managers of the system

JAD involves a number of stages, in which the group collectively develop an agreed pattern for the design and implementation of the system.

19. what is meant by data acquisition?

data acquisition is the sampling of real world physical conditions and conversion of the resulting samples into digital numeric values that can be manipulated by a computer. Sometimes abbreviated DAQ, data acquisition typically involves the conversion of analog signals and waveforms into digital values and processing the values to obtain desired information. 20. list out the components of data acquisition. The components of data acquisition systems include:

Sensors that convert physical parameters to electrical signals. Signal conditioning circuitry to coerce sensor signals into a form that can be converted to digital values.

Analog-to-digital converters, which convert conditioned sensor signals to digital values.

21. define a project monitoring and control The purpose of project monitoring and control is to keep the team and management up to date on the project\'s progress. If the project deviates from the plan, then the project manager can take action to correct the problem. Project monitoring and control involves status meetings to gather status from the team. When changes need to be made, change control is used to keep the products up to date.

Part b-(16marks)

1. (a) Which is a measure of interconnection among modules in a program structure? Explain. (b) What is he difference between Level-0 and Level-1 DFD? draw a Level-0 and Level-1 DFD for safe Home Security System. 2. (a) How the interrupts are handled in real time systems? Explain. (b) How to identify the objects in the software configuration? Explain in detail. 3. What are the different types of architectural styles exist for software and explain any one software architecture in detail. 4. (a) Describe activities of SCM in detail. (b) Explain the user interfaces design activities. 5. (a) Explain data, architectural and procedural design for a software explain. One software architecture in detail. (b) Describe the design procedure for a data acquisition system. one software architecture in detail.

6. Discuss briefly Effective Modular Design. 7. Explain Real Time Systems. 8. What is Software Architecture? Explain it. 9. (a) Draw a translating diagram for analysis model into a software design specification. (b) Given complete template for documentation design specification. 10. (a) How the interrupts are handled in real time systems? Explain. (b) Write a note on real time software design.

2 Marks & 16 Marks Unit-IV

1.Define black box testing strategy.

Black box testing focuses on the functional requirements of the software. Test cases are decided on the basis of the requirements or specifications of the program and internals of program are not considered. Test cases are generated based on program code.

2.What is meant by software change? Software change is defined as the change in nature of software as the requirements of software changes.

3. Why testing is important with respect to software? A testing process focuses on logical internals of software ensuring that all statements have been tested and all are functional externals. While testing, we execute the entire program before it gets to the customer with specific indent of finding and removing all errors. In order to find the highest number of errors, test must be conducted systematically and test cases must be designed using disciplined techniques.

4. Write short notes on empirical estimation models. Estimation model for computer software uses empirically derived formulas to predict effort as a function of line of codes (LOC) and function points (FP). The values of LOC and FP estimated are plugged into estimation model. The empirical data that support most estimation models are derived from a limited sample of projects. So, results obtained from models should be used judiciously. The model must be tested and compared with actual and predicted data.

5. Justify the term Software is engineered Software is engineered not manufactured. Although some similarities exit between software development and hardware manufacture, the two activities are fundamentally different. Both activities are dependent on people, but the relationship between people applied and work accomplished is entirely different. Both activities require the construction of a Product but the approaches are different.

6. State Lehmans Fifth law. Over the lifetime of a system, the incremental change in each release is approximately constant.

7. Define software scope. The first software project management activity is the determination of software scope. Scope is defined answering the following questions. Context: What constraints are imposed as a result of the context. Information objectives: What data objects are required for input? Function and performance: Are any special performance characteristics to be addressed?

8. Define process maturity. In recent years there has been a significant emphasis on process maturity. The Software Engineering Institute. (SEI) has developed a comprehensive model predicated on a set of software engineering capabilities that should be present as organizations reach different levels of process maturity .The grading schema determines compliance with a capability maturity model (CMM) that defines key activities required at different levels of process maturity.

9.Distinguish between alpha testing and beta testing. The alpha test is conducted at the developer site. The software is used in a natural setting with the developer looking over the shoulder of the user and recording The beta test is conducted at one or more customer sites by the end user of the software. The beta test is a Live application of the software in an environment that problems. cannot be controlled by the developer.

10. What is software architecture. The software architecture of a program or computing system is the structure or structures of the system, which comprises software components, the externally visible properties of those components and the relationships among them.

11. What is meant by software change? Once software is put into use, new requirement emerge and existing requirements

change as the business running that software changes parts of the software may have to be modified to correct errors that are found in operation, improve its performance or other non functional characteristics. This entire means that ,after delivery ,software system always evolve in response to demands for changes.

12. define Performance Testing. This type of testing checks whether the system is performing properly, according to the user\'s requirements. Performance testing depends upon the Load and Stress Testing, that is internally or externally applied to the system.

Load Testing : In this type of performance testing, the system is raised beyond the limits in order to check the performance of the system when higher loads are applied. Stress Testing : In this type of performance testing, the system is tested beyond the normal expectations or operational capacity

13.what is meat by Regression Testing? Regression Testing: Regression testing is one of the most important types of testing, in which it checks whether a small change in any component of the application does not affect the unchanged components. Testing is done by re-executing the previous versions of the application. 14. what is meant by Boundary value analysis?

Boundary value analysis is a software testing design technique in which tests are designed to include representatives of boundary values. Values on the edge of an equivalence partition or at the smallest value on either side of an edge. The values could be either input or output ranges of a software component. Since these boundaries are common locations for errors that result in software faults they are frequently exercised in test cases.

15.define White box testing .

White box testing (a.k.a. clear box testing, glass box testing, transparent box testing, translucent box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

16. what is meant by unit testing? unit testing is a software verification and validation method in which a programmer tests if individual units of source code are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. 17. what is the goal of unit testing?

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits. Unit tests find problems early in the development cycle.

18.what is meant by Integration testing

Integration testing is the activity of software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. 19.list out the types of validation testing.

Content Validation Concurrent Validation Predictive Validation

20. lis tout the types of system testing. The following examples are different types of testing that should be considered during System testing:

GUI software testing Usability testing Performance testing Compatibility testing Error handling testing Load testing Volume testing Stress testing

21.define debugging. Debugging is a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware thus making it behave as expected. Debugging tends to be harder when various subsystems are tightly coupled, as changes in one may cause bugs to emerge in another.

22.define Anti-debugging. Anti-debugging is \"the implementation of one or more techniques within computer code that hinders attempts at reverse engineering or debugging a target process\"

Part -B(16 marks)

1. (a) How to derive test cases for the given project? Explain with detail. (b) How the RST (Reflexive, Symmetric and Transitivity) condition is verified in black box testing? Explain with example. 2. (a) Why unit testing is so important? Explain the concept of unit testing in detail. (b) Write a note on regression testing. 3. (a) Explain the testing procedure for boundary conditions. (b) Describe verification and validation criteria for software. 4. (a) Describe unit testing and integration testing. How test plans are generated. (b) Suggest software testing sequence for 100% bug free software explains. 5. (a) Why is testing important? (b) Narrate the path testing procedure in detail with a sample code. 6. (a) Distinguish between black box and white box testing. (b) Explain the different integration testing approaches. 7. Explain in detail Black box testing in detail . 8. How Boundary test conditions are achieved? 9. Explain in detail Structural testing? 10. Explain in detail Software Testing Strategies.

11. Explain the test coverage criteria based on Data flow mechanisms. 12. (a) What are all the formulas for cyclomatic complexity? Calculate cyclomatic Complexity for greatest of three numbers. (b) Explain about system testing. 13. Explain different types of software measures .

Unit V 1. What is RMM plan? The risk mitigation, monitoring, and management plan documents all work performed as part of risk analysis and is used by the project manager as part of the overall project plan. Once the RMMM has been documented and the project has begun risk mitigation and monitoring steps commence.

2. What are the qualities team leaders should posses? Motivation, organization, ideas and innovation, problem solving, managerial identity, achievement, and influence and team building.

3. What is an agile team? Agile software development encourages customer satisfaction and early incremental delivery. Agile team Is a highly motivated project team which adopts informal methods, and overall development simplicity.

4. What are the categories of activities connected with measurement process? Formulation, Collection, Analysis, Interpretation and feedback.

5. What are the different measurable characteristics of an OO design? Size, complexity, coupling, sufficiency, completeness, cohesion, primitiveness, similarity, volatility.

6. What are the measures of software quality? Correctness, maintainability, integrity usability.

7. What is metrics evaluation? Metrics evaluation focuses on the underlying reasons for the results obtained and produces a set of indicators that guide the project or process.

8. What is software quality assurance? Software quality assurance is a planned and systematic pattern of actions that are required to ensure high quality in software.

9. What is SQA group? SQA group consists of many different constituencies like software engineers, project managers, customers, salespeople and the individuals which are having software quality assurance responsibility.

10. What are the activities associated with SQA group? Planning, oversight, record keeping, analysis and reporting.

11. What are the different SCM features? Versioning, dependency tracking and change management, requirements tracing, configuration management, audit trails.

12. What are reactive risk strategies? Reactive strategy the software team does nothing about risks until something goes wrong.

13. What are the characteristics of software risks? Uncertainty and loss

14. What is software availability? Software availability is the probability that a program is operating according to requirements at a given point in time.

15. What are the management responsibilities regarding ISO 9001 requirements? Management commitment, Customer focus, Quality policy, Planning, Responsibility, Authority, Communication, and Management review.

16. Define SPICE. SPICE (Software Process Improvement and Capability dEvelopement) standard defines a set of requirements for software process assessment. The intent of the standard is to assist organizations in developing an objective evaluation of the efficacy of any defined software process.

17. What is MALCOLM BALDRGE award? MALCOLM BALDRIGE award is the most prestigious quality award in the United States. The award is given annually to recognize U.S companies that exceed in quality management and quality achievement.

18. What are the ISO 9000 series of quality management standards? ISO 9000, ISO9001, ISO9002, ISO9003, ISO9003, ISO9004

19. Define CMM. The capability maturity model (CMM) for s/w is a widely accepted set of guidelines for developing high performance s/w organizations.

20. What are the capability levels defined in SPICE? Level0: Not performed, 1: Performed informally, 2: Planned and tracked, 3: Well defined, 4: Quantitatively controlled, 5: Continuously improving.

21. What are the four ps focused on effective software project management? 1. People, 2. Product, 3. Process, 4. Project

22. Define software configuration management.

SCM is a set of activities that have been developed to manage change throughout the life cycle of computer software.

23. What is quality planning? Quality planning refers to the activities that establish the objectives and requirements for quality.

24. What is quality improvement? QM aims at attaining unprecedented levels of performance which are significantly better than the past level.

25. What is quality management? Quality management comprises all activities of the overall management function that determine the quality policy, objectives and responsibilities, and implement them by means such as other quality planning, quality control, etc.

26. What are the benefits of QFD? 1. Reduces product development time 2. Reduce engineering costs 3. Reduces the time to market. 4. Improves design quality 5. Improves customer satisfaction. 6. Reduce quality costs. etc.

27. What are the different dimensions of quality?

Performance, features, reliability, conformance, durability, serviceability, aesthetics, perceived quality and reputation, response.

28.Define quality. Quality is the degree of goodness of a product or service or perceived by the customer. Quality concept is the way business organizations perform their business activities that focuses on two things.

29. What is quality cost? The expenditure incurred by the producer, by the user and by the community associated with the product and service quality.

30. What are the 7 QC tools? 1. Check sheet 2. Graphs 3. Histograms 4. Pareto charts 5. Cause and effect diagrams 6. Scatter charts 7. Control charts

16 MARKS

1. Explain Quality Function Deployment in detail. 2. Describe in detail the standardization procedure of benchmarking. 3. Explain how software quality assurance is ensured in a software firm.

4. Explain the seven basic quality control tools in detail. 5. Explain software project management in detail. 6. Explain how software quality assurance is ensured in a software firm 7. What are the different software testing tactics? Explain. 8. Write detail notes on risk management. 9. Write detail notes on ISO9000 series of quality management standards. 10. Account on CMM in detail. 11. Give a detail note on SPICE in detail. 12. Write detailed notes on Malcolm Baldrige award. 13. Explain how software process assessment helps software organizations to improve themselves. 14. Explain the testing phase of software development in detail. 15. Give detailed description about software process assessment. 16. Explain software inspections in detail. 17. Explain OO methodology in detail. 18. Write detailed notes on the techniques for error cause analysis and defect prevention. 19. Account on clean-room software engineering. 20. Write notes on TSP and PSP.

1 CS 1632 SOFTWARE QUALITY ASSURANCE 2 Marks Sample Questions and Answers 1. Define quality. Quality is the degree of goodness of a product or service or perceived by the customer. Quality concept is the way business organizations perform their business activities that focuses on two things.

2. What is quality cost? The expenditure incurred by the producer, by the user and by the community associated with the product and service quality. 3. What are the building blocks of total quality management? Management commitment, customer focus, process focus, continuous improvement, benchmarking, teams, supplier teaming, employee involvement, training of employees, inventory management, communication. 4. What are the 7 QC tools? 1. Check sheet 2. Graphs 3. Histograms 4. Pareto charts 5. Cause and effect diagrams 6. Scatter charts 7. Control charts 5. What is business process reengineering? BPR is the search for, and the implementation of, radical change in business process to achieve breakthrough results Define Quality Function Deployment. 6. Define Quality Function Deployment. QFD is a systematic and structured planning tool which is used to convert the voice of the customer into appropriate requirements. 7. Define six sigma. Six sigma is a highly disciplined process that helps the enterprise to focus on

developing and delivering new perfect products and services. 8. What are the uses of arrow diagram? Arrow diagrams help in scheduling the activities so that any project can be completed in the best possible way. It will provide a time sequential action plan for all the tasks that are to be carried out in a project. 2 9. What are the different dimensions of quality? Performance, features, reliability, conformance, durability, serviceability, aesthetics, perceived quality and reputation, response. 10. What is external failure? Costs of correction methods adopted to meet quality standards after reaching the customers. 11. What are the uses of control charts?.

1. Monitoring the process. 2. Identifying the state of statistical control 3. Finding the reasons for out of control. 4. finding out of mean and variation 5. identifying the randomly occurring variations 12. Steps involved in the bench marking process. Decide the function to be benchmarked, look into and understand the current performance, plan, study the other players in the market, learn from the data that you have collected, implement the findings. 13. What is statistical process control?

Statistical process control procedures are designed to divert attention from individual data and focus on the system as a whole. SPC is used to measure and control the degree of variation in material, service, process and product. 14. Define TQM. Total quality management is customer oriented management philosophy and strategy. It is centered on quality so as to result in customer delight. 15. What is quality planning? Quality planning refers to the activities that establish the objectives and requirements for quality. 16. What is quality improvement? QM aims at attaining unprecedented levels of performance which are significantly better than the past level. 17. What is quality management? Quality management comprises all activities of the overall management function that determine the quality policy, objectives and responsibilities, and implement them by means such as other quality planning, quality control, etc. 18. What are the benefits of QFD? 1. Reduces product development time 2. Reduce engineering costs 3. Reduces the time to market. 3 4. Improves design quality 5. Improves customer satisfaction. 6. Reduce quality costs. etc.

19. What is internal benchmarking>? Internal benchmarking compares best practices followed in different departments with in a company instead of looking other companies. 20. What are the four ps focused on effective software project management? 1. People, 2. Product, 3. Process, 4. Project 21. Define software configuration management. SCM is a set of activities that have been developed to manage change throughout the life cycle of computer software. 23. What are CASE tools? CASE is the use of computer based support in the S/W development process. Tools used to assist in this way are known as CASE tools. 24. What are function-oriented metrics? Function oriented software metrics use a measure of the functionality delivered by the application as a normalization value. Since functionality can not be measured directly, it must be derived indirectly using other direct measures. 25. Define white box testing? White box testing sometimes called as glass box testing is a test case design method that uses the control of the procedural design to drive test cases. 26. What are the steps implied by statistical quality assurance? 1. Information about s/w defects, 2. An attempt is made to trace each defect to its underlying cause, 3. Using the pareto principle, 4. Move to correct the problems that have caused the defects. 27. Define Verification and Validation.

Verification refers to the set of activities that ensure that s/w correctly implements a specific function. Validation refers to a different set of activities that ensure that the s/w that has been built is traceable to customer requirements. 28. What is RMM plan? The risk mitigation, monitoring, and management plan documents all work performed as part of risk analysis and is used by the project manager as part of the overall project plan. Once the RMMM has been documented and the project has begun risk mitigation and monitoring steps commence. 4 29. What are the qualities team leaders should posses? Motivation, organization, ideas and innovation, problem solving, managerial identity, achievement, and influence and team building. 30. What is an agile team? Agile software development encourages customer satisfaction and early incremental delivery. Agile team Is a highly motivated project team which adopts informal methods, and overall development simplicity. 31. What are the categories of activities connected with measurement process? Formulation, Collection, Analysis, Interpretation and feedback. 31. What are the different measurable characteristics of an OO design? Size, complexity, coupling, sufficiency, completeness, cohesion, primitiveness, similarity, volatility. 32. What are the measures of software quality? Correctness, maintainability, integrity usability. 33. What is metrics evaluation?

Metrics evaluation focuses on the underlying reasons for the results obtained and produces a set of indicators that guide the project or process. 34. What is software quality assurance? Software quality assurance is a planned and systematic pattern of actions that are required to ensure high quality in software. 35. What is SQA group? SQA group consists of many different constituencies like software engineers, project managers, customers, salespeople and the individuals which are having software quality assurance responsibility. 36. What are the activities associated with SQA group? Planning, oversight, record keeping, analysis and reporting. 37. What are the different SCM features? Versioning, dependency tracking and change management, requirements tracing, configuration management, audit trails. 38. What are reactive risk strategies? Reactive strategy the software team does nothing about risks until something goes wrong. 39. What are the characteristics of software risks? Uncertainty and loss 5 40. What is software availability? Software availability is the probability that a program is operating according to requirements at a given point in time. 41. What are the management responsibilities regarding ISO 9001 requirements?

Management commitment, Customer focus, Quality policy, Planning, Responsibility, Authority, Communication, and Management review. 42. Define SPICE. SPICE (Software Process Improvement and Capability dEvelopement) standard defines a set of requirements for software process assessment. The intent of the standard is to assist organizations in developing an objective evaluation of the efficacy of any defined software process. 43. What is MALCOLM BALDRGE award? MALCOLM BALDRIGE award is the most prestigious quality award in the United States. The award is given annually to recognize U.S companies that exceed in quality management and quality achievement. 44. What are the ISO 9000 series of quality management standards? ISO 9000, ISO9001, ISO9002, ISO9003, ISO9003, ISO9004 45. Define CMM. The capability maturity model (CMM) for s/w is a widely accepted set of guidelines for developing high performance s/w organizations. 46. What are the capability levels defined in SPICE? Level0: Not performed, 1: Performed informally, 2: Planned and tracked, 3: Well defined, 4: Quantitatively controlled, 5: Continuously improving. 47. What are the types of accreditation? First party, Second party, Third party. 48. What are the components of the ISO 9000 series to which SPICE is related? ISO 9001, ISO 9000-3, ISO 9004-4., ISO DIS.

49. What is and assessment instrument? An assessment instrument is a tool, or set of tools, used during the performance of an assessment to assist the assessor in obtaining reliable, consistent and repeatable results. 50. What are the goals of SPICE project? 1. developing a working draft for a standard for software process assessment 2. conducting industry trials of the emerging standards. 3. promoting the technology transfer of software process assessment into the software industry world wide. 6 51. What are the benefits that an international standard will provide to industry? 1. Software suppliers will submit to just one process assessment scheme. 2. Software development organizations will have a tool to initiate and sustain a continuous process improvement 3. Programme managers will have a means to ensure that their software development is aligned with, and supports, the business needs of the organization. 52. What are the benefits of ISO 9000 verification? 1. Provides know-how for establishing a quality management system. 2. Certification has become the minimum requirement of quality for any tender. 3. It is a status symbol for the organizations. 4. Improves products and services. 5. Improves employee morale. 53. What are the events associated with quality management? Establishing, Documenting, Implementing, Maintaining, Continuously improving its effectiveness.

54. What are the documents required to implement quality management system in an organization? 1. Quality policy and quality objectives 2. Quality manual 3. Document to ensure the effective planning, operation and control of its processes 4. Records. 55. What are the pre-requisites for employees? Education, training, skill, experience 56. What are the requirement of internal auditing? 1. Set up an internal audit program 2. Develop an internal audit procedure 3. Plan internal audit procedure. 4. Perform regular internal audits 5. Take corrective action. 57. What are the different organizations to which the Malcolm Balridge award is given? 1. Manufacturing 2. Service 3.Small businesses 58. What are the different process maturity levels? 1. Initial 2. Repeatable 3. Defined 4. Managed

5. Optimizing 7 59. Who are the steps organizations has to take to improve their software capabilities?? 1. Understand the current status 2. Develop a vision of the desired process 3. Establish a list of process improvement actions. 4. Produce a plan to accomplish the required actions. 5. Commit the resources to execute theplans. 60. What are the requirements of ISO 9001: 2000 standard? 1. Demonstrate ability to consistently provide product that meets customer and applicable regulatory requirements. 2. Enhance customer satisfaction. 61. What are the different principles of software assessment? 1. Start with a process model 2. Observe strict confidentiality 3. Involve senior management 4. Keep an open mind and a level head 5. Focus on action 62. Who are the different inspection participants? 1. The moderator 2. The producers 3. The reviewers 63. Define software engineering process. The total set of software engineering activities needed to a users requirement into

software. 64. Define software process architecture. A framework within which project specific software process are defined 65. Define software process model. One specific embodiment of a software process architecture. 66. Define software process. The set of activities, methods, and practices that are used in the production and evolution of software. 67. What are the critical software process issues? Quality, product technology, Requirement instability and complexity. 68.What are the different process model views? Organizational view and Control and measurement view. 69. What are the drawbacks of water fall model? 1. It does not adequately address changes. 2. It assumes a relatively uniform and orderly sequence of development steps. 8 3. It does not provide for such methods as rapid prototyping or advanced languages. 70. What are the different levels of software process models? U process models, A process models and U process models 71. What are the different types of software tests? 1. Unit testing 2. Integration testing 3. Function testing 4. Regression testing

5. System test 72. Define testing. The process of executing a program with the intention of finding errors. 73. Define debugging. Diagnosing the precise nature of a known error and then correcting it. 74. What are integration tests. Integration tests verify the interfaces between system parts suchas modules, components and subsystems. 75. What are regression tests? Regression tests run a subset of previously executed integration and function tests to ensure that program changes have not degraded the system. 76. What are installation tests? Installation tests validate the instability and operability of the users system. 77. What are the major test plan elements? 1. Establish objectives for each test phase 2. Establish schedules and responsibilities for each test activity 3. Determine the availability of tools, facilities, and test libraries. 4. Establish the procedure and standards to be used for planning and conducting the tests and reporting the test results. 5. Set the criteria for test completion as well as for the success of each test. 78. What should be the qualities of assessment team members? The assessment team members should all be experienced software developers, and one or more should have experience in each phase of the software process.

79. What are the different risks associated with a software process? Schedule conflict, inadequate support and lack of follow through. 80. What are the basic objectives of inspections? 1. To find errors at the earliest 2. To ensure that the appropriate parties technically agree on the work. 9 3. To verify that the work meets predefined criteria. 4. To formally complete a technical task 5. To provide data on the product and the inspection process. 81. Why defect prevention is crucial to the software process? Finding and fixing errors accounts for much of the cost of software development and maintenance. Also the process of fixing defects is even more error prone than original software creation. 82. What are the principles of software defect prevention? 1. The programmers must evaluate their own errors 2. Feedback is essential part of defect prevention 3. There is no single cure all that will solve all the problems. 4. Process improvement must be an integral part of the process. 5. Process improvement takes time to learn. 83. What are the different steps of software defect prevention? Defect reporting, Cause analysis, action plan development, action implementation, performance tracking and starting over. 84. What are the different errors for which defect prevention analysis is required? Technological, Organizational, Historic, Group dynamic, Individual and others.

85. What are the different ways in which CMMI represents a process meta model? As a Continuous model and as a staged model 86. What is PSP? The personal software process emphasizes personal measurement of both the work product that is produced and the resultant quality of the work product. 87. What are the different framework activities defined by PSP model? Planning, High-level design, High level design-review, development and postmortem. 88. What is postmortem in PSP? Determining the effectiveness of the process using the measures and metrics is defined as postmortem. 89. What are the objectives of TSP? 1. Build self-directed teams that plan and track their work. 2. Show managers how to coach and motivate their teams. 3. Accelerate software process improvement 4. Provide improvement guidance to high maturity organizations. 5. Facilitate university teaching of industrial grade team skills. 10 90. What are the framework activities defined by TSP? Launch, high level design, implementation, integration, and test and postmortem. 91. What is cleanroom software engineering? The clean room process emphasizes rigor in specification and design, and formal verification of each design element using correctness proofs that are mathematical based. It also emphasizes statistical quality control. Cleanroom software engineering is a process

model that removes defects before they can precipitate serious hazards. 92. What are the tasks associated with cleanroom strategy? Increment planning, Requirements gathering, Box structure specification, Formal design, and Correctness verification. Code generation, inspection and verification, statistical test planning, Statistical use testing and certification. 93. What are the different boxed used in cleanroom software engineering? Black box, State box and Clear box 94. What is state box? The state box is a simple generalization of a state machine. The state box uses a data abstraction to determine the transition to the next state and the action that will occur as a consequence of the transition. 95. What are the different models require for cleanroom software engineering certification? 1. Sampling model 2. Component model 3. Certification model 96. What is object oriented systems development methodology? Object oriented systems development is a way to develop software by building self contained modules or objects that can be easily replaced, modified and reused. Furthermore, it encourages a view of the world as a system of cooperative and collaborating systems. 97. What are the reasons for the necessity of object orientation? 1. Higher level abstraction

2. Seamless transition among different phases of software development. 3. Encouragement of good programming technique. 4. Promotion of reusability 98. What is UML? Unified modeling language (UML) is intended to be a universal language for modeling systems, meaning that it can express models of many different kinds and purposes, just as a programming language or a natural language can be used in many different ways. 11 99. What are the different diagrams defined in UML? Class diagram, Use-case diagram, Behavior diagram, interaction diagram, sequence diagram, collaborative diagram, statechart diagram, activity diagram, implementation diagram, component diagram, deployment diagram. 100. What is classification? Classification is the process of checking to see if an object belongs to a category or a class. 16 MARKS 1. Explain Quality Function Deployment in detail. Introduction what is QFD? QFD team Benefits of QFD customer satisfaction, reduce implementation time, promotes team work, provides documentation House of quality effectiveness, advantages, importance to customer, target value, scale up factor, sales point QFD process Conclusion. 2. Describe in detail the standardization procedure of benchmarking. Introduction Definitions - Reasons for benchmarking Process function,

understanding performance, planning, internal benchmarking, competitive benchmarking, process benchmarking, learning from data, using the findings, Advantages of benchmarking Conclusion. 3. Explain how software quality assurance is ensured in a software firm. Quality concepts quality, quality control, quality assurance, cost of quality Software quality assurance- background issues, SQA activities Software reviews Cost impact of software defects, defect amplification and removal Formal technical reviews the review meeting, review reporting and record keeping, review guidelines, sample-driven reviews- Formal approaches to SQA Statistical SQA, Software reliability. 4. Explain the seven basic quality control tools in detail. Statistical process control- 7QC tools- check sheet graphs Histograms bar charts cause and effect diagrams Inter relationship diagrams control charts Definition, steps example and applications. 5. Explain software project management in detail. The management spectrum Effective project management focuses on 4 Ps the people, the product, the process, the project- people- the players, team leaders, the software team, coordination and communication issues the product Software scope, problem decomposition The process- melding the product and the process, problem decomposition The project W5 HH Principle Critical Practices risk management, empirical cost and schedule estimation, metric based project management, eaned value tracking, defect tracking, People aware

program management. 12 6. Explain how software quality assurance is ensured in a software firm Quality concepts quality, quality control, quality assurance, cost of quality Software quality assurance- background issues, SQA activities Software reviews Cost impact of software defects, defect amplification and removal Formal technical reviews the review meeting, review reporting and record keeping, review guidelines, sample-driven reviews- Formal approaches to SQA Statistical SQA, Software reliability. 7. What are the different software testing tactics? Explain. Testing fundamentals - Basis path testing flow graph notation, independent program paths, deriving test cases, graph matrices Control structure testing Black box testing Graph based testing method, equivalence partitioning, Boundary value analysis, Orthogonal array testing Object oriented testing methods White box testing Testing methods applicable at the class level Interclass test case design Testing for specialized environments, architectures, and applications _ Testing patterns. 8. Write detail notes on risk management. Reactive and proactive risk strategies software risks risk identification assessing overall project risks risk components and diagrams risk projection developing a risk table assessing risk impact risk refinement risk mitigation monitoring and management. 9. Write detail notes on ISO9000 series of quality management standards. The purpose of standards The ISO9000 series The contents of the standard

 seeking accreditation An assessment of the ISO9001 standard- ISO90003:notes for guidance on the application of ISO9001 to software development ISO9000-3 The impact of ISO9000 and TickIT- survey design Questionnaire format Impact of organization size upon uptake of third party accreditation Historical development of third party accreditation Reasons for not having external accreditation The effect of business type and size for organizations using QA procedures Reasons for developers seeking or not seeking an external QA standard

10. Account on CMM in detail. Introducing Software Process Maturity - The Evolution of the CMM, Immature versus Mature Software Organizations, Fundamental Concepts Underlying Process Maturity, Total Quality Management and the CMM, Customer Satisfaction, Benefits and Risks of Model-Based Improvement - The Software Process Maturity Framework - The Structure of the Capability Maturity Model Interpreting the CMM - Using the CMM - The Key Areas for Level 2: Repeatable - Process Areas for Level 3: Defined - The Key Process Areas for Level 4: Managed - The Key Process Areas for Level 5:Optimizing.. 13 11. Give a detail note on SPICE in detail. Principal goals SPICE document Capability levels not performed, performed informally, planned and tracked, well defined, quantitatively controlled, continuously improving Award categories leadership, strategic planning, customer and market focus, information and analysis, human source

focus, process management, business results Overview of award process Relationship to other international standards. 12. Write detailed notes on Malcolm Baldrige award. Categories of organizations Quality award Award criteria 13. Explain how software process assessment helps software organizations to improve themselves. Assessment overview Assessment phases Five assessment principles Start with a process model, observe strict confidentiality, involve senior management, keep an open mind and level head, focus on action The assessment process forming an assessment team, self assessment considerations, assessment ground rules, assessment team training, the on-site period Assessment conduct implementation consideration. 14. Explain the testing phase of software development in detail. Definitions testing, verification, validation, debugging The seven types of software tests Testing methods Software testing principles The axioms of testing The proper role of testing Types of software tests Unit testing Integration testing Function testing Regression testing System test Test planning The test files The success criteria Test development Test coverage techniques Test execution and reporting Test tools and methods Real-time testing The test organization. 15. Give detailed description about software process assessment. Assessment overview assessment phases Five assessment principles the assignment process assessment conduct implementation considerations.

16. Explain software inspections in detail. Types of reviews Inspection objectives basic inspection principles the conduct of inspections inspection training reports and tracking other considerations initiating an inspection program future directions. 17. Explain OO methodology in detail. OO system development Object basics OO system development life cycle Rumbaugh, Booch, Jacobson methodologies Patterns Frameworks OO analysis classification, identifying object relationships, attributes, and methods OO design designing classes, access layer, view layer Quality assurance system usability and measuring user satisfaction 14 18. Write detailed notes on the techniques for error cause analysis and defect prevention. Defect prevention not a new idea Why defect prevention is crucial to the software process The principles of software defect prevention The steps of software defect prevention - defect reporting error cause categories cause analysis The cause analysis meeting The action team Tracking action progress Prevention feedback - Process changes for defect prevention Defect prevention considerations The role of tools and technology The costs and benefits of defect prevention - Managements role. 19. Account on clean-room software engineering. The clean-room approach The clean-room strategy functional specification black-box, state-box and clear-box specifications clean-room design design refinement and verification advantages of design verification clean-room testing statistical use testing certification.

20. Write notes on TSP and PSP. Personal software process framework activities planning high-level design high-level design view development postmortem. Team software process framework activities launch High-level design implementation integration test postmortem.