Q) Outline the Principles of Modelling.

A) OODA is based on a set of principles that help guide the modelling

process. Here are some of the key principles of modelling in Object-
Oriented Design and Analysis:
Encapsulation: Encapsulation is the principle of bundling data and
the methods that act on that data into a single unit, known as a class.
Encapsulation helps to maintain the integrity of the data and makes
it easier to modify the implementation without affecting the rest of
the system.
Inheritance: Inheritance is the principle of creating a new class by
inheriting properties and behaviours from an existing class. The new
class, known as the subclass, Inheritance promotes code reuse and
allows for more efficient and organized code.
Polymorphism: It is the principle of allowing objects of different
types to be treated as if they were of the same type. Polymorphism
can be achieved through method overloading or method overriding.
Method overloading, Method overriding in Polymorphism allows for
greater flexibility & extensibility in the system.
Abstraction: Abstraction is the principle of reducing complex systems
to a set of essential characteristics, or abstractions. Abstractions
allow developers to focus on the most important aspects of the
system. it makes the system easier to understand and modify.
Composition: It is the principle of creating a new class by combining
existing classes. The new class, known as the composite class,
contains instances of other classes, known as its components. It
promotes code reuse and allows for greater flexibility in the system.
Dependency: Dependency is the principle of defining the
relationships between classes in terms of dependencies
Dependencies can be represented using UML diagrams, which show
the relationships between classes.
Q) Establish the relationship between SDLC and UML.
A) The Software Development Life Cycle (SDLC) and Unified
Modelling Language (UML) are two complementary concepts that
are used in software development. The SDLC is a methodology for
designing, developing, and maintaining software systems, while UML
is a visual language for modelling software systems. The relationship
between SDLC and UML is that UML is often used as a tool within the
SDLC to represent the various phases of the development process.
The SDLC includes several phases, such as requirements gathering,
design, implementation, testing, and maintenance. Each of these
phases has its own set of tasks and objectives, and UML can be used
to model the various artifacts and deliverables associated with each
phase. For example, during the requirements gathering phase, UML
can be used to create use case diagrams, which represent the
interactions between users and the system. During the design phase,
UML can be used to create class diagrams, which represent the
classes and their relationships within the system.
UML can also be used to model the flow of data and control within
the system, as well as the system architecture and deployment. By
using UML to model the various aspects of the system, developers
can create a more complete and accurate representation of the
system, which can help to reduce errors and misunderstandings
during the development process.
In summary, the relationship between SDLC and UML is that UML is
used as a tool within the SDLC to model and represent the various
phases of the development process. By using UML to model the
various aspects of the system, developers can create a more
accurate and complete representation of the system, which can help
to reduce errors and misunderstandings during the development
process.