AKTU 2023 -24 session Previous year question’s solution

SECTION A

1. Define the term Software Engineering.

Answer: Software Engineering is the systematic application of engineering principles to the

development, operation, and maintenance of software. It involves the use of methodologies,
tools, and techniques to ensure that software is reliable, efficient, and meets user
requirements.

2. Discuss the various characteristics of software.

Answer:

• Functionality: The software must perform its intended functions correctly.

• Reliability: The software should operate consistently under specified conditions.
• Usability: The software should be user-friendly and easy to navigate.
• Efficiency: The software should make optimal use of system resources.
• Maintainability: The software should be easy to modify and update.
• Portability: The software should be able to run on different platforms without
modification.

3. Explain the need of an SRS.

Answer: A Software Requirements Specification (SRS) is crucial because it:

• Provides a clear and detailed description of the software to be developed.

• Serves as a contract between stakeholders and developers, ensuring mutual
understanding.
• Helps prevent misunderstandings and scope creep during development.
• Facilitates validation and verification processes to ensure the final product meets
requirements.

4. Explain stubs and drivers.

Answer:

Stubs: These are dummy modules used in top-down integration testing to simulate the
behavior of lower-level modules that have not yet been developed.

Drivers: These are dummy modules used in bottom-up integration testing to simulate the
behavior of higher-level modules that call the lower-level modules.

5. Discuss LOC? List two advantages and disadvantages of LOC.

Answer:
LOC (Lines of Code): A metric used to measure the size of a software program by counting the
number of lines in the source code.

Advantages:

• Simple to measure and understand, providing a quick estimate of project size.

• Useful for estimating development effort and project timelines.

Disadvantages:

• Does not account for code quality or complexity, potentially misleading project
assessments.
• Can incentivize writing more lines of code rather than focusing on efficient and
maintainable code.

6. What is Pseudo Code? How it differs from Algorithm?

Answer:

Pseudo Code: A high-level description of an algorithm that uses the structural conventions of
programming languages but is intended for human reading rather than machine execution.

Difference from Algorithm: An algorithm is a step-by-step procedure for solving a problem,

while pseudo code is a way to express that algorithm in a readable format that is not bound
to specific syntax.

7. Describe the importance of white box testing.

Answer: White box testing is important because it:

• Allows testers to verify the internal workings of the software, ensuring that all code
paths are tested.
• Helps identify hidden errors and optimize code performance.
• Ensures that the software meets its design specifications and functions correctly.

8. Explain Error, Fault and Failure.

Answer:

Error: A human action that produces an incorrect result, often due to a misunderstanding or
mistake.

Fault: A defect in the software that can cause an error when executed.

Failure: The manifestation of a fault in the software when it does not perform as expected,
leading to incorrect results or behavior.

9. List any two reasons for increase in the software costs.

Answer:
Complexity of Requirements: As software requirements become more complex, the cost of
development increases due to the need for more resources and time.

Maintenance Needs: Ongoing maintenance and updates can significantly add to the overall
cost of software, especially if the software is not designed for easy modification.

10. Discuss the need of Risk Management in software engineering.

Answer: Risk Management is essential in software engineering because it:

• Identifies potential risks that could impact the project, allowing for proactive
measures.
• Helps in planning and implementing strategies to mitigate risks, reducing the likelihood
of project failure.
• Ensures project success by minimizing the impact of unforeseen issues and
maintaining project timelines and budgets.

SECTION B

1. Illustrate the statement “Software engineering is layered technology.”

Answer: Software engineering is described as layered technology because it consists of several

layers that build upon each other to create a comprehensive framework for software
development. The layers include:

Process Layer: Defines the framework for software development processes, including
methodologies like Agile, Waterfall, etc.

Methods Layer: Provides the techniques and practices for software development, such as
requirements gathering, design, coding, and testing.

Tools Layer: Includes software tools that assist in the development process, such as IDEs,
version control systems, and testing tools.

Quality Assurance Layer: Ensures the quality of the software through testing, reviews, and
validation processes.

2. Discuss the importance of Feasibility Study. Also discuss its various types.

Answer:
A Feasibility Study is important because it:

• Assesses the viability of a project before significant resources are committed, helping
to avoid costly failures.
• Identifies potential challenges and risks that could impact the project.
• Provides stakeholders with a clear understanding of the project's potential benefits
and drawbacks.
 • Types of Feasibility Studies:

• Technical Feasibility: Evaluates whether the technology needed for the project is
available and can be implemented.
• Economic Feasibility: Analyzes the cost-effectiveness of the project, including cost-
benefit analysis.
• Operational Feasibility: Assesses whether the project can be integrated into the
existing operational environment and whether users will accept it.

3. Explain Code Inspection, Formal Technical Reviews (Peer Reviews) and Walk Through
in detail.

Answer:

• Code Inspection: A formal review process where the code is examined by a team of
peers to identify defects, ensure adherence to standards, and improve code quality. It
involves a structured process with defined roles and responsibilities.
• Formal Technical Reviews (Peer Reviews): A structured review process involving peers
who evaluate the software product to ensure it meets requirements and standards. It
includes preparation, review meetings, and follow-up actions.
• Walk Through: An informal review process where the author of the code presents it
to a group for feedback and discussion. It allows for collaborative input and is less
structured than formal inspections.

4. Write a short note on: Mutation testing, Alpha & Beta testing, Regression testing.

Answer:

• Mutation Testing: A testing technique that involves modifying the program's code in
small ways (mutations) to evaluate the effectiveness of test cases. If the test cases can
detect the mutations, they are considered effective.
• Alpha Testing: A type of acceptance testing performed by internal staff at the
developer's site. It aims to identify bugs before the software is released to external
users.
• Beta Testing: A type of acceptance testing conducted by a limited number of external
users in a real-world environment. It helps gather feedback and identify issues before
the final release.
• Regression Testing: A type of testing that ensures that recent changes or
enhancements to the software have not adversely affected existing functionality. It
involves re-running previously completed tests.

5. What do you mean by the term software re-engineering? Why is it required?

Answer Software re-engineering refers to the process of examining and altering existing
software systems to reconstitute them in a new form. It is required to:
 • Improve performance and maintainability of legacy systems that may be outdated or
inefficient.
• Adapt the software to new requirements or technologies, ensuring it remains relevant.
• Extend the life of software systems by updating them to meet current standards and
practices.

SECTION C

1. Explain Software Quality Attributes in detail.

Answer:Software Quality Attributes are critical characteristics that determine the overall
quality and effectiveness of software. Understanding these attributes helps in designing and
developing software that meets user expectations and industry standards. Key attributes
include:

Performance:

• Refers to how well the software responds to user inputs and processes data.
• Measured in terms of response time, throughput, and resource utilization.
• Important for applications requiring real-time processing, such as gaming or financial
systems.

Reliability:

• The ability of the software to perform its intended functions under specified conditions
for a specified period.
• Measured by metrics such as mean time to failure (MTTF) and mean time to repair
(MTTR).
• High reliability is crucial for mission-critical applications, such as healthcare systems.

Usability:

• The ease with which users can learn and use the software.
• Involves user interface design, accessibility, and user experience (UX).
• Usability testing is often conducted to gather feedback from real users.

Security:

• The ability of the software to protect against unauthorized access and data breaches.
• Involves implementing authentication, authorization, encryption, and secure coding
practices.
• Security testing is essential to identify vulnerabilities and ensure data integrity.

Maintainability:
 • The ease with which the software can be modified to correct defects, improve
performance, or adapt to changes.
• Measured by the time and effort required to make changes.
• High maintainability reduces long-term costs and improves software longevity.

Portability:

• The capability of the software to run on different platforms or environments without

requiring significant changes.
• Involves considerations for operating systems, hardware, and software dependencies.
• Portability testing ensures that the software functions correctly across various
environments.

Scalability:

• The ability of the software to handle increased loads or accommodate growth without
performance degradation.
• Important for applications expected to grow in user base or data volume.
• Scalability can be achieved through architectural design, such as microservices or
cloud-based solutions.

Interoperability:

• The ability of the software to interact and operate with other systems or software
applications.
• Involves the use of standard protocols and data formats to facilitate communication.
• Critical for enterprise applications that need to integrate with existing systems.

