1.

1
a) List the activities of spiral model.
The Spiral Model is an iterative development model that combines the iterative nature of prototyping with the systematic aspects of
the waterfall model. Its key activities are:
Planning: Defining objectives, alternatives, and constraints.
Risk Analysis: Identifying and analyzing risks.
Engineering: Designing, coding, and testing.
Evaluation: Evaluating the results and planning the next iteration.

b) What is class & object?

In object-oriented programming, a class is a blueprint or template for creating objects. It defines the properties (attributes) and
behaviors (methods) that objects of that class will have.
An object is an instance of a class. It represents a real-world entity with specific values for its attributes. For example, a "Car" class
might define attributes like color, make, and model. A specific "Honda Civic" would be an object of the "Car" class with specific
values for these attributes.

c) What does ASD stands for?

ASD stands for Agile Software Development. It is a group of software development methodologies based on iterative development,
where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

d) Define Agility
Agility in software development refers to the ability to respond quickly to changes in requirements or the market. Agile teams are
flexible, adaptable, and efficient, allowing them to deliver high-quality software products faster.

e) Draw a symbol of component.

UML component symbol

A component is a modular part of a system with well-defined interfaces. It can be a physical hardware module or a software
module.

f) Name any two key XP activities.

Pair Programming: Two programmers work together on the same code, improving code quality and knowledge sharing.
Test-Driven Development (TDD): Writing automated tests before writing the actual code, ensuring that the code meets the
specified requirements.

g) A design notation is a symbolic representational System". Justify.

A design notation is a symbolic language used to represent software designs. It provides a visual and formal way to communicate
design ideas among team members. It's a symbolic system because it uses symbols (like boxes, arrows, and lines) to represent
different concepts, and it's a representational system because it represents real-world entities and their relationships.

h) What is meant by structural analysis?

Structural analysis in software engineering involves breaking down a system into its components and analyzing their relationships. It
helps in understanding the system's architecture, identifying dependencies, and assessing potential risks.

i) Define Pattern
A pattern is a reusable solution to a recurring software design problem. It captures the problem, the solution, and the context in
which the solution is applicable. Patterns help in designing software systems that are efficient, maintainable, and scalable.

j) What are the common notation for deployment diagram?

Nodes: Represent hardware components like servers, workstations, and devices.
Artifacts: Represent software components like executables, libraries, and databases.
Communication Paths: Represent the connections between nodes.
Deployment Specifications: Describe the deployment of artifacts onto nodes.
These notations are typically used in the Unified Modeling Language (UML) to visualize the physical architecture of a software
system.
1.2
a) What is Software Patterns?
Software patterns are reusable solutions to common software design problems. They provide a proven design approach, often
expressed in a template-like format, that can be adapted to specific situations. Patterns promote code readability, maintainability,
and reusability.

b) Define: Software Engineering.

Software engineering is the systematic approach to the design, development, testing, and maintenance of software. It involves
applying engineering principles to software development to produce high-quality, reliable, and efficient software systems.

c) Explain the purpose of sequence model.

A sequence diagram is a UML diagram that illustrates the interaction between objects in a system over time. It's particularly useful
for understanding the dynamic behavior of a system and identifying potential issues in the interaction flow.

d) Define: Dependency.
In software engineering, a dependency is a relationship between two software modules or components where one module relies on
another. This means that a change in the dependent module can potentially impact the functionality of the relying module.
Dependencies can be direct or indirect and can affect the system's complexity, maintainability, and testability.

e) What is agility?
Agility in software development refers to the ability to respond quickly to changes in requirements or the market. Agile teams are
flexible, adaptable, and efficient, allowing them to deliver high-quality software products faster. Agile methodologies prioritize
customer satisfaction, iterative development, and continuous improvement.

f) What is the importance of design model?

A design model is a blueprint of a software system, representing its architecture, components, and relationships. It is crucial for
several reasons:
Communication: It serves as a common language for developers, stakeholders, and testers to understand the system's design.
Quality Assurance: It helps identify potential issues early in the development process, reducing the risk of defects.
Maintainability: A well-designed system is easier to maintain and modify.
Reusability: Design patterns and modular components can be reused in future projects.

g) state in brief for separation of concerns.

Separation of concerns is a design principle that suggests breaking down a complex system into smaller, more manageable modules,
each responsible for a specific part of the functionality. This helps in improving code organization, modularity, and maintainability.

h) Explain requirement validation.

