Table of Contents

1. Introduction
1.1. Objective
1.2. Target Audience
1.3. System Scope
1.4. Sources

2. General Overview
2.1. System Context
2.2. System Capabilities
2.3. User Roles
2.4. Technical Environment
2.5. Development Limits
2.6. Support Materials
2.7. Assumptions and Dependencies

3. Interface Specifications
3.1. User Interactions
3.2. Hardware Specifications
3.3. Software Specifications
3.4. Communication Protocols

4. Core Functions
4.1. Access Control
4.1.1. Purpose and Priority
4.1.2. Process Flow
4.1.3. Functional Needs
 4.2. Event Creation
4.2.1. Purpose and Priority
4.2.2. Process Flow
4.2.3. Functional Needs
4.3. Attendee Registration
4.3.1. Purpose and Priority
4.3.2. Process Flow
4.3.3. Functional Needs
4.4. Event Scheduling
4.4.1. Purpose and Priority
4.4.2. Process Flow
4.4.3. Functional Needs

5. Performance Criteria
5.1. Efficiency Standards
5.2. Safety Measures
5.3. Security Measures
5.4. Quality Standards
5.5. Operational Policies

6. Supplemental Requirements
Appendix:
Use Case Visualization
Use Case Details
 1. INTRODUCTION

1.1. Objective
This document outlines the Online Event Management System (OEMS), a digital solution
to streamline event planning and participation for the client. It manages event creation, attendee
registration, scheduling, and notifications, developed through comprehensive research to meet
modern event management needs.

1.2. Target Audience

The primary target audience for the Online Education Management System (OEMS) is
the system administrators, who are responsible for managing the platform, including adding new
content, controlling user access, and maintaining the system's security and functionality. The
secondary target audience is the registered users who can access the OEMS with valid
credentials and utilize the available resources based on their authorized permissions.

1.3. System Scope

The Online Event Management System (OEMS) transforms manual event management
into a user-friendly, web-based platform, enabling organizers and attendees to create, register for,
and manage events using mobile devices from anywhere with internet access. This enhances
efficiency, reduces errors, improves accessibility, and supports events of all sizes by centralizing
operations and fostering collaboration.

1.4. Sources
- IEEE Std. 830-1998: Software Requirements Practices
- Pressman, Roger S. *Software Engineering: A Practitioner’s Approach*, 7th Edition
- Online resources on event management software
 2. GENERAL OVERVIEW

2.1. System Context

This SRS defines the OEMS, a digital upgrade from manual event systems. It enables
event creation, scheduling, and registration by title, date, location, and category, improving user
experience for organizers and attendees.

System Flow:
- Organizers create and manage events via a web interface.
- Attendees register and receive updates online.
- The system tracks schedules, availability, and notifications seamlessly.
2.2. System Capabilities

The OEMS empowers its users with a range of tailored functionalities designed to
enhance event management and participation.

Organizers:

-Allocate to participants.

-Evaluate by type/location.

-Check info for planning.

-Manage attendee updates.

Attendees:
-Browse options in the portal.
-Check events by date/location.
-Create personal profiles in the system.
-Access past registered events.

2.3. User Roles

There are two different users who will be using this product.

 Organizers: Manage system operations, requiring advanced technical skills.

 Attendees: Access services online, needing basic digital literacy.

Features available to the organizers are:

 Assign events to participants and oversee the distribution process.

 Assess the range of events categorized by type or location within the system.

 Review event details across various categories for effective planning.

 Process event returns and updates from attendees.

 Incorporate new events and related information into the platform.

 Revise details of existing events as needed.

 Generate reports on events that have been assigned to attendees.

 Review comprehensive reports on assigned events.

 Manage full access to attendee profiles and activities.

Features available to the attendees are:

 Explore the variety of event types available through the online portal.

 Confirm availability of events based on specific dates or locations.

 Establish their own profiles within the system.

 Review their previously registered events.

 Access a history of their past event participations.

 Look up specific events using search tools.

 Submit proposals for new event ideas.

2.4. Technical Environment
The system will be operated on the Windows platform. It requires a high-speed internet
connection and the ability to run in popular web browsers like Microsoft Internet Explorer,
Google Chrome, and Mozilla Firefox.

Hardware Requirements
- Server PC should have:
- RAM greater than 4GB
- HDDs larger than 500GB
- Basic input/output devices (monitor, mouse, keyboard, printer)
- Barcode scanner (optional)

Software Requirements
The server PC should use Windows 7 or higher, or Linux as the operating system.

2.5 Design and Implementation Constraints

 The product was developed using ASP (Active Server Pages).
 It can also run on Android devices.
 The backend database is SQL Server.
 It uses a login feature to make certain functionalities available to specific users.

2.6User Documentation

 A user manual has been provided.

 Quick-start guides are included for both administrators and participants.
 Online help resources are accessible within the system interface.
2.7 Assumptions and Dependencies

Assumptions

- The coding should be error-free.

- The system should be user-friendly and easy to use.

- User, book, and library information must be stored in a way that can be easily accessed online.
- The system should have sufficient storage capacity and provide fast access to the database.
- The system should provide search functionality and support quick transactions.
- The library system should be accessible 24/7.
- Users can access the site from any computer with internet and browsing capabilities.
- Users must have correct usernames and passwords to access their accounts and take actions.
- The hardware and network connection should never fail.

