CCS356-OBJECT ORIENTED SOFTWARE ENGINEERING

PART- A

1. What is Software Engineering?

Ans: Software engineering is a discipline that applies engineering
principles to the design, development, testing, and maintenance of
software systems.

2. State few differences between traditional and agile software

development?

Ans:

traditional agile
Development linear iterative and
Process incremental
Project Learning rigid process ongoing learnings
Focus software delivery discovery, flexibility
Duration and Cost larger teams, clear smaller teams, self-
hierarchies organized

3. How do you differentiate Functional Requirements and Non-

Functional Requirements?
Ans: Functional requirements specify what the system should
do, outlining its core features and functionalities.

Non-functional requirements, on the other hand, specify how the

system should perform, focusing on quality attributes like speed,
security, and usability.

4. What is the use of Data Flow Diagrams?

Ans: Dataflow is a Google Cloud service that provides unified
stream and batch data processing at scale. Use Dataflow to create
data pipelines that read from one or more sources, transform the
data, and write the data to a destination.

5. List any 4 Software Design Patterns?

Ans:
 Factory Method
 Adapter
 Decorator
 Singleton.

6. What is a Publish Subscribe model in Software Design?

 Ans: In software design, the Publish-Subscribe (Pub/Sub) model is a
messaging pattern that allows different system components to
communicate asynchronously.

7. Write the steps for debugging?

Ans:

Step 1: Reproduce the conditions.

Step 2: Find the bug
Step 3: Determine the root cause.
Step 4: Fix the bug.
Step 5: Test to validate the fix.
Step 6: Document the process.

8. Define Regression Testing?

Ans: Regression testing is a software testing process that verifies
that changes made to a software application, such as bug fixes,
updates, or new features, haven't introduced any new issues or
negatively impacted existing functionalities.

9. List any tools for Quality control in Project Management.

Ans: check sheets, Pareto charts, control charts, histograms, and
scatter diagrams.

10. What are the testing tools available in DevOps

software practice?
Ans: DevOps testing tools are used to automate and streamline the
testing process within a CI/CD pipeline, ensuring high-quality
software releases efficiently. Some popular tools include Selenium,
JUnit, TestNG, Cucumber, Jenkins, SonarQube, Docker,
Postman, and Artillery.

PART-B

11. Explain in brief shout the Extreme Programming

process with a neat diagram?
Ans: Extreme Programming (XP) is an Agile software
development methodology that focuses on delivering high-quality
software through frequent and continuous feedback, collaboration,
and adaptation. XP emphasizes a close working relationship
between the development team, the customer, and stakeholders,
with an emphasis on rapid, iterative development and deployment.

Agile development approaches evolved in the 1990s as a reaction to

documentation and bureaucracy-based processes, particularly the
waterfall approach. Agile approaches are based on some common
principles, some of which are:

1. Working software is the key measure of progress in a project.

2. For progress in a project, therefore software should be developed
and delivered rapidly in small increments
3. Even late changes in the requirements should be entertained.
4. Face-to-face communication is preferred over documentation.
5. Continuous feedback and involvement of customers are
necessary for developing good-quality software.
6. A simple design that involves and improves with time is a better
approach than doing an elaborate design up front for handling all
possible scenarios
Extreme programming is one of the most popular and well-known
approaches in the family of agile methods. an XP project starts with user
stories which are short descriptions of what scenarios the customers and
users would like the system to support. Each story is written on a separate
card, so they can be flexibly grouped.

Good Practices in Extreme Programming

Some of the good practices that have been recognized in the extreme
programming model and suggested to maximize their use are given
below:

 Code Review: Code review detects and corrects errors efficiently. It

suggests pair programming as coding and reviewing of written code
carried out by a pair of programmers who switch their work between
them every hour.
 Testing: Testing code helps to remove errors and improves its
reliability. XP suggests test-driven development (TDD) to continually
write and execute test cases. In the TDD approach, test cases are
written even before any code is written.
 Incremental development: Incremental development is very
good because customer feedback is gained and based on this
development team comes up with new increments every few days
after each iteration
 Simplicity: Simplicity makes it easier to develop good-quality code
