True / false
1. The cost of change after release of software is comparatively less than before
release.
///correct line more expensive after release
false
2. In location, we ask a set of questions that establish technical structure of the
problem.
True
[Link] plan-driven process personnel succeed on structure and order.
True
[Link] does not "deteriorate" but "wearing our"
False.
5. Most software continuing to be custom built.
True.
6. Microsoft word in an example of system software.
False.
7. The Developers can change, add, or remove the Sprint Backlog Hems after the
Sprint Planning meeting has ended, often in consultation with the Product Owner.
True
8. If we get behind schedule in n software development, we can add more
programmers and catch up.
False.
9. Until we get the program "running," we have no way of assessing its quality.
False.
10. Waterfall model addresses the maximum risk at the later stages of software
development.
True.
11. In iterative development, the products are visible at the early stage of
development.
True.
12. XP includes the development team to be located in remote place.
False.
13. In DSDM, functionalities are fixed in respect of varied time and recourses.
False.
14. Sprint review meeting takes place at the beginning of the sprint process.
False.
15. In Incremental development, once the development of an increment starts, the
relevant requirements are frozen.
True.
Part-B
Multiple Choice Question
16 Which model doesn't allow defining requirements early in the cycle?
a Waterfall
b. Prototyping
c. Iterative waterfall
d. Scrum
17. Waterfall model is not suitable for?
a. Small Projects b. Complex Projects c. Accommodating changes d. None
18. Which of the following is the most important phase of the Software
Development Life Cycle (SDLC)?
a. Requirements analysis b. Coding c. Testing d. Designing
19. Which of the following is not a named phase in the software development life
cycle?
a Assessment
b, Maintenance
development
d. Testing
Matching Questions: Match the Testing type of pert 4 questions with the equivalent
please of 'V-model' of software development as given in the following list
(A) Architectural Desiga (B) Component Design
(C) Code Generation (D) Requirements Modeling
20 Acceptance Testing
21. Integration Testing
22. System Testing
23. Unit Testing
24. Which prioritization decides the urgency of the requirements development?
(a) Must have b. Should have c. Could have d. Want to have but won’t have
25. The functionality is "important, but project does not rely on it" sets the priority
of
(a) Must have b. Should have c. Could have d. Want to have but won’t have
26 Which of the following is mandated in FDD7
(A) Workshop b. Code Inspection c. User interface prototyping d. Moscow rules
Matching Questions: In case of SCRUM, match the roles given in the following list (A-
D) with the tasks/
characteristics written in the nest 4 questions:
(A) Seram Master (B) Product Owner (C) Scrum Team (D) Management
Matching Questions: In case of SCRUM, match the roles given in the following list (A-
D) with the tasks/
characteristics written in the next 4 questions:
(A) Seram Master
(B) Product Owner
(C) Scrum Team
(D) Management
27. Makes the final decisions of the tasks related to product Backlog
29. Ensures that the project is carried through according to the practices, values
and rules of Scrum.
28. Sets the goals
30. Has the authority to decide on the necessary actions and to organize itself in
order to achieve the goals of each Sprint.
Part - C
Descriptive Questions
Answer any TWO out of Three Questions in the Answer Script
31. In FDD, what is a Feature? Write the template of a Feature with examples. How
is the feature team selected and organized in Feature-Driven-Development?
32. Explain Baselining with importance in Requirements specification and
management? How do you motivate your development team who are new to use
Scrum process model. Explain the answer in accordance with scrum principle.
33. What are the key differences between Agile process and Plan Driven Process?
What does Agile propose when Scope cannot be completed in given Timebox'? And
why? How does 80-20 rule can be applied in the whole project as well as in an
iteration?
-
Sample question 2
25. ___ is a process of testing the individual units or components.
Answer: (C) Unit Testing
26. Which of the following is applicable to Linear Sequential Model of development?
Answer: (B) Requirement first Development Cycle
27. Which one of the following models is not an example of a linear process model?
Answer: (D) Spiral
28. What is SRS?
Answer: (A) Software Requirements Specification
29. ___ is used for Product Backlog item estimation.
Answer: (D) Sprint Backlog
30. Which prioritization technique arranges the requirements according to priority?
Answer: (A) MoSCoW
31. What is the primary goal of Requirement Analysis?
Answer: (C) Development of a feature
32. Matching Questions: Match the 5 phases of development in agile with the Agile
methodologies given in the below options.
Phases:
Planning
Analysis
Design and Prototype
Testing
Evaluation & Release
Options: (A) DSDM
(B) XP
(C) FDD
(D) DSDM
📝 Since DSDM is mentioned twice and the exact match format isn't provided clearly
in the image, this one may require clarification. But generally, DSDM (Dynamic
Systems Development Method) supports all five phases in an iterative way. XP
(Extreme Programming) emphasizes design, coding, testing and feedback. FDD
(Feature Driven Development) focuses on feature planning, design, and
building.
So a possible match:
Planning → DSDM
Analysis → FDD
Design and Prototype → XP
Testing → XP
Evaluation & Release → DSDM
Q1. (Any Two of Three)
a) Elaborate on MoSCoW prioritization in context to DSDM and Explain
with diagram. How does 80:20 rule apply here?
Answer: MoSCoW prioritization helps in managing requirements by categorizing
them into four types:
Must Have: Essential for system success.
Should Have: Important but not vital.
Could Have: Desirable but not necessary.
Won’t Have (this time): Agreed to be left out for now.
In DSDM, this is used to prioritize the product backlog and maintain project control.
80:20 Rule in MoSCoW:
Only 60% Must Have requirements should be allowed.
Remaining 20% should be Should and Could.
This gives room to adjust scope while ensuring delivery of vital features.
Diagram (Text-based Format):
matlab
CopyEdit
+-------------------+
| MoSCoW Priorities |
+-------------------+
| Must Have - 60% |
| Should Have - 20% |
| Could Have - 20% |
| Won’t Have - 0% |
+-------------------+
b) Differentiate between Prototyping and Evolutionary Model of SDLC with
diagram.
Answer:
Aspect Prototyping Model Evolutionary Model
Build a quick prototype to Gradual refinement of system
Goal
understand user needs through iterations
Customer
High during prototype validation High throughout the process
Involvement
Prototype discarded after final System evolves with each
Flexibility
system developed iteration
Use Case Good for unclear requirements Good for large, complex systems
Diagram:
Prototyping:
sql
CopyEdit
Requirements → Prototype → Feedback → Refine → Final System
Evolutionary:
sql
CopyEdit
Iteration 1 → Iteration 2 → Iteration 3 → ... → Final Product
c) Explain the 4 values and 12 principles of Agile Manifesto.
Answer:
4 Values:
1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
12 Principles:
1. Customer satisfaction through early and continuous delivery
2. Welcome changing requirements
3. Deliver working software frequently
4. Business and developers work together
5. Build projects around motivated individuals
6. Face-to-face conversation is best
7. Working software is the primary measure of progress
8. Maintain constant pace indefinitely
9. Continuous attention to technical excellence
[Link] is essential
[Link] architectures emerge from self-organizing teams
[Link] reflect to become more effective
Q2. (Compulsory)
a) How do we manage Product Backlog in Agile Scrum Development? What
are the SPRINT processes in detail with the ROLES in Scrum explained.
Answer:
Product Backlog Management:
Product Owner maintains the Product Backlog.
Items are prioritized by business value.
Grooming sessions ensure backlog is refined.
SPRINT Processes:
1. Sprint Planning – Decide what to build this Sprint.
2. Daily Scrum – 15-minute standup to sync.
3. Sprint Execution – Development work happens.
4. Sprint Review – Demonstrate what was built.
5. Sprint Retrospective – Improve next sprint.
Scrum Roles:
Product Owner – Defines the backlog and priorities.
Scrum Master – Facilitates Scrum process and removes blockers.
Development Team – Builds and delivers the product.
Q3. (Any One of Two)
a) What are the key differences between Agile process and Plan Driven
Process? What does Agile process favor: Scope control or completed goals
in Timboxes? And why?
Answer:
Plan Driven
Aspect Agile Process
Process
Flexibility High, embraces change Low, resists change
Detailed upfront
Planning Iterative, just-in-time planning
planning
Minimal, focused on working Extensive
Documentation
software documentation
Delivery Incremental Big-bang at end
Team Formal
Close, daily interaction
Collaboration communication
**Agile favors scope control in timeboxes:
Timeboxes (fixed-duration Sprints) are prioritized.
Scope can be adjusted within the timebox.
This supports flexibility, early delivery, and feedback.
b) Write the drawbacks of waterfall model.
Answer:
1. Inflexible – Cannot handle changing requirements.
2. Late Testing – Issues are found too late.
3. No Working Software Until Late – Users can’t validate early.
4. Poor Risk Management – All risks handled after planning.
5. Customer Involvement Low – Only at the beginning and end.