Evenman
A project submitted to the
Department of Computer Science
In
Partial Fulfilment of the Requirements for the
Bachelor’s Degree in Computer Science
By
Umer Farooq
Wadood Nasir
Internal Supervisor
Amna Nadeem
Lecturer
Department of Computer Science
External Examiner
______________________
_______________________
Chairperson
Dr. Muhammad Asif
Assistant Professor
Department of Computer Science
________________________
i
COPYRIGHTS
This is to certify that the project titled “Evenman” is the genuine work carried out by Umer
Farooq, Wadood Nasir, student of BSCS of Computer Science Department, Lahore Garrison
University, Lahore during the academic year 2019-23, in partial fulfilment of the requirements for
the award of the degree of Bachelor of Computer Science and that the project has not formed the
basis for the award previously of any other degree, diploma, fellowship or any other similar title.
Umer Farooq _____________
Wadood Nasir______________
ii
DECLARATION
We hereby declare that this project titled “Evenman” is not copied out from any other source.
This authentic work done by signatory, in practical achievement for the degree “Bachelor of
Science in Computer Science” at Computer Science Department, Lahore Garrison University,
Lahore. Besides, it is declared that we have designed this APP or project report completely on the
basis of our own intention under the kind leadership of our internal supervisor Ms. Amna Nadeem.
All the analysis, design & system development have been accomplished by the signatory.
Moreover, this project has not been submitted to any other college or university.
Group Members
Umer Farooq ____________
Wadood Nasir ____________
Supervisor
Amna Nadeem____________
iii
Date: ________________
ACKNOWLEDGEMENTS
First and for most uncounted thanks to ALMIGHTY ALLAH who created us worthy of all praise
who mentor us in crises. Secondly all salutations are presented to our beloved PROPHET
MUHAMMAD (PBUH) who empower us to recognize our creator and whose life is the best
example for us. During this project, we received support, assistance or practical help from many
people and it is bliss to acknowledge their intentions.
Our heartiest prayers go to our parents, siblings and to all family members for their assistance and
moral support. Our success is possible only due to prayers or support of our mothers who really
loves us and always pray for us in every moment of our life.
We are very thankful to all our family members, senior’s fellows and we also feel vastly in debt to
our supervisor Ms. Amna Nadeem for providing us precise research-oriented opinions, advices,
backing and assistance during the project and throughout the academic session.
iv
DEDICATION
I dedicated this work to First of all, ALLAH Almighty who glorified us with the knowledge and
bravery to complete this responsibility with elegance. Secondly, my affectionate supportive family
whose prayers, advises and continuous support played a major role in achieving this goal. Finally,
to the Lahore Garrison University and Especially, the department of Computer Science.
v
Table of Contents
COPYRIGHTS...................................................................................................................................................... II
DECLARATION ..................................................................................................................................................III
DEDICATION ...................................................................................................................................................... V
LIST OF ABBREVIATION .................................................................................................................................. XII
CHAPTER 1 ...................................................................................................................................................... 1
INTRODUCTION ............................................................................................................................................ 1
1.1 BACKGROUND......................................................................................................................................................1
1.2 OVER VIEW..........................................................................................................................................................1
1.3 OBJECTIVE ...........................................................................................................................................................1
1.4 GANTT CHART .....................................................................................................................................................2
1.5
REPORT ORGANIZATION ...............................................................................................................................2
CHAPTER 2 ...................................................................................................................................................... 4
CHAPTER 3 PROBLEM DEFINITION ....................................................................................................... 5
CHAPTER 4 SOFTWARE REQUIRED SPECIFICATION ...................................................................... 6
4.1 PURPOSE ..............................................................................................................................................................6
4.1.1REVISION HISTORY ......................................................................................................................................6
4.2 DOCUMENT CONVENTIONS ..................................................................................................................................6
4.3 INTENDED AUDIENCE AND READING SUGGESTIONS ............................................................................................7
4.4 PRODUCT SCOPE ..................................................................................................................................................8
4.5 OVERALL DESCRIPTION .......................................................................................................................................8
4.5.1 Product Perspective ....................................................................................................................................8
4.5.2 Product Functions .......................................................................................................................................8
4.5.3 User Classes and Characteristics ...............................................................................................................9
4.5.3.1 User ..........................................................................................................................................................9
4.5.3.2 Registered Companies ..............................................................................................................................9
4.5.4 Operating Environment ............................................................................................................................. 10
4.5.4.1 Hardware ............................................................................................................................................... 10
4.5.4.2 Software ................................................................................................................................................. 10
vi
4.5.5 Design and Implementation Constraints ................................................................................................... 10
4.5.6 User Documentation ................................................................................................................................. 10
4.5.7 Assumptions and Dependencies ................................................................................................................ 11
4.6 EXTERNAL INTERFACE REQUIREMENTS ............................................................................................................. 11
4.6.1 User Interfaces .......................................................................................................................................... 11
4.6.2 Hardware Interfaces ................................................................................................................................. 15
4.6.3 Software Interfaces.................................................................................................................................... 15
4.6.4 Communications Interfaces ....................................................................................................................... 15
4.7 SYSTEM FEATURES ............................................................................................................................................ 16
4.7.1 System Feature 1 ..................................................................................................................................... 16
4.7.1.3 Functional Requirements ....................................................................................................................... 18
4.7.2 System Feature 2 ..................................................................................................................................... 19
4.8 OTHER NONFUNCTIONAL REQUIREMENTS ......................................................................................................... 19
4.8.1 Performance Requirements ....................................................................................................................... 19
4.8.2 Safety Requirements .................................................................................................................................. 20
4.8.3 Security Requirements ............................................................................................................................... 20
4.8.3.1 User Authentication ............................................................................................................................... 20
4.8.3.2 Data Encryption ..................................................................................................................................... 21
4.8.3.3 Access Control ....................................................................................................................................... 21
4.8.3.4 Vulnerability Management ..................................................................................................................... 21
4.8.4 Software Quality Attributes ....................................................................................................................... 21
4.8.5 Business Rules ........................................................................................................................................... 21
CHAPTER 5 METHODOLOGY .................................................................................................................. 23
5.1 INTRODUCTION .................................................................................................................................................. 23
5.2 PLANNING .......................................................................................................................................................... 24
5.2.1 Data Collection ......................................................................................................................................... 24
5.2.2 Hardware and software requirements ....................................................................................................... 24
5.2.2.1 Hardware requirements ......................................................................................................................... 24
5.2.2.2 Software requirements ........................................................................................................................... 24
5.3 IMPLEMENTING .................................................................................................................................................. 24
5.4 ANALYSIS .......................................................................................................................................................... 24
CHAPTER 6 DETAILED DESIGN AND ARCHITECTURE .................................................................. 26
6.1 SYSTEM ARCHITECTURE .................................................................................................................................... 26
6.1.1 Architecture Design Approach .................................................................................................................. 26
6.1.1.1 Initial Approach ..................................................................................................................................... 26
6.1.1.2 Test ......................................................................................................................................................... 27
6.1.1.3 Next Initial.............................................................................................................................................. 27
vii
6.1.2 Architecture Design .................................................................................................................................. 27
6.1.3 Subsystem Architecture ............................................................................................................................. 28
6.1.3.1 Functional Description .......................................................................................................................... 28
6.2 DETAILED SYSTEM DESING ....................................................................................................................... 28
6.2.1 Classification ............................................................................................................................................ 28
6.2.2 Definition .................................................................................................................................................. 28
6.2.3 Responsibilities ......................................................................................................................................... 28
6.2.4 Constrains ................................................................................................................................................. 29
6.2.5 Composition .............................................................................................................................................. 29
6.2.6 Uses/interaction ........................................................................................................................................ 29
6.2.7 Resources .................................................................................................................................................. 29
6.2.8 Processing ................................................................................................................................................. 29
6.2.9 Interface/Export ........................................................................................................................................ 29
6.2.10 Detailed Subsystem Design ..................................................................................................................... 29
Diagrams............................................................................................................................................................ 30
6.2.10.1 Use case Diagram ................................................................................................................................ 31
6.2.10.2 Activity Diagram .................................................................................................................................. 32
6.2.10.3 Sequence Diagram ............................................................................................................................... 33
6.2.10.4 Component Diagram ............................................................................................................................ 34
6.2.10.5 State machine ....................................................................................................................................... 35
6.2.10.6 Architectural Diagram ......................................................................................................................... 36
6.2.10.7 Class Diagram ..................................................................................................................................... 37
6.2.10.7 Interaction Diagram............................................................................................................................. 38
CHAPTER 7 IMPLEMENTATION AND TESTING ................................................................................... 40
7.1 TOOLS ................................................................................................................................................................ 41
7.2 TESTING METHODS............................................................................................................................................. 41
CHAPTER 8 RESULTS AND DISCUSSION ............................................................................................ 44
8.1 RESULTS OF TEST EVALUATION......................................................................................................................... 44
CHAPTER 9 CONCLUSION AND FUTURE WORK .............................................................................. 46
viii
LIST OF TABLES
Table 1.1 Gantt chart....................................................................................................................... 2
Table 2 Revision History ................................................................................................................ 6
Table 3:Document convention ........................................................................................................ 7
Table 4: Software Interface ........................................................................................................... 15
ix
LIST OF FIGURES
Figure 1:Loading Screen ............................................................................................................... 12
Figure 2:Login Page ...................................................................................................................... 12
Figure 3: Home Page .................................................................................................................... 13
Figure 4: Drawer Menu ................................................................................................................. 13
Figure 5: Send Offer ..................................................................................................................... 14
Figure 6: Profile ............................................................................................................................ 14
Figure 7: SDLC ............................................................................................................................. 23
Figure 8: SDLC steps .................................................................................................................... 23
Figure 9:Architecture Design ........................................................................................................ 27
Figure 10: Use Case Diagram ....................................................................................................... 31
Figure 11: Activity Diagram ......................................................................................................... 32
Figure 12: Sequence Diagram ....................................................................................................... 33
Figure 13: Component Diagram ................................................................................................... 34
Figure 14: State machine .............................................................................................................. 35
Figure 15: Architectural Diagram ................................................................................................. 36
x
Figure 16: Class Diagram ............................................................................................................. 37
Figure 17: ER Diagram ................................................................................................................. 38
Figure 18: Interaction Diagram ..................................................................................................... 39
Figure 19: Data Flow Diagram ..................................................................................................... 40
Figure 20: Accepted Offers ........................................................................................................... 44
Figure 21: Offer received .............................................................................................................. 44
Figure 22: Messages Notification ................................................................................................. 45
Figure 23: Chat System ................................................................................................................. 45
xi
LIST OF ABBREVIATION
Short Form
Complete Form
App
Application
Description
User
A person used the application
Android
A mobile device operating
system developed by Google
Inc.

Helps the reader identify key
information.
Developers
A person who build something
DB
Database
DFD
Data flow diagram
SDK
Software Development Kit
EVENMAN
Name of the application.
TBD
To Be Decided
SDLC
System development life
cycle
xii
Abstract
Evenman is a mobile app designed to simplify event planning and management. It provides a userfriendly platform for people looking to organize events to connect with suitable event organizers.
Users can create an account, specify their event preferences and budget, and search for event
organizers based on location, event type, and budget. Event organizers can register on the app,
showcase their services, and submit proposals and quotes for user-defined events.
Evenman incorporates a bidding system, allowing event organizers to compete and submit their
best offers. Users can review and compare the proposals, communicate with organizers, and
choose the most suitable one. The app also includes a review and rating system to share
experiences and help others make informed decisions.
Evenman aims to revolutionize the event management industry by offering a convenient and
efficient platform for users to find event organizers that match their preferences and budget. Its
user-friendly interface, comprehensive features, and focus on quality and convenience make event
planning easier and more enjoyable for both users and event organizers.
xiii
xiv
xv
Chapter 1
INTRODUCTION
1.1 Background
The purpose of this document is to specify the requirements for the mobile application "Evenman",
which allows users to find the best option of event organizers within their budget. This SRS covers
the entire scope of the product, including user interface, database management, and biding system.
This project will be helpful for business man and customer to deal with each other and there is no
need to form company to company for information.
1.2 Over View
The Evenman app is a user-friendly event planning solution that simplifies the process of
organizing events. It connects event organizers with individuals and organizations looking for their
services. Users can search for organizers based on location, event type, and budget, making event
planning hassle-free. Organizers can showcase their services, submit proposals through a
competitive bidding system. The app aims to revolutionize the event management industry by
providing a convenient and reliable platform for both organizers and clients.
1.3 Objective
This App is developed with clear objectives that provide ease to user.

