Final Year Project Report

on
Project Title

Submitted By
Faisal Rehman BSSE07203039
Nouman Hassan BSSE07203019 Qasim
Ali BSSE07203039

In Partial Fulfillment of
The Requirements for the Degree of
Degree Name
Software Engineering

Supervised by: Mr Saqlain

Department of Computer Sciences

University of Lahore, Sargodha Campus
Session:

2|Page
 Final Approval

This project titled

Cermoney Crafter

By

Faisal Rehman BSSE07203039

Nouman Hassan BSSE07203019
Qasim Ali BSSE07203039

Has been approved for the

Department of Computer Sciences,
University Of Lahore (Sargodha Campus)

External Examiner:______________________________________________________________
Mr Yasir Ghayoor Malik
Lecturer
The University of Lahore
Sargodha

Supervisor: _____________________________________________________________________
Mr Yasir Ghayoor Malik
Lecturer
The University of Lahore
Sargodha

FYP Committee Head: ___________________________________________________________

Ms. Fatima Iqbal
Lecturer
The University of Lahore
Sargodha

HoD: __________________________________________________________________________
Dr.Umar Ajaib Khan

3|Page
Assistant Professor
The University of Lahore
Sargodha

Declaration
I/We hereby declare that this work, neither as a whole nor as a part there of has been copied out
from any source. No portion of the work presented in this report has been submitted in support of
any application for any other degree or qualification of this or any other university or institute of
learning.

_________________________
Name:
Reg#:

4|Page
Dedication

5|Page
Acknowledgement

6|Page
 Table of Contents

CHAPTER 1 Introduction and Background......................................... 1

1.1 Statement of Problem Area .................................................................................. 1
1.2 Background History ............................................................................................. 1
1.3 Previous and current work ................................................................................... 3
1.4 Project description ............................................................................................... 4
1.5 Purpose................................................................................................................. 4
1.6 Objectives ............................................................................................................ 4
1.7 Scope .................................................................................................................... 5
1.8 Introduction .......................................................................................................... 5
1.9 Tools and Technologies used ............................................................................... 5
1.10 Deployment Platform ......................................................................................... 6
1.11 Project Scheduling ............................................................................................. 7

CHAPTER 2 Software Requirements Specifications (SRS) ............... 5

2.1Functional Requirements ...................................................................................... 5
2.2 Nonfunctional Requirements ............................................................................... 7
2.3 Project/Product Feasibility Report ....................................................................... 8
2.3.1. Technical Feasibility ................................................................................ 9
2.3.2. Operational Feasibility ............................................................................. 9
2.3.3. Legal & Ethical Feasibility ...................................................................... 9
2.3.4. Economic Feasibility ............................................................................... 9
2.3.5. Schedule Feasibility ................................................................................. 9
2.3.6. Motivational Feasibility ......................................................................... 10
2.3.7. Information Feasibility .......................................................................... 10
2.3.8. Specification Feasibility ........................................................................ 10

CHAPTER 03 System Performance Requirements ........................... 11

3.1 Efficiency ........................................................................................................... 11
3.2 Reliability........................................................................................................... 11
3.3 Security .............................................................................................................. 12
3.4 Maintainability ................................................................................................... 12
3.5 Modification....................................................................................................... 12
3.6 Portability........................................................................................................... 12

7|Page
CHAPTER 04 System Analysis & Design Overview .......................... 14
4.1 Use Case Diagrams…………………………………………………………
4.2 Software Process Model……………………………………………………
4.3 Data Model…………………………. ...............................................................
4.3.1 ERA Model……….. ................................................................................
4.3.2 System Data Dictionary ..........................................................................
4.4 Behavioral Models ............................................................................................
4.4.1 Data Flow Models ....................................................................................
4.4.2 System Sequence Models .........................................................................
4.5 Object Models ...................................................................................................
4.5.1 State Models .............................................................................................
4.5.2 Class Inheritance Model ...........................................................................
4.6 Implementation Languages ..............................................................................
4.7 Required Support Software ...............................................................................

CHAPTER 05 User Interface Design .................................................. 52