as well as to test and debug it.
 Design: Good quality design is important to develop good quality
software. So, everybody should design daily
 Integration testing: Integration Testing helps to identify bugs at
the interfaces of different functionalities. Extreme programming
suggests that the developers should achieve continuous integration
by building and performing integration testing several times a day.

Basic of Extreme Programming.

XP is based on the frequent iteration through which the developers

implement User Stories. User stories are simple and informal
statements of the customer about the functionalities needed. A User
Story is a conventional description by the user of a feature of the
required system. Some of the basic activities that are followed during
software development by using the XP model are given below:

 Coding: The concept of coding which is used in the XP model is

slightly different from traditional coding. Here, the coding activity
includes drawing diagrams (modelling) that will be transformed into
 code, scripting a web-based system, and choosing among several
alternative solutions.
 Testing: The XP model gives high importance to testing and
considers it to be the primary factor in developing fault-free
software
 Listening: The developers need to carefully listen to the customers
if they have to develop good quality software. Sometimes
programmers may not have the depth knowledge of the system to
be developed. So, the programmers should understand properly the
functionality of the system and they have to listen to the customers.
 Designing: Without a proper design, a system implementation
becomes too complex, and very difficult to understand the solution,
thus making maintenance expensive. A good design results
elimination of complex dependencies within a system. So, effective
use of suitable design is emphasized.

 Collective Code Ownership: In XP, there is no individual

ownership of code. Instead, the entire team is responsible for the
codebase. This approach ensures that all team members have a
sense of ownership and responsibility towards the code.

 Projects with tight deadlines: The XP model can be used in

projects that have a tight deadline, as it emphasizes simplicity and
iterative development.

(Or).

(b). Illustrate an overview of Object-oriented Software

Engineering Development Activities and their products.
Object-Oriented Analysis and Design (OOAD) is a way to design software
by thinking of everything as objects like real-life things. In OOAD, we first
understand what the system needs to do, then identify key objects, and
finally decide how these objects will work together. This approach helps
make software easier to manage, reuse, and grow.

Important Aspects of OOAD.

Below are some important aspects of OOAD:
 Object-Oriented Programming: In this the real-world items are
represented/mapped as software objects with attributes and
methods that relate to their actions.
  Design Patterns: Design patterns are used by OOAD to help
developers in building software systems that are more efficient and
maintainable.
 UML Diagrams: UML diagrams are used in OOAD to represent the
different components and interactions of a software system.
 Use Cases: OOAD uses use cases to help developers understand
the requirements of a system and to design software systems that
meet those requirements.

Object-Oriented Analysis

Object-Oriented Analysis (OOA) is the process of understanding and

analysing the system requirements by looking at the problem scenario in
terms of objects.

 These objects represent real-world entities or concepts that are

relevant to the system being developed.
 During OOA, the goal is to identify the objects, their attributes,
behaviors, and relationships, without focusing on how the system
will be implemented.

For example: Let’s say you’re building a game:

 OOA helps you figure out all the things you need to know about the
game world – the characters, their features, and how they interact.
 It’s like making a map of everything important.
 OOA also helps you understand what your game characters will do.
It’s like writing down a script for each character.
 Every program has specific tasks or jobs it needs to do. OOA helps
you list and describe these jobs.
 In our game, it could be tasks like moving characters or keeping
score. It’s like making a to-do list for your software.
 OOA is smart about breaking things into different parts. It splits the
job into three categories: things your game knows, things your
game does, and how things in your game behave.
Object-Oriented design
In the object-oriented software development process, the analysis model,
which is initially formed through object-oriented analysis (OOA),
undergoes a transformation during object-oriented design (OOD) i.e
implementation of the conceptual model developed in OOA. This evolution
is crucial because it shapes the analysis model into a detailed design
model.
Furthermore, as part of the object-oriented design process, it is essential
to define specific aspects:
Data Organization of Attributes:
 OOD involves specifying how data attributes are organized within
the objects.
 This includes determining the types of data each object will hold
and how they relate to one another.

Procedural Description of Operations:

 OOD requires a procedural description for each operation that an

object can perform.
 This involves detailing the steps or processes involved in carrying
out specific tasks.

