Course Reservation
Course Reservation
LOGIN SELECTION:
ENROLL:
DATABASE:
USER TABLE:
COURSE REGISTERED:
COURSE TABLE:
ABSTRACT:
The "Online Course Reservation System" is a web-based platform designed to
streamline the course enrollment process for students and simplify
administrative tasks for educators. The system offers user and admin login
functionalities, providing separate interfaces tailored to the needs of each user
group.
INTRODUCTION:
The "Online Course Reservation System" with user and admin login
functionality. This system provides a seamless experience for both students and
administrators in managing course enrollments.
Upon logging in, users are greeted with a user-friendly interface displaying
available courses. Users can easily browse through the course offerings and
enroll in their desired classes with just a few clicks.
For administrators, a dedicated login interface grants access to administrative
features. Admins can view a list of registered students for each course by simply
clicking the "Display Details" button. This feature streamlines administrative
tasks and ensures efficient management of course enrollments.
Overall, our "Online Course Reservation System" simplifies the process of
course enrollment for users while providing administrators with convenient
tools to oversee student registrations effectively.
TASKS PERFORMED IN THIS PROJECT:
For Users:
SYSTEM REQUIREMENTS
1.Hardware
Server: Multi-core processor, 4GB RAM (16GB recommended), SSD
storage
Client Devices: Modern web-browsing devices with adequate processing
power and memory
2.Software
SYSTEM DESIGN:
System design is a process through which requirements are translated into a
representation of software. Initially the representation depicts a holistic view of
software. Subsequent refinement leads to a design representation that is very
close to source code. Design is a place where quality fostered in software
development. Design provides us with representation of software that can be
assessed for quality; this is the only way that can accurately translate the
customer requirements into finished software product or system. System design
serves as the foundation for all software engineering and software maintenance
steps that follow.
We look the design process from three distinct perspectives:
• Conceptual Design
• Logical Design
• Physical Design
The higher view is the conceptual view, followed by the logical view and finally
the physical view. In designing an application, we generally begin and end each
phase in a sequentially order, although they may overlap one another along the
way.
Conceptual Design
Conceptual Design is the process of acquiring and evaluating, documenting and
then validating what the user envisions to be the business relation. It identifies
the user and business requirements of the application and leads to a business
solution as seen by the user. All applications are built to solve business
problems, and it is important to pay close attention to principle that the business
need drives application development. At any point in the design process, the
current state of the design should be directly traceable to a business problem and
requirements. To achieve this conceptual design is driven by developing usage
scenarios. These scenarios are a direct representation of the user’s view of the
solution to a specific business problem.
Logical Design
Logical Design derives business objects and their related services directly from
these usage scenarios. The logical view of the solution provides a basis for
evaluating different physical options. It also formalizes the solution for the
project team. The idea of the application is that the system first emerges in
logical design. Its boundaries and business objects and it contains the system
definition. Logical design specifies the interfaces between the system and
external entities, such as users and other systems. Within a system there may be
a number of sub-systems, and these boundaries are also specified.
• File Specifications
• Processing Specifications
Logical design should be technologically independent as possible, in order to
separate system behaviour issues from system implementation issues.
Implementation constraints should only be considered only after the project
team verifies that the essential behaviour has been incorporated onto a logical
design. This approach does not establish a technical direction until the system is
well understood and documented
Physical Design
The purpose of Physical Design is to translate the logical design into a solution
that can be implemented effectively, according to performance, administration
and development process requirements. This physical view should correctly
implement the desired system behaviour while meeting the constraints imposed
by the technology. In Physical Design, the perspective shifts from an abstraction
of system behaviour to an implementation of the behaviour. Whereas the logical
design is largely technology independent, physical design is necessarily tied to
chosen set of technologies, these being the hardware and software on which the
application will run.
DESIGN:
ONLINE COURSE
REGISTRATION SYSTEM Database
Add
student/
Staff
View details
Login
ER DIAGRAM:
USECASE DIAGRAM:
STATECHART DIAGRAM:
SEQUENCE DIAGRAM:
DEPLOYMENT DIAGRAM:
COLLABORATION DIAGRAM:
COMPONENT DIAGRAM:
CLASS DIAGRAM:
IMPLEMENTATION:
import java.sql.Connection;
DatabaseUtil.getConnection("course_reservation_system");
}
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated
Code">//GENBEGIN:initComponents
loginbtn.setText("Login"); loginbtn.addActionListener(new
java.awt.event.ActionListener() { public void
actionPerformed(java.awt.event.ActionEvent evt) {
loginbtnActionPerformed(evt);}});
jLabel4.setIcon(new
javax.swing.ImageIcon("F:\\AYISHU\\pictures\\student.jpeg")); // NOI18N
jLabel3.setFont(new java.awt.Font("Tahoma", 1, 14)); // NOI18N
jLabel3.setForeground(new java.awt.Color(255, 0, 51));
jLabel3.setText("Student login");
staffloginbtn.addActionListener(new java.awt.event.ActionListener() {
});
javax.swing.GroupLayout jPanel3Layout = new
javax.swing.GroupLayout(jPanel3);
jPanel3.setLayout(jPanel3Layout);
jPanel3Layout.setHorizontalGroup(
jPanel3Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEA
DING)
try {
for (javax.swing.UIManager.LookAndFeelInfo info :
javax.swing.UIManager.getInstalledLookAndFeels()) {
if ("Nimbus".equals(info.getName())) {
javax.swing.UIManager.setLookAndFeel(info.getClassName());
break; } }
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new home().setVisible(true);
}}); }
private javax.swing.JLabel jLabel1;
private javax.swing.JLabel jLabel2;
private javax.swing.JLabel jLabel3;