COMPUTER SCIENCE & ENGINEERING

3RD YEAR
SE QUESTIONS FOR CLASS TEST
1. What is Software Engineering? What is the role of a software engineer? Compare Hardware and
Software product characteristics?
Software engineering is the systematic application of engineering principles to the development,
operation, maintenance, and retirement of software. It's a discipline that combines computer science,
mathematics, and project management to produce high-quality software.
A software engineer plays a pivotal role in the software development lifecycle. Their responsibilities often
include:
Requirements analysis: Understanding the client's needs and translating them into technical specifications.
Design: Creating the architecture and structure of the software system.
Coding: Writing the actual code that implements the design.
Testing: Ensuring the software meets quality standards and functions as intended.
Maintenance: Updating and improving the software over time.
Hardware vs. Software: A Comparison
2. How do we define software engineering? Draw and explain software engineering layers.
Software engineering is a fully layered technology, to develop software we need to go from one layer to
another. All the layers are connected and each layer demands the fulfillment of the previous layer.
Layered technology is divided into four parts:

Layered technology is divided into four parts:

1. A quality focus: It defines the continuous process improvement principles of software. It provides
integrity that means providing security to the software so that data can be accessed by only an authorized
person, no outsider can access the data. It also focuses on maintainability and usability.

2. Process: It is the foundation or base layer of software engineering. It is key that binds all the layers
together which enables the development of software before the deadline or on time. Process defines a
framework that must be established for the effective delivery of software engineering technology. The
software process covers all the activities, actions, and tasks required to be carried out for software
development.

Process activities are listed below:-

Communication: It is the first and foremost thing for the development of software. Communication is
necessary to know the actual demand of the client.
Planning: It basically means drawing a map to reduce the complication of development.
Modeling: In this process, a model is created according to the client for better understanding.
Construction: It includes the coding and testing of the problem.
Deployment:- It includes the delivery of software to the client for evaluation and feedback.
3. Method: During the process of software development the answers to all “how-to-do” questions are
given by method. It has the information of all the tasks which includes communication, requirement
analysis, design modeling, program construction, testing, and support.

4. Tools: Software engineering tools provide a self-operating system for processes and methods. Tools are
integrated which means information created by one tool can be used by another.

3. Explain Spiral model with suitable example. Also explain how it differs from the Software
Prototyping model.
The Spiral Model is a software development lifecycle (SDLC) model that combines elements of the
waterfall model and prototyping model. It is particularly suitable for large, complex projects where risks
need to be carefully managed.
Stages of the Spiral Model
The Spiral Model consists of several cycles (or spirals), each containing four main phases:

Planning: Requirements are gathered and analyzed. Goals for the next iteration are defined.
Risk Analysis: Risks are identified, evaluated, and mitigation strategies are planned. Prototypes may be
developed to understand and reduce risks.
Engineering: The actual development and testing of the system take place. This includes coding, building,
and testing the software based on the identified requirements and risk assessments.
Evaluation and Review: The developed system is reviewed by stakeholders, and feedback is collected for
the next iteration. This phase ends with deciding whether to proceed with another spiral or conclude the
project.
Example
Suppose a company is developing an e-learning platform. The Spiral Model might be used as follows:

First Spiral: Basic requirements (e.g., user registration, course browsing) are defined, and potential risks
(like security vulnerabilities) are analyzed. A prototype focusing on the user interface is developed.
Second Spiral: More detailed features (e.g., interactive course modules) are added based on user feedback
from the first prototype. The team assesses risks such as scalability issues and builds a new prototype.
Subsequent Spirals: Further enhancements, like integrating AI-based personalized recommendations, are
introduced, and risks like algorithm bias are addressed.
4. Explain Agile Process Model. Explain XP (Extreme Programming) as the process model.
Agile Process Model

The Agile Process Model is an iterative and incremental approach to software development that
emphasizes flexibility, collaboration, and customer satisfaction. Instead of building the entire product in
one go, the project is broken down into smaller parts called iterations or sprints, which typically last 1-4
weeks. At the end of each iteration, a working product is delivered, which is then tested and reviewed
with stakeholders.

Key principles of Agile include:

- Customer collaboration over contract negotiation
- Responding to change over following a plan
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation

Agile methodologies, such as Scrum and XP, encourage close communication between developers,
customers, and other stakeholders, which helps to quickly adapt to changes and ensure the final product
meets user needs.
Extreme Programming (XP)

Extreme Programming (XP)** is an Agile process model that focuses on improving software quality and
responsiveness to customer requirements. It aims to deliver software faster and with higher quality by
emphasizing frequent releases in short development cycles.

Key practices in XP include:

1. Pair Programming: Two developers work together at one workstation, collaborating to write code. This
ensures better quality as it promotes knowledge sharing and immediate feedback.
2. Test-Driven Development (TDD): Tests are written before the code itself, ensuring that the code works
as expected and meets the requirements.
3. Continuous Integration: Developers integrate code into a shared repository several times a day to detect
and fix integration issues early.
4. Refactoring: The codebase is continuously improved without changing its functionality to make it more
efficient and maintainable.
5. Small Releases: Small, frequent releases are delivered to the customer to gather feedback and adapt
quickly to changes.
6. Customer Collaboration: A customer representative is actively involved with the development team,
ensuring that the requirements are clear and priorities are understood.

XP is ideal for projects where requirements are uncertain or likely to change, as it allows for rapid
adaptation while maintaining a high standard of code quality.

5. List and Explain requirement engineering tasks.

Requirement engineering involves systematically gathering, documenting, and managing the requirements
of a system. It is a crucial phase in the software development lifecycle and includes the following tasks:

1. Elicitation
- This task involves gathering requirements from stakeholders, such as customers, end-users, and
business managers.
- Techniques used: interviews, surveys, workshops, observation, document analysis, and brainstorming.
- Goal: Understand what the system needs to accomplish and identify constraints.
2. Analysis
- The gathered requirements are analyzed to identify conflicts, gaps, and ambiguities.
- The analysis helps ensure that requirements are clear, complete, consistent, and feasible.
- Requirements are categorized as functional, non-functional, and domain-specific.

3. Specification
- This step involves documenting the analyzed requirements in a formal, structured, and precise manner.
- The specification can be in the form of Software Requirements Specification (SRS) documents, use
cases, user stories, or models (e.g., data flow diagrams).
- This ensures a clear understanding of the requirements by both the development team and
stakeholders.

4. Validation
- Requirements are reviewed and validated to ensure they meet the needs of stakeholders and are
achievable within technical and business constraints.
- Techniques include requirements reviews, prototyping, and model validation.
- The goal is to identify any issues or misunderstandings early before development begins.

5. Management
- Involves controlling, tracking, and managing changes to requirements throughout the project lifecycle.
- A requirements management tool or system is often used to track changes, versions, and dependencies.
- It ensures that any changes to the requirements are reviewed, approved, and communicated properly to
maintain project alignment.

These tasks work together to establish a solid foundation for developing software that meets stakeholders'
needs while reducing risks and rework during later stages of development.

6. Explain User Interface Design Rules with examples.

User Interface (UI) design rules are guidelines that help designers create interfaces that are effective,
efficient, and enjoyable for users. These rules focus on visual, interactive, and usability aspects of the
interface. Here are some key UI design rules with examples:

1. Consistency
 - Ensure that design elements (buttons, colors, fonts) and behavior (navigation, interaction) are
consistent throughout the interface.
- Example: If a "Save" button is blue and located at the bottom-right corner in one screen, it should
appear similarly across all screens. Consistency helps users learn how to navigate and interact without
confusion.

2. Simplicity
- Keep the interface simple and clutter-free. Focus on essential elements and remove unnecessary
details.
- Example A login screen should have only necessary fields like "Username" and "Password" with a
simple "Login" button. Avoid adding irrelevant information that could distract or overwhelm the user.

3. Visibility of System Status

- Inform users about the system’s status and provide feedback for their actions.
- Example When a file is uploading, showing a progress bar indicates the status of the upload process,
letting the user know that their action is being processed.

4. Affordance and Signifiers

- Design elements should visually indicate how they are meant to be used, making the interaction
intuitive.
- Example Buttons should look clickable with a raised or shadow effect. Icons for functions like "trash"
should resemble a garbage bin to signify deletion.

5. Error Prevention and Handling

- Design interfaces that prevent errors and provide clear instructions for resolving issues when they
occur.
- Example: Disable the "Submit" button until all required fields are filled. If an error occurs, display a
message like "Password must be at least 8 characters" near the problematic field.

