Subject Name & Code : Software Engineering & 23CSN110

Class: III Year CSE (Networks) Sem : II Academic Year: 2025-26

ASSIGNMENT – I

[Link] Reg. No Set no.

1 23691A4002 - 23691A4009 Set -1

2 23691A4010 - 23691A4016 Set -2
3 23691A4017 - 23691A4023 Set -3
4 23691A4024 - 23691A4030 Set -4
5 23691A4031 - 23691A4038 Set -5
6 23691A4039 - 23691A4045 Set -6
7 23691A4047 - 23691A4054 Set -7
8 23691A4055 - 23691A4061 Set -8
9 23691A4062 - 23691A4066 Set -9
10 24695A4001- 24695A4006 Set -10
 SET-1 CO BL
Q1. A software project has an estimated duration of 12 months and a
budget of $500,000 using the Waterfall model. If switching to Agile
reduces the project duration by 20% but increases resource costs by 10%, 1 4
analyze and calculate the new project duration and budget. Discuss the
trade-offs involved in adopting Agile over Waterfall.
Q2. Requirements for a system change by 10% every 2 months due to
evolving stakeholder needs. Analyze how this volatility affects project
2 3
scope and calculate the estimated increase in total development time if
each 10% change adds 4 weeks to the schedule.
SET-2 CO BL
Q1. A risk matrix categorizes project risks in different phases of the Spiral
and Incremental models. Given estimated risk mitigation costs for each
phase, analyze which model offers better cost-efficiency in managing 1 4
risks. Provide a comparison of total mitigation costs and explain the
implications on project success.
Q2. A system consists of 5 modules. Each module requires 10 functional
and 5 non-functional requirements to be specified. Calculate the total
2 3
number of requirements and analyze how this volume impacts the
complexity of requirement management.
SET-3 CO BL
Q1. A Scrum team plans to complete a backlog of 50 user stories in sprints
lasting 2 weeks each. If the team completes 5 user stories per sprint,
calculate how many sprints are required and estimate total project
1 4
duration. Analyze how a 20% increase in team velocity would affect the
schedule.

Q2. Studies show 40% of software defects originate from poor

requirement specifications. Given a 1,000-line codebase with an average
defect density of 0.5 defects per 100 lines, calculate the estimated number 2 3
of defects caused by requirement issues and analyze the importance of
clear requirements.
SET-4 CO BL
Q1. After implementing CMMI Level 2, a software company reduces
defect rates from 15% to 8%. Calculate the percentage decrease in defects
and analyze how this improvement affects product quality and customer 1 4
satisfaction.

Q2. A requirements traceability matrix indicates that 85% of requirements

have corresponding test cases. Calculate the percentage of missing
2 3
coverage and analyze risks associated with incomplete traceability in
testing.
SET-5 CO BL
Q1. Agile’s adaptive process requires 30% more time in meetings but
results in 25% fewer post-release defects compared to traditional models.
Analyze the overall time efficiency by calculating if the extra meeting time 1 4
is justified by the reduction in defect-fixing effort post-release.

Q2. Each iteration of requirement elicitation takes 2 weeks, followed by a

3-week stakeholder feedback cycle. Over 4 iterations, calculate the total 2 3
time needed to finalize requirements and analyze the impact on project
timelines.

SET-6 CO BL
Q1. A software project delivers functionality incrementally, with each
increment providing 25% of the total features. Calculate the number of
increments needed to complete the system and analyze how this approach 1 4
helps manage project risks.

Q2. Ambiguous requirements cause 25% of the requirements engineering

effort to be spent on rework. If the initial effort is estimated at 400 hours,
2 3
calculate the additional hours needed and analyze the consequences on
project scheduling.
SET-7 CO BL
Q1. Project milestones have different probabilities of delay: 10% for the
design phase, 15% for development, and 5% for testing. Analyze how
these probabilities affect the expected project completion date under 1 4
different software process models.

Q2. An entity-relationship diagram (ERD) has 20 entities, with each entity

having an average of 3 relationships. Calculate the total number of
2 3
relationships in the system and analyze the complexity this introduces in
database design.
SET-8 CO BL
Q1. Moving from a traditional development process to Dynamic Systems
Development Method (DSDM) increases communication overhead by
20%. Calculate the additional time spent on communication and analyze 1 4
its effect on project efficiency, assuming total development time is 1,000
hours.
Q2. A system behavioral model has 10 states; adding 5 new states
increases complexity and validation time. Calculate the percentage
2 3
increase in states and discuss how this affects testing and system
maintenance.
SET-9 CO BL
Q1. In the Crystal methodology, communication overhead grows
quadratically with team size. Calculate and analyze the relative
1 4
communication overhead for teams of sizes 3, 7, and 12, and discuss
implications for team scalability.
Q2. Requirement validation takes 15 hours out of a total 120-hour
requirements engineering phase. Calculate the percentage of time spent on 2 3
validation and analyze its significance in reducing downstream defects.
SET-10 CO BL
Q1. Defect discovery rates differ between Waterfall and Agile models,
with Agile detecting 60% of defects in early phases while Waterfall
1 4
detects 30%. Analyze and calculate the difference in early defect detection,
discussing the impact on overall project quality and cost.
Q2. After finalizing the Software Requirements Specification (SRS), three
major requirement changes occur, each requiring 10 days of rework.
2 3
Calculate the total rework time added to the schedule and analyze how late
requirement changes affect project cost and delivery.