AL-403 · Software Engineering/Unsolved PYQ Paper
AL-403 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 MarksaDifferentiate between software product characteristics and software process characteristics.
How to answer
- Define software product characteristics (correctness, reliability, usability, efficiency, maintainability, portability).
- Define software process characteristics (understandability, visibility, supportability, acceptability, reliability, robustness, rapidity, maintainability).
- Compare focus: product = outcome qualities vs process = development activity qualities.
- Give examples and relationship between process quality and product quality.
-
7 MarksbExplain the Linear Sequential Model and discuss its advantages and disadvantages.
How to answer
- Define Linear Sequential Model / Waterfall with sequential phases.
- Explain phases: requirements, design, implementation, testing, maintenance.
- List advantages: simple, disciplined, documentation oriented.
- List disadvantages: inflexible, late working product, poor handling of change.
- Diagram of waterfall flow.
-
7 MarksaWhat is the Component Assembly Model? How does it differ from the Incremental Model?
How to answer
- Define Component Assembly / Component-Based Development model and reusable components.
- Explain steps: component identification, qualification, adaptation, assembly, testing.
- Define Incremental Model with increments and deliveries.
- Compare on reusability, development approach, cost, time, flexibility.
-
7 MarksbExplain the purpose of process customization and improvement with reference to CMM.
How to answer
- Define process customization: tailoring standard process to project needs.
- Define process improvement: continuous enhancement of capability.
- Explain CMM 5 maturity levels and KPAs.
- Explain role of assessment, measurement and improvement cycle.
-
7 MarksaDescribe functional and non-functional requirements with examples.
How to answer
- Define functional requirements: what system does.
- Define non-functional requirements: quality constraints.
- Give examples: login, calculation vs performance, security, usability.
- Summarize differences in tabular form.
-
7 MarksbWhat are the major requirement elicitation techniques? Discuss any two in detail.
How to answer
- List major elicitation techniques: interviews, questionnaires, workshops, observation, prototyping, brainstorming.
- Explain any two in detail with steps.
- Discuss merits and limitations.
- Mention selection criteria for technique.
-
7 MarksaExplain use case modeling with the help of an example.
How to answer
- Define use case, actor, scenario, use case diagram elements.
- Explain steps to build use case model.
- Give example e.g., ATM / Library with actors and use cases.
- Mention include, extend relationships and diagram.
-
7 MarksbWhat are the key contents of a Software Requirement Specification (SRS) document?
How to answer
- Define SRS purpose and IEEE 830 structure.
- List contents: introduction, overall description, specific requirements, appendices.
- Explain functional, non-functional, interface, performance requirements sections.
- Mention characteristics of good SRS.
-
7 MarksaDescribe any four fundamental software design principles.
How to answer
- List principles: abstraction, modularity, information hiding, separation of concerns, coupling-cohesion, etc.
- Describe any four with meaning.
- Give small example for each.
- Explain impact on maintainability and reusability.
-
7 MarksbExplain the SA/SD approach to function-oriented design.
How to answer
- Define SA/SD: Structured Analysis and Structured Design.
- Explain DFD, data dictionary, ERD in analysis.
- Explain structure chart, modular decomposition in design.
- Explain transformation from DFD to structure chart with example.
-
7 MarksaWhat are architectural views? Briefly describe different architectural styles.
How to answer
- Define architectural views: logical, process, physical, development (4+1).
- Define architectural style concept.
- Briefly describe styles: layered, client-server, pipe-filter, MVC, microservices.
- Compare applicability with examples.
-
7 MarksbWhat are the key design metrics used to evaluate software design quality?
How to answer
- Define design metrics purpose for quality assessment.
- List metrics: coupling, cohesion, complexity, fan-in/fan-out, LOC.
- Explain cyclomatic complexity, CK metrics briefly.
- Explain how metrics indicate maintainability and testability.
-
7 MarksaDifferentiate between static and dynamic code analysis.
How to answer
- Define static analysis: without execution, code review, inspections.
- Define dynamic analysis: with execution, testing, profiling.
- Compare on technique, defects found, tools.
- Give examples of tools for each.
-
7 MarksbDescribe the black-box testing technique with an example.
How to answer
- Define black-box testing: testing without internal knowledge.
- Explain techniques: equivalence partitioning, boundary value, decision table.
- Give example with test cases.
- Mention advantages and limitations.
-
7 MarksaWhat is Software Configuration Management (SCM)? Describe its major activities.
How to answer
- Define SCM: control of software evolution and configuration items.
- List activities: identification, version control, change control, auditing, status accounting.
- Explain each activity briefly.
- Mention tools e.g., Git.
-
7 MarksbExplain software project feasibility analysis and its types.
How to answer
- Define feasibility analysis purpose in project planning.
- Explain types: technical, economic, operational, legal, schedule.
- Explain cost-benefit analysis, feasibility report.
- Give example of evaluation criteria.
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