Dependencies
- The specific hardware and software requirements will be tested, and the project will be
developed and tested based on the requirements and specifications.
- The end users (admins) should have a proper understanding of the product.
- User information must be stored in a database that can be easily accessed by the library system.
- Any updates to books in the library must be recorded in the database, and the data entered
should be correct.
 3. INTERFACE SPECIFICATIONS

3.1. User Interactions

The system provides a complex platform for users to enter account information and log
in. If a user enters incorrect account information, an error message will pop up. New users can
simply sign up to become members. If a user forgets their password, they can retrieve it after
answering a security question. The system produces a graphical user interface for both users and
administrators.
Key features:
 Ability to view quick reports on events, registrations, and attendance.
 Stock verification and search facility for various criteria.
 Customizable user interface for administrators.
 Straightforward and standardized design across interfaces.
 Separate user interfaces for login/logout, user management, and other modules.

Login Interface:
Unregistered users can enter their information to create an account. Registered users can
log in by entering their username and password. If the user enters incorrect login credentials, an
error message will appear.

Search Interface:
Users (organizers, attendees) can search for events by entering criteria like event name,
category, date, etc. The system should provide a comprehensive search functionality to help
users find relevant events.

View Interface:
The system should display the categories of available events and allow organizers to add,
edit, or delete event categories. Organizers should be able to view event details, registrations, and
attendance reports.

Control Panel:
 The control panel should allow administrators to manage users, events, resources, and
lending options. Administrators should be able to add, edit, or remove users, events, and
resources through the control panel.

3.2 Hardware Interfaces

Server-side:
- Operating system: Windows 7 or higher, or Linux

- RAM greater than 4GB

- HDDs larger than 500GB

Client-side:
- Operating system: Windows 7 or higher, Linux, macOS, Android 5.1 or higher

- RAM greater than 4GB

- HDDs larger than 500GB

3.3 Software Interfaces

- The system should support any Windows or Android operating system.
- JDK (Java Development Kit) or JRE (Java Runtime Environment) must be installed on
the system to run the application.
- In addition, NetBeans or Eclipse IDE should also be installed for easier execution of the
application.

3.4 Communications Interfaces

The communications standard that will be used is GUI (Graphical User Interface). This
interface must be highly intuitive and interactive, as there will be no direct assistance for the user
operating the system. The interface is designed to be user-friendly, so that even users with
minimal computer knowledge can operate the system. The password should be kept private,
which can be achieved by using asterisks in the password panel.

4. CORE FUNCTIONS

4.1. Access Control

4.1.1. Purpose and Priority

Users secure access with usernames and passwords.

Priority: Critical

4.1.2. Process Flow

1. User opens the OEMS.

2. System displays a login screen.

3. User enters credentials and submits.

4. System verifies access, granting entry or showing errors.

4.1.3. Functional Needs

- Restrict access to valid credentials.
- Assign roles for access levels.
- Require logout after sessions.

4.2. Event Creation

4.2.1. Purpose and Priority

Organizers create new events with details.

Priority: Critical

4.2.2. Process Flow

1. Organizer logs in.

2. System offers a “Create Event” option.
3. Organizer fills a form with event data.
4. System confirms success or notes errors.

4.2.3. Functional Needs

- Limit updates to organizers only.

- Validate and store event data securely.
- Prevent duplicate events.

4.3. Attendee Registration

4.3.1. Purpose and Priority

Attendees create accounts for event access.

Priority: Critical

4.3.2. Process Flow

1. Attendee visits registration.

2. System shows a “Register” form.
3. Attendee enters details and submits.
4. System generates an ID and confirms registration.

4.3.3. Functional Needs

 - Issue unique credentials to new attendees.
- Store data securely in a database.
- Verify all required fields.

4.4. Event Scheduling

4.4.1. Purpose and Priority

Attendees register for events, managed by organizers, updating records.

Priority: Critical

4.4.2. Process Flow

1. Attendee logs in and selects an event.
2. System lists available events.
3. Attendee picks an event and submits a registration.
4. System updates records, confirming or denying registration.

4.4.3. Functional Needs

- Update attendee and event records.
- Check availability before registration.
 5. PERFORMANCE CRITERIA

5.1. Efficiency Standards

- Available 24/7 for users.
- Responses within 2 seconds.
- Server handles tasks efficiently, minimizing errors.
- Supports large event datasets without lag.

5.2. Safety Measures

- Protect data with regular backups.
- Secure personal and sensitive information.
- Limit changes to user-specific data.
- Use strong login security.
- Restrict database edits to organizers.

5.3. Security Measures

- Secure database with role-based access: organizers edit, others view.
- Prevent unauthorized access with robust authentication.

5.4. Quality Standards

- Ensure the system is intuitive, reliable, and maintainable.

- Send alerts for event updates and availability.
- Optimize for fast searches and logins.
- Secure payment data and ensure accurate updates.
- Enable event platform sharing and thorough testing.

6. SUPPLEMENTAL REQUIREMENTS

Data Management:
- Supports roles (organizers, attendees, admins) with tailored access.
- Organizes events by type, displaying details clearly.

Ethical Standards:
- Protect user privacy, especially sensitive data, operating ethically.