Q1[3 Marks]The Software Process
Why do we need to perform requirement analysis and refinement during requirement engineering process? Explain the spiral model of software development. Why is it preferred in high-risk projects?
ENCT 352Bachelor in Computer Engineering · Semester 61 Paper Available
Software Engineering
Past examination question papers and complete curriculum syllabus for Software Engineering (ENCT 352), Bachelor in Computer Engineering Semester 6 under Institute of Engineering (IOE), Tribhuvan University.
Sem 6 Subjects (6)View Full Semester Overview →
ENCE 356Engineering EconomicsENCT 351Artificial IntelligenceENCT 352Software EngineeringENCT 353Simulation and ModelingENCT 354Minor ProjectENCT 385-399Elective II
Past Question Papers (PDF)
Switch tabs to view different exam papersNote: This question paper file (5th sem) was archived from an IOE exam session for the common Software Engineering curriculum.
5th-sem_Software Engineering.pdf
IOE Past Examination Paper
Served via fast CDN. Read in full view or download for offline study.
Document information: This past examination paper is identified as an IOE/TU academic document and was cataloged from a public Google Drive archive. This independent website did not create the examination paper and is not affiliated with TU or IOE.
Rights holders can request correction or removal by emailing subeshgaming@gmail.com with this page URL and supporting details.
Most Frequently Asked Questions
Top recurring IOE board exam questions for Software Engineering with verified mark schemes, formula notation, and recurrence frequency.
Showing 40 of 40 top repeated questions
9 Chapters · Click any chapter to expand
·
Year-wise & Session-wise Exam Papers
Complete questions from each exam session (Regular & Back exams from 2082 to 2069) for Software Engineering. Click any session paper to expand.
Showing 311 questions across 22 exam session papers
Institute of Engineering • 2083 Baishakh Board Examination
Q2[4 Marks]Architectural Design
Explain provided and required interfaces in a software component with example.
Q3[4 Marks]System Modeling
Draw the use case diagram for the following system.
In an online food delivery system where the customer order food and make payment from the Fonepay by providing the necessary information. Food delivery system validates the payment and processes the order to deliver. The delivery person takes the order and ship to the customer address. The customer receipts the order and acknowledges the food ordering system.
Q4[6 Marks]System Modeling
Design level 0 and level 1 DFD for the case study given below.
Suppose a buses garage repairs wants to develop automation system that helps to maintain their records. In the garage, buses come for repairs. A mechanic and helper perform the repair, record the reason for the repair and record the total cost of all parts used on a shop repair order. Information on labor, parts and repair outcome is used for billing by the accounting department, parts monitoring by the inventory management computer system and a performance review by the supervisor.
Q5[2 Marks]Coding and Testing
Why end-user can’t perform white-box testing? Compare integration testing and incremental integration testing.
Q6[3 Marks]Introduction
Justify this statement “Software doesn't wear out like hardware components”.
Q7[3 Marks]Software Requirements Engineering
Why do we need to do feasibility study before accepting any project? Differentiate between functional and non-functional requirement with example.
Q8[1 Marks]The Software Process
What is software architecture? Why architecture is important to drive software development? Explain multi-tier architecture with example.
Q9[2 Marks]Recent Trends
Differentiate between hard real time system and soft-real time system.
Q10[4 Marks]Introduction
What are the benefits and risks of software reuse?
Q11[3 Marks]Coding and Testing
Differentiate between verification and validation with examples. What type of system are validated using the formal methods and why?
Q12[4 Marks]Recent Trends
What is COCOMO? Calculate COCOMO effort, development time in calendar month, average staffing and productivity for project of application program that is estimated to be 49,200 lines of code.
Q13[2 Marks]Coding and Testing
What is the significance of "the vital few" in statistical SQA? How the Formal Technical Review help to enhance quality of a product? Why do we prefer lower value of Fan-In for any function in a program as software metric? Explain.
Q14[6 Marks]Software Configuration Management
Describe the staged CMMI model with levels and key process areas. Differentiate version and variants in the context of configuration management.
Curriculum Syllabus & Course Topics
Sourced from TU curriculum portalChapter-wise Units & Micro-Syllabus Topics (9 Units)
1. Introduction
- 1.1Software and software engineering
- 1.2Nature and characteristics of software
- 1.3Software application domains
- 1.4Legacy software
- 1.5Software crisis
- 1.6Software myths
- 1.7Software engineering practice: Essence of practice, general principles
2. The Software Process
- 2.1Process framework and umbrella activities
- 2.2Traditional (Plan-driven) process models
- 2.2.1Waterfall model and its extensions
- 2.2.2Incremental process model
- 2.2.3Evolutionary process models (Prototyping, spiral)
- 2.3Agile and adaptive process models
- 2.3.1Agile manifesto and the 12 principles
- 2.3.2Agile versus plan-driven development
- 2.3.3Scrum framework (Roles, artifacts, ceremonies)
- 2.3.4Extreme programming (XP) practices
- 2.3.5Lean software development
- 2.4Model selection considerations
3. Software Requirements Engineering
- 3.1Requirement engineering process
- 3.2SRS (Structure, characteristics, users)
- 3.3Functional and non-functional requirements
- 3.4Gathering requirements using use cases modeling and scenarios
- 3.5Agile requirements engineering
- 3.5.1User stories and acceptance criteria
- 3.5.2Product backlog creation and prioritization
- 3.5.3Story mapping basics
- 3.5.4Continuous requirements refinement (Backlog grooming)
4. Architectural Design
- 4.1Introductions and importance
- 4.2Architectural design principles
- 4.3Taxonomy of architectural styles
- 4.4Modular design, cohesion and coupling
5. System Modeling
- 5.1System modeling
- 5.1.1Need for system modeling
- 5.1.2Role of abstractions in managing complexity
- 5.2Process modeling using DFD
- 5.3Scenario-based analysis
- 5.3.1Concept of scenarios
- 5.3.2Use-case descriptions and diagrams
- 5.4Behavioral and structural modeling
- 5.4.1Activity diagrams
- 5.4.2Class-based modeling
6. Coding and Testing
- 6.1Coding standards and guidelines
- 6.2Code review
- 6.2.1Code walkthrough
- 6.2.2Code inspection
- 6.2.3Cleanroom technique
- 6.3Software testing fundamentals
- 6.3.1Verification and validation
- 6.3.2Unit testing
- 6.3.3Integration testing
- 6.3.4System testing
- 6.3.5Acceptance testing
- 6.4Black-box and white-box testing approach
- 6.5Agile testing practices
- 6.5.1Test-driven development (TDD)
- 6.5.2Continuous testing
- 6.5.3Automated unit testing basics
- 6.5.4Refactoring for code quality
7. Software Quality, Assurance, Maintenance
- 7.1Quality concepts
- 7.2Quality attributes
- 7.3Reviews, inspections and QA concepts
- 7.4ISO standards, CMMI levels
- 7.5Software maintenance and its types
- 7.6Maintenance effort and lifecycle considerations
8. Software Configuration Management
- 8.1Software configuration management
- 8.2Version control and continuous integration
- 8.3Change management process
- 8.4Branching strategies (Git-flow basics)
9. Recent Trends
- 9.1DevOps and continuous deployment pipelines
- 9.2Continuous integration/continuous delivery (CI/CD) in modern projects
- 9.3Cloud-native, microservices architectures and infrastructure as code (IaC)
- 9.4AI-assisted software development
- 9.5Low-code/no-code, green software engineering
Examination Scheme & Marks Distribution
Evaluation Structure
- Final Board Theory Exam: 60 Marks (Pass mark: 24)
- Internal Assessment: 40 Marks (Pass mark: 16)
- Practical / Lab Exam: 25 or 50 Marks (Continuous lab evaluation + viva, where applicable)
* This is the general current IOE 60/40 scheme; verify course-specific details in the syllabus above.
Exam Preparation Guidelines
- Review the available past examination paper to understand question styling, typical derivation topics, and marks allocation.
- Practice writing clean algorithms and code implementations, tracing dry runs with sample inputs, and explaining complexity trade-offs.
- Structure answers with labeled diagrams, concise bullet points, and highlight final answers in numerical solutions.
Authentic IOE Past Papers
Free Direct PDF Download
Curriculum Syllabus & Marking Scheme