JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY HYDERABAD
JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY HYDERABAD B.Tech III Year SOFTWARE ENGINEERING Previous Question Paper (March - 2024 - R18)
Note: i) Question paper consists of Part A, Part B. ii) Part A is compulsory, which carries 25 marks. In Part A, Answer all questions. iii) In Part B, Answer any one question from each unit. Each question carries 10 marks.
PART - A
What do you mean by software myths?
Answer
Software myths are erroneous beliefs or misconceptions held by managers, customers, and practitioners regarding software development, processes, and products. These myths often originate from the early days of computing and persist despite evidence to the contrary, leading to unrealistic expectations and poor decision-making.
- Management Myths: These include the belief that adding more programmers to a late project will make it faster (Brooks' Law) or that a set of general objectives is sufficient to begin development without detailed requirements.
- Customer Myths: These involve the assumption that software requirements change easily and that such changes are inexpensive, or that once the code is written, the work is finished.
- Practitioner Myths: These center on the idea that coding is the most important part of software engineering or that the only deliverable is the working program, ignoring the necessity of documentation and maintenance.
Software myths are dangerous because they create false expectations, lead to inadequate planning, and result in projects that fail to meet quality or schedule targets.
What is process assessment, and how is it conducted in software engineering?
Answer
Process assessment is a systematic evaluation of an organization's software development processes against a defined model or standard. Its primary objective is to determine the current maturity or capability level of these processes, identify strengths and weaknesses, and provide a roadmap for continuous improvement.
The assessment process is typically conducted through the following structured steps:
- Preparation and Planning: Defining the scope of the assessment, identifying the specific projects or organizational units to be evaluated, and selecting an appropriate assessment model such as CMMI (Capability Maturity Model Integration) or ISO/IEC 15504 (SPICE).
- Data Collection: Gathering evidence through various methods, including interviews with key stakeholders, document reviews (e.g., project plans, requirement specifications, test logs), and direct observation of development activities.
- Data Analysis: Comparing the collected evidence against the criteria established by the chosen process model. Assessors evaluate whether the processes are performed, managed, defined, and quantitatively controlled.
- Rating and Reporting: Assigning maturity levels or capability ratings based on the findings. The final report highlights process gaps, identifies risks, and provides actionable recommendations for process improvement to enhance software quality and productivity.
- Feedback and Follow-up: Communicating the findings to the management and development teams to foster a culture of improvement and to track the implementation of corrective actions.
What are structured methods in the context of system modelling?
Answer
Sign in to view the complete answer paper.
How do requirements management tools and techniques facilitate the organization and tracking of requirements throughout the software development lifecycle?
Answer
Sign in to view the complete answer paper.
How does UML facilitate the representation and visualization of software architectures?
Answer
Sign in to view the complete answer paper.
How do class diagrams depict relationships and interactions among classes in a system?
Answer
Sign in to view the complete answer paper.
What do you understand by equivalence partitioning in software testing?
Answer
Sign in to view the complete answer paper.
Differentiate between validation testing and verification testing in software engineering.
Answer
Sign in to view the complete answer paper.
Define software reliability.
Answer
Sign in to view the complete answer paper.
Define software quality assurance and its role in software development processes.
Answer
Sign in to view the complete answer paper.
PART - B
Discuss incremental process models and provide examples of their application in real-world projects. Compare and contrast personal and team process models in software development.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
What are evolutionary process models, and how do they differ from traditional approaches like the waterfall model? Explain how process models facilitate collaboration and communication among project stakeholders.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Define functional and non-functional requirements in software engineering. Provide examples of each. Write a software requirement specification document for the Android to-do list application.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
What role does validation play in ensuring the correctness and completeness of software requirements? Discuss different validation techniques. What is a feasibility study, and why is it conducted during the requirements engineering process? Discuss the key factors considered in a feasibility study.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Explain the design process in software engineering. What are the key phases involved, and how do they contribute to the overall development lifecycle? Discuss the role of software architects in defining and implementing architectural designs.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Describe the design model in software engineering. How does it serve as a blueprint for implementing and maintaining software systems? Describe basic structural modelling techniques in UML.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Compare and contrast black-box and white-box testing techniques. Provide examples of scenarios where each technique would be most appropriate. Evaluate the effectiveness of using cyclomatic complexity as a metric for measuring the complexity of source code.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Describe common debugging techniques and strategies for identifying and fixing software defects efficiently. Define software quality metrics and explain why they are essential for assessing the overall quality of software products.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Define software measurement and explain its importance in the software development process. Discuss the differences between reactive and proactive risk management strategies. Provide examples of situations where each strategy would be most appropriate.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.
Explain the concept of Risk Mitigation, Monitoring, and Management (RMMM) in software engineering. Discuss the benefits of conducting FTRs and the roles of stakeholders involved.
Answer
Sign in to view the complete answer paper.
Answer
Sign in to view the complete answer paper.