IDENTIFY A SOFTWARE SYSTEM THAT NEEDS TO BE

DEVELOPED

Introduction:
CASE tool known as computer-aided software engineering tools is a kind of component –
based development which allows its users to rapidly develop information systems . The
prefabricated components are customized as per the requirements of the customers.

Charasteristics of CASE:
Some of the characteristics of case tools that make it better than customised
development are:

 It is a grapic oriented tool

 It supports decomposition of process
Some typical Case tools are:
 Unified Modeling Language
 Data Modeling Tools
 Source Code Generation Tools

Introduction to UML(Unified Modeling Language):

The UML is a language for specifying, constructing,visualizing and documenting the
software system and its component.

The UML defines nine graphical diagrams:

1. Class diagram

2. Use-Casediagram

3. Behaviourdiagra

3.1 Interaction diagram

3.1.1 Sequence diagram
3.1.2 Collaboration diagram
3.2 State chart diagram
3.3 Activity diagram
4. Implemented diagram

4.1 Component diagram

4.2 Deployment diagram

Notation Elements:
These are explanatory ports of UML. They provide the information for understanding the
necessary details of the diagram.
Relations in the UML:
These are four kinds of relationship used in an UML Diagrams, they are:
 Dependency
 Association
 Generation
 Replication

Use CASE diagram:

Description:
A use case is a set of scenarios tied together by a common user goal.
A use case is a behavioural diagram that shows a set of use case and their relationships.
Class diagram:
A class diagram describes the types of objects in system and various kinds of relationships
that among them.

A class diagram is represented as:

<<class name>.
<<Attribute 1>>
<<Attribute n>>
<<operation()>>

State Chart:
The state chart diagram made the dynamic behaviour of individual classes.
A state chart contains one state ‘state’ and multiple ‘end’ states.
Activity diagram:
Activity diagram provides a way to model the workflow of a development process.
Activity diagrams can model different types of diagram.There are various tools involed in the
activity diagram.

Sequence diagram:
A sequence diagram is a graphical view of scenario that shows object interaction in a time
based sequence what happens first what happens next.
Sequence diagram are closely related to collobration diagram.
The sequence diagram for the e-mail client system consists of the following objectives.
The various objects in e-mail client system are as follows:

 User
 Website
 Login
 Groups
Collaboration diagram:
Collaboration diagram and sequence diagrams are alternate of an interaction.
A collaboration diagram is an interaction between that shows the order of messages that
implement an operation or a transaction.
It shows objects, their links and their messages. They can allso contain simple class
instancesand class utility instances.
 DOCUMENT THE SOFTWARE REQUIREMENTS
SPECIFICATION(SRS) FOR
THE IDENTIFIED SYSTEM

Problem statement:
The Current method of course enrollment typically involves manual registration processes,
paper forms, and fragmented information across multiple platforms. This leads to several pain
points for both students and educational institutions.

Students face difficulty in finding courses that match their interests, schedules, and
prerequisites a midst a vast array of options.

Software requirement specification:

Introduction:
The “Online Course Reservation System” has been developed to override the problems
prevailing in the providing manual system.

Purpose:
The Purpose of the Online Course Reservation System is to provide a streamlined and
efficient platform for both students and educational institutions to manage the process of course
selection, registration, and enrollment for online courses. By digitizing and automating these
processes, the system aims to achieve the following objectives.

Scope:
 Browse available course by category, institution, or keyword.

 View detailed information about each course, including schedule, instructor, and
prerequisites.

Reference:
IEEE software requirements specification format

Definitions, Acronyms and the Abbreviations:

 OCRS: Online Course Reservation System.

 Registrar: Refers to the Super user with the privilege to manage the entire system.
 Applicant: A Student who wishes to register for course.
 Waitlist: A list of student who wish to register for a course if space between available.
 Capacity: The maximum number of students allowed to register for a course.
 Student: An individual enrolled in a course.
  Course: A unit of study offered by an institution.