2. Explain SDLC. Also discuss various activities during SDLC.

Answer: SDLC (Software Development Life Cycle) is a structured process that outlines the
stages involved in developing software applications. It provides a systematic approach to
software development, ensuring quality and efficiency. The main phases of SDLC include:

Requirement Analysis:

• Involves gathering and analyzing requirements from stakeholders, including users,

clients, and business analysts.
• Techniques such as interviews, surveys, and workshops are used to elicit requirements.
• The output is a Software Requirements Specification (SRS) document that outlines
functional and non-functional requirements.

Design:

• The design phase translates requirements into a blueprint for the software.
 • Involves creating architectural designs, user interface designs, and detailed design
specifications.
• Design models such as UML diagrams may be used to visualize system components
and interactions.

Implementation:

• The actual coding of the software takes place in this phase.

• Developers write code based on the design specifications using programming
languages and development tools.
• Version control systems are often used to manage code changes and collaboration
among team members.

Testing:

• Involves verifying that the software meets the specified requirements and is free of
defects.
• Various testing methods are employed, including unit testing, integration testing,
system testing, and acceptance testing.
• Testing ensures that the software is reliable, functional, and ready for deployment.

Deployment:

• The software is released to users after successful testing.

• Deployment may involve installation, configuration, and training for end-users.
• Feedback is gathered from users to identify any issues or areas for improvement.

Maintenance:

• Ongoing support and updates are provided to address defects, enhance features, and
adapt to changing requirements.
• Maintenance activities include corrective maintenance (fixing bugs), adaptive
maintenance (modifying for new environments), and perfective maintenance
(improving performance).

Documentation:

• Throughout the SDLC, documentation is created to capture requirements, design

decisions, testing results, and user manuals.
• Proper documentation is essential for knowledge transfer, maintenance, and future
development.

3. Explain Requirement Elicitation techniques in detail.

Answer:Requirement elicitation is the process of gathering requirements from

stakeholders to ensure that the software meets their needs. Various techniques are employed
to effectively elicit requirements:
Interviews:

• Conducting one-on-one or group interviews with stakeholders to gather detailed

information about their needs and expectations.
• Allows for in-depth discussions and clarification of requirements.
• Can be structured (with predefined questions) or unstructured (open-ended
discussions).

Surveys/Questionnaires:

• Distributing structured forms to collect information from a larger audience.

• Useful for gathering quantitative data and opinions from a diverse group of
stakeholders.
• Can include multiple-choice questions, rating scales, and open-ended questions.

Workshops:

• Facilitating collaborative sessions with stakeholders to discuss and prioritize

requirements.
• Involves brainstorming techniques to generate ideas and reach consensus on
requirements.
• Encourages active participation and engagement from stakeholders.

Observation:

• Observing users in their natural environment to understand their workflows and

identify requirements based on real-world usage.
• Helps uncover implicit requirements that users may not articulate.
• Useful for understanding user interactions with existing systems.

Prototyping:

• Creating mock-ups or prototypes of the software to gather feedback and refine

requirements based on user interactions.
• Allows stakeholders to visualize the software and provide input on design and
functionality.
• Can be low-fidelity (paper sketches) or high-fidelity (interactive digital prototypes).

Document Analysis:

• Reviewing existing documentation, such as business plans, user manuals, and system
specifications, to identify requirements.
• Helps in understanding the context and background of the project.
• Useful for gathering historical data and insights.

Use Cases and User Stories:

 • Developing use cases or user stories to describe how users will interact with the
software.
• Use cases outline specific scenarios, while user stories capture user needs in a simple
format.
• Helps in understanding user goals and system interactions.

4. Compare SEI CMM Model and ISO 9000 Model. Also discuss five levels of CMM.

Answer:

SEI CMM Model (Software Engineering Institute Capability Maturity Model):

• A framework for assessing and improving software development processes.

• Focuses on process maturity and provides a roadmap for continuous improvement.
• Emphasizes the importance of defined processes and practices in achieving high-
quality software.

ISO 9000 Model:

• A set of international standards for quality management systems.

• Emphasizes meeting customer requirements and continuous improvement.
• Applicable to various industries, not limited to software development.