5.1 User Interface Specification ............................................................................... 52
5.1.1 User Interface Designs ............................................................................ 52
5.1.2 Report Formats/Sample Data
5.2 User Support ...................................................................................................... 60
5.2.1 On-line Help Material
5.2.1 Error Conditions and System Messages ................................................. 60

CHAPTER 06 System Verification & Validation ................................ 53

6.1 Items/Functions to be Tested……………………………………………………
6.2 Description of Test Cases……………………………………………........……
6.3 Justification of Test Cases………………………………………………………
6.4 Test Run Procedures and Results ……………………………………………..

CHAPTER 07 Conclusions .................................................................. 62

7.1 Summary ............................................................................................................ 62
7.2 Problems Encountered and Solved .................................................................... 63
7.3 Suggestions for Better Approaches to Project ................................................... 63
7.4 Suggestions for Future Extensions to Project .................................................... 63

Bibliography & References ................................................................... 64

8|Page
Glossary .................................................................................................. 65

List of Figures
Figure 1: Project scheduling………………………………………………………………..18
Figure 2: Class activity diagram……………………………………………………………20

List of Tables

9|Page
Table 1: Summary of Platforms……………………………………………………………10
Table 2: Supporting OS…………………………………………………………………….20

10 | P a g e
 Chapter 1 Introduction and Background

1.1 Statement of Problem Area:

The manual organization of home events show significant challenges for customers, including
time-consuming coordination of various services such as catering, car decoration, lighting,
photography, rent car packages, and bridal makeup. The inefficiencies in communication between
service providers and customers often result in a stressful planning process and suboptimal event
experiences.

1.2 Background History:

Traditional methods of event planning, including hiring event planners, online searches, and
word-of-mouth recommendations, are often expensive, time-consuming, and unreliable. This
project aims to address these challenges by offering a user-friendly platform that streamlines the
process of planning and booking essential services for home events.

1.3 Previous and Current Work:

Prior to the development of this platform, customers relied on manual coordination and
negotiation with service providers. Existing event planning methods lacked centralized solutions
and efficient communication channels between users and service providers. This project seeks to
revolutionize the home event planning process by providing a comprehensive and convenient
platform.

11 | P a g e
1.4 Project Description:
The project involves the development of a centralized platform that facilitates home-based event
services. It aims to simplify event organization by offering a wide range of services, including
catering, hoteling, sound system, car decoration, lighting, photography, rent car packages, and
bridal makeup. The platform will serve as a one-stop solution for users to plan and execute home
events efficiently.

1.5 Purpose:
The purpose of this project is to develop a comprehensive platform that simplifies the process of
organizing home events. By offering a range of services and streamlining the booking process, the
platform aims to provide users with a convenient and efficient solution for planning their special
occasions.

1.6 Objectives:
1. Develop a centralized platform for home event services.
2. Implement user interfaces for seamless service booking.
3. Provide modules for each service category, ensuring a comprehensive offering.
4. Enable secure and convenient payment options for users.
5. Establish communication channels between users and service providers.
6. Incorporate a review and rating system for user feedback.
7. Ensure scalability for potential growth in the user base over time.

1.7 Scope:
The scope of the project includes creating a user-friendly platform that connects customers with
various service providers. It encompasses modules for catering service booking, car decoration,
lighting arrangements, photography services, rent car packages, and bridal makeup.

1.8 Introduction:
Lighting, photography, rent car packages, and bridal makeup becomes a time-consuming and stressful
task. Coordinating communication between different service providers, ensuring availability, and
managing last-minute changes can lead to a less-than-optimal Event experience. . The main issue is a
wastage of time to organize event at home.
People usually hire Event planners, search online, or rely on recommendations. However, these methods
can be expensive, time-consuming, and not always reliable.]
Planning an Event on your own can be stressful. The customer face challenges on hiring and meet
manually and bargaining with service providers such as catering, car decoration, lighting, photography,
rent car packages, and bridal makeup.
This project addresses this demand by providing a user-friendly interface where customers can
effortlessly plan and book various services crucial for a home Event, including catering, car decoration,
lighting, photography, rent car packages, and bridal makeup

