IT-604 (B) · Software Engineering/Unsolved PYQ Paper
IT-604-B Software Engineering - Jun 2025 Question Paper
Under each question, How to answer lists the points an answer should cover, outlined by CampusPrep from the syllabus. Check the details against your textbook.
-
7 MarksaExplain iterative waterfall for software life cycle and discuss various activities in each phase.
How to answer
- Define iterative waterfall model and feedback loops between phases
- Explain phases: feasibility, requirements, design, coding, testing, maintenance
- List activities/deliverables in each phase
- Diagram of iterative waterfall with feedback paths
-
7 MarksbWhat are the necessities of life cycle model? Elaborate on the various issues of software life cycle.
How to answer
- Define need for life cycle model: visibility, control, quality, predictability
- Elaborate issues: requirement change, complexity, risk, maintenance, cost overrun
- Discuss phased vs evolutionary concerns
- Conclude with selection criteria
-
7 MarksaGive detail explanation about agile process.
How to answer
- Define Agile manifesto, values and principles
- Explain iterative-incremental delivery, sprints, roles
- Describe popular agile methods: Scrum, XP, Kanban
- Discuss applicability, benefits and limitations
-
7 MarksbWhat are the Extreme programming advantages?
How to answer
- Define Extreme Programming (XP) and its values
- List practices: pair programming, TDD, continuous integration, refactoring
- Explain advantages: quality, adaptability, customer satisfaction
- Note conditions for effectiveness
-
7 MarksaDiscuss on the various method encountered in cost estimation.
How to answer
- Define cost estimation need in project planning
- Discuss methods: expert judgment, analogy, Delphi, LOC, FP, empirical models
- Compare algorithmic vs non-algorithmic approaches
- Summarize selection factors
-
7 MarksbDescribe about the constructive cost model in detail.
How to answer
- Define COCOMO origin and purpose
- Explain Basic, Intermediate and Detailed COCOMO
- Give effort and schedule equations with cost drivers
- Discuss project modes: organic, semi-detached, embedded
-
7 MarksaState the advantages and disadvantages in LOC based cost estimation.
How to answer
- Define LOC-based estimation approach
- List advantages: simple, quantitative, automation
- List disadvantages: language dependent, poor for early estimation, penalizes conciseness
- Conclude with comparison to Function Points
-
7 MarksbExplain the ways and means for collecting the software requirements and how are they organized and represented?
How to answer
- List elicitation techniques: interviews, questionnaires, observation, prototyping
- Explain organization: categorization, prioritization, traceability
- Describe representation: SRS, use cases, DFD, ER diagrams
- Mention validation and negotiation
-
7 MarksaExplain the Feasibility studies. What are the outcomes? Does it have either implicit or explicit effects on software requirement collection?
How to answer
- Define feasibility study types: technical, economic, operational, legal
- List outcomes: feasibility report, go/no-go decision
- Explain implicit/explicit effect on requirements scope and prioritization
- Give example of requirement refinement after study
-
7 MarksbWhat is the prototyping technique? How prototype models are prepared for a software process? Discuss.
How to answer
- Define prototyping and its purpose in requirement validation
- Explain steps: quick design, build prototype, evaluate, refine
- Describe types: throwaway, evolutionary, incremental
- Discuss advantages and limitations
-
7 MarksaExplain a typical SRS structure and its parts.
How to answer
- Define SRS and IEEE standard structure
- Explain parts: introduction, overall description, specific requirements
- List characteristics of good SRS
- Mention importance for design and testing
-
7 MarksbJustify "Design is not coding and coding is not design".
How to answer
- Define design vs coding activities and abstraction levels
- Justify design as modeling decisions before implementation
- Explain why coding cannot replace design verification
- Give examples of design errors vs coding errors
-
7 MarksaWhat do you mean by Integration testing? Explain their outcomes.
How to answer
- Define integration testing and its objective
- Explain approaches: top-down, bottom-up, big-bang
- List outcomes: interface defects detected, verified interactions
- Mention stubs and drivers
-
7 MarksbWhat do you mean by System testing? Give a case study of a system testing for operating system?
How to answer
- Define system testing as end-to-end validation
- Describe types: functional, performance, security, recovery
- Present case study for OS: test plan, test cases, results
- Conclude with entry/exit criteria
-
7 MarksaExplain in detail about the maintenance process.
How to answer
- Define software maintenance and its need
- Explain types: corrective, adaptive, perfective, preventive
- Describe maintenance process: change request to release
- Discuss challenges and cost factors
-
7 MarksbWhat are the different activities in project planning?
How to answer
- Define project planning objectives
- List activities: estimation, scheduling, staffing, risk management
- Explain WBS, milestones and monitoring
- Mention tools: Gantt, PERT, CPM
Go to where you left off?
Quick Add to Notes
Save questions, your own notes and screenshots into notes filed by unit. It takes a free account.
Create free accountHave an account? Log in
Notes Panel