Challenge of Object-Oriented Analysis and Design(OOAD)

 Because objects and their interactions need to be carefully

explained and handled, it might complicate a software system.
 Because objects must be instantiated, managed, and interacted
with, this may result in additional overhead and reduce the
software’s speed.
 For beginner software engineers, OOAD might have a challenging
learning curve since it requires a solid grasp of OOP principles and
methods.
 It can be a time-consuming process that involves significant upfront
planning and documentation. This can lead to longer development
times and higher costs.
 OOAD can be more expensive than other software engineering
methodologies due to the upfront planning and documentation
required.

12. (a). Summarize on Petri nets with a suitable use case of your
choice.
Petri nets are a graphical and mathematical tool for modelling and
analysing dynamic systems, especially those involving concurrency,
parallelism, and synchronization. They use places, transitions, and arcs
to represent system components, events, and their relationships,
respectively. A common use case for Petri nets is modelling
manufacturing systems, allowing engineers to analyse and improve the
flow of materials, resources, and production processes.

Here's a more detailed breakdown:

Places:
 Represent conditions or states in the system (e.g., a part waiting to be
processed, a machine in a specific status).
Transitions:
Represent events or actions that can change the state of the system
(e.g., a machine starting a process, a part moving to the next stage).
Arcs:
Directed connections between places and transitions, showing the flow
of tokens (representing resources or data).
Tokens:
Represent resources or data flowing through the net, moving from one
place to another after a transition fires.

In the context of manufacturing systems, Petri nets can be used

to:

Model the flow of materials:

Visualize how raw materials move through different stages of
production (e.g., from receiving to storage, machining, assembly, and
shipping).
Analyse bottlenecks and inefficiencies:
Identify potential congestion points in the production line and suggest
improvements to optimize the flow of materials.
Model machine operations:
Represent the sequence of actions performed by machines, including
start, stop, wait, and process steps.
Analyse the impact of disruptions:
Evaluate how different events (e.g., machine breakdowns, raw material
shortages) can affect the production process.
Optimize production scheduling:
Explore different scheduling scenarios and their impact on throughput
and production costs.

Benefits of using Petri nets in manufacturing:

Visualization and communication:

Provide a clear and intuitive way to represent complex manufacturing
processes to different stakeholders, including engineers, managers,
and operators.
Analysis and optimization:
Help identify areas for improvement and guide decisions about
resource allocation, scheduling, and process optimization.
Simulation and prediction:
 Allow engineers to simulate different scenarios and predict the
outcome of changes to the production process.

In summary, Petri nets offer a powerful and versatile tool for modelling,
analysing, and improving manufacturing systems by visualizing the
flow of materials, resources, and production processes.

(Or)

(b). Illustrate the Interaction diagrams for Online Electric Vehicle

Purchase System.

Ans: An interaction diagram for an online electric vehicle (EV) purchase

system can be illustrated using various UML diagrams, such as sequence
diagrams and collaboration diagrams. These diagrams visually represent
the flow of interactions between different components or actors involved
in the purchase process. The main components/actors would include the
user, the system, and potentially external systems like payment gateways
or vehicle manufacturers.

Sequence Diagram Example:

13. (a) Distinguish between Coupling and Cohesion using a

suitable scenario?
Ans:

Coupling and Cohesion are two key concepts in software engineering that
are used to measure the quality of a software system’s design. Both
coupling and cohesion are important factors in determining the
maintainability, scalability, and reliability of a software system. High
coupling and low cohesion can make a system difficult to change and test,
while low coupling and high cohesion make a system easier to maintain
and improve.

Cohesion.
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 multiple
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.
Coupling refers to the degree of interdependence between software
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 little
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

Differences between Coupling and Cohesion

The differences between cohesion and coupling are given below:

Aspect Cohesion Coupling

Definition Cohesion refers to the Coupling refers to the
 degree to which elements degree of