12 | P a g e
1.9 Tools and Technologies Used:
Programming(e.g., React Native )
- Push Notification(e.g., firebase cloud management)
- Database(e.g., Firebase)
- Payment(e.g., jazz cash, easy paisa and Bank Transfer)
- UI/UX (e.g., Adobe PS/ Figma)
- Documentation (e.g., MS Office)

1.10 Deployment Platform:

-Android

1.11 Project Scheduling:

Project scheduling is a crucial aspect of project management that involves planning, organizing,
and allocating resources to specific tasks within a defined timeframe. In the context of the
Ceremony Crafter project, a well-structured project schedule outlines the chronological sequence of
activities required for successful development and deployment. The scheduling process in the
Software Requirements Specification (SRS) involves breaking down the project into manageable
tasks, estimating the time required for each task, and establishing dependencies between tasks. This
creates a roadmap for the development team, guiding them through the project phases and ensuring
that activities are executed in a logical order. The project schedule aids in resource management,
identifies critical paths, and allows for the tracking of progress. Additionally, it provides
stakeholders with a clear timeline for milestone achievements, helping to manage expectations and
ensuring timely delivery of the Ceremony Crafter platform. Regular updates and adjustments to the
schedule, based on ongoing assessments and feedback, are integral to maintaining project
momentum and achieving successful outcomes.

CHAPTER 2 Software Requirements Specifications

(SRS)

2.1 Functional Requirements:

The functional requirements outline the specific features and capabilities that the software system
must possess to fulfill its intended purpose effectively. These requirements serve as the foundation

13 | P a g e
for the development and design of the platform. Here is a detailed description of the functional
requirements:

- User Registration: The system should allow users to create accounts as either customers or
service providers. Registration should include necessary information and validation steps. -
Account Management: Users should be able to manage their accounts, including profile
information, preferences, and settings.
- Admin Panel: An admin panel should be available to manage user accounts securely,
including the ability to add, remove, and block users as needed.
- Live Chat Functionality: The platform should facilitate real-time communication between
customers and service providers through a live chat feature.
- Service Booking: Users should be able to browse and select services based on categories
such as catering, car decoration, lighting arrangements, photography services, rent car packages,
and bridal makeup.
- Availability Calendar: Service providers should maintain availability schedules that users
can check to book services at suitable times.
- Booking Confirmation and Notifications: Users should receive instant booking
confirmations and timely notifications regarding their bookings and service status updates.
- Secure Payments: The system should support secure payment options, allowing users to
make transactions within the platform.
- Ratings and Reviews: Users should be able to rate and review services they have received,
providing valuable feedback for both service providers and other users.
- Feedback and Support: The platform should facilitate the collection of feedback from both
customers and service providers, with mechanisms in place for problem resolution through
customer support channels.

2.2 Nonfunctional Requirements:

Nonfunctional requirements define the quality attributes and constraints of the software system
beyond its specific functionality. These requirements focus on aspects such as performance,
security, usability, and reliability. Examples of nonfunctional requirements include: -
Performance: The system should be able to handle a certain number of simultaneous users
without significant performance degradation.
- Security: The platform should implement robust security measures to protect user data and
transactions.
- Usability: The user interface should be intuitive and easy to navigate, catering to users with
varying levels of technical proficiency.

14 | P a g e
- Reliability: The system should be always reliable and available for use, with minimal
downtime for maintenance or updates.

2.3 Project/Product Feasibility Report:

The feasibility report assesses the viability of the project/product from various perspectives,
including technical, operational, legal, ethical, economic, schedule, motivational, information, and
specification feasibility. Each aspect evaluates the project's potential success and identifies
potential challenges or risks that may impact its implementation and adoption.

Specific details regarding technical feasibility, operational feasibility, legal and ethical feasibility,
economic feasibility, schedule feasibility, motivational feasibility, information feasibility, and
specification feasibility should be provided in the report, outlining the project's strengths,
weaknesses, opportunities, and threats across these dimensions. This comprehensive assessment
helps stakeholders make informed decisions regarding the project's execution and resource
allocation.
2.3.1 Technical Feasibility

