DHYANESH M 710723104302

Ex.no: 1 OBJECT ORIENTED SOFTWARE

Date: ENGINEERING STUDY OF UML

AIM:
To learn about object-oriented software engineering by using study of UML notations.

UML NOTATION:
1. Unified Modeling Language.
2. Set of notations and conventions used to describe and model an application.
3. Universal language for modeling systems.
4. Standard notation for OO modeling systems.
5. Does not specify methodology to develop an application.

UML DIAGRAMS:
1. Class Diagram
2. Use Case Diagram
3. Behavioral Diagram
4. Interaction Diagram
i. Sequence Diagram
ii. Collaboration Diagram
5. State Chart Diagram
6. Activity Diagram
7. Implementation Diagram
i. Component Diagram
ii. Deployment Diagram

CLASS DIAGRAM:
 Shows the static structure of the model. Collection of static modeling elements such as classes
and their relationships connected as a graph.
 Provides visual representation of objects, relationships and their structures.
Class:-
 A class is a set of objects that share a common structure and common behavior.
 It is represented as: <Class>
<Attribute>
<Operations>

1
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
 DHYANESH M 710723104302

Interface:-
 Specifies the externally-visible operations of a class and/or component.

Association:-
 Model properties of associations.
 The properties are stored in a class and linked to the association relationship.
 Example,

Bank Account Person

Generalization:-
 A generalize relationship is a relationship between a more general class or use case and a
more specific class or use case.
 Example,
Vehicle

Bus Truck Car

USE CASE DIAGRAM:

 Set of use cases enclosed by system boundary, communication association between actors and
use cases, and generalization among use cases.

Actors:-
 External factors that interact with the system from the user's perspective.

Use Cases:-
 Set of scenarios that describe how actor uses the system.
 Represented as,

Relationship:-
 Communication – Communications with the use case normally.
 Uses – Shown by generalization arrow from the use cases.
 Extends – Used when one case does more than another that is similar to it.

2
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
DHYANESH M 710723104302

BEHAVIOR DIAGRAM:
 Behavioral diagrams describe the dynamic aspects of a system, such as how objects interact
and change state over time in response to events or activities.
 They focus on system behavior, workflows, and interactions, including diagrams like Use
Case, Activity, Statechart, Sequence, and Collaboration diagrams.

INTERACTION DIAGRAM:
 Diagrams that describe how group of objects are collaborated.

I. SEQUENCE DIAGRAM:
 Describes the behavior of the system through interaction between the system and
the environment in time sequence.
 Two dimensions:
Vertical dimension – represents time. Horizontal
dimension – represents objects.
 Life line – Object's existence during the interaction

Relationship:
 Communication – communications with the use case normally.
 Uses – Shown by generalization arrow from the use cases.
 Extends – Used when one case does more than another that is similar to it.

Object 1 Object 2

<Events>

II. COLLABORATION DIAGRAM:

 An interaction diagram that shows the order of messages that implement an operation or
a transaction.
 Collaboration diagrams show objects, their links, and their messages

<Events>
Object 1 Object 2

Object:
 An object has state, behavior, and identity.
 Objects interact through their links to other objects.

3
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
DHYANESH M 710723104302

Link:
 A link is an instance of an association, analogous to an object.
Message:
 A message is the communication carried between two objects that trigger
an event.

STATECHART DIAGRAM:
 Models the dynamic behavior of individual classes or any other kind of object.
 Shows the sequences of states, events, and actions.
State:-
 Represents a condition or situation during the life of an object during which it satisfies
some condition or waits for some event.

<State>

Start state:-
 Shows the beginning of workflow.
End state:-
 Represents the final or terminal state.

ACTIVITY DIAGRAM:
 Used for modeling the sequence of activities in a process.
 Special case of a state machine in which most of the states are activities and most of the
transitions are implicitly triggered by completion of the actions in the source activities.
Activity:-
 Represents the performance of task or duty in a workflow.

<Activity>

Swim lanes:-
 Represents organizational units or roles within a business model.

IMPLEMENTATION DIAGRAM:
 Shows the implementation phase of system development.
 Two types of implementation diagrams:
i. Component diagram
ii. Deployment diagram
4
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
DHYANESH M 710723104302

I. COMPONENT DIAGRAM:
 Models the physical components in the design.
 A graph of the design’s components connected by dependency relationships.
 Includes concept of packages.
 Package is used to show hoe classes are grouped together.
II. DEPLOYMENT DIAGRAM:
 Shows the configuration of runtime processing elements and software components.
 It is a graph of nodes connected by communication association.
 Nodes are the components that are connected to other components
through dependencies.
 Used in conjunction with component diagrams to show the distribution of
physical modules.

RESULT:
Thus, the study of UML notations has been successfully completed.

5
22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING LABORATORY
DHYANESH M 710723104302

Ex.no: 2 Document the Software Requirements

Date:
specification (SRS) for the identified
system
AIM
: To document the Software Requirements Specification (SRS) for the Online
Course Reservation System.

SOFTWARE REQUIREMENT SPECIFICATION:

1. SOFTWARE INTERFACE:
 Front-End Client:
The user interface is designed for students and administrators using HTML and JSP It allows users to
view courses, reserve slots, and manage their bookings easily.
 Web Server:
The application runs on the GlassFish server provided by Oracle.
 Back-End:
Uses a MySQL or PostgreSQL database to store user details, course information, and reservations
.
 HARDWARE INTERFACE:
The client systems (agent workstations) are directly connected to a central server via a secure LAN
or intranet.
All client machines interact with the centralized database hosted on the server to retrieve or update
Conference operational data in real time.
DESCRIPTION:
This project outlines the main software requirements for the Online Course Reservation System:

1. Front-End Development:
 HTML: Structures the webpages for login, course catalog, reservation form,
and confirmation pages.
 CSS: Styles the webpages to be user-friendly and responsive on different devices.

 JavaScript: Adds interactive features like live search, validation of form inputs, and
dynamic course availability display.
2. Back-End Development:
 Java/PHP/Node.js: Handles the business logic such as booking a course,

updating availability, and user login.

 Spring Boot (Java): Supports creating APIs for booking and managing course data.

 Express.js (Node.js): Used if Node.js is chosen for building fast REST APIs for
student interactions.

3. Database:

22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING

LABORATORY
DHYANESH M 710723104302
 MySQL or PostgreSQL:
Stores student information, course details, seat availability, and reservation history.
4. Web/Application Server:
 Apache Tomcat (for Java-based back-end):
Hosts the application and manages user sessions and requests.
 Node.js (for JavaScript-based back-end):
Useful for serving both front-end and back-end operations efficiently.
5. Frameworks:
 Hibernate (Java):
Helps in connecting Java classes with the database easily for storing and updating data like course
reservations.
6. Testing Tools:
 JUnit (Java):
Used to test back-end functions like seat allocation and user authentication.
 Selenium (optional):
Useful for checking if the user interface works as expected (e.g., booking flow).
7. Operating System:
 Windows/Linux/Mac OS:
The system should work well on any major operating system so students and staff can use it on their
devices.

RESULT:
The Software Requirements Specification (SRS) for the Online Course Reservation System has been
clearly documented.It lists the required tools and technologies needed to build a reliable and user-friendly
course booking platform for students.

22UCS503 – OBJECT ORIENTED SOFTWARE ENGINEERING

LABORATORY