Software Engineering NTA UGC NET Question Analysis PART2
Software Engineering NTA UGC NET Question Analysis PART2
i ➥ 3,1,2,4
ii ➥ 3,1,4,2
iii ➥ 4,3,2,1
iv ➥ 2,4,1,3
i ➥ Path Testing
ii ➥ Integration Testing
i ➥ Sun-way TaihuLight
ii ➥ Titan
iii ➥ Piz Daint
iv ➥ Sequoia
i ➥ K-Mean method
ii ➥ Self Organizing feature map method
iii ➥ K-nearest neighbor method
i ➥ Zigbee
ii ➥ Bluetooth
iii ➥ Wi-Fi
iv ➥ GSM/CDMA
i ➥ only I
ii ➥ only II
iii ➥ both I and II
iv ➥ neither I nor II
i ➥ 28,16,000
ii ➥ 20,90,000
iii ➥ 26,95,000
iv ➥ 27,50,000
i ➥ 11.2 months
ii ➥ 12.2 months
iii ➥ 13.2 months
iv ➥ 10.2 months
i ➥ Only S1 and S2
ii ➥ Only S3
iii ➥ All of S1, S2 and S3
iv ➥ Only S1
i ➥ Adapter
ii ➥ Decorator
iii ➥ Delegation
iv ➥ Proxy
i ➥ 96.3%
ii ➥ 97.3%
iii ➥ 98.3%
iv ➥ 99.3%
i ➥ 25 person months
ii ➥ 75 person months
iii ➥ 62.5 person months
iv ➥ 72.5 person months
i➥n1/n2
ii ➥ n 2 / n 1
iii ➥ n 1 + n 2
iv ➥ n 1 – n 2
i ➥ iterative model
ii ➥ prototype model
iii ➥ spiral model
iv ➥ waterfall model
i ➥ 4k – 1
ii ➥ 4k
iii ➥ 4k + 1
iv ➥ 2 k – 1
i ➥ Robustness
ii ➥ Correctness
iii ➥ Reliability
iv ➥ Accuracy
i ➥ 1 + (S 3 / S 1 )
ii ➥ 1 – (S 3 / S 1 )
iii ➥ 1 + (S 1 / S 3 )
iv ➥ 1 – (S 1 / S 3 )
i ➥ Requirement analysis
ii ➥ Risk analysis
iii ➥ Design
iv ➥ Coding
i➥P+1
ii ➥ P – 1
iii ➥ P – 2
iv ➥ P + 2
i ➥ Accuracy
ii ➥ Reliability
iii ➥ Correctness
iv ➥ Robustness
i ➥ Loosely coupled hardware on tightly coupled software and disk sharing, respectively.
ii ➥ Tightly coupled hardware on loosely coupled software and shared memory, respectively
iii ➥ Tightly coupled software on loosely coupled hardware and message passing, respectively
iv ➥ Loosely coupled software on tightly coupled hardware and file sharing, respectively.
i ➥ Pareto analysis is a statistical method used for analyzing causes, and is one of the primary tools
for quality management
ii ➥ Reliability of a software specifies the probability of failure-free operation of that software for a
given time duration.
iii ➥ The reliability of a system can also be specified as the Mean Time To Failure (MTTF)
iv ➥ In white-box testing, the test cases are decided from the specifications or the requirements
i ➥ Error leads to failure but fault is not related to error and failure.
ii ➥ Fault leads to failure but error is not related to fault and failure.
iii ➥ Error leads to fault and fault leads to failure.
iv ➥ Fault leads to error and error leads to failure.
i ➥ Prototyping
ii ➥ Iterative
iii ➥ Time-boxing
iv ➥ Glass-boxing
i ➥ Inheritance
ii ➥ Polymorphism
iii ➥ Encapsulation
iv ➥ Abstraction
i ➥ refers to the set of activities that ensure that software correctly implements a specific function
ii ➥ gives answer to the question – Are we building the product right ?
iii ➥ requires execution of software
iv ➥ both (A) and (B)
i ➥ Consistency
ii ➥ Conciseness
iii ➥ Efficiency
iv ➥ Accuracy
i ➥ Requirements validation
ii ➥ Requirements elicitation
iii ➥ Feasibility study
iv ➥ Requirements reviews
i ➥ Top-down approach
ii ➥ Complementary of Abstraction concept
iii ➥ Process of elaboration
iv ➥ All of the above
i ➥ Validation testing
ii ➥ Integration testing
iii ➥ Regression testing
iv ➥ System testing
i ➥ Waterfall model
i ➥ Abstraction concept
ii ➥ Refinement concept
iii ➥ Information hiding concept
iv ➥ Modularity
Which one from the following is highly associated activity of project planning?
i ➥ The PVM communication model provides asynchronous blocking send, asynchronous blocking
receive, and non-blocking receive function.
ii ➥ Message buffers are allocated dynamically.
iii ➥ The PVM communication model assumes that any task can send a message to any other PVM
task and that there is no limit to the size or number of such messages.
iv ➥ In PVM model, the message order is not preserved.