6. Flexibility and Efficiency of Use

- Provide shortcuts for experienced users while maintaining a simple pathway for new users.
- Example: In a text editor, you can access functions via toolbar buttons (easy for beginners) and
keyboard shortcuts (e.g., Ctrl + C for copy) for advanced users.
7. Aesthetic and Minimalist Design
- Avoid overwhelming users with too much information or design elements. Keep interfaces visually
appealing but minimal.
- Example: A dashboard should highlight important metrics using simple graphs and icons rather than
displaying excessive text or data that might confuse the user.

7. Describe FOUR Ps for Project Management and explain in detail.

The Four Ps of Project Management are a framework used to plan, execute, and control projects
effectively. They are:

1. Purpose:

Definition: The overall goal or objective of the project.

Explanation: The purpose sets the direction for the project, ensuring that all efforts are aligned towards
achieving a common outcome. It is essential to clearly define the purpose to gain stakeholder buy-in,
allocate resources effectively, and measure project success.

2. Process:

Definition: The sequence of activities or steps involved in completing the project.

Explanation: The process outlines the workflow and dependencies between different tasks. It helps in
visualizing the project timeline, identifying critical path activities, and managing project resources
efficiently. A well-defined process ensures that all project activities are carried out in a logical order and
that progress can be monitored and controlled effectively.

3. People:

Definition: The individuals involved in the project, including the project manager, team members,
stakeholders, and external resources.
Explanation: The people involved in the project play a crucial role in its success. The project manager is
responsible for leading the team and ensuring that the project is completed on time, within budget, and to
the desired quality standards. Team members contribute their skills and expertise to various project tasks.
Stakeholders have a vested interest in the project and their input is essential for its success. External
resources, such as consultants or vendors, may also be involved in certain project activities. Effective
communication and collaboration among all stakeholders are essential for project success.

4. Product:
Definition: The final output or deliverable of the project.
Explanation:The product is the tangible or intangible result of the project. It should meet the defined
requirements and provide value to the stakeholders. The product should be clearly defined and
documented throughout the project lifecycle to ensure that it meets the expectations of all parties
involved.
8. What is the W5HH principle? Explain in detail.
The W5HH Principle is a project management guideline introduced by Barry Boehm. It is used to help
project managers ensure that key aspects of a project are understood and addressed effectively. The
W5HH acronym stands for What, Why, When, Who, Where, How, and How Much, which are the
essential questions that should be answered to properly manage a project. Here's a breakdown:
9. Explain Project Planning (Scheduling) activities.
Project Planning (Scheduling) Activities

Project planning, particularly scheduling, is a critical phase in project management. It involves breaking
down a project into manageable tasks, estimating their duration, and sequencing them to create a timeline
for completion.

Here are the key activities involved in project planning and scheduling:

1. Define Project Scope

Identify project goals: Clearly outline what the project aims to achieve.
Define deliverables: Specify the tangible outcomes or products of the project.
Create a project charter: A formal document that outlines the project's objectives, scope, and initial
budget.

2. Break Down Project into Tasks :

Work Breakdown Structure (WBS): Divide the project into smaller, more manageable tasks.
Task decomposition: Continue breaking down tasks until they are granular enough for accurate
estimation.
Identify dependencies: Determine which tasks must be completed before others can begin.

3. Estimate Task Durations:

Expert judgment: Use the knowledge and experience of team members to estimate task durations.
Historical data: Refer to previous projects or industry benchmarks for similar tasks.
Estimating techniques: Employ techniques like PERT (Program Evaluation and Review Technique) or
CPM (Critical Path Method) to calculate expected durations.

4. Create a Network Diagram:

Visual representation: Depict the sequence of tasks using a diagram (e.g., Gantt chart, PERT chart).
Identify critical path: Determine the longest sequence of tasks that must be completed on time for the
project to finish on schedule.
Calculate project duration: Calculate the total time required for project completion based on the critical
path.

5. Develop a Schedule:
Assign resources: Allocate necessary resources (e.g., people, equipment) to each task.
Create a timeline: Develop a schedule that outlines the start and end dates for each task.
Consider constraints: Account for any limitations or constraints that may affect the schedule (e.g.,
resource availability, deadlines).

6. Create a Resource Allocation Plan:

Identify resource requirements: Determine the specific resources needed for each task.
Allocate resources:Assign resources to tasks based on their availability and skills.
Manage resource conflicts: Resolve any conflicts that arise due to resource shortages or competing
demands.

7. **Review and Adjust:

Conduct regular reviews: Periodically assess the project's progress and make necessary adjustments to the
schedule.
Monitor performance: Track the actual performance of tasks against their planned durations.
Implement changes: If necessary, make changes to the schedule or resource allocation to ensure project
completion on time and within budget.

10.Explain Risk Management. Explain RMMM plan.

A Risk management strategy can be included in the software project
plan, or the risk management steps can be organized into a separate
risk mitigation, monitoring, and management plan (RMMM).
The RMMM plan documents all work performed as part of risk
analysis and is used by the project manager as part of the overall
project plan. Each risk may be documented individually using a risk
information sheet (RIS). Once RMMM has been documented and the
the project has begun, risk mitigation and monitoring steps commence.
Risk mitigation (avoidance) is the primary strategy and is achieved
through a plan.
During Risk monitoring, the project manager monitors factors that
may provide an indication of whether a risk is becoming more or less likely.
11. Compare: Coupling and Cohesion. Explain Different types of Coupling and its effect on
software modules.
Cohesion refers to the degree to which elements within a module work together to fulfill a single,
well-defined purpose. High cohesion means that elements are closely related and focused on a single
purpose, while low cohesion means that elements are loosely related and serve mul􀆟ple purposes.
Types of Cohesion
The following are the types of cohesion:
1. Functional Cohesion
2. Procedural Cohesion
3. Temporal Cohesion:
4. Sequential Cohesion.
5. Layer Cohesion.
6. Communication Cohesion.

Coupling refers to the degree of interdependence between so􀅌ware modules. High coupling means
that modules are closely connected and changes in one module may affect other modules. Low
coupling means that modules are independent, and changes in one module have li􀆩le impact on
other modules.
Types of Coupling
Following are the types of Coupling:
1. Data Coupling
2. Stamp Coupling
3. Control Coupling
4. External Coupling
5. Common Coupling
6. Content Coupling
12. Define Software Quality Assurance (SQA) and explain SQA activities.
Software Quality Assurance (SQA)
Software Quality Assurance (SQA) is a systematic approach to ensure that software products meet
predefined quality standards throughout their development lifecycle. It involves a set of planned activities
to prevent defects and ensure that the software meets user requirements and expectations.

Key SQA Activities

Quality Planning:

Defining quality goals and objectives

Identifying quality metrics and standards
Developing a quality assurance plan
Review and Audits:
Conducting code reviews, design reviews, and document reviews
Performing audits to assess compliance with quality standards
Testing:

Designing and executing various types of tests, including unit testing, integration testing, system testing,
and acceptance testing
Analyzing test results and identifying defects
Defect Tracking and Management:

Tracking and managing defects throughout their lifecycle

Prioritizing defects and assigning them to developers for resolution
Metrics and Reporting:

Collecting and analyzing quality metrics

Preparing reports on quality status and trends
Continuous Improvement:

Identifying opportunities for improvement

Implementing process changes and best practices
Training and Education:

Providing training to team members on quality assurance concepts and techniques

13. Write a short note on 1) Code Review Techniques 2) Reverse Engineering

1. Code Review Techniques
Code review is a critical process in software development that involves inspecting code for errors,
inconsistencies, and potential improvements. Effective code review techniques can significantly enhance
software quality, maintainability, and team collaboration. Some common techniques include:

Peer Review: This involves a group of developers examining each other's code. It's often done in a formal
setting, such as a code review meeting, or informally, like pair programming.
Walkthrough: A walkthrough involves the author presenting their code to a group of reviewers, explaining
their thought process and design decisions.
Inspection: An inspection is a highly structured code review process that follows a defined checklist and
involves a team of reviewers.
Tool-Assisted Review: Tools can automate certain aspects of code review, such as identifying common
coding errors, checking for compliance with coding standards, and suggesting improvements.
Key considerations for effective code reviews:

Focus on quality: The primary goal of code review is to improve code quality, not to criticize the
developer.
Be respectful: Treat all reviewers and their suggestions with respect.
Provide constructive feedback: Offer specific suggestions for improvement rather than vague criticisms.
Be open to feedback: Be willing to accept feedback and make changes to your code.
2. Reverse Engineering
Reverse engineering is the process of analyzing a product or system to understand its design, principles,
and operation. It's often used in various fields, including software development, hardware engineering,
and forensic analysis.