Provide a user-friendly platform for event planning.

Simplify the process of finding event organizers based on location, event type, and budget.

Foster competition among organizers through a bidding system to ensure clients receive
competitive proposals.

Revolutionize the event management industry by offering a comprehensive and reliable
solution for both organizers and clients.
1
1.4 Gantt Chart
Gant Chart of our APP is given below in table 1.1
Table 1.1 Gantt chart
Activities
Week/Semester
Front End
Week 7 ,9(7th)
Data-Base
Week 10 ,11,12(7th)
Bidding System
Week 13,14(7th)
APP Security
Week 15(7th) Week 1(8th)
Profile Changer
Week 2 ,3,4(8th)
Chat System
Week 5,6,7(8th)
Company Portfolio
Week 9,10,11(8th)
Testing
Week 12,13(8th)
Documentation
Week 7 (7th) – Week 13(8th)
1.5 Report Organization
This report present Chapter wise organization of project as individual chapter explain tasks which
were crucial for the deed of project. List of chapter wise report is given as follow.
Chapter 1: In first chapter background and Overview of App were discussed and also. This chapter
also included Gantt chart which display evaluation time for this project.
Chapter 2: This chapter Define project problem definition.
Chapter 3: This chapter included Software Requirements Specification, functional and nonfunctional requirements.
Chapter 4: This chapter includes method tools technology used for deed of project.
2
Chapter 5: In this chapter, system’s structure and behavior is discussed through diagrams. Also,
ER are discussed in detail.
Chapter 6: This chapter includes that how to perform tests and also the test plans and maintenance
details of the project.
Chapter 7: This define evaluation of results.
Chapter 8: This chapter concludes the whole working and post work of the project.
3
Chapter 2
LITERATURE REVIEW
The literature surrounding the innovative "EVENMAN" app underscores its significance as a
transformative solution within the realm of event service accessibility. Addressing the challenges
of accessing and availing event services, the app emerges as a critical bridge connecting customers
with a wide range of services offered by registered companies. Notably, the incorporation of a
bidding system within the app has drawn attention for its potential to foster healthy competition
among service providers, ultimately benefiting customers by offering competitive prices and a
plethora of choices.
There are many event management applications in the market but our project have different
functionality than the others. Other applications on playstore are providing calendar to the user to
save the timing, Date, etc but our application has totally different functionality it provides a
platform to the business man to scope their business and get better opportunities to grow and also
help people to get everything related to event on single platform. There will be no need to visit
website by website or travel from one manager to the other physically in the search of better option
they are getting all of this on a single platform.
EVENMAN takes a business-centric approach, recognizing the needs of both customers and
registered companies. While some apps primarily cater to individual users, EVENMAN empowers
businesses by providing them with a platform to expand their reach, scope their services, and
discover growth opportunities. This unique focus on businesses makes it an invaluable tool for
event service providers. A standout feature of EVENMAN is its incorporation of a bidding system.
Unlike other apps that primarily facilitate bookings or appointments, EVENMAN fosters healthy
competition among service providers. By allowing companies to submit competitive bids for
customer requirements, the app ensures that customers not only receive competitive pricing but
also have access to a wide variety of service options to choose from.
4
Chapter 3
PROBLEM DEFINITION
The event service industry is marked by a dynamic landscape, with customers and service
providers seeking effective and efficient ways to connect and collaborate. However, existing event
management applications often fall short in addressing the diverse needs of users. Many of these
apps primarily focus on calendar and scheduling features, leaving a significant gap in providing
comprehensive event-related services.
Furthermore, there is a lack of platforms that prioritize the interests of both customers and event
service businesses. Customers require a centralized solution that simplifies the process of planning
and managing events while allowing them to access a wide range of service options. On the other
hand, businesses in the event service sector seek opportunities to expand their reach, scope their
services, and discover growth possibilities.
The incorporation of a bidding system within event management apps to foster healthy competition
among service providers is a novel concept that has not been widely explored. Such a system has
the potential to benefit customers by offering competitive prices and a plethora of service choices
while simultaneously empowering event service businesses to showcase their capabilities and
secure valuable contracts.
In light of these challenges and opportunities, the problem at hand is to develop a transformative
event management application, named "EVENMAN." This application aims to bridge the gap
between customers and event service providers by offering a unique and comprehensive
ecosystem. EVENMAN will provide customers with a one-stop platform for all event-related
needs, from planning and coordination to connecting with service providers. Moreover, it will
empower businesses by offering them a platform to scope their services, compete through a
bidding system, and seize growth opportunities.
5
Chapter 4
SOFTWARE REQUIRED
SPECIFICATION
4.1 Purpose
The present report is designed to define the detailed function of this android App “EvenMan”.
We are providing a platform for both customer and seller. Before this app the customer have
to visit multiple websites or different organizations physically we are reducing time and
expenses by getting both (Seller, Buyer) on this single platform. This is very hard to build and
maintain (app, website) for small startup, so we are solving this problem for all the
organizations. It was hard to grow in the market for small companies because established
companies was taking all the orders and they don’t get any chance to grow.
4.1.1REVISION HISTORY
The following revision of the EvenMan App in table 3.1.1 [1].
Table 2 Revision History
Name
Date
Reason
Version
Umer Farooq
18-11-2022
Add feature of call generator.
0.9
Wadood Nasir
18-11-2022
Add feature of call generator.
0.9
4.2 Document Conventions
This report uses the following delegations as show in List of Abbreviations [2].
6
Table 3:Document convention
Short Form
Complete Form
App
Application
Description
User
A person used the application
Android
A
mobile
device
operating
system developed by Google
Inc.

Helps the reader identify key
information.
Developers
A person who build something
DB
Database
DFD
Data flow diagram
SDK
Software Development Kit
EVENMAN
Name of the application.
TBD
To Be Decided
SDLC
System development life
cycle
4.3 Intended Audience and Reading Suggestions
That report do advised for developers and user [3].

Developers shall refer to this documentation to obtain the observation of the APP in term
of framework used to build the App, performance and functional issues, processes and data
processing.
7

User shall refer to this documentation to observe what the APP is intended to provide in
term of features, functions through user interface.
4.4 Product Scope
Evenman is beneficial for those who want to build a business which can handle all the features of
event organizations through a single App. This project will help in finding orders and guide their
way. This project will be helpful for business man and customer to deal with each other. This
application helps to find a better deal for both users. This application is for those who are new to
the market and want their business to be a reputed one.

To facilitate event business in a better way.

Develop a new application for service.

Money and time saving
4.5 Overall Description
4.5.1 Product Perspective

The Evenman app is a platform for event management businesses to showcase their work
and provide services to customers. It is designed to be used on android and IOS devices.
This application developed using react native that aims to provide an affordable and
convenient way for users to find a event manager within their budget. This product is a
standalone application that does not rely on any external systems or interfaces.

The idea for Evenman originated from the need for a simple and cost-effective solution for
finding a event manager within a specific budget. Many consumers struggle to find
affordable options that meet their style preferences, and Evenman aims to address this issue
by providing a platform for users to browse and select a suitable person who can work
according to their demand within their budget range.
4.5.2 Product Functions

Register and login to the app
8

Manage their account information

Create a business profile and showcase their past work as an event planner (business
owners only)

Submit event requirements and budget (customers only)

Respond to event requests with services and prices (business owners only)

View and compare the work profiles of different event planners and make a selection
(customers only)

Provide a user profile section for users to view and edit their personal information.

Implement a review and rating system for users to leave feedback on event managers
profile
4.5.3 User Classes and Characteristics
This section contain two types of user [5] in EvenMan application.
4.5.3.1 User
The primary user class for the Evenman mobile application will be trend-conscious individuals
who are interested in finding a event organizers who can work according to their wish within a
specific budget. These users will likely be of various kind like some of them wants to organize a
birthday party, engagement ceremony or any kind of event on their location. They may use the app
on a regular basis, or only occasionally when they are looking to celebrate their special event.
4.5.3.2 Registered Companies
A secondary user class for the app will be event companies owners who want to register their
brands and have their products included in the app's search results. These users will likely have
more technical expertise and be more familiar with the app's functions, as they will be responsible
for managing their brand's listings within the app.
9
4.5.4 Operating Environment
"Evenman" will be developed for use on both iOS and Android devices. It will require a device
running at least iOS 11 or Android 5.0 and an active internet connection.
4.5.4.1 Hardware

The Evenman mobile application will be available on both iOS and Android devices.

Minimum hardware requirements for the application include:
o
iOS: iPhone 6 or later with iOS 10 or higher
o
Android: smartphone with Android 5.0 (Lollipop) or higher
4.5.4.2 Software

The Evenman mobile application will be built using React Native framework.

