All mock tests are FREE till 31 December — register to save your progress
Paper 2 CS · UNIT 06 · MOCK TEST

Mock 4 – Requirements & Software Design (Part 2)

Unit 6: Software Engineering · 24 questions · about 28 minutes. Press End Mock any time to see your score and the correct answers.

All 15 topic-wise mocks in this unit
0 / 24 answered 00:00
Q1.
Cohesion is an extension of:
Q2.
Level – 0 DFD is also called as:
Q3.
Given two statements:
Assertion A: Validity checks real need of system users
Reason R: Completeness checks system user defined requirements
In the light of the above statements, choose the correct answer:
Q4.
Which of the following is not a Non-functional requirement?
Q5.
If every requirement can be checked by a cost-effective process, then SRS is called
Q6.
The process to gather the software requirement from client, analyze and document is known as
Q7.
A good software requirement specification does NOT have the characteristic
Q8.
The Software Requirement Specification (SRS) is said to be ________ if and only if no subset of individual requirements described in it conflict with each other.
Q9.
Let n1 be the number of requirements for which all reviewers have identical interpretations and n2 be the total number of requirements. Which of the following is used to determine the specificity of the requirements?
Q10.
Which one of the following statements, related to the requirements phase in Software Engineering, is incorrect?
Q11.
Requirements prioritisation and negotiation belongs to:
Q12.
The prototyping model has the sequence:
(A) Customer Evaluation
(B) Quick design
(C) Requirements
(D) Implement
(E) Design
Q13.
Statement (I): In Reuse Oriented Model, Modification of the old system parts appropriate to the new requirements.
Statement (II): In Reuse Oriented Model, Integration of the modified parts are not possible into the new systems.
Q14. Which document outlines the functional and non-functional requirements of a software system?
Q15. Which of the following cohesions are better than the Procedural Cohesion?
A. Functional Cohesion
B. Sequential Cohesion
C. Temporal Cohesion
D. Communicational Cohesion
E. Logical Cohesion
Choose the correct answer from the options given below:
Q16. Which of the following is NOT a requirement elicitation technique?
Q17. Arrange the following in increasing order of coupling, from lowest coupling to highest coupling.
A. Common Coupling
B. Stamp Coupling
C. Control Coupling
D. External Coupling
E. Content Coupling
Choose the correct answer from the options given below:
Q18. Find the correct sequence of the prototype software development model.
A. Start
B. Develop Prototype
C. Deliver to customer
D. Quick Design
E. Quick Plan
Choose the correct answer from the options given below:
Q19. In Software Engineering, Jackson's principles are based on
A. Designation
B. Definitions
C. Refutable Assertions
D. Formal Review
E. Requirement Elicitation
Choose the correct answer from the options given below:
Q20. Which one of the following is NOT a part of requirement management?
Q21. The characteristics of modern (modular) programming are:
A. Each module should do only one thing.
B. Communication between modules is allowed only by a calling module.
C. Communication can take place directly between modules that do not have a calling–called relationship.
D. All modules are designed as single-entry, single-exit systems using control structures.
Choose the correct answer from the options given below:
Q22. Arrange the following steps of the Feature Driven Development (FDD) process in the correct sequence:
(A) Develop an overall model
(B) Build by feature
(C) Plan by feature
(D) Design by feature
(E) Build a feature list
Choose the correct answer from the options given below:
Q23. Which of the following are typical activities in the software process lifecycle?
(A) Requirement Analysis
(B) System Design
(C) Code Refactoring
(D) Deployment
(E) Substructure
Choose the correct answer from the options given below:
Q24. Match List I (software design principles) with List II (Definition)
List IList II
(A) Cohesion(I) Degree to which one module relies on another module.
(B) Coupling(II) Dividing a software system into distinct modules.
(C) Abstraction(III) Degree to which elements of a module belong together.
(D) Modularity(IV) Simplifying complex reality by modelling classes appropriate to the problem.