Requirement validation is the process of ensuring that the requirements gathered from stakeholders are correct, complete,
consistent, and feasible. It involves techniques like reviews, walkthroughs, and formal verification to identify and address any issues
or ambiguities in the requirements.

i) What is meant by XP?

Extreme Programming (XP) is an agile software development methodology that emphasizes simplicity, communication, feedback,
and courage. Key practices of XP include pair programming, test-driven development, continuous integration, and frequent releases.

j) Define : prototyping.
Prototyping is a software development technique where a simplified version of a system is created to explore its design,
functionality, and user interface. Prototypes can be used to gather feedback from users, validate requirements, and identify
potential issues early in the development process.

a) What is a unified process?

The Unified Process (UP) is a software development process framework that emphasizes iterative development and risk
management. It combines the best practices of several software development methodologies, including object-oriented analysis
and design (OOAD). The UP is flexible and can be adapted to various project types and organizational needs.

c) List the goals of Software Engineering.

The primary goals of software engineering are:
Product Quality: Developing software that is reliable, efficient, and meets user requirements.
Developer Productivity: Creating a productive development environment that enables efficient development and maintenance.
Customer Satisfaction: Delivering software that satisfies customer needs and expectations..
e) What is negotiation?
Negotiation is the process of resolving conflicts and reaching agreements among stakeholders with different interests. In software
engineering, negotiation is often used to prioritize requirements, allocate resources, and resolve disputes.
1.3
d) What is elicitation?
Elicitation is the process of gathering and understanding the requirements of a software system from stakeholders. It involves
techniques like interviews, workshops, surveys, and document analysis to identify the functional and non-functional requirements.

f) Draw a symbol of extend.

UML extend symbol

The extend relationship in UML is used to show how one use case can extend the behavior of another use case under specific
conditions.

g) Define: Association.
An association in UML is a relationship between two or more classes that indicates a semantic connection between them. It can be a
simple relationship or a more complex one with additional information like multiplicity, direction, and role names.

h) List of UML diagrams (any Two).

Use Case Diagram: A use case diagram shows the interactions between users and the system, focusing on the functional
requirements.
Class Diagram: A class diagram represents the static structure of a system, showing classes, their attributes, and relationships.

i) What is software design?

Software design is the process of creating a blueprint for a software system. It involves defining the system's architecture,
components, and interfaces. The goal of software design is to produce a design that is efficient, maintainable, and meets the
system's requirements.

j) Define: data Abstraction.

Data abstraction is the process of hiding the implementation details of a data structure and providing a simplified interface to
interact with it. This allows for modularity, reusability, and easier maintenance.
a) Define process Flow.
A process flow is a sequential representation of a series of steps or activities involved in a specific process. It visually depicts the
flow of work, decisions, and actions from start to finish. Process flows are used to analyze, optimize, and document processes.

b) List any two agile principles.

Customer Satisfaction: Prioritize customer satisfaction by delivering valuable software frequently.
Embrace Change: Welcome changing requirements, even late in development.

c) What are the different building blocks of UML?

UML (Unified Modeling Language) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of a
software-intensive system. Its building blocks include:
Structural Elements: Classes, Interfaces, Packages, Components, Nodes
Behavioral Elements: Use Case Diagrams, Sequence Diagrams, Activity Diagrams, State Machine Diagrams
Grouping Elements: Packages
Annotational Elements: Notes

d) Write any two purposes served by SRS. (Software Requirements Specification)

Communication: Serves as a common understanding between the development team, stakeholders, and clients.
Baseline for Development: Provides a basis for design, testing, and project management.

e) Define abstraction.
Abstraction is the process of simplifying complex systems by focusing on the essential features while hiding unnecessary details. It
allows developers to manage complexity and create modular, reusable components.
1.4
f) List the advantages of waterfall model.
Simple and Easy to Understand: Its linear, sequential approach is straightforward.
Well-Defined Phases: Clear milestones and deliverables.
Suitable for Smaller Projects: Works well for projects with well-defined requirements.

g) What is requirement validation?

Requirement validation is the process of ensuring that the requirements gathered from stakeholders are correct, complete,
consistent, and feasible. It involves techniques like reviews, walkthroughs, and formal verification to identify and address any issues
or ambiguities in the requirements.

h) Write the purpose of activity diagram.

An activity diagram in UML visualizes the workflow of a system, showing the sequence of activities and decisions involved in a
process. It's useful for modeling business processes, software algorithms, and user interactions.