within a module work interdependence
together to fulfil a single, betweensoftware
well-defined purpose. modules. High coupling
means that modules are
closely connected and
changes in one module
may affect other
modules.
ModuleDepende Cohesion is the concept of Coupling is the concept
ncy an intro-module of inter-module.
Purpose Cohesion represents the Coupling represents the
relationship within a relationships between
module. modules.
Quality Increasing cohesion is Increasing coupling is
good for software. avoided for software.
Focus Cohesion represents the Coupling represents the
functional strength of independence among
modules modules
Relationship Highly cohesive gives the Whereas loosely coupling
best software gives the best software
Example In cohesion, the module In coupling, modules are
focuses on a single thing connected to the other
modules
Creation Cohesion is created Coupling is created
between the same between two different
module modules
(Or)

(b) Summarize on the various Architectural styles in Software

Design?
Ans:
The software needs an architectural design to represent the design of the
software. IEEE defines architectural design as “the process of defining a
collection of hardware and software components and their interfaces to
establish the framework for the development of a computer system.” The
software that is built for computer-based systems can exhibit one of these
many architectural styles.

System Category Consists of

 A set of components (eg: a database, computational modules) that
will perform a function required by the system.
 The set of connectors will help in coordination, communication, and
cooperation between the components.
 Conditions that define how components can be integrated to form
the system.
  Semantic models that help the designer to understand the overall
properties of the system.

The use of architectural styles is to establish a structure for all the

components of the system.

Taxonomy of Architectural Styles

1. Data Centered architectures:

 A data store will reside at the center of this architecture and is
accessed frequently by the other components that update,
add, delete, or modify the data present within the store
 The figure illustrates a typical data-centered style. The client
software accesses a central repository. Variations of this
approach are used to transform the repository into a
blackboard when data related to the client or data of interest
for the client change the notifications to client software
 Data can be passed among clients using the blackboard
mechanism.

Advantages of Data centered architecture:

 Repository of data is independent of clients.

 Client work independent of each other
 It may be simple to add additional clients
 Modification can be very easy

2. Data Flow Architecture:

 This kind of architecture is used when input data is
transformed into output data through a series of
computational manipulative components.
 The figure represents pipe-and-filter architecture since it uses
both pipe and filter and it has a set of components called
filters connected by lines
 Pipes are used to transmitting data from one component to
the next.
 Each filter will work independently and is designed to take
data input of a certain form and produces data output to the
next filter of a specified form.
 If the data flow degenerates into a single line of transforms,
then it is termed as batch sequential. This structure accepts
the batch of data and then applies a series of sequential
components to transform it.

Advantages of Data Flow architecture:

 It encourages upkeep, repurposing, and modification.

 With this design, concurrent execution is supported.

3. Call and return architecture:

It is used to create a program that is easy to scale and modify. Many
sub-styles exist within this category. Two of them are explained below:
 Remote procedure call architecture: This components is
used to present in a main program or sub program architecture
distributed among multiple computers on a network.
 Main program or Subprogram architectures: The main
program structure decomposes into number of subprograms or
function into a control hierarchy. Main program contains number
of subprograms that can invoke other components.

4. Object Oriented Architecure:

The components of a system encapsulate data and the operations that
must be applied to manipulate the data. The coordination and
communication between the components are established via the
message passing.

Characteristics of Object-Oriented architecture:

 Object protect the system’s integrity.
 An object is unaware of the depiction of other items

Advantage of Object-Oriented architecture:

 It enables the designer to separate a challenge into a collection of

autonomous objects.
 Other objects are aware of the implementation details of the object,
allowing changes to be made without having an impact on other
objects

5. Layered Architecture.
 A number of different layers are defined with each layer performing
a well-defined set of operations. Each layer will do some operations
that becomes closer to machine instruction set progressively.
  At the outer layer, components will receive the user interface
operations and at the inner layers, components will perform the
operating system interfacing (communication and coordination with
OS)
 Intermediate layers to utility services and application software
functions.
 One common example of this architectural style is OSI-ISO (Open
Systems Interconnection-International Organisation for
Standardisation) communication system.

14. (a) Explain in detail about the criterion for completion of

software testing?

Ans:

The completion of software testing is determined by specific criteria

outlined in the test plan, ensuring the software meets defined quality
standards and is ready for release. These criteria are crucial for organized
quality control and include things like test case execution, bug resolution,
code coverage, and risk assessment. Essentially, test completion means
meeting the set benchmarks for a software to be considered ready for
production.

