Final Project Report
RecipeSharing.com
Project Supervisor
Hafiz Bilal Saqib
Submitted By
Group ID: S2402DFF7F
STUDENT NAME: ASIF SALEEM
STUDENT ID: (BC210405182)
Software Projects & Research Section,
Department of Computer Sciences,
Virtual University of Pakistan
CERTIFICATE
This is to certify that STUDENT NAME: ASIF SALEEM (STUDENT ID:
BC210405182 has worked on and completed their Software Project at Software &
Research Projects Section, Department of Computer Sciences, Virtual University of
Pakistan in partial fulfillment of the requirement for the degree of Computer
Sciences under my guidance and supervision.
In our opinion, it is satisfactory and up to the mark and therefore fulfills the
requirements of Computer Sciences.
Supervisor / Internal Examiner
Hafiz Bilal Saqib
Supervisor,
Software Projects & Research Section,
Department of Computer Sciences
Virtual University of Pakistan
___________________
(Signature)
External Examiner/Subject Specialist
<<External Supervisor Name>>
___________________
(Signature)
Accepted By:
_____________
(For office use)
EXORDIUM
In the name of Allah, the Compassionate, the Merciful.
Praise be to Allah, Lord of Creation,
The Compassionate, the Merciful,
King of Judgment-day!
You alone we worship, and to You alone we pray for help,
Guide us to the straight path
The path of those who You have favored,
Not of those who have incurred Your wrath,
Nor of those who have gone astray.
DEDICATION
The completed work to be devoted to someone closer to you e.g., Mother, Father etc.
ACKNOWLEDGEMENT
Thankfulness to your loved ones for their support in the completeness of the project.
PREFACE
This project has helped me in gaining valuable knowledge Moreover, during this phase
of learning, this project helped me to enhance my knowledge regarding the work. I had
undergone many experiences related to the programming concepts, procedures, views,
triggers and many other concepts, through this project I come to know the importance
of online learning and role of devotion towards the work.
TABLE OF CONTENTS
CHAPTER NO. 1
SOFTWARE REQUIREMENTS SPECIFICATION (SRS DOCUMENT)
1.1 SCOPE
1.2 FUNCTIONAL & NON-FUCNTIONAL)
1.3 USE CASE DIAGRAM
1.4 WORK PLAN (USE MS PROJECT TO CREATE SCHEDULE/WORK PLAN)
CHAPTER NO. 2
DESIGNING THE PROJECT (DESIGN DOCUMENT)
2.1 INTRODUCTION OF DESIGN DOCUMENT
2.2 DATA FLOW DIAGRAM (DFD)
2.3 ENTITY RELATIONSHIP DIAGRAM (ERD)
2.4 DATABASE DESIGN
2.5 INTERFACE DESIGN
CHAPTER 1
SOFTWARE REQUIREMENTS SPECIFICATION (SRS DOCUMENT)
1.1 Scope of Project:
The scope of RecipeSharing.com involves developing a comprehensive web
application for cooking enthusiasts to find, share, and manage recipes. The project
includes secure user registration, login, and password reset functionalities. Users can
edit their profiles and browse recipes categorized by cuisine types and dietary needs.
Logged-in users can submit, edit, and delete their own recipes, while all users can
search for recipes using keywords, ingredients, or categories. The platform aims to
offer a user-friendly interface, robust search capabilities, and a secure environment.
Additionally, the project focuses on ensuring high performance, scalability, and data
protection, along with thorough testing and quality assurance to provide a seamless user
experience.
1.2 Functional and non Functional Requirements:
Functional Requirements
Users should be able to register for an account.
Users should be able to log in to their accounts securely.
Users should be able to edit their profile information.
Users should be able to reset their passwords if forgotten.
Users should be able to browse recipes without logging in.
Logged-in users should be able to submit new recipes.
Users should be able to edit and delete their own recipes.
Users should be able to search for recipes based on keywords, ingredients, or
categories.
Non Functional Requirements
Non-functional requirements describe the characteristics, constraints, and qualities that
the system must have. Here are some non-functional requirements for the Copy Pencil
online stationery store management software:
Performance Requirements:
1.Response Time:
The system should respond to user actions (e.g., login, order placement) within
2 seconds to provide a seamless user experience.
2.Scalability:
The system should be scalable to accommodate a growing number of users
and a larger inventory of stationary items without a significant degradation in
performance.
Security Requirements:
1.Data Encryption:
Customer and admin login credentials, as well as sensitive data, should be
encrypted to ensure secure data transmission.
2.Access Control:
The system should implement role-based access control, ensuring that only
authorized users have access to specific functionalities.
Reliability Requirements:
1.System Availability:
The system should be available 99.9% of the time during standard operating
hours.
2.Data Backup:
Regular automated backups of the system data should be performed to prevent
data loss in the event of system failures.
Usability Requirements
1.Language Support:
The user interfaces for both customers and admins should be available in
English, ensuring a consistent and understandable user experience.
2.Intuitive Design:
The system interfaces should be designed in an intuitive manner, requiring
minimal training for users to navigate and perform tasks.
Compatibility Requirements:
1.Browser Compatibility:
The system should be compatible with popular web browsers (e.g., Chrome,
Firefox, Safari) to ensure a consistent experience across different platforms.
2.Device Compatibility:
The system should be accessible and functional on various devices, including
desktops, laptops, tablets, and smartphones.
Maintainability Requirements:
1.Modularity:
The system should be designed with modular components, allowing for easier
maintenance and future updates.
2.Documentation:
Comprehensive documentation, including user manuals and system architecture
documentation, should be provided for administrators and users.
Compliance Requirements:
1.Legal Compliance:
The system should comply with relevant data protection and privacy laws to
ensure the lawful handling of customer information.
2.Industry Standards:
The development and implementation of the system should adhere to industry
best practices and standards.
Performance Requirements:
1.Response Time:
The system should respond to user actions (e.g., login, order placement) within
2 seconds to provide a seamless user experience.
2.Scalability:
The system should be scalable to accommodate a growing number of users and
a larger inventory of stationary items without a significant degradation in
performance.
1.3 Use Case Diagram
1.4 Work Plan (Use MS Project to create Schedule/Work Plan)
CHAPTER 2
Designing the Project
(Design Document)
2.1 Introduction of Design Document
Introduction of Design Document
The design document describes the whole information about the software. During
the design phase the focal point shifts from what to how.
A design document is a complete abnormal state determination to the inconvenience
available. A design document is imperative to build up a framework. Programming
configuration prepare rotates pretty much rotting of the framework into littler and more
straightforward units to accomplish the craving result.
In design document of “web based application” is based on Virtual University of
Pakistan final year project to develop the library management system as per
requirements given in a project file. Design phase will further explore our Functional
specifications. These functional requirements will describe important features that are
directly exposed to users. We have to explain the Functional Requirements in the form
of the Flow of Data. Design documents contains introduction of design document. This
document also includes ERD, database diagram, interface design will be explained in
this project.
1. Purpose of design document:
2. The purpose of the software design document is to provide a description of the
design of a system fully enough to allow for software develop meant to proceed
with an understanding of what is to be built and how it is expected to build.
3. Benefits of design document:
Benefits of documentation. Accurate and up to date documentation makes your
components, web services, schemas and databases easier to use and maintain,
reducing support requirements whilst improving quality and productivity.
4. Road Map for project:
The design activity provides a roadmap to progressively transform the
requirements through a number on stages into the final product by describing
the structure of the system to be implemented. Different activities that are used
in this document are briefly explained below.
5. Entity Relationship Diagram (ERD):
It is graphical representation of entities and their relationships to each other.
6. Database Diagram:
This describes a way to logically group objects.
7. Interface Design:
This design shows the important features of a product.
2.2 Entity Relationship Diagram (ERD)
2.3 Database Design
Users Interface
