Q1: Why do we need metrics? (2 marks)
Answer: Metrics give better insight into the state of a process or product. They indicate potential problems but are not the problems themselves. Software engineers collect measures, develop metrics, and derive indicators.
Q2: Degree of Rigor? (2 marks)
Answer: The degree of rigor determines the set of tasks to be performed in a project. It can be categorized as:
- Casual
- Structured
- Strict
- Quick Reaction
Q3: Uses of Control Chart (3 marks)
Answer: Control charts determine whether trends are statistically valid and which changes are meaningful. Types include:
- Moving Range Control Chart
- Individual Control Chart
Q4: Effect of bug fixes on software quality (5 marks)
Answer: Defect repair/maintenance supports the release functionality specification and may involve fixing bugs or enhancing performance. Proper defect management improves software quality.
Q5: Effort validation (2 marks)
Answer: Ensure that no more than the allocated number of staff members are scheduled at any time during the project.
Q6: Flexibility vs Maintainability (3 marks)
Answer:
- Flexibility: Ease of expanding the product with new features.
- Maintainability: Ease of fixing bugs and adding minor features.
They are different aspects determined by architecture and code quality.
Q7: Effect of decreasing spoilage on maintainability (3 marks)
Answer: Spoilage cost measures the cost to correct defects after release. Decreasing spoilage indicates improved maintainability.
Q8: Define “Baseline Data”
Answer: Baseline data is collected from past projects, cleaned, and stored in a database. It is used for estimation, process improvement, and performance analysis.
Q9: Differentiate between Casual and Structured Rigor (2 marks)
Answer:
- Casual: Minimum tasks, reduced documentation, basic SE principles followed.
- Structured: Complete framework applied with all tasks, SQA, SCM, documentation, and measurements.
Q10: Can we guarantee 100% risk-free software? (5 marks)
Answer: No. Software development always involves risk. Not taking action is also a risk. Risk can be mitigated through careful planning and the ability to undo mistakes.
Q11: ILFs vs EIFs (3 marks)
Answer: Both are user-identifiable groups of data.
- ILF: Holds data maintained by the application.
- EIF: Holds data referenced but maintained by another application.
Q12: What is Risk Projection?
Answer: Risk projection estimates and rates risks based on likelihood and consequences. Steps include:
- Establish a likelihood scale
- Delineate consequences
- Estimate impact
- Note overall accuracy of projection
Q13: Can a logical file be counted as both ILF and EIF?
Answer: No. A logical file satisfying both rules is counted as an ILF only.
Q14: Role of interdependency and time allocation in project schedule
Answer:
- Interdependency: Determine tasks that must occur sequentially or in parallel.
- Time Allocation: Assign work units and start/end dates based on dependencies and resources.
Numerical / Diagram Questions
Q15: Draw a moving range control chart
Given Data: Project: 1 2 3 4 5
Data: 4 3 1 3 5
Answer:
| Project | Value | Range (difference from previous) |
| 1 | 4 | – |
| 2 | 3 | 1 |
| 3 | 1 | 2 |
| 4 | 3 | 2 |
| 5 | 5 | 2 |
- Plot values on Y-axis vs Project on X-axis.
- If points are within control limits (±2σ or ±3σ), process is stable.
- In this case, range variations are small → process is stable.
Q16: Lack of Ambiguity Calculation
Given: Nf = 25, Nnf = 5, Nui = 10
Formula (typical):
Lack of Ambiguity=NfNf+Nnf+Nui=2525+5+10=2540=0.625\text{Lack of Ambiguity} = \frac{Nf}{Nf + Nnf + Nui} = \frac{25}{25 + 5 + 10} = \frac{25}{40} = 0.625Lack of Ambiguity=Nf+Nnf+NuiNf=25+5+1025=4025=0.625
Q17: Factors in deciding to develop from scratch or use 3rd party software
Answer: Consider:
- Cost of development vs cost of acquisition
- Time to market
- Reliability of third-party components
- Maintenance and flexibility
- Integration with existing systems
Q18: Product stability based on defect/fix graph
Answer: If the gap between defects reported and defects fixed is increasing → Product is unstable.