The application will require an active internet connection to function properly.
4.5.5 Design and Implementation Constraints
The app must be developed using react native and must adhere to the design guidelines of the
respective app stores (iOS App Store and Google Play Store). The app must also be optimized for
use on devices with different screen sizes and resolutions .The application will be available in
English language only. Users must have a valid email address to register as a brand owner. Users
must enter a valid budget in order to search for a event within their budget.
4.5.6 User Documentation
User documentation for "Evenman" will include an in-app help feature and a user manual in the
form of a PDF document. The user manual will be available for download from the app's page on
the app store. The app is developed using react native and is available for both Android and iOS
devices.
10
4.5.7 Assumptions and Dependencies
Evenman have the following Assumptions and dependencies.

It is assumed that the user has a smartphone with a compatible operating system (iOS or
Android) to run the mobile application.

It is assumed that the user has an active internet connection to use the application and
access the different event companies.

It is assumed that the user has a valid payment method to make purchases within the
application.

The project depends on the availability and proper functioning of the react native
framework to develop the mobile application.
4.6 External Interface Requirements
4.6.1 User Interfaces
When user use this mobile APP for the very first time should see splash activity page when he/she
open the application, see in Figure 4.3.1(a). Then APP proceed towards next procedure.
After splash screen he/she able to see password setting page to set a password for application, see
in Figure 4.3.1(b)
When APP is opened he/she now have to choose a type of thing he/she wants to conduct, see in
Figure3.3.1(c).
Now user can explore all the options, see in Figure3.3.1 (d). Then user add their budget and
requirements and make a bid, see in Figure 3.3.1(e).
He/she also see the user manual about How to use EVENMAN in the APP to know how to use
this application, see in Figure 3.3.1(f).
After all the functionality user can set his/her account information see in Figure 3.3.1(g).
11
Figure 1:Loading Screen
Figure 2:Login Page
12
Figure 3: Home Page
Figure 4: Drawer Menu
13
Figure 5: Send Offer
Figure 6: Profile
14
4.6.2 Hardware Interfaces

Processor: Dual-core or higher

Memory: 2 GB or higher

Storage: 1 GB or higher

Operating System: iOS 11 or higher, Android 6.0 or higher
4.6.3 Software Interfaces
Following are the software components used for Evenman android APP as show in table 3.3.3.
Table 4: Software Interface
Software Used
Description
Operating system
In development of Evenman APP android 5.0(Kit Kat) is used
because of highest no’s running android devices.
DB
To generate a record of transection performed by client and
vendor.
4.6.4 Communications Interfaces
The Evenman mobile application will not require any communication functions beyond the API
calls to the database. All data transfer will be handled securely using HTTPS protocols. There will
be no need for communication security or encryption beyond standard practices for API calls. Data
transfer rates will be optimized for efficient loading of event options and user data.
15
4.7 System Features
4.7.1 System Feature 1
 Budget Input

The user will be able to input their budget for organizing an event

The budget input will be in numerical form and must be within a certain range (e.g. 10K50K)

The budget input will be saved for future use in the app
 Event Search

The app will allow the user to search for Event manager within their budget

The search will be based on user-specified criteria such as birthday, engagement ceremony,
or any other home function.

The search results will include a variety of event options from different companies.

The user will be able to view detailed information about each event manager work,
including price and event description
 Brand Registration

Users will have the option to register their own event management company on the app

The brand registration process will include submitting information such as brand name,
contact information, and a portfolio of event manager

Registered brands will be able to add and update their work profile on the app for users to
browse and place order.
 User Profile

Users will have the option to create a personal profile within the app
16

The profile will include information such as name, email, and payment information
4.7.1.1 Description and Priority
The "Evenman" mobile application aims to provide a platform for users to easily find event
manager that fits their budget and event theme preferences. The application will utilize
react native technology and will be available on both iOS and Android devices.
Users will be able to input their budget and select their event theme preferences, and the
application will then search companies to find best event manager options that fit within
the user's budget and match their theme preferences. Users will also have the option to
register their own event management company and list their work on the platform.
This project has a high priority as it addresses a common problem faced by many
consumers - finding affordable, theme event options. By providing a convenient and userfriendly platform for searching and selecting the suitable event theme , the "Evenman"
application has the potential to make a significant impact on the event management
industry.
4.7.1.2 Response Sequences
Initial Launch of the App

Stimulus: The user opens the Evenman app on their mobile device

Response: The app will display the login screen, allowing the user to either sign in or create
a new account
 User Login

Stimulus: The user inputs their login information and clicks the "login" button

Response: The app will verify the login information and, if successful, will display the
main menu screen
17
 Setting Budget

Stimulus: The user selects the "Set Budget" option from the main menu

Response: The app will display a form for the user to input their desired budget amount
 Searching for Event

Stimulus: The user selects the "Search for Event" option from the main menu and inputs
their desired search criteria (such as marriage ceremony, birthday parties etc)

Response: The app will display a list of event manager options options within the user's
budget and search criteria
 Registering Brand

Stimulus: The user selects the "Register your company" option from the main menu and
inputs the necessary information (such as brand name, contact information, and work
experience, event till organized)

Response: The app will verify the information and, if successful, will add the brand to the
available options for other users to browse and purchase from.
4.7.1.3 Functional Requirements

The application should allow users to enter their budget and receive a list of event managers
options within that budget.

The application should provide a variety of event manager options, including their work
profile and a list of event with pictures along the budget they organized .

The application should provide images and detailed descriptions of each event company
(manager) option.

The application should allow users to save their favorite event organizers options for later
consideration.
18
REQ-1: The app must be able to retrieve event options from a database or API.
REQ-2: The app must display event organizers options to the user in a visually appealing
manner.
REQ-3: The app must allow the user to select and save event pictures from some companies
work profile options for future reference.
4.7.2 System Feature 2
 Registration