Technologies to be used:
 HTML

 CSS

 JavaScript

 React

 Java

 Python

 C

Tools to be used:
 Eclispse IDE (Integrated Development Environment)

 Rational Rose tool for developing UML Patterns.

Overview:
The Online Course Reservation System (OCRS) is a web-based platform designed to
streamline the course registration process for educational instituations. It offers a user-friendly
interface for both students and administrator to manage course enrollment efficiently.

Overall Description

Product Perspective:
Product Perspective of Online Course Reservation System focus on delivering a efficiency
champion, accessibility advocate, transparency enforcer, communication bridge, information
powerhouse that meets need of customer course operators.

Hardware Interface:
The hardware interface for an online course reservation system primarily consists of the
devices that users interact with to access the system.

Software Interface:
 Backend System – MYSQL, Oracle

 APIs and Web Services – Stripe, Banking APIs.

Specific Requirements

User Interface:
 Home Page: Search bar for finding courses by keyword, subject, or instructor.

 Course Catalog: Detailed Course information including descriptions, schedules,

instructors, and capacity.

 Registration Process: User-friendly interface for selecting course and building a schedule.

Hardware Interface:
 Number of users.

 Data Storage.

 System Complexity.

Software Interface:

 User interface.
 Backend System.

Communication Interface:
 User – Facing Communication.

 System – to – System Communication.

Software system Attributes:

1. Scalability: The System should be able to accommodate a growing number of users and
course without experiencing performance degradation.

2. Accessibility: The UI should be accessible to users with disabilities, adhering to WCAG

guidelines for color contrast, keyword navigation, and screen reader compatibility.
USE CASE DIAGRAM- Online Course Reservation System.

CLASS DIAGRAM- Online Course Reservation System.

STATE CHART DIAGRAM- Online Course Reservation System.
 IDENTIFY USE CASES AND DEVELOP USE CASE

MODEL DESCRIPTION

Guideline: To find the use cases:

Use cases are defined to satisfy the goals of the privacy actors. hence the basic
procedure is:

Step 01: Choose the system boundary. it is just a software application the hardware and
application as a unit. That plus a person using it or an entire organization.

Step 02: Identify the primary actors those that have goals fulfilled through using service of
the system. the following question help identify other that may be missed

Who starts and stops the system? Who does system administration?

Who does user and security management IS ‘time’ an actor become the system does
in response to a time event?

Is there a monitoring process that restarts the Who evaluates system activity or
system if it fails? performance?

Who starts and stop the system? Who does system administration?

Who evaluates logs? Errors or failures?

Step 03: Identify the goals for each primary actor

For example, use this table to prepare actor goal list.

Actor Goal

1. Student The Student actors selects a course and check

for available seats.

2. Administrator Manage course, add/remove instructors, view

reservation reports.

Step 04: Define use cases

In general define one use case for each user goal name the use case similar to the user
goalstart the name of use case with a verb.

UML Notation:
Actor: An actor as mentioned is a user of the system and is depicted using a stick figure. The
role of the uses is written beneath the icon.
 Use Case: A use case is funtionality provided by the system , typically described as verb object.
Usecases are depicted with an ellipse.
Association:
Association are used to link Actor with the use case and indicate that an actor participate
in the use case in some from. Association are depicted by a line connecting theActor and the use
case.

Actor Association Use cases

Use Cases:
 The system will consist of login screen to authenticate the participants whose
informationis update in the database.
 The applicant make registration for the customer or agent to make an order and agent
cancheck the order.
 The customer order the stock and agent maintain company information and
updating billand customer records.
The is how the whole system works

Functional Requirements:
Use Case:
The use case describes how an applicant login into the Online Course Reservation System.

Use Case Section Comment

Use case name Login

Scope Online Course Reservation System

Primary actor Student

State holders and Interest list -Student: login into OCRS

-Admin: Controls OCRS
 Main success Scenario 1. The system requests the actor to