Here's a more detailed breakdown:

1. Defining Test Completion Criteria:

Test Plan:

The criteria are usually defined in the test plan, which outlines the
scope, objectives, and methods for testing.

Stakeholder Involvement:

All project stakeholders should agree on the criteria to ensure

alignment and understanding.

Risk-Based Approach:

The severity of risks to the software should influence the rigor of the
completion criteria, according to Software Testing Genius. Higher
risks necessitate more stringent criteria.

2. Key Elements of Test Completion Criteria:

 Test Case Execution: Ensuring all planned test cases have been
executed.
  Bug Resolution: Addressing critical and high-severity bugs, with a
focus on stability and quality.

 Code Coverage: A metric indicating the percentage of code

covered by tests, as explained by Tutorialspoint.

 Risk Assessment: Identifying and mitigating potential risks related

to the software's quality and functionality.

 Performance Testing: Validating the software's performance

under various conditions and workloads.

 Security Testing: Ensuring the software is secure against

vulnerabilities and threats.

 Test Data: Preparing and managing the necessary test data for
execution

 Documentation: Completing all testing documentation, including

reports and test case details

3. Completion at Different Levels of Testing:

Component Testing:

Focuses on achieving a high percentage of unit test coverage and

ensuring no critical defects impact component integration, according to
Tools QA.

Component Integration Testing:

Ensuring all integrated components have been tested and that there are
no critical defects impacting system testing.

System Testing:

A detailed closure report at this level, often including Key Performance

Indicators (KPIs) like 100% test execution, a high pass rate, minimal
critical defects, and completion of cross-browser/device, accessibility, and
analytics testing, according to Tools QA.

4. Benefits of Defined Test Completion Criteria:

 Organized Approach: Provides a structured way to manage

testing and ensure all crucial aspects are addressed.
 Quality Control: Helps maintain quality standards and ensures the
software meets defined requirements.
  Efficient Resource Allocation: Allows for better planning and
allocation of testing resources.
 Improved Collaboration: Fosters communication and
collaboration among stakeholders.
 Reduced Risk: Minimizes the risk of releasing a flawed product by
providing a clear framework for evaluating the software's quality.

In essence, test completion criteria act as a checklist to ensure that

software is thoroughly tested and meets the required standards before
release. They provide a framework for making informed decisions about
when testing is complete and when the software can be moved to the
next phase.

b) Compare White box testing and Black box Testing with a

Banking Application?

Ans: In a banking application developed using Object-Oriented Software

Engineering (OOSE), White Box testing focuses on examining the internal
workings of the code, including its structure, algorithms, and logic, while Black
Box testing focuses on testing the application's functionality from the end-user's
perspective without knowledge of its internal workings.
White Box Testing:
 Focus: Internal code, structure, and logic.
 Purpose: To ensure the code is correct, efficient, and meets design
specifications.
 Example: Unit testing individual banking functions like deposit, withdrawal, or
balance inquiry to verify that the calculations and data updates are accurate.
 Requires: Knowledge of the code and internal workings.
 Methods: Control flow testing, data flow testing, statement coverage, branch
coverage.
 Benefits: Helps identify structural issues, code defects, and ensures internal
logic is correct.
Black Box Testing:
Focus:
Functionality and behavior of the application from an end-user perspective.
Purpose:
To verify that the application meets requirements and performs as expected
from a user's standpoint.
Example:
Testing the entire banking application as a user would, including depositing,
withdrawing, checking balance, transferring funds, and ensuring these
processes are working correctly.
Requires:
No knowledge of the internal code or structure.
Methods:
Functional testing, non-functional testing (e.g., security, performance), error
handling, and integration testing.
Benefits:
Helps identify functional defects, ensures user experience meets requirements,
and provides a realistic view of how the application behaves in real-world
scenarios.
Comparison in a Banking Application:
Feature White Box Testing Black Box Testing

Focus Internal code and structure Functionality and user

experience

Knowledge of Required Not required

Internal Working

Testing Level Lower (e.g., unit, Higher (e.g., system,

integration) acceptance)

Examples Testing individual Testing the entire banking

deposit/withdrawal application flow, including
functions, verifying data multiple transactions and
updates security aspects

Purpose Ensuring correctness and Verifying that the

efficiency of individual application meets
components functional and non-
functional requirements

Developer/Tester Primarily developers Can be performed by either

Involvement developers or independent
testers
 15.a) Summarize the motivation behind adopting Devops in Software
Engineering?
Ans: The primary motivation for adopting Devops in software engineering is to
streamline the software development lifecycle, leading to faster delivery of
higher quality software. It achieves this by fostering collaboration between
development and operations teams, automating processes, and facilitating
continuous feedback. This approach breaks down silos, improves
communication, and enables organizations to respond more quickly to changing
customer needs and market demands.
Here's a more detailed breakdown of the motivations:
Faster time to market:
DevOps accelerates the entire software development lifecycle, from code
creation to deployment, allowing businesses to bring new features and updates
to users faster.
Improved software quality: By automating testing and incorporating
continuous feedback, Devops helps identify and fix issues earlier in the process,
resulting in higher quality software.
Increased agility and responsiveness:
Devops enables organizations to adapt more quickly to changes in the market,
user needs, and technology trends.
Enhanced collaboration:
Devops fosters a collaborative environment where development and operations
teams work together seamlessly, breaking down traditional barriers and
improving communication.
Reduced operational costs:
Automation and continuous feedback loops in Devops can reduce manual
tasks and improve efficiency, leading to lower operational costs.
Increased innovation:
By creating a faster and more efficient software development process, Devops
allows organizations to experiment with new technologies and approaches
more readily.
Better resource utilization:
 DevOps practices optimize resource utilization across the entire software
development lifecycle, ensuring that resources are used efficiently and
effectively.

(Or)

b) Demonstrate the application of cloud as a platform in project

management through an appropriate illustration?
Ans: A cloud-based project management system facilitates seamless
collaboration among team members, provides real-time access to project
information, and streamlines communication and task management. For
example, a software development team can use a cloud platform like Asana to
track tasks, assign roles, manage dependencies, and communicate updates to
stakeholders, all from anywhere with an internet connection.
Here's a more detailed illustration in OOSE (Object-Oriented Systems
Engineering):
Scenario: A remote software development team working on a new mobile
application.
Cloud as a Platform: The team utilizes a cloud-based project management
system (e.g., Asana, Trello) to manage the project lifecycle.
OOSE Classes and Relationships:
1. Project:
 Attributes: projectId, projectName, projectDescription, startDate, endDate, status
 Methods: addTasks(), removeTasks(), updateStatus(), getTaskDetails()
2. Task:
 Attributes: taskId, taskName, taskDescription, status, priority, assignedTo, dueDate, startTime, endTime
 Methods: updateStatus(), assignTo(), getDetails()
3. TeamMember:
 Attributes: memberId, memberName, email, role
 Methods: getTaskAssignment(), updateTaskStatus()
4. CommunicationChannel:
 Attributes: channelId, channelType (e.g., email, chat, forum)
 Methods: sendMessage(), receiveMessage()
5. FileRepository:
 Attributes: fileId, fileName, fileSize, uploadDate
 Methods: uploadFile(), downloadFile(), getFileDetails()
Relationships:
 Project: has many Tasks.
 Task: is assigned to one TeamMember.
 Project: uses CommunicationChannel for team communication.
 Project: stores files in FileRepository.
Cloud Platform's Role:
Centralized Data Storage:
The cloud platform stores all project-related data (tasks, documents,
communication) in a central location, accessible to authorized team members.
Real-time Collaboration:
The cloud platform enables real-time collaboration on tasks, allowing team
members to make updates and receive feedback simultaneously.
Accessibility and Mobility:
The cloud platform allows team members to access project information and
tools from anywhere with an internet connection, enhancing mobility and
flexibility.
Scalability:The cloud platform can scale to accommodate the needs of
growing project teams and large datasets.
Integration:
The cloud platform can be integrated with other cloud-based applications (e.g.,
email, file storage) for seamless workflow.
Benefits of Using Cloud in Project Management:
Improved collaboration and communication, Enhanced project visibility and
control, Increased efficiency and productivity, Reduced costs associated with
infrastructure and software, and Greater flexibility and accessibility for project
teams.

