HARISH M S 710723104027

Ex.no: 4 IDENTIFY THE CONCEPTUAL CLASSES AND

DEVELOP A DOMAIN MODEL AND DERIVE A
Date:
CLASS DIAGRAM FROM THE DOMAIN MODEL
AIM:
To identify the key conceptual classes relevant to the Conference Management System and represent
their attributes and relationships through a Domain Model. This model will then be used to derive a Class
Diagram that accurately reflects the structural design and supports further software development.
CONCEPTUAL CLASS:

A conceptual class is an abstract representation of a real-world entity or concept within a specific

domain. It serves as a blueprint for modeling the system's structure and behavior in software development.
Conceptual classes encapsulate attributes (data) and behaviors (methods or functions) relevant to the entity
they represent.

CONCEPTUAL CLASS FOR CONFERENCE MANAGEMENT SYSTEM:

• Conference
The Conference class represents a scheduled academic or professional event. It is uniquely identified by
conferenceID. It contains information such as the title, date, venue, organizer, and list of speakers.
▪ Attributes:
› conferenceID
› title
› date
› venue
› organizer
› topic
› speakerList
› status

› Methods:
› addConference(): Adds a new conference to the system.
› updateConferenceDetails(): Edits the details of an existing conference.
› deleteConference(): Deletes a conference record.
› assignSpeaker(): Assigns a speaker to a conference.
› checkConferenceStatus(): Checks the current status of the conference.
› markAsCompleted(): Updates the status when the conference is completed.

14
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
HARISH M S 710723104027

• Attendee
The Attendee class represents participants who register to attend the conference. Each attendee is
uniquely identified by an attendeeID.
▪ Attributes:
› attendeeID
› name
› email
› organization
› contactNumber
› registrationStatus
▪ Methods:
› registerAttendee(): Registers a new attendee in the system.
› updateProfile(): Updates personal and professional information.
› viewSchedule(): Displays the list of sessions registered by the attendee.
› requestSessionRegistration(sessionID): Sends a request to attend a specific session.
› cancelRegistration(): Cancels the attendee's conference registration.
› viewNotifications(): Displays announcements or messages sent by the admin.

• Admin
The Admin class handles administrative control over the system. Admins manage conferences,
attendees, speakers, sessions, and notifications.
▪ Attributes:
› adminID
› username
› password
› role
▪ Methods:
› login(): Authenticates admin access.
› logout(): Ends the admin session.
› addConference(): Adds a new conference to the system.
› removeConference(conferenceID): Removes a specific conference.
› updateConference(conferenceID): Updates details of an existing conference.
› manageAttendee(attendeeID): Edits or removes attendee records.
› manageSession(sessionID): Manages conference sessions (create, edit, delete).

15
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
HARISH M S 710723104027
› sendNotification(message): Sends messages or alerts to all users.

• Sesssion

The SessionRegistration class models the registration and attendance tracking of sessions by
conference attendees.
▪ Attributes:
› registrationID
› sessionID
› attendeeID
› registrationDate
› attendanceStatus
› attendanceStatus
▪ Methods:
› issueBook(studentID, bookID): Issues a book to a student.
› returnBook(): Accepts and processes book returns.
› calculateDueDate(): Determines the due date based on rules.
› calculateFine(): Calculates overdue fines.
› isOverdue(): Checks if the book is returned late.
› generateReceipt(): Provides a receipt for issue/return.
• Category
The SessionCategory class is used to classify sessions into different categories such as technical,
keynote, workshop, or panel.

▪ Attributes:
› categoryID
› name
› description
▪ Methods:
› addCategory(): Adds a new category.
› updateCategory(): Updates the details of an existing category.
› deleteCategory(): Deletes a session category.
› listBooksInCategory(): Displays all sessions under a specific category.
• Notification
The Notification class handles alerts, messages, and reminders sent to attendees (e.g., session start time,
schedule changes, feedback requests).

16
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
HARISH M S 710723104027

▪ Attributes:
› notificationID
› message
› recipientID
› dateTime
› type
▪ Methods:
› sendNotification(attendeeID, message): Sends a message or reminder to the
attendee.
› scheduleNotification(): Schedules future notifications.
› viewNotifications(): Displays all notifications for the user.

DOMAIN MODEL:

A Domain Model is a conceptual representation that outlines the real-world entities relevant to a
specific problem domain and their relationships. It acts as a bridge between the problem space (real-world
understanding) and the solution space (software implementation), serving as a foundational guide for
designing the system.

In the Conference Management System, the domain model identifies the core concepts involved in managing
academic or professional conferences, such as Conferences, Admins, Sessions, Attendees, and Notifications.
It defines their attributes and associations without diving into technical implementation or specific data
structures.
This model helps in:

• Visualizing the major components and actors of the system.

• Understanding how data flows between different parts of the system.
• Assisting developers, testers, and stakeholders in aligning their expectations.
• Laying the groundwork for deriving a Class Diagram during the design phase.

CLASS DIAGRAM:
A Class Diagram is a key component of UML (Unified Modeling Language) that provides a static view
of a system’s structure. It models the classes (blueprints for objects), their attributes (data), methods (behavior),
and the relationships among them. It plays a critical role in object-oriented analysis and design.

In the Conference Management System, the class diagram represents the logical structure of the application
by identifying core classes such as Conference, Admin, Session, Attendee, SessionRegistration,
SessionCategory, and Notification.

17
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
HARISH M S 710723104027

OUTPUT:

RESULT:
Thus, the conceptual classes of the Conference Management System were successfully identified, and
a Domain Model and corresponding Class Diagram were developed to represent the system's structure and
relationships effectively.

18
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY