Software Development Plan (SDP)
SEMESTER MARCH-AUGUST 2025
GROUP: CDCS110/4D
MOHAMMAD SYAHID FAWWAZ BIN BAHARUDIN , 2023659456
AHMAD ZIKRI ZAIM BIN MUHAMMAD , 2023616852
SYAH IDHAM BIN RUSLAN, 2023823064
NIK MUHAMMAD NASEEM BIN NIK NEZAR , 2023660752
Revision History
Date Version Description Author
<dd/mm/yyyy> <x.x> <reason to change the documentation <name>
contents>
Confidential Page 2 of 18
Table of Contents
1. Introduction 4
1.1 History of Organization 4
1.2 Organizational Chart 4
1.3 Current System Description 4
1.4 Current System Problem 4
2. Proposed Project Overview 5
2.1 Proposed System Process 5
2.2 Proposed System Objectives 5
2.3 Proposed System Scopes 5
2.4 Proposed System Entity and Attributes 5
3. Project Organization 6
3.1 Organizational Structure 6
3.2 Roles and Responsibilities 6
4. Management Process 7
4.1 Project Plan 7
Appendix 8
Confidential Page 3 of 18
Software Development Plan
1. Introduction
1.1 History of Organization
Founded in 2025, EventoR was created by a team of experienced event planners and software developers
who recognized the challenges organizers faced in planning events. They saw that traditional methods
were often inefficient, leading to the development of a web-based application designed to simplify event
management. By focusing on improving user experience and streamlining workflows, EventoR aims to
transform the way events are planned and executed.
EventoR's strengths include a user-friendly interface that enhances the planning process, innovative
features like customizable templates that cater to diverse needs, and advanced analytics that provide
valuable insights. However, the platform also encounters some weaknesses: a reliance on technology that
can lead to disruptions during events, competition in a crowded market that makes differentiation
challenging, and potential difficulties in persuading traditional planners to switch to a new system.
Looking to the future, EventoR has numerous opportunities to explore. The growing global event industry
offers a larger market for their services, while the increasing trend toward hybrid events allows for the
development of innovative features to enhance user engagement. However, the company must also
navigate several threats, including rapid technological changes that require constant updates and
adaptations, as well as economic downturns that may lead to reduced budgets for events and lower
demand for event management software.
Mission
To simplify and enhance the event planning process and provide user-friendly interfaces that make it easy
for users that want to create events and for participants to join them, empowering everyone to create
memorable experiences effortlessly.
Vision
To make EventoR the most widely used event management platform globally, revolutionizing how events
are planned and executed by fostering creativity, flexibility, and engagement for organizers and
participants alike.
Confidential Page 4 of 18
1.2 Organizational Chart
The organizational chart of EventoR is designed to support the company's mission of creating a platform
where users can join and create events. At the helm is Syah Idham Bin Ruslan, the CEO, who provides
strategic direction and oversees overall vision. Beneath him, Ahmad Zikri Zaim Bin Muhammad, the
COO, manages daily operations to ensure smooth functionality of the platform. Mohd Syahid Fawwaz
Bin Baharudin, the CTO, leads the technology team to develop and maintain the website and its features.
Nik Muhammad Naseem Bin Nik Nezar, the CMO, drives marketing strategies to promote EventoR,
making it appealing to users looking to join or host events. Customer support, handled by Albert Bin
Johnsan, ensures users have assistance with inquiries and issues. Nur Faizah Iman provides essential IT
support to maintain system reliability, while Nik Muhammad Abu Bin Nasir, the accountant, manages
financial records and budgeting. This structure is tailored to facilitate collaboration and efficiency,
ultimately enhancing user experience on the EventoR platform.
Confidential Page 5 of 18
1.3 Current System Description
The current event management process used by organizers is heavily reliant on manual work and basic
digital tools. Although these methods can be effective for small-scale events, they often lead to
inefficiencies, lack of coordination, and difficulty in tracking progress when managing more complex or
larger events. The main processes involved are:
1. Event Registration:
Users register for events through Google Forms. Organizers manually compile and manage the
responses using spreadsheets such as Google Sheets. This process becomes inefficient and
error-prone when handling many participants.
2. Guest List and Invitations:
Invitations are manually sent out through platforms like WhatsApp or email. The responses are
tracked in separate documents, which can result in disorganized guest lists and make follow-ups
more difficult
3.
4. Task Management:
Event planning is managed using physical notebooks or basic tools like Microsoft Excel. There is
no centralized platform for assigning tasks or tracking progress, leading to delays and unclear
responsibilities among team members.
Figure 1:Current System Flowchart
Confidential Page 6 of 18
Current System Problem
● Traditional methods are time-consuming and often rely on manual processes.
● Lack of centralized tools leads to scattered information and poor communication.
● Organizers face difficulties in customizing event details to suit different audiences.
Figure 2: Fishbone
Confidential Page 7 of 18
EventoR Version: 1.0
Software Development Plan (SDP) Date: 11/04/2025
Syahid,Zikri,Syah,Naseem
2. Proposed Project Overview
2.1 Proposed System Process
Figure 3: Proposed System Flowchart
Confidential Page 8 of 18
2.2 Proposed System Objectives
1. Simplify Event Planning Workflows
EventoR streamlines complex event planning tasks by offering an all-in-one platform where
users can manage schedules, venues, registrations, and communications with ease.
2. Reduce Administrative Overhead
By automating time-consuming tasks such as guest list management and task assignments, the
system allows organizers to focus more on strategic planning and creativity.
3. Enable Real-Time Insights and Monitoring
The platform provides real-time data dashboards and analytics that help users make informed
decisions before, during, and after events—enhancing responsiveness and performance tracking.
2.3 Proposed System Scopes
Stakeholders (Users of the System)
● Event Organizers
These are the primary users who will use EventoR to create, customize, and manage events efficiently
from start to finish.
● Event Attendees
Participants who will interact with the platform to register, check schedules, and provide feedback.
● Supervisory Team
Responsible for monitoring the progress of the system development and ensuring it aligns with project
goals and academic requirements.
● Executive Team
Plays a strategic role in making decisions, allocating resources, and guiding the overall direction of the
project.
● Technical Support Team
Handles maintenance, bug fixing, and the continuous improvement of the system’s features.
● Marketing Team
Uses EventoR to promote events, track user engagement, and evaluate the success of event campaigns.
Confidential Page 9 of 18
Limitations of the System
● Internet Needed
EventoR needs a good internet connection to work. If the internet is slow or not available, users may face
problems using the system.
● Not Fully Connected to Other Tools
EventoR cannot fully connect with some outside tools like payment systems or customer databases unless
more work is done.
● Limited for Special Events
Some events that are very unique or different may need extra features that are not in EventoR .
2.4 Proposed System Entity and Attributes
Provide Entity Relationship Diagram (ERD) in appendix.
Confidential Page 10 of 18
3. Project Organization
3.1 Organizational Structure
Describe the organizational structure of the project team (Project Manager, Database Designer,
Programmer 1, Programmer 2, System Analyst, and supervisor among lecturers.
Figure 4: Organizational Structure
Confidential Page 11 of 18
3.2 Roles and Responsibilities
Provide your group member’s formal picture and their responsibilities with job designation
ROLES RESPONSIBILITIES
● In charge of establishing the project's
objectives, timetable, resources, and
scope in order to guarantee its
success.
● Provide specific instructions to every
team member and work closely with
them to make sure the project's
advancement.
● Participating in code testing and
troubleshooting to recitfy error
efficiently,thereby facilitating seamless
system operation
● Cooperating with developers to
incorporate front-end design element,
ensuring the system function optimally
and delivers a satisfying user
experience across all the aspects.
Confidential Page 12 of 18
● The system analyst is responsible for
gathering and analyzing stakeholder
requirements, designing the overall
system architecture, and developing
technical specifications that accurately
translate business needs into a
functional solution for EventoR.
● The analyst collaborates closely with
the development team, actively
participates in testing and
troubleshooting to resolve issues, and
maintains comprehensive
documentation to ensure continuous
system improvement and reliable
operation.
● Ensuring the accurate of data and
overseeing tasks such as
inserting,deleting,and updating data to
maintain its integrity and consistency.
● Crafting the database framework to
align with project needs,which
involves outlining the data
structure,establishing data relationships
and enhancing data efficiency
Figure 5: Roles and Responsibilities
Confidential Page 13 of 18
4. Management Process
4.1 Project Plan
The Gantt chart outlines a project timeline divided into five key phases: Planning, System Analysis,
System Design, Implementation, and Security & Support. In the Planning phase (Weeks 14-15),
foundational tasks such as defining the project's objectives and current issues are established. The System
Analysis phase (Weeks 15-16) focuses on detailed assessments, like defining system requirements and
organizational roles. During System Design (Week 16), the project plan and system specifications are
created to guide development. The Implementation phase begins in Week 16, where the system is built
and deployed according to the design framework. Lastly, the Security & Support phase ensures ongoing
maintenance and security measures are implemented, extending beyond Week 16 to ensure the system
remains functional and secure.
Confidential Page 14 of 18
Appendix
Confidential Page 15 of 18
Confidential Page 16 of 18
Confidential Page 17 of 18
Confidential Page 18 of 18