enter his/her name and password
2. The actor enter his/her name and
password
3. The system validates the entered
name and password
4. The system validates the entered
name and password and logs the
actors into the system

Frequency of Occurance Could be nearly continuous

Non-Functional requirements:
Non –functional requirements are often called qualities of a system non-functional
requirements can be divided into two main categories
1. Execution qualities: such as security and usability which are observable at runtime.

2. Evaluation qualities: such as testability maintainability extensibility and scalability

which are emboided in the static structure of the software system

Design constraints:
The system shall provide a window-based desktop interface.

USE CASSE DIAGRAM- Online Course Reservation System.

 IDENTIFY THE CONCEPTUAL CLASSES AND DEVELOP A
DOMAIN MODEL AND ALSO DERIVE CLASS DIAGRAM

Description:
A class diagram in the Unified modelling Language(UML) is a type of Static
StructureDiagram that describes the structure of a system by showing the systems classes,
their attributes and the relationship between the classes.
The class in a class diagram represent both the main objects and or interactions in the
application and the object to be programmed. In the class diagram there classes are
represented with boxes which contain three parts.
 The upper part holds the name of the class.
 The middle part contains the attributes of the class.
 The bottom part gives the methods or operations the class can take or undertake.

For example: A class name Login contains attributes and operations (methods)

Login
Name: String

Roll No: Integer

Mark: Integer

study()

In a system design of a system, a number of classes are identified and grouped together in a
class diagram which helps to determine the statically relations between those objects. With
detailed modelling, the class of the conceptual design are often split in a number of
subclasses.
CLASS DIAGRAM- Online Course Reservation System.
 USING THE IDENTIFIED SCENARIOS, FIND THE
INTERACTION BETWEEN OBJECTS AND REPRESENT
THEM USING UML SEQUENCE AND COLLABORATION
DIAGRAMS

Description:
Sequence diagrams document the interaction between classes to achieve a result,such as
a use case. Because UML is designed for object oriented programming messages. It lists the
objects horizontally, and time vertically, and models these message overtime.

Notation:
In a sequence diagram, classes and actors are listed as columns, with verticallifelines
indicating the lifetime over time.

Actor:

Lifeline:

Activation:
Message:

Collaboration Diagram:
It illustrate that object interaction in a graph or network format in which object can be
placedanywhere on the diagram.
In collaboration diagram the relationship between student and online course reservation
system.

SEQUENCE DIAGRAM- Online Course Reservation System

COLLABORATION DIAGRAM- Online Course Reservation System.
DRAW RELEVANT STATE CHART AND ACTIVITY DIAGRAM FOR
THE ONLINE COURSE RESERVATION SYSTEM

State Chart Diagram Description:

UML preserves the general form of the traditional state diagram. The UML state
diagrams are directed graphs in which nodes denote state and connectors denote state
transitions.

The Main Purposes of using State Chart Diagrams:

 To model dynamic aspect of a system
 The model life time of a reactive system
 To descriptive different states of an object during its life time
 Define a state machine to model states of an object
Steps to Prepare State Chart Diagram:
 Identify important object to be analyzed
 Identify the states

 Identify the events

State Chart Diagram:
The purposes of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram.

Activity Diagram Description:

Activity diagram are used to document workflows in a system, from thebusiness level
down to the operational level.

Activity States:
Activity states mark an action by an object. The notations for these states areround
rectangles, the same notations as found in state chart diagram.

TRANSITION:
When an activity state is completed, processing moves to another activity states.
Transitions are used to mark this movement.
Swim Lane:
Swim lanes divide activities according to objects in column format and placing
activities by that object within the column.

Initial State:
It makes the entry point and the initial activity state.

Final State:
Final states make the end of the modelled workflow

Synchronization Box:
Activities often can be done in parallel. These are modelled as solid rectangles,
with multiple transition going in and/or out.
 STATE CHART DIAGRAM- Online Course Reservation
System

ACTIVITY DIAGRAM- Online Course Reservation System