PART-C(15*1=15)

16. a) Draw UML Diagram for Hospital Management System in Detail?

Ans: A detailed UML diagram for a Hospital Management System would
include several key elements. This diagram should represent the
system's classes, their attributes, and relationships to model the
functionalities of the system.
Usecase diagram:

Class diagram :

Sequence diagram:
 Activity diagram:

Collaboration diagram:

B) Scenario:

Assume a Hotel Management System for a chain of hotels with

multiple hranches. This system would facilitate online booking of
hotel rooms, where users can search for hotels, browse available
rooms based on desired tariffs, check room availability for
 specified datos, and complete bookings by making a 50%
payment through a payment gateway.

Question

For the given Scenario, identify classes, attributes, and methods

for the system and Draw a class diagrams showing the
relationships between

Ans: Ideas for Solving the Problem

1. Identify Key Entities: The problem describes a hotel management

system. Key entities will likely include Hotels, Rooms, Bookings, Users, and

Payments.

2. Define Attributes: Each entity has attributes that describe it. For

example, a Hotel has a name, location, and rating. A Room has a room

number, type, and tariff.

3. Define Methods: Each class will have methods that define its behavior.

For example, a Hotel class might have a method to search for available

rooms. A Booking class might have methods to create, modify, or cancel a

booking.

4. Determine Relationships: Consider how the entities relate to each

other. A Hotel has many Rooms. A User makes many Bookings. A Booking

involves a Room and a Payment.

5. Draw the Class Diagram: Represent the classes, attributes, methods,

and relationships visually using UML notation.

Solution Steps

Step 1: Identify Classes

Based on the problem description, the following classes are identified:

 Hotel: Represents a hotel branch.

 Room: Represents a room in a hotel.

 User: Represents a user of the system.

 Booking: Represents a booking made by a user.

 Payment: Represents a payment made for a booking.

Step 2: Define Attributes for Each Class

 Hotel:

 hotelID: Integer (Unique identifier for the hotel)

 name: String (Name of the hotel)

 location: String (Location of the hotel)

 rating: Float (Hotel rating, e.g., 4.5 stars)

 contactInformation: String (Phone number, email, etc.)

 Room:

 roomID: Integer (Unique identifier for the room)

 roomNumber: String (Room number, e.g., "101")

 roomType: String (e.g., "Single", "Double", "Suite")

 tariff: Float (Price per night)

 availability: Boolean (True if available, False otherwise)

 User:

 userID: Integer (Unique identifier for the user)

 username: String (User's username)

 password: String (User's password)

 email: String (User's email address)

 phoneNumber: String (User's phone number)

 Booking:

 bookingID: Integer (Unique identifier for the booking)

 userID: Integer (Foreign key referencing User)

 roomID: Integer (Foreign key referencing Room)

 checkInDate: Date (Check-in date)

 checkOutDate: Date (Check-out date)

 numberOfGuests: Integer (Number of guests)

 bookingDate: Date (Date the booking was made)

 status: String (e.g., "Confirmed", "Cancelled")

 Payment:

 paymentID: Integer (Unique identifier for the payment)

 bookingID: Integer (Foreign key referencing Booking)

 paymentDate: Date (Date of payment)

 amount: Float (Amount paid)

 paymentMethod: String (e.g., "Credit Card", "Debit Card")

 transactionID: String (Transaction ID from the payment gateway)

Step 3: Define Methods for Each Class

 Hotel:

 addRoom(Room room): Adds a room to the hotel.

 removeRoom(Room room): Removes a room from the hotel.

 getAvailableRooms(Date checkInDate, Date checkOutDate): Returns a list of

available rooms for the given dates.

 searchRooms(String roomType, float maxTariff): Returns a list of rooms

matching the search criteria.

 Room:

 isAvailable(Date checkInDate, Date checkOutDate): Checks if the room is

available for the given dates.

 setAvailability(Date checkInDate, Date checkOutDate, boolean availability):

Sets the availability of the room.

 getTariff(): Returns the tariff of the room.

 User:

 register(): Registers a new user.

 login(): Logs in an