The technical feasibility of the proposed system is robust, supported by the utilization of proven
and widely adopted technologies. The use of React Native for the mobile application ensures
crossplatform compatibility, reaching a broad user base. The choice of Node.js as the backend
language and MongoDB as the database offers scalability and flexibility, accommodating potential
growth in users and data. Integration with Firebase for push notifications enhances real-time
communication. The selected payment gateways, including Jazz Cash, Easy Paisa, and Bank
Transfer, contribute to the system's financial viability. The adoption of industry-standard UI/UX
design tools such as Adobe PS and Figma ensures an intuitive user interface. Additionally, the
deployment on the Android platform aligns with market trends and user preferences. Overall, the
technical framework is well-founded, promoting efficiency, security, and a seamless user
experience.

2.3.2. Operational Feasibility

Operational feasibility, as outlined in the Software Requirements Specification (SRS), underscores

the practicality and viability of implementing the proposed system within the existing operational
environment. This encompasses an assessment of the organization's infrastructure, staff
capabilities, and workflows to determine whether the introduction of the new home-based event
services platform aligns with the current operational processes. The feasibility study evaluates
factors such as user acceptance, adaptability to existing business practices, and the ease with which
users, both customers and service providers, can integrate the platform into their daily operations.
By considering these aspects, the SRS ensures that the proposed system not only meets technical
requirements but also seamlessly integrates into the operational fabric of the organization, fostering
efficiency and user satisfaction.

2.3.4. Economic Feasibility

15 | P a g e
Economic feasibility is a critical aspect of project evaluation that examines the financial viability
and potential economic benefits of implementing a proposed system. In the context of the Software
Requirements Specification (SRS), economic feasibility involves a detailed analysis of the costs
and returns associated with developing, deploying, and maintaining the home-based event services
platform. This assessment includes factors such as development costs, infrastructure expenses,
operational and maintenance costs, and potential revenue streams. By conducting a comprehensive
economic feasibility study, the SRS aims to provide stakeholders with a clear understanding of the
financial implications and benefits associated with the project. It assists in making informed
decisions about resource allocation, budgeting, and assessing the project's overall financial
sustainability. The goal is to ensure that the project aligns with the organization's financial
objectives and is a sound investment in terms of both short-term and long-term economic
considerations.

2.3.5. Schedule Feasibility

Schedule feasibility in the context of the Ceremony Crafter project, as outlined in the Software
Requirements Specification (SRS), addresses the practicality and achievability of the proposed
system within a specified timeframe. The development plan for the Ceremony Crafter project
involves several phases to ensure a systematic and timely delivery of the platform. In the initial
phase, which spans the first month, a comprehensive requirement analysis will be conducted,
detailing the specific functionalities and features needed for the platform. Following this, the
second and third months will focus on UI/UX design and backend development, respectively. The
fourth and fifth months will be dedicated to frontend development, service integration, and rigorous
testing to ensure the platform's robustness. The sixth month will witness the deployment of the
platform, including user training and initial marketing efforts. Subsequent months will involve
ongoing support, updates, and feature enhancements based on user feedback and evolving
requirements. This phased development plan ensures that the Ceremony Crafter project adheres to a
realistic schedule, allowing for efficient and timely delivery while accommodating potential
adjustments and improvements throughout the development lifecycle.

2.3.6. Motivational Feasibility

Motivational feasibility within the context of the Ceremony Crafter project, as outlined in the
Software Requirements Specification (SRS), focuses on assessing the enthusiasm, commitment,
and motivation levels of the key stakeholders involved in the project. This includes both the
development team responsible for creating the home-based event services platform and the
endusers who will engage with the system. The SRS aims to ensure that the envisioned platform
aligns with the motivational factors of these stakeholders, inspiring a shared sense of purpose and
dedication to the project's success. By addressing motivational feasibility, the document considers
factors such as the perceived value of the platform, user engagement strategies, and the potential
impact of the system on the satisfaction and motivation of both customers and service providers. A
project that resonates with the motivations of its stakeholders is more likely to garner active
participation, foster collaboration, and contribute to the overall success and sustainability of the
Ceremony Crafter platform.

2.3.6. Information Feasibility