This feature allows users to register their own event company and make their services
available for recommendation to other users. The system will require brand owners to input
information about their work, including pricing and theme preferences.

Personalized Recommendations
This feature allows users to receive personalized recommendations based on their previous
purchases and theme preferences. The system will consider the user's budget and event
preferences to make the most relevant recommendations.
4.8 Other Nonfunctional Requirements
4.8.1 Performance Requirements

The Evenman mobile application must be able to search for event organizers within a
specified budget from various event companies.

The application must be able to display the available event organizers options to the user
with relevant information such as budget and event type.

The application must allow users to register their own event organization and upload their
products for other users to browse and booking.

The application must have a user-friendly interface with easy navigation for users.
19

The application must be able to handle large amounts of data efficiently and with minimal
loading times.

The application must be compatible with both Android and iOS devices.
4.8.2 Safety Requirements

The mobile application must ensure that user's personal information is securely stored and
protected from unauthorized access.

The mobile application must have a secure login system to prevent unauthorized access to
user's account.

The mobile application must have a password recovery feature in case the user forgets their
password.

The mobile application must have a system in place to detect and prevent any fraudulent
activity.

The mobile application must have a privacy policy in place to protect user's personal
information.

The mobile application must comply with all relevant data protection laws and regulations.

The mobile application must have a system in place to regularly update and patch any
security vulnerabilities.

The mobile application must have a system in place to regularly backup user data to prevent
data loss.
4.8.3 Security Requirements
4.8.3.1 User Authentication

The Evenman mobile application will require users to create an account and log in before
they can access the app's features. The app will use secure authentication methods to ensure
that only the rightful owner of the account can log in.
20
4.8.3.2 Data Encryption

All data transmitted between the Evenman mobile app and the server will be encrypted to
protect against unauthorized access or tampering. This includes user data like password
etc.
4.8.3.3 Access Control

The Evenman mobile app will implement access control measures to ensure that only
authorized users can access specific features or data. This includes measures such as rolebased access and permissions.
4.8.3.4 Vulnerability Management

The Evenman mobile app will have a process in place to identify, assess, and mitigate
vulnerabilities that may arise in the app or its infrastructure. This will include regular
security testing and updates to ensure the app remains secure.
4.8.4 Software Quality Attributes
Evenman is very user-friendly APP which only provide the user with its function but also with
many quality attributes. The APP is a smart adaptive it could run in any smart environment. This
APP will always be available for the users whenever any user open the APP it also provides the
full correctness of the functions of the application. The Location, Contacts, Profile, all will be
accurate depending on the command. If the user will give proper command the APP will provide
correct result.
4.8.5 Business Rules

Users must create an account in order to use the app.

Users must enter their budget in order to receive event organizers options.

Seller will reply to the bid if the user share its budget then seller will send him the list of
option buyer can get in this budget.
21

If the buyer bid the list of requirements then sellers will send him budget and buyer can
select the option according to his choice.

Users can only register one event organization company per account.

Users are not allowed to manipulate the app in order to receive clothing recommendations
outside of their budget.

Users are not allowed to spam or harass other users or the app administrators.

Users are not allowed to use the app for any illegal activities.

The app administrators reserve the right to terminate a user's account at any time for any
reason, including but not limited to violating these business rules.
22
Chapter 5
METHODOLOGY
5.1 Introduction
The process is used to attain the objective of the project that will carry out a perfect result. In order
to appraise this project, the methodology based on System Development Life Cycle (SDLC),
usually have three major steps, which is Implementing, planning and analysis as show in Fig 4.1.
Figure 7: SDLC
This project use three major steps to implement project starting with Planning, Implementing and
testing. All these steps use for finding, analyzing of data according to the meet of project.
Figure 8: SDLC steps
23
5.2 Planning
To analyze all the information and needs like hardware and software, related to the project the
planning must be done in appropriate manner. It have two main elements namely as Data collection
and requirements of hardware and software.
5.2.1 Data Collection
Data collection is the important phase of any project. In that stage I planned to collect the
requirements, resources to gather all the necessary information from the internet, researches, books
etc. Within the time the data gather from all the resources are filtered to get important things that
necessarily to develop the project.
5.2.2 Hardware and software requirements
The hardware and software requirements are as follow.
5.2.2.1 Hardware requirements

Smart Phone Sim supported (having android greater than 5.0)
5.2.2.2 Software requirements

Android Studio 3.2.0

Adobe Photoshop

MS Word

MS PowerPoint

MS Vision
5.3 Implementing
In this phase all the data gathering from the first phase is to implement using software requirement
to build the App. After successfully build the app requirements that are supposed to meet the main
objective and goes to final process.
5.4 Analysis
In this phase after being implement all the required data to successfully build the App its need a
conclusion to identify that project are built with the right methodologies.
24
Finally in the Analysis phase the project are successfully completing its functions as testing. First
users can find an event manager within their budget from various event companies. Users can also
register their own event company and sell their services through the app. The app is developed
using react native and is available for both Android and iOS devices
25
Chapter 6
DETAILED DESIGN AND
ARCHITECTURE
6.1 System Architecture
Evenman is composed within two sub system that are connected together to make App more user
friendly. Each subsystem have different module regarding the App and are composed to rely on
each other to perform a function for this there are responsibilities of each module are as follow and
System Architecture figure is given below in section 6.1.2 for better understanding.

The application should allow users to enter their budget and receive a list of event managers
options within that budget.

