| 61. | A software project was estimated at 352 Function Points (FP). A four person team will be assigned to this project consisting of an architect, two programmers, and a tester. The salary of the architect is Rs.80,000 per month, the programmer Rs.60,000 per month and the tester Rs.50,000 per month. The average productivity for the team is 8 FP per person month. Which of the following represents the projected cost of the project? |
| a. | Rs.28,16,000 |
| b. | Rs.20,90,000 |
| c. | Rs.26,95,000 |
| d. | Rs.27,50,000 |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (d).Rs.27,50,000
|
| 62. | Complete each of the following sentences in List-I on the left hand side by filling in the word or phrase from the List-II on the right hand side that best completes the sentence: List-I List-II I. Determining whether you have built the right system is called ............. A. Software testing II. Determining whether you have built the system right is called ......... B. Software verification III. ............ is the process of demonstrating the existence of defects or providing confidence that they do not appear to be present. C. Software debugging IV. .......... is the process of discovering the cause of a defect and fixing it. D. Software validation Codes: I II III IV |
| a. | B D A C |
| b. | B D C A |
| c. | D B C A |
| d. | D B A C |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (d).D B A C
|
| 63. | A software company needs to develop a project that is estimated as 1000 function points and is planning to use JAVA as the programming language whose approximate lines of code per function point is accepted as 50. Considering a=1.4 as multiplicative factor, b=1.0 as exponention factor for the basic COCOMO effort equation and c=3.0 as multiplicative factor, d=0.33 as exponention factor for the basic COCOMO duration equation, approximately how long does the project take to complete? |
| a. | 11.2 months |
| b. | 12.2 months |
| c. | 13.2 months |
| d. | 10.2 months |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (b).12.2 months
|
| 64. | Which of the following is used to determine the specificity of requirements ? (A) n1/n2 (B) n2/n1 (C) n1+n2 (D) n1–n2 Where n1 is the number of requirements for which all reviewers have identical interpretations, n2 is number of requirements in a specification. |
| a. | A |
| b. | B |
| c. | C |
| d. | D |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (a).A
|
| 65. | The major shortcoming of waterfall model is |
| a. | the difficulty in accommodating changes after requirement analysis. |
| b. | the difficult in accommodating changes after feasibility analysis. |
| c. | the system testing. |
| d. | the maintenance of system. |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (a).the difficulty in accommodating changes after requirement analysis.
|
| 66. | The quick design of a software that is visible to end users leads to ............ |
| a. | iterative model |
| b. | prototype model |
| c. | spiral model |
| d. | waterfall model |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (b).prototype model
|
| 67. | For a program of k variables, boundary value analysis yields .............. test cases. |
| a. | 4k – 1 |
| b. | 4k |
| c. | 4k + 1 |
| d. | 2k – 1 |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (c).4k + 1
|
| 68. | The extent to which a software performs its intended functions without failures, is termed as |
| a. | Robustness |
| b. | Correctness |
| c. | Reliability |
| d. | Accuracy |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (c).Reliability
|
| 69. | An Operating System (OS) crashes on the average once in 30 days, that is, the Mean Time Between Failures (MTBF) = 30 days. When this happens, it takes 10 minutes to recover the OS, that is, the Mean Time To Repair (MTTR) = 10 minutes. The availability of the OS with these reliability figures is approximately : |
| a. | 96.97% |
| b. | 97.97% |
| c. | 99.009% |
| d. | 99.97% |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (d).99.97%
|
| 70. | Match each software lifecycle model in List – I to its description in List – II: List – I List – II I. Code-and-Fix a. Assess risks at each step; do most critical action first. II. Evolutionary prototyping b. Build an initial small requirement specifications, code it, then “evolve” the specifications and code as needed. III. Spiral c. Build initial requirement specification for several releases, then design-and-code in sequence IV. Staged Delivery d. Standard phases (requirements, design, code, test) in order V. Waterfall e. Write some code, debug it, repeat (i.e. ad-hoc) Codes : I II III IV V |
| a. | e b a c d |
| b. | e c a b d |
| c. | d a b c e |
| d. | c e a b d |
| View Answer Report Discuss Too Difficult! Search Google |
|
Answer: (a).e b a c d
|