Common techniques used in reverse engineering:

Decompilation: This involves converting compiled code (e.g., machine code) back into a higher-level
programming language.
Disassembly: This involves breaking down machine code into assembly language instructions.
Static analysis: This involves analyzing code without executing it, to identify potential vulnerabilities,
bugs, and security risks.
Dynamic analysis: This involves executing code in a controlled environment to observe its behavior and
identify issues.
Applications of reverse engineering:

Software piracy: Reverse engineering can be used to create unauthorized copies of software.
Security analysis: Reverse engineering can help identify vulnerabilities in software and hardware systems.
Interoperability: Reverse engineering can enable compatibility between different systems.
Research and development: Reverse engineering can be used to learn from existing products and develop
new ones.
Ethical considerations:

Reverse engineering is a complex topic with ethical implications. It's important to be aware of copyright
laws and ethical guidelines when engaging in reverse engineering activities.

14. Differentiate between Black-box Testing and White-Box Testing. Explain White-Box Testing in
detail.

White-Box Testing
Definition: White-box testing, also known as clear box testing, glass box testing, or structural testing, is a
software testing methodology that examines the internal workings of an application. Unlike black-box
testing, which focuses on input and output without knowledge of the internal code structure, white-box
testing requires knowledge of the code and the logic behind it.
Advantages
Thorough Testing: It allows for a detailed and thorough examination of the code, ensuring that all paths
and branches are tested.

Code Optimization: Testers can identify inefficient code and suggest improvements, enhancing
performance.

Early Bug Detection: Bugs can be identified and fixed early in the development cycle, reducing the cost
and time associated with later-stage bug fixes.

Knowledge Transfer: Involves developers in the testing process, fostering better collaboration and
understanding of the code.

Disadvantages
Requires Skilled Resources: It requires testers to have programming knowledge and familiarity with the
application’s codebase, which may not be available in all testing teams.

Time-Consuming: The process of thoroughly analyzing and testing every path and branch can be
time-consuming, especially in large applications.

Not a Substitute for Black-Box Testing: White-box testing focuses on internal structures and logic; thus, it
may miss issues related to user interactions and external requirements.

Complexity: Analyzing complex code structures and logic can be challenging, leading to potential
oversight if not done carefully.

15. Explain Software Configuration Management Process.

Software Configuration Management (SCM) is a process used in software engineering to systematically
control and manage changes to software products during their development and maintenance. It ensures
the integrity and traceability of the software configuration throughout the lifecycle of the software
product. The main goals are to improve productivity, maintain consistency, and enhance quality. Here’s an
overview of the SCM process:

1. Configuration Identification
Purpose: To identify and define the software items that need to be controlled. This includes source code
files, documents, test cases, and other artifacts.
Activities:
Establish baselines for different versions of the software.
Assign unique identifiers to each configuration item for tracking.
Record and maintain version details.
2. Configuration Control
Purpose: To manage changes to configuration items systematically.
Activities:
Evaluate and approve or reject change requests.
Ensure all changes are documented, evaluated, and authorized.
Implement changes while maintaining integrity and consistency.
3. Configuration Status Accounting
Purpose: To record and report information about configuration items and changes made.
Activities:
Track configuration items' history and changes.
Maintain records of change requests, approvals, and the status of different versions.
Generate reports on configuration status and activities.
4. Configuration Audits and Reviews
Purpose: To verify that the software and its configuration items comply with the required standards and
specifications.
Activities:
Conduct functional audits to ensure the software performs as intended.
Perform physical audits to check that all configuration items are present and correctly documented.
Review the completeness and accuracy of records.
5. Configuration Management Planning and Management
Purpose: To establish the SCM process, including policies, procedures, and tools.
Activities:
Develop a configuration management plan that outlines roles, responsibilities, and procedures.
Select and implement tools for version control, change tracking, and documentation.
Train the development team on SCM practices and ensure adherence.
Benefits of Software Configuration Management:
Maintains the integrity and consistency of the software over time.
Facilitates collaboration among team members by tracking changes and managing versions.
Ensures traceability of changes, making it easier to identify, resolve, and understand issues.
Supports the automation of build and release processes, improving efficiency and reducing errors.