The application should provide a variety of event manager options, including their work
profile and a list of event with pictures along the budget they organized.

The application should provide images and detailed descriptions of each event company
(manager) option.

The application should allow users to save their favorite event organizers options for later
consideration.
6.1.1 Architecture Design Approach
For the development of Evenman APP Architecture design are as follow.

Initial Approach.

Test.

Next initial.
6.1.1.1 Initial Approach

Design the initial technique of current problem.

Create the module one by one.

Test design after module completion.
26
6.1.1.2 Test

Environmental test (runs on condition to meet the real time response).

Module run on different testing techniques.
6.1.1.3 Next Initial

Repeat the first two step.

Terminate.
6.1.2 Architecture Design
The System Architecture Design is given Figure 5.1.2.
Figure 9:Architecture Design
This system is linked with one another to perform the functions and if one of the following is
decomposed or unlinked with the other then the functions are not going to perform like if there is
no validation for the user then the whole system is false to breech the whole functionality.
27
6.1.3 Subsystem Architecture
Subsystem Architecture are described with Functional description.
6.1.3.1 Functional Description
It provide an overview of all components/module of Evenman App that are working together to
perform task and each single module working is also described in a smaller overview as show in
Fig 5.1.3.1(a) and in Fig 5.1.3.1(b)

User will need to generate a bid to get response.

Bid will be circulated to all the companies.

Companies will respond to bid and make an arrangement.

After accepting the offer client and vendor are free to discuss the event via build-in chat
system.
6.2 DETAILED SYSTEM DESING
6.2.1 Classification

Client and vendor/organizer.

Client will make a bid and vendor will respond to it.

They can communicate with each other via build in chatting system.
6.2.2 Definition
Budget in "Evenman" app cannot be overstated, as it serves as a fundamental aspect of the app's
value proposition and user experience. By allowing users to set their event budget, "Evenman" can
provide personalized event options that align with each user's financial constraints. User is the one
who is going to make a bid to book an event and vendor/organizer is the one who is going to
respond to the bid and organize the event for them.
6.2.3 Responsibilities
Budget plays a key role in the evaluation of this Evenman app. User provides the budget and the
vendor respond to the bid according to the budget and tell their services with in budget user selects
the company who’s work they like the most in their portfolio.
28
6.2.4 Constrains

user is getting real time response from companies.

Meeting the expected launch date while ensuring the app's quality and performance is a
crucial constraint for the development team.
6.2.5 Composition
There is no subcomponent of this Component.
6.2.6 Uses/interaction
Bidding is a key component of Evenman APP. It first linked the user and vendor with each other
through this app they both registered on the app as different user for us and then they will
communicate with each other through this app and make offer accept/reject and user can see the
portfolio of vendor before making a deal.
6.2.7 Resources
Budget for development, marketing, and operational expenses, or advertisements. User and
vendor data and databases to store and retrieve information required for app functionality.
6.2.8 Processing
First of all both the user registered their self to get access to the app then client make a bid and the
bid goes to all the companies and companies respond to the bid after getting a suitable offer for
both the users they can communicate with each other through build in chat system and then they
are good to go.
6.2.9 Interface/Export
It provide the following services.

Send bid from one user to another.

Make a successful communication between them.

Save their account information and vendors portfolio.
6.2.10 Detailed Subsystem Design
These subsystems may include Frontend, Backend, Database, and External Integrations. The
Frontend handles the user interface using React, while the Backend manages budget (bidding) and
29
chat system. The Database stores user and vendor data, vendor portfolio data , chat data and other
relevant information.
Diagrams
1. Use case Diagram.
2. ER Diagram.
3. Architectural Diagram.
4. Activity Diagram.
5. Sequence Diagram.
6. Component Diagram.
7. State Machine Diagram.
8. Class Diagram.
9. Data Flow Diagram.
10. Database Diagram.
30
6.2.10.1 Use case Diagram
Bidding
<<extend>>
<<extend>>
Recent news
Login
<<extend>>
Chat
User
Profile
<<extend>>
Accept/Remove bid
<<extend>>
Login
<<extend>>
Organizer
Post share
Figure 10: Use Case Diagram
31
6.2.10.2 Activity Diagram
EVENMAN
Fork
Connect
User Account
Client Send
Offer
Yes
Home
Vendor
Receive Offer
Chat
No
Not Connect
Login
Vendor
Accept/Reject
Offer
Marge
Vendor
Account
Login Page
End
Figure 11: Activity Diagram
32
6.2.10.3 Sequence Diagram
Figure 12: Sequence Diagram
33
6.2.10.4 Component Diagram
<<component>>
user/organizer
Required
<<component>>
Landing Page
Provide
<<component>>
Registered user
<<component>>
<<component>>
User/organizer
Required
send bid/accept bid
Provide
Depend
Association
<<component>>
<<component>>
User Input
company
Figure 13: Component Diagram
34
6.2.10.5 State machine
Figure 14: State machine
35
6.2.10.6 Architectural Diagram
Figure 15: Architectural Diagram
36
6.2.10.7 Class Diagram
Evenman
-CompanyName
-OwnerName
-Details
+DeveloperName
+SetCompanyName()
+SetOwnerName()
+SetDetails()
+GetCompanyName()
+GetOwnerName()
+GetDetails()
Client
Organizer
-MemberName
-MemberPassword
-MemberName
-Password
+SetMemberName()
-SetPassword()
+GetMemberName()
-GetPassword()
+SetmemberName()
+GetmemberName()
+SetPassword()
+GetPassword()
Associating
chat
+accept
prefrences
+communicate()
-budget
-Requirements
Bidding
-requirements
-budget
+accept bid ()
+reject bid()
Figure 16: Class Diagram
37
6.2.10.8 ER Diagram
Figure 17: ER Diagram
38
6.2.10.9 Interaction Diagram
Interaction overview Diagram
SD
User
System
Login
Landing Page
Send Bid
Accept/Reject
Accept offer
Chat
Account
profile Build
Forget Password
Receive Email
Ref:Activity diagram
[Not accurate]
Database
[Accurate]
END
Figure 18: Interaction Diagram
39
6.2.10.10 Data Flow Diagram
Start
Incoming request
Login Panel
LOGIN ID
INVALID
ID Checking
VALID
VALID
User
DATA
Firebase
DATA
Company
Recent News
Portfolio
Create offer
Received offer
Sent offer
Accepted offer
Chat
Chat
Account
Account
Figure 19: Data Flow Diagram
40
Chapter 7
IMPLEMENTATION AND TESTING
7.1 Tools

