Q1 – The Selection of spiral model based on characteristics of requirements
(a) Are requirements easily understandable and defined?
(b) Do we change requirements quite often?
(c) Can we define requirements early in the cycle?
(d) Requirements are indicating a complex to be built
Choose the correct answer from the given options
(c) only
(b) only
(b) and (d) only
(a) and (c) only
(UGC NET DEC 2023)
Ans – (3)
Explanation – The Spiral Model is the recommended option in software development when projects face high levels of risk and complexity. Further, it combines the iterative nature of the Prototyping Model with the systematic aspects of the Waterfall model while focusing on a risk analysis in each phase.
The Spiral Model is a perfect choice when
- The requirements keep changing.
- The stakeholders or clients are not able to finalize the requirements in the initial process.
- The project will take several iterations or refinements, so it means (b).
The Spiral Model is good when
- In case of higher complexity and risk.
- Whenever new technologies and methodologies are incorporated.
- Whenever the assessment and evaluation of risks take place repeatedly throughout the entire project. This means (d) is validated.
Option (a)
The Spiral Model is not recommended when clear and well-defined requirements at the start of the project exist. Thus, a better choice would be the Waterfall Model or V-Model.
Option (c)
If requirements are known upfront, go with Waterfall. However, Spiral is for projects where requirements evolve through the length a little.
Q2 – The prototyping model has the sequence:
(a) Customer Evaluation
(b) Quick Design
(c) Requirements
(d) Implement
(e) Design
Choose the correct answer from the options given below:
(c) -> (a) -> (d) -> (b) -> (e)
(b) -> (c) -> (a) -> (d) -> (e)
(c) -> (b) -> (d) -> (a) -> (e)
(e) -> (b) -> (c) -> (d) -> (a)
(UGC NET DEC 2023)
Ans – (3)
Explanation – The Prototyping Model is iterative, and the prototype is built, tested, and later refined through user feedback before the final system is developed.
1. Take down requirements from customers.
2. Create a quick design (prototype) based on early requirements.
3. Implement a prototype and show it to the customer for evaluation.
4. The customer evaluates the prototype and provides feedback.
5. This feedback is used to modify the final design before the actual development starts.
Thus, the correct answer is option 3.
Q3 – Level-0 DFD is also called as:
Use Case diagram
Sequence diagram
Context diagram
Prototype diagram
(UGC NET DEC 2023)
Ans – (3)
Explanation – A Data Flow Diagram(DFD) is an illustration showing how data flows through a system. It contains different levels with varying detail of expression.
Level 0 DFD – Sometimes called a Context Diagram represents the entire system as a single process. It shows the external entities which are users and other systems and their interaction with the system. No internal process details.
An example of a very simple flow is that of a library management system wherein the “Library System” interacts with “Students” and “Librarians”
Level 1 DFD – This level breaks the single process mentioned in Level 0 into the main sub-processes and indicates major data flows between these processes.
Example – Issue Books; Return Books
Level 2 DFD – More particular information concerning each Level 1 process is supplied. Shows exact data storage and interactions.
An example is, verify student’s ID and check book availability for Issue books.
Level 3 DFD – Further breakdown of Level 2 subprocesses are required. This is usually required in case of a complex system.
Example – Verify student’s eligibility.
Q4 – Given below are two statements:
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.
In the light of the above statements, choose the most appropriate answer from the options given below:
Both Statement I and Statement II are correct.
Both Statement I and Statement II are incorrect.
Statement I is correct but Statement II is incorrect.
Statement I is incorrect but Statement II is correct.
(UGC NET DEC 2023)
Ans – (3)
Explanation – Statement I is correct. In the Reuse-Oriented Model, existing system components (or software modules) are altered to fit new requirements. This, therefore, shortens the time and costs of development.
Statement II is Incorrect. The Reuse-Oriented Model provides a way to integrate modified parts into the new system. In fact, integration is a crucial step of this model to ensure that the reused components interact within the new system.
Thus, the correct choice is option 3.
Q5 – Test suite is consist of:
Set of defect cases
Set of boundary cases
Set of test cases
Set of nest cases
(UGC NET DEC 2023)
Ans – (3)
Explanation – Set of test case refers to a condition that is specific in terms of verifying the expected performance of a software application under which a software tester can ascertain its expected behavior. A Test Suite, on the other hand, brings together a collection of multiple test cases to be executed systematically.
A test suite should contain a variety of test cases that address many aspects of that software under test. These can be
1. Defect cases,
2. boundary cases, and
3. regular test cases.
Option 3 is correct.
Q6 – The steps for analysis and design of object oriented system.
(A) Draw interaction diagrams
(B) Draw state chart and object diagram
(C) Draw use case and activity diagram
(D) Draw component and deployment diagram
(E) Draw class diagram
Choose the correct answer from the options given below :
(E)→(B)→(A)→(C)→(D)
(B)→(A)→(E)→(D)→(C)
(E)→(C)→(B)→(D)→(A)
(C)→(A)→(E)→(B)→(D)
(UGC NET DEC 2023)
Ans – (4)
Explanation – (C) Draw use case and activity diagram
The first step is talking about how requirements of the system are secured and how users will interact with the system.
Use case diagrams describe what functionalities a system should provide to different actors within a particular scope.
Activity diagrams describe the flow of activities to be executed.
(A) Draw interaction diagrams
Now that use cases have been defined, interaction diagrams (sequence and collaboration diagrams) will be developed to gain insight into how objects interact under varying scenarios.
(E) Draw class diagram
Following the definition of interactions comes the identification of objects and the relations to one another, thus leading into the class diagram, the backbone of object-oriented design.
(B) Draw state chart and object diagram
State chart diagrams describe how states are transformed by the internal objects whereas the object diagrams describe the object instances with respect to some scenario.
(D) Draw component and deployment diagram
Finally, this is where the focus is on the implementation, the drawing-up of component diagrams (software components) and deployment diagrams (physical system architecture).