i) List any two umbrella activities of software process.

Project Management: Planning, tracking, and controlling the project.
Risk Management: Identifying, assessing, and mitigating risks.

j) Define Artifacts.
Artifacts are the tangible products of software development, such as code, design documents, test cases, and user manuals. They
are created and used throughout the software development lifecycle.
2 marks
a) What is negotiation?
Negotiation is a process of discussion and compromise between two or more parties to reach an agreement. In the context of
software engineering, negotiation is often used to resolve conflicts, prioritize requirements, allocate resources, and make decisions
that involve multiple stakeholders. Effective negotiation skills are crucial for project managers and team leaders to ensure smooth
project execution.

b) Describe the terms cohesion & coupling.

Cohesion: Cohesion refers to the degree to which the elements within a module are related to each other. A highly cohesive
module performs a single, well-defined task, making it easier to understand, test, and maintain.
Coupling: Coupling measures the degree of interdependence between modules. Loose coupling is desirable, as it reduces the impact
of changes in one module on other modules. Tight coupling, on the other hand, can make the system more complex and difficult to
modify.

c) State the purpose of use case diagram.

A use case diagram in UML is a visual representation of the functional requirements of a system. It shows the interactions between
users (actors) and the system, focusing on the system's behavior from the user's perspective. The primary purposes of a use case
diagram are:
Understanding System Functionality: It helps to clarify the system's capabilities and the services it provides to users.
Identifying System Boundaries: It defines the scope of the system and what lies outside its boundaries.
Communicating with Stakeholders: It can be used to communicate the system's requirements to stakeholders, such as clients,
business analysts, and developers.
Planning and Testing: It can be used to plan test cases and identify potential scenarios for testing.

d) Write a short note on concurrent deployment model.

A concurrent deployment model is a software deployment strategy where multiple versions or components of a software system
are deployed simultaneously. This approach can be used to introduce new features or bug fixes without disrupting the existing
system. However, it requires careful planning and testing to ensure compatibility and minimize risks.

e) What are the elements which are used in activity diagram?

Activity diagrams in UML are used to model the dynamic behavior of a system, focusing on the flow of activities and decisions. The
key elements used in activity diagrams are:
Activities: Represent actions or processes.
Initial Node: The starting point of the activity diagram.
Final Node: The ending point of the activity diagram.
Decision Nodes: Represent decision points where the flow can take different paths based on conditions.
Merge Nodes: Combine multiple flows into a single flow.
Fork Nodes: Split a flow into multiple concurrent flows.
Join Nodes: Synchronize multiple concurrent flows into a single flow.
Object Flows: Represent the flow of objects between activities.
Swimlanes: Organize activities into different groups or participants.
1.5
a) Explain in brief about waterfall model.
The Waterfall Model is a linear, sequential design approach where each phase must be completed before the next begins.
The phases typically include:
Requirement Gathering and Analysis: Defining the system's requirements.
System Design: Designing the system's architecture and components.
Implementation: Developing the software.
Testing: Testing the software to ensure it meets requirements.
Deployment: Deploying the software to the production environment.
Maintenance: Maintaining and updating the software.
b) State any two symbols with an example for developing use cases.
Actor: Represents a user or external system that interacts with the system.
Example: A "Customer" actor can interact with an online shopping system.
Use Case: Represents a specific function or behavior that the system provides.
Example: A "Place Order" use case can be initiated by a "Customer" actor.
c) State the disadvantages Incremental model.
Risk of Overlooking System Requirements: The incremental approach may lead to overlooking overall system requirements, as the
focus is on delivering smaller increments.
Potential for Integration Issues: Integrating different increments can be challenging, especially if they are not well-coordinated.
Requires Skilled Developers: Effective incremental development requires experienced developers who can manage the complexity
of iterative development.
d) What is difference between system and application software?
System Software: Controls the hardware and provides basic services to the system.
Examples: Operating systems, device drivers, firmware.
Application Software: Designed to perform specific tasks for users.
Examples: Word processors, spreadsheets, web browsers, games.
e) Explain the purpose of class diagram.
A class diagram in UML is used to visualize the static structure of a software system. It shows the classes, their attributes, and the
relationships between them. The primary purpose of a class diagram is to:
Understand the System's Structure: It provides a clear overview of the system's components and how they are organized.
Identify Classes and Their Responsibilities: It helps in identifying the classes needed in the system and their roles.
Define Relationships Between Classes: It shows how classes interact with each other, such as inheritance, association, and
aggregation.
Document the System's Design: It serves as a valuable documentation tool for developers and stakeholders.
a) What is system software and Application Software?
System Software:
Controls the hardware and provides basic services to the system.
Examples: Operating systems (Windows, Linux, macOS), device drivers, firmware.
Application Software:
Designed to perform specific tasks for users.
Examples: Word processors, spreadsheets, web browsers, games.
b) What are the advantages of scrum?
Flexibility and Adaptability: Scrum is highly adaptable to changing requirements and market conditions.
Customer Satisfaction: By delivering working software frequently, Scrum ensures customer satisfaction.
Improved Team Collaboration: Scrum promotes teamwork and communication among team members.
Reduced Time to Market: Scrum can accelerate software development and reduce time-to-market.
Risk Mitigation: Regular iterations and feedback help identify and mitigate risks early on.
c) What is class and object?
Class: A class is a blueprint or template for creating objects. It defines the properties (attributes) and behaviors (methods) that
objects of that class will have.
Object: An object is an instance of a class. It represents a real-world entity with specific values for its attributes.
d) What is Actor?
In the context of software engineering, an actor is a role played by a user or an external system that interacts with the system.
Actors can be people, organizations, or other systems. They initiate use cases and interact with the system to achieve specific goals.
e) What are the elements of design model?
A design model is a blueprint of a software system, representing its architecture, components, and relationships. The key elements
of a design model include:
Architectural View: The overall structure of the system, including its components and their interactions.
Component Design: The design of individual components, their interfaces, and their responsibilities.
Data Design: The design of the system's data structures, including databases and data models.
Interface Design: The design of user interfaces and APIs.
Deployment Design: The deployment of the system on hardware and software platforms.
1.6
a) What is Functional independance? Which qualitative criteria is applied to assessed independance.
Functional independence is a software design principle that aims to create modules that are self-contained and have minimal
dependencies on other modules.
This promotes modularity, reusability, and maintainability.
Qualitative Criteria for Assessing Independence:
Cohesion: Measures the degree to which elements within a module are related to each other. High cohesion indicates a
well-defined module with a clear purpose.
Coupling: Measures the degree of interdependence between modules. Low coupling indicates that modules are loosely connected,
minimizing the impact of changes.

b) Define diagrams. Write classification of UML diagrams.

Diagrams are visual representations used to illustrate different aspects of a system.
UML (Unified Modeling Language) is a widely used standard for creating diagrams.
UML diagrams can be classified into two main categories:
Structural Diagrams:
Class Diagram: Shows the static structure of a system, including classes, attributes, and relationships.
Object Diagram: Represents specific instances of classes at a particular point in time.
Component Diagram: Depicts the physical components of a system and their relationships.
Deployment Diagram: Visualizes the physical deployment of system components on hardware.
Package Diagram: Organizes elements into packages to improve modularity.
Behavioral Diagrams:
Use Case Diagram: Illustrates the functional requirements of a system by showing interactions between actors and the system.
Sequence Diagram: Depicts the sequence of messages exchanged between objects during a particular scenario.
Collaboration Diagram: Emphasizes the relationships between objects and the messages they exchange.
State Machine Diagram: Models the different states an object can be in and the transitions between those states.
Activity Diagram: Shows the flow of activities and decisions in a process.

c) List the elements of Andysis model.

An analysis model typically includes the following elements:
Data Design: Defines the data structures and data stores used in the system.
Functional Requirements: Specifies the functional behaviors that the system must provide.
Behavioral Requirements: Defines the system's non-functional requirements, such as performance, security, and usability.
User Interface Design: Describes the user interface elements and their interactions.

d) Write the role of scrum.

Scrum is an agile framework for managing and executing complex projects. Its key roles include:
Product Owner: Responsible for the product backlog and prioritizing requirements.
Scrum Master: Facilitates the Scrum process, resolves impediments, and ensures the team follows Scrum principles.
Development Team: Self-organizing team that is responsible for delivering the product increment.

e) Write advantages of RAD model.

Rapid Development: The iterative nature of RAD allows for quick development cycles.
Early User Feedback: User involvement in each iteration helps ensure that the product meets user needs.
Flexibility: RAD can adapt to changing requirements more easily than traditional models.
Improved Quality: Frequent testing and feedback loops lead to higher quality products.
Increased Customer Satisfaction: Early and continuous delivery of working software can increase customer satisfaction