Visual studio code.

MS VISIO.

Smart Phone.
7.2 Testing methods
In this process we test two main Activities, bidding send and receive properly and communication
between vendor and client.
7.2.1 Test plan for generate contact list.
Screen Name: Bidding Screen.
Test Plan ID: 001
APP Name: Evenman.
Engineers: Umer Farooq/Wadood Nasir.
Test no: 1
Purpose
Checking the APP activity working properly for bidding send and receive.
Scenario:
APP is responsive to all devices having android version 6.0(marshmallow) or greater and also to
complete that module to cover Dimensions.
Environment:
Visual studio code.
Pre-Requisite:
Observing / Checking Bidding Screen.
Strategy:

Click on “Send Offer” Section to open required Screen.
41

Show the option for sending a bid.

Enter the requirements and budget.

Offer send to all the registered companies.
Expected Result:

Companies will respond to the offer.

All section are working properly.
Observation:

All section are selected and working successfully.

Displayed the response of bid.
7.2.2 Test plan for Checking Settings Enables.
Screen Name: Chat Activity.
Test Plan ID: 002
APP Name: Evenman.
Engineers: Umer Farooq/ Wadood Nasir.
Test no: 02
Purpose:
Checking the APP activity Select and can chat with the other person.
Scenario:
APP is responsive to all settings that enabled
Environment:
Visual Studio Code/Smart Phone.
Pre-Requisite:
Observing / Checking Chat Screen.
Strategy:

Click on “Accepted Offer” Section to open required activity.

Show All Accepted offer to the vendor.
42

Press the offer to start chat with client.
Expected Result:

Selected screen display properly and achieved result.

All settings are enabled properly.
Observation:

All Settings enabled successfully.
.
43
Chapter 8
RESULTS AND DISCUSSION
8.1 Results of Test Evaluation
From the previous chapter testing evaluation results are shown in figure 8.1(a,b,c), 8.2(b).
Figure 22
Figure 23: Offer received
Figure
Figure
21:20
Accepted Offers
44
Figure 24: Messages Notification
Figure 25: Chat System
45
Chapter 9
CONCLUSION AND FUTURE WORK
9.1 Future Work
The future work of "EVENMAN" involves a strategic approach to enhancing the app's
functionality and user experience. One of the key areas of focus would be expanding the
event catalog with a broader range of event designs, collaborating with more companies
to give user a complete package, build a store in app so user can make purchase related to
their event, and build a build-in payment system to avoid any kind of frauds.
9.2 Conclusion
In conclusion, "Evenman" is an innovative and user-friendly mobile application designed
to assist fashion-conscious users in finding clothing items that fit their budget. Developed
using React Native, the app offers cross-platform compatibility, catering to both iOS and
Android users. The purpose of this application problem is to provide a platform to small
business to grow their business more faster by showing their valuable word to the client,
user will make a bid and companies will respond to the bid and make user decide who is
willing to done his/her work with in his budget. Basically we are reducing the time and
money by collecting all the users and vendors on a single app, there will no need to go
from one company to another for getting the best price and work.
46
References
[1] Karl E. Wiegers, system required specification for n traveler,
https://cs.gmu.edu/~dfleck/classes/cs421/spring08/SampleProject/FINAL%20SRS.pdf
[2] AnılDoğan, BahadırHatunoğlu, System required specification for A Mobile Barter shop,
https://senior.ceng.metu.edu.tr/2014/epicfail/docs/SRSv10.pdf
[3] Catherine Suh, System required specification for mobile navigation control for planetary web
portals,
https://csns.calstatela.edu/department/cs/project/resource/view?projectId=5530050&resourceId=
5696648
[4] AnılDoğan, BahadırHatunoğlu, System required specification for A Mobile Barter shop,
https://senior.ceng.metu.edu.tr/2014/epicfail/docs/SRSv10.pdf
[5] Ravi Bandakkanavar, sample-software-requirements-specificationsrs-report-airline-database,
https://krazytech.com/projects/sample-software-requirements-specificationsrs-report-airlinedatabase
[6] GitHub, android-location-services,
https://github.com/googlesamples/androidlocation/tree/master/LocationUpdatesForegroundServi
ce
[7] Aritraroy, Pattern-lock-view,
https://github.com/aritraroy/PatternLockView
[8] MXSPY, 2 way to hack into Smartphone,
https://mxspy.com/how-to-hack-a-phone/
47