16 | P a g e
Information feasibility in the Software Requirements Specification (SRS) for the Ceremony Crafter
project refers to the viability and effectiveness of managing information within the proposed
system. This involves an assessment of the availability, relevance, accuracy, and timeliness of the
information that the platform will handle. The SRS aims to ensure that the home-based event
services platform can efficiently gather, store, and process the necessary data related to catering,
car decoration, lighting, photography, rent car packages, and bridal makeup. It considers factors
such as data sources, data storage mechanisms, and the reliability of information presented to users.
The information feasibility analysis within the SRS ensures that the system provides users with
reliable and up-to-date information, contributing to the overall success and user satisfaction of the
Ceremony Crafter project.

2.3.8. Specification Feasibility

Specification feasibility within the Software Requirements Specification (SRS) for a project like
"Ceremony Crafter" involves evaluating the practicality and achievability of the outlined
requirements and specifications. This assessment ensures that the proposed system's specifications,
such as features, functionalities, and technical requirements, are clear, well-defined, and attainable
within the given constraints. The SRS aims to address potential challenges related to the specificity
and clarity of requirements, ensuring that they are not overly complex or ambiguous. Specification
feasibility also considers the technical capabilities of the chosen development tools and platforms
to meet the outlined specifications. By conducting a thorough analysis of specification feasibility,
the SRS aims to establish a solid foundation for the development team, ensuring that the outlined
requirements are realistic, technically sound, and align with the overall objectives of the Ceremony
Crafter project. This process enhances the likelihood of successful implementation and minimizes
the risk of misinterpretation or misalignment with project goals.

17 | P a g e
CHAPTER 04 System Analysis & Design Overview .......................... 14
4.1 Use Case Diagrams…………………………………………………………
4.2 Software Process Model……………………………………………………
4.3 Data Model…………………………. ...............................................................
4.3.1 ERA Model……….. ................................................................................
4.3.2 System Data Dictionary

4.4 Behavioral Models ............................................................................................

4.4.1 Data Flow Models ....................................................................................
4.4.2 System Sequence Models .........................................................................
4.5 Object Models ...................................................................................................
4.5.1 State Models .............................................................................................
4.5.2 Class Inheritance Model ...........................................................................
4.6 Implementation Languages ..............................................................................
4.7 Required Support Software .

18 | P a g e
 CHAPTER 05
User Interface Design
5.1 User Interface Specification
It is a path between user and computer program. It is a set of actions that
user can perform to communicate with the application. We can enter
different commands that can perform actions. We select command which
we want to play onscreen. A User Interface Specification is a written
document that comprehensively outlines the details of the software's user
interface. This document encompasses all potential actions that an end
user might undertake, as well as detailing all visual, auditory, and other
interactive elements. It is important and basic part of a project. Without it a
user did not do anything. User interface is user friendly which guides the
user how to use a program. Because of user interface we can make the
program what to do easily.

5.1.1 User Interface Designs

5.1.2 Report Formats/Sample Data

5.2 User Support
5.2.1 On-line Help Material
5.2.1 Error Conditions and System Messages

19 | P a g e
 References

In this section you list in standard bibliographic format the books, papers, course notes and project
or thesis reports which you have used in preparing your project documentation.

References must be numbered alphabetically. In the text they should be referred to by squared
bracketed numerals, e.g. [1]. The list of references must be typed on a separate sheet(s), in the same
format as the main text, and ordered consecutively, according to the following models:

For a paper in a contributed volume:

[1] D.B. Lenat, R. Davis, J. Doyle, M. Genesereth, I. Goldstein and H. Schrobe, "Reasoning about
reasoning," in Building Expert Systems (F. Hayes-Roth, D.A. Waterman and D.B. Lenat, eds.)
Addison-Wesley Publishing Company, Inc., 1983, pp. 219-240.

For a paper in a journal:

[2] D.W. Jones, "Concurrent operations on Priority Queues," Communications of the ACM, 32,
l(January 1989), pp- 132-137.

For a book:

[3] H.F. Korth and A. Silberschatz, Database System Concepts, McGraw-Hill, New York, 1986.

For an unpublished paper:

[4] S.E. Feahlman, A system for representing and using real-world knowledge, MIT Technical
Report Al-TR-40, Cambridge, MA, 1977.

20 | P a g e