Comparison:

• Focus: CMM focuses specifically on software development processes, while ISO 9000
applies to broader quality management practices.
• Structure: CMM is structured in maturity levels, while ISO 9000 provides guidelines for
establishing a quality management system.
• Implementation: CMM emphasizes process improvement, while ISO 9000 emphasizes
compliance with quality standards.

Five Levels of CMM:

Level 1 - Initial: Processes are unpredictable and reactive. Success depends on individual
efforts rather than defined processes.

Level 2 - Managed: Processes are planned and executed in accordance with policy. Projects
are tracked and controlled, leading to more predictable outcomes.

Level 3 - Defined: Processes are well-defined and standardized across the organization. Best
practices are established, and there is a focus on process improvement.

Level 4 - Quantitatively Managed: Processes are measured and controlled using quantitative
techniques. Performance is predictable, and data is used to manage processes.
Level 5 - Optimizing: Focus on continuous process improvement through incremental and
innovative technological improvements. Organizations strive for excellence and adapt to
changing environments.

5. Explain the term Cohesion and Coupling? Also explain the various forms of cohesion
and coupling?

Answer:

Cohesion: Refers to how closely related and focused the responsibilities of a single module
are. High cohesion is desirable as it indicates that a module performs a single task or a group
of related tasks effectively.

Forms of Cohesion:

• Functional Cohesion: All elements contribute to a single, well-defined task. This is the
highest and most desirable form of cohesion.
• Sequential Cohesion: Elements are grouped because the output from one part is the
input to another, creating a sequence of operations.
• Communicational Cohesion: Elements operate on the same data or contribute to the
same output, but do not necessarily perform the same task.
• Temporal Cohesion: Elements are grouped by their timing of execution, meaning they
are executed at the same time but may not be related in functionality.
• Procedural Cohesion: Elements are grouped because they always follow a certain
sequence of execution, but they may not be related in purpose.
• Coincidental Cohesion: Elements are grouped arbitrarily, with little or no relationship.
This is the lowest form of cohesion and should be avoided.
• Coupling: Refers to the degree of interdependence between modules. Low coupling is
desirable as it indicates that modules can operate independently, making the system
more modular and easier to maintain.

Forms of Coupling:

• Content Coupling: One module directly accesses the content of another, leading to
high interdependence. This is the worst form of coupling.
• Control Coupling: One module controls the behavior of another by passing control
information, leading to some level of dependency.
• Data Coupling: Modules share data through parameters, but do not share control
information. This is a desirable form of coupling.
• Stamp Coupling: Modules share a composite data structure, but use only a part of it.
This can lead to unnecessary dependencies.
• Message Coupling: Modules communicate through message passing, leading to low
interdependence. This is the best form of coupling and promotes modularity.
 6. Explain software metric? Also explain the various metrics for the size estimation of
a project.

Answer: Software metrics are quantitative measures used to assess various attributes of
software development and maintenance processes, helping to evaluate quality, performance,
and efficiency.

Importance:

• Quality Assurance: Identifies defects and areas for improvement.

• Project Management: Aids in estimating timelines, costs, and resource allocation.

• Process Improvement: Highlights bottlenecks and inefficiencies.

• Performance Measurement: Ensures software meets user expectations.

Metrics for Size Estimation of a Project

1. Lines of Code (LOC):

• Definition: Counts the number of lines in the source code.

• Usage: Estimates project size and effort.

• Advantages: Simple to measure.

• Disadvantages: Does not reflect code quality.

2. Function Points (FP):

• Definition: Measures functionality based on user requirements.

• Usage: Assesses software size based on inputs, outputs, and user interactions.

• Advantages: Language-independent and focuses on functionality.

• Disadvantages: Requires detailed requirement analysis.

3. Use Case Points (UCP):

• Definition: Estimates size based on use cases.

• Usage: Considers complexity of use cases and technical environment.

• Advantages: Relevant for user-centered design.

• Disadvantages: Needs detailed use case documentation.

4. Story Points:

• Definition: Estimates effort for implementing user stories in Agile.

• Usage: Relative measure of complexity and effort.

 • Advantages: Encourages team collaboration.

• Disadvantages: Subjective and varies between teams.

5. Object Points:

• Definition: Estimates size based on the number of objects, classes, and

methods in object-oriented software.

• Usage: Measures complexity of object-oriented systems.

• Advantages: Relevant for object-oriented development.

• Disadvantages: May require detailed design documentation.

7. A program reads an integer number within the range [1,100] and determines
whether it is a prime number or not. Design test cases for this program using BVC,
robust testing, and worst-case testing methods.

Answer:

Boundary Value Cases (BVC):

Test with inputs:

• 1 (not prime)
• 2 (prime)
• 3 (prime)
• 50 (not prime)
• 99 (not prime)
• 100 (not prime)

Robust Testing:

• Test with inputs:

• 0 (invalid input)
• 101 (invalid input)
• -5 (invalid input)
• 50.5 (invalid input)

Worst-Case Testing:

Test with inputs:

• 97 (largest prime number within the range)

• 99 (largest non-prime number within the range)
• 50 (a non-prime number)
 • 73 (a prime number)

8. What is Integration Testing? Explain different approaches used for integration

testing.

Answer:
Integration Testing is a phase in software testing where individual modules are combined and
tested as a group to ensure they work together correctly. It helps identify interface defects
and ensures that integrated components function as expected. Different approaches include:

Top-Down Integration Testing:

• Testing starts from the top of the module hierarchy and progresses downwards.
• Higher-level modules are tested first, while lower-level modules are simulated using
stubs.
• Allows early detection of design flaws and interface issues.

Bottom-Up Integration Testing:

• Testing starts from the bottom of the hierarchy and moves upwards.
• Lower-level modules are tested first, while higher-level modules are simulated using
drivers.
• Useful for validating the functionality of lower-level components before integrating
them into higher-level modules.

• Big Bang Integration Testing:

• All modules are integrated at once and tested together.

• This approach can make it difficult to isolate defects, as multiple

components are tested simultaneously.

• Often used in smaller projects where the number of modules is

limited.

• Incremental Integration Testing:

• Modules are integrated and tested one at a time, either in a top-

down or bottom-up manner.

• Allows for easier identification of defects and ensures that each

module works correctly before moving on to the next.

• Promotes a more systematic approach to integration.

9. Discuss the need of maintenance. Also discuss various categories of maintenance.

Answer:
Maintenance is essential for ensuring that software continues to function correctly and meets
user needs over time. The need for maintenance arises from various factors, including:

Defect Fixing: Addressing bugs and issues that arise after deployment to ensure the software
operates as intended.

Adaptation to Changes: Modifying the software to accommodate changes in the

environment, technology, or user requirements.

Performance Improvement: Enhancing the software to improve efficiency, speed, and overall
user experience.

User Feedback: Incorporating user suggestions and feedback to improve functionality and
usability.

Categories of Maintenance:

Corrective Maintenance: Involves fixing defects and issues identified after the software is
deployed. This is reactive maintenance aimed at resolving problems.

Adaptive Maintenance: Modifying the software to work in a new environment or with new
technologies. This may involve updating software to be compatible with new operating
systems or hardware.

Perfective Maintenance: Enhancing the software to improve performance or add new

features based on user requests. This proactive maintenance aims to increase user
satisfaction.

Preventive Maintenance: Making changes to prevent future problems, such as refactoring

code to improve maintainability or updating documentation to reflect changes in the
software.

10. Discuss COCOMO model in detail. Also explain the term Person Month (PM).

Answer:COCOMO (Constructive Cost Model) is a model used to estimate the cost, effort, and
schedule for software projects based on the size of the software. It provides a framework for
project managers to assess the resources needed for software development. The model has
three levels:

• Basic COCOMO Model: Provides a rough estimate of effort based on the size of the
software in lines of code (LOC). It uses a simple formula to calculate effort in person-
months.
• Intermediate COCOMO Model: Considers additional factors such as product,
hardware, personnel, and project attributes. It provides a more accurate estimate by
incorporating cost drivers that affect project effort.
• Detailed COCOMO Model: Offers a comprehensive estimation by incorporating
various cost drivers and their impact on project effort. It allows for detailed analysis
and planning.