Post Top Ad

Responsive Ads Here

Featured Posts

Scientific Paper Digital Library System Free Source Code in PHP

- No comments
Scientific Paper Digital Library System Free Source Code in PHP

Problem Statement

The Scientific Paper Digital Library System Free Source Code in PHP is designed to keep track of scientific papers such as scientific publications, conferences, journals, authors, institutions, and subscribers. In the digital library system, a member can register the system. Member may be an author which belongs to an institution or a subscriber.

The system allows subscribers to access any publication, attend conferences and subscribe compositions. An author can either be a student or an academic. When the expertise level of an academic reaches some point he/she will be assigned as an editor. The system also allows to emit publications such as tech reports and papers. Some number of publications compose and create compositions such as conferences and journals. An editor is able to review a publication and manages the publications that can be in a composition.

Functional Requirements and Limitations of Scientific Paper Digital Library System Free Source Code in PHP

There are 4 different types of users of the system according to their functionalities: researchers, editors, students, and subscribers. All users of the system regarded as a member. A member must be either an author or a subscriber. An author can be a researcher or a student. Furthermore, the researcher can be specialized as editors.

The library system also includes ins7tutions, sponsors, publications and compositions such as journals and conferences.


Member is the generalization of all the users enrolled in the system. A member can have attributes of userName, password, name, phone, address.

Functional Requirements:

  • All members should be able to subscribe to a composition.
  • All members should be able to view publications.
  • The system should inform a member about conferences and journals that the member subscribes.
  • A member should be able to attend a conference.
  • A person should be able to fill a related enrolment form in order to be enrolled in the system as a member.


    An author is a member who can contribute to the publications of the digital library. Thus, does not have an annual fee. An author can have attributes of no of Publications, resume.

    Functional Requirements:

    An author should be able to
    • contribute a publication to the library that he/she wrote or collaborated.
    • contribute to his/her own publication that is in the library.
    • receive feedback of his own publication that is reviewed by an editor.
    • contribute to his own publication after he receives feedback.
    • approved by an editor to finalize his registration.


      An author should belong to an institution.


      A researcher is an author. A researcher can have attributes of diploma, expertise level, profession.

      Functional Requirements:

      A researcher should be able to
      • submit a publication to a composition.
      • submit his/her own publication or a publication that he/she contributed to the system.
      • have a diploma that is applicable.
      • an expert level that is sufficient.
      • have a valid profession.
      • A researcher gains the expertise level of 10 when he/she uses the system.


      An editor is an author who is a researcher. In order for a researcher to be an editor, he/she should improve his/her expertise level. An editor can have attributes of editor keys.

      Functional Requirements:

      An editor should be able to
      • review a publication to determine its status.
      • give feedback to the related author about the publication he/she reviewed.
      • manage composition submissions in order to decide which publications should be involved in a composition.
      • Afera researcher reaches the specified expertise level, the system should give the editor an editor key.
      • An editor should use his/her editor key to review a publication and decides if a publication should involve in a publication or not.


      An editor should have an expert level of at least 100.


      A student is an author. A student can have attributes of eduStatus.

      Functional Requirements:

      • A student should be able to contribute to a publication because of him being an author.


      • A student cannot submit his/her work to a composition.


      The subscriber is a member of the system. However, he/she does not contribute to the system. Thus, he/she pays an annual fee to have member functions such as access publications, attend conferences and subscribe to conferences and journals. A subscriber can have attributes of the annual fee.

      Functional Requirements:

      • A subscriber should pay an annual fee to remain registered to the system.


      An institution can have attributes of name, address.

      Functional Requirements:

      • An institution may have many authors.


      A publication can have attributes of ISBN, name, topic, status, type.

      Functional Requirements:

      • A publication should be able to submit into a composition.
      • A publication should be able to be cited.


      • A publication should have at least 5 citations.
      • There should be at least 5 authors of a publication to be valid.
      • There should be at least 3 researchers.
      • A publication can have status accepted, rejected, on review or on submit.
      • A publication can be the type of paper or tech report.


      • A composition is either a conference or a journal.
      • The composition is managed by an editor.
      • A composition can have attributes of ID, name, topic, no of Publications, status.


      A journal is a composition. A journal can have a^ributes of issueNo.


      • A journal should be published monthly.
      • A journal should contain at least 7 publications.


      A conference is a  composition. It is a collection of publications that is presented in a conference hall. A conference can have attributes of sponsor, place, date, time, noOfAttendees, status


      • A conference should have at least 1 sponsor. 
      • A conference has a status that is either upcoming, past or canceled.
      • A member should be able to attend a conference if the event is upcoming. If the conference is past, he/she should be able to attend it on the library system.
      • A conference should have a proper conference hall.
      • A conference should have at least 30 attendees.
      • The conference should present at least 5 publications.

      Scientific Papers Data Management System Free source code PHP

      - No comments
      Scientific Papers Data Management System Free source code PHP

      1. Project Description

      This project aims to design a database system for keeping track of scientific publications, authors, conferences, institutions, reviewers, editors and subscribers. There are different cases that explain the relationship between these entities and there are different constraints for entities and their relationships.

      As a general user, subscribers can view, search and filter publications. When they find the publication they are searching for, they can view some information about the publication such as the author, publishment date, download count and some other details. Each subscriber may subscribe to many journals. As they become a subscriber of a journal they can get notifications about the subscribed journal. Subscribers can belong to institutions.

      Authors must have a subscriber account to make a submission. Once they have their account and confirmed as an author, they can make publication submission to many journals and conferences. However, each submission can only be published in one conference or a journal.

      There is a chain of events during publishment of a submission. After the author/authors make their submissions to conference/journal, first the editor decides whether the submission is suitable for the applied publisher, if the editor finds it unsuitable he/she can reject the submission. If the editor finds it suitable, he/she invites one or more reviewer to peer review the submission for content examination.


      Reviewers can accept/deny invitations. Each reviewer must be an expert in the topic of the submission. Reviewers who accept invitations must give a feedback to the editor within the specified time period. According to the feedbacks, the editor may choose to reject the paper, send it for a revision/resubmission or approve the submission. If the editor chooses to send it for resubmission, an author must clarify the changes. If the editor chooses to approve the paper, he/she corrects the grammar, style of the paper and sends it to the author and asks for approval. When the author/authors approve the submission, the publisher publishes the paper at the specified publishment date. Some publications might co-operate with institutions which provide the necessary tools/labs etc.

      Publications may have sponsors which provide some research budget to the publication and its authors. Sponsors may have some threshold goals for the publications they sponsored. Some publications which have industrial application can have patents to protect their use of rights. The patent must have a patent id number, patent date, and a publication.

      For example, a publication can be written by many authors and can be submitted to many conferences. However, it can be published in a single conference or journal. After the submission, reviewers and editors decide if the submission will be published or not.

      Publications which are published in a conference must be presented by its authors and additionally, the editor or reviewer of the publication can also join the presentation. Conferences can have the audience which can be subscribers or other people who want to attend the conference.

      2. Project Requirements of Scientific Papers Data Management System Free source code PHP

      2.1. Functional Requirements

      2.1.1. Reviewer Requirements

      Reviewers should be able to
      • accept/decline peer review invitations from editors.
      • view the submission if they have accepted the peer review invitation.
      • approve or reject the submission by sending a report to the editor.

      2.1.2. Editor Requirements

      Editors should be able to
      • examine submissions.
      • reject submissions if the submission is unsuitable for the journal.
      • ask for the revision of the submission if the submission can be made suitable.
      • approve the requirements and ask for peer review from more than one reviewers if the submission is suitable for the journal.
      • approve/reject to publish the submission according to the peer reviewers’ report.
      • edit the submission for style (citations, references, tables, clarity, grammar etc.) before sending it to publication.
      • ask authors to approve the final submission.

      2.1.3. Author Requirements

      Authors should be able to
      • make new submissions to journals and conferences.
      • edit their submissions by specifying the changes.
      • cancel their submissions.
      • view the status of their submissions.
      • search for publications, institutions, journals, and conferences.
      • view details of publications, institutions, journals, and conferences.
      • approve/reject the finalized submission.
      • demand patent for their publications.

      2.1.4. Subscriber Requirements

      • Subscribers should be able to view publications.
      • Subscribers should be able to subscribe/unsubscribe journals and conferences.

      2.1.5. Sponsor Requirements

      Sponsors should be able to
      • make a sponsorship offer to publications.
      • set a sponsorship goal to the publications they sponsored for.
      • set a budget for the publications they sponsored for.

      2.1.6. Audience Requirements

      • Audience should be able to attend conferences.

      2.1.7. System Requirements

      • A system must keep track of how many publications a reviewer is currently working on.
      • System should remind reviewers as their feedback deadline gets close.

      2.1.8. Pseudo Requirements

      • MySQL is used for database management.
      • Front-end of the web application will use HTML, CSS, Javascript, Bootstrap, Ajax, and jQuery.
      • PHP will be used to develop back-end.

      2.2. Non-functional Requirements Scientific Papers Data Management System Free source code PHP

      2.2.1. User-Friendly Interface

      Our design will assure a simple way of surfing through the web application. As the domain of users is of science-related fields, yet not all of them are familiar with web technology. Hence, it will provide an easy-to-understand interface to perform all tasks: submitting publications, modifying, assigning, reviewing, searching, etc.

      2.2.2. Easy Maintenance

      The architecture of our application will follow a modular, layer approach. this approach makes it easier to debug errors and apply future changes.

      2.2.3. Reliability

      As our system will be used for scientific purposes, it cannot bear errors. The data provided by the application should be true and always consistent. Submissions are not made available to the public until all submission process is finalized. It is not possible to make changes to publications after they are published. Users should be able to access available papers at any time.

      2.2.4. Quick Response Time

      Quick response time depends on two factors: the time it takes to retrieve a paper related to a search query, and to the size of documents retrieved. For search, we will use algorithms to detect matching papers as fast as possible depending on the similarity of words. Pagination will be used to limit papers retrieved per page view. Pagination can also be applied to a single paper view if it is long. Multimedia that is part of the paper (photos & videos) should load fast, not affecting user experience.

      2.2.5. Security

      Non-subscribers should not be able to view the content of the application nor download it. Viewers cannot see the pre-publication process/history.

      3. Limitations Scientific Papers Data Management System Free source code PHP

      • An author cannot make a submission to a journal/conference which is not related to the journal/conference topic.
      • An author must include a revision note to its re-submission.
      • An editor cannot invite someone as a reviewer who is not an expert in submission topic.
      • Reviewers must give their reports within the specified time period.

      4. Conclusion Scientific Papers Data Management System Free source code PHP

      Scientific Papers Data Management System is a web-based application for managing and viewing scientific publications. Different subscription types such as author, editor, reviewer have different tasks and functionalities to perform. In this report, we tried to propose an overall system. We illustrate the system capabilities in the description of the project. We identified the use cases and functionalities of the system in functional requirements. Also express the non-functional, system and pseudo requirements clearly as possible to propose a well functioning system.

      To download Source Code and report, please contact us at

      Software Developer Recruiting System Free Project

      - No comments
      Software Developer Recruiting System Free Project

      1.    Introduction

      This proposal document consists of the requirements, limitations and the ER diagram for a Software Developer Recruiting System database design. The software developer recruiting system aims to provide a platform where companies can publish challenges in a desired topic and software developers can show their skills. While the system provides networking and an opportunity for software developers to prove themselves, it also provides reliable service to company owners before recruiting an employee.

      2.    Requirements

      2.1.  Users

      Users have:
      • User ID
      • E-mail
      • Password
      • Name
      • Surname

      There are two types of users: Company users and Software Developer users. Users are able to search for information about companies, questions, challenges, tracks and software developers. Users can make comments about questions and challenges and communicate with each other.

      2.2. Company Users

      Company users:
      • have Company Name
      • can open challenges for recruiting users.
      • have a profile in which the challenges are displayed. Company profiles also have a Q&A section which they can answer questions posted on their profiles.

      2.3.  Software Developer Users

      • Scores on tracks, challenges or questions can be displayed in developers profile.
      • A user can only solve a challenge once.
      • Developers’ skills related to computer science can be endorsed by another user.
      • Software Developer Users can post related questions on Company User profile, and Company Users can post answers to the questions.

      2.4. Challenges

      Challenges have
      • Challenge id
      • Deadline
      • Challenge
      Each challenge has a deadline indicated from the company user. The time spent on the challenge effects the score of the user. Submissions after the deadline will not be scored.

      2.5. Questions

      Questions have
      • Question id
      • Question text

      The time spent on a question affects the score of the user.

      Questions should be solved with at least one programming language indicated by the company users.

      2.6. Tracks

      Tracks have
      • Track id
      • Track name

      Tracks are the general domain areas which a user selects to specialize at.

      2.7. Topics

      Topics have
      • Topic id
      • Topic name

      Topics are the subdomains of a track.

      2.8.  Question and Answers

      Q&A posts have
      • Date
      • Text

      Developers can post on the Q&A section of a Company profile, Company users can answer on their profile’s Q&A section

      2.9.  Comment

      Comments have
      • Comment id
      • Comment text

      3.    Limitations of Software Developer Recruiting System Free Project

      • Company users can create many challenges.
      • A user can make many comments. 
      • A challenge cannot exist unless a company creates one. 
      • A challenge should have at least one question and each question is specific to a challenge.
      • Each question should be asked to implement with at least one programming language.
      • Each challenge is about one and only one Topic.
      • Tracks include multiple topics (subdomains) related to computer science. Each topic is specific to a track.
      • A question score is assigned after the question is answered.
      • A challenge score is the summation of all the question scores.
      • The time spent on solving the questions is kept in the database.
      • A Q&A cannot exist unless a user posts a question on the company profile.
      • Company users can have a question pool of their previous challenge questions or add their own customized questions.

      4.    ER Diagram

      To download Source Code and report, please contact us at

      Online Accommodation System Free Project Source Code in PHP

      - No comments
      Online Accommodation System Free Project Source Code in PHP


      This report will talk about our project proposal of an Online Accommodation System by firstly talking about why and how we will use a database, then describing the project, its limitations, and requirements and finally the ER diagrams will be given.

      In the next phases, we are planning on delivering a design report which includes the database, the software, and the user interface and the final report will be on our demo.

      Why/How do we use a database?

      This project aims to serve a platform that brings house owners and tenants together. This means that a huge amount of information needs to be stored and secured. We need to create a pool of information that will be used for this purpose and databases are the most proper way to accomplish this goal. Therefore, the design of the database system that we will implement is a vital issue.

      The database should contain the information about rentals, the owner of the house and guests. The interaction between those subjects should also be included in the database system.

      Description of Online Accommodation System Free Project Source Code in PHP

      An online accommodation system helps you find places to rent and stay from all around the world. In the accommodation system, there are users who search for a house/apartment to stay and users who also rent their houses/apartments. To discard confusion, we will call the users who find and rent the houses as guests and who owns the houses as hosts. Hosts can also be guests and they are able to edit and add/remove their houses to make deals.

      The system will provide a search mechanism for the users to find and reserve houses according to the location and the status of the house at a specified date. Furthermore, they can sort houses according to their ratings and view house photos. The guests can also ask questions to the host via message and add the house to the wishlist section for tracking information about the houses that customers want. There will be a different panel for hosts that enables to edit their houses’ attributes and keep track of the guests’ status.

      Hosts will be able to rent their entire houses or a private room in the house or a shared room. Hosts are meant to enter the information about the house and utilities that a house provides. Also, hosts will assign some due dates for guests to renounce their stay without paying money.


      The database system holds data such as houses’ facilities. Furthermore, users’ information which includes id and passwords will be stored. The messages between the users will be kept in the database. Since the database management systems are used to store information faster and more secure, we intend to implement a database management system to make an interaction between database and application. Different kinds of programming languages can be used to access and update databases like C#, Java and Microsoft SQL Server.


      Firstly, we differentiate the quest’s and the host’s abilities even though they are both treated as a user in the database. The customers need the ability to create, access, edit and delete their profiles, make, cancel and view reservations. Also can add a house to their wish list, send a message to the host and rate hosts and houses. We will offer hosts to rent someone else’s house with the same account. Therefore, the hosts have the same opportunities as the customers. Apart from these abilities, hosts should be able to add houses, cancel the reservation made to their houses. Also should be able to change the information about their houses. The hosts can also rate the customers in addition.

      Requirements of Online Accommodation System Free Project Source Code in PHP

      • The search and sorting must be efficient since searching is the base of an accommodation system.
      • The system needs to be both user-friendly and appealing to the user.
      • Since the system contains information about both customers and hosts there must not be any security issues.

      To download Source Code and report, please contact us at

      Social Discussion Website Free Source Code in PHP

      - No comments
      Social Discussion Website Free Source Code in PHP

       1. Introduction

      The following is a project proposal of a Social Discussion Website database system. The proposal will contain a short and brief description of the program that we will create, discuss functional and non-functional requirements along with the limitations of the database and it will give a detailed E/R model of the database schema we will use.

      The outline of the proposal starts with the project description which will try to give an insight on what our database system will be and how it will be used. Further on the requirements section will try to discuss in detail what the requirements for building this system will be and what will be the organization of the system based on these requirements. The non-functional requirements will focus on the discussion of the performance, usability, capacity, reliability and the security of the database. These will try to point out interaction with the database. This discussion will be followed by the Limitations that the organizational structure of the database will face based on the Entity-Relationship model that we have introduced.

      2. Description

      The database build-up that is going to be outlined in the following is a social discussion website similar to Reddit and vBulletin. This platform aims to connect the users in a shared environment for their subjects of interest. It will help people who want to learn something new on a particular subject or topic by letting them ask their questions on the system under the topic. There will be comments by the other users which will appear as an answer to the question or as a new information for the topic being discussed. The users will be able to follow other users that they like and report discussions which violate the terms of the discussion.


      An administrator of the website is someone who has the power to arrange the website and its categories. He will also be able to administrate the users by handling their problems and banning the users who don’t comply with the terms of use of the website.


      Categories will be associated with a category name which will appear as a heading containing many topics related to it. The number of such topics which are related to the category and the number of the subtopics is kept and stored. These categories can be created and modified by an administrator of the website.


      Topics consist of a topic name which will appear as a heading for the relevant topic. Each topic may be associated with many categories and they will contain subtopics. The topics can be created by the users of the database and they can be approved by the moderators of the database.


      Subtopics consist of the name, description and they will contain a number of comments. In order for the subtopic to exist firstly, the topic must be created. Similarly to topics, subtopics can be created by the users and approved by the moderators. They will contain a certain number of comments that users have on this subtopic.


      A comment is a piece of text, image, emoji or icons or any combination of these that the users will be able to create. In order for comments to be created a user must have created them. Comments are not only made to a subtopic but they can also be made to other comments that other users may have left on the topic. These are moderated and checked if they violate any of the website policies by the moderator and they can also be liked or reported by the users.

      Follow user

      A user can choose to follow other users based on their activities and the topics that these users are interested in. The user of the website can also have favorite comments that are made on the on a specific subtopic. He can either add more favorites or discard old favorites. They will be of two types Moderators and Regular users.


      Moderators are users who have the permissions to approve topics, subtopics and moderate the comments made on these.

      Regular user

      Regular user is one user of the website who can have a different status (Ex Active, Away, On Vacation etc).
      Favorites are comments which are embedded based on the preferences of a user. In order for favorites to be populated a user must have added his favorite comments.

      3. Requirements

      3.1. Functional Requirements

      Functional requirements of Social Discussion Website free source code in php are,

      3.1.1. Regular Users

      • are able to rearrange their profile info.
      • can search through topics and subtopics.
      • can follow each other.
      • are able to like or report comments.
      • can make comments on subtopics and others’ comments.
      • are able to save comments as a favourite.
      • are able to discard comments from their favorite.
      • can change their status from online to offline, away, busy etc.

      3.1.2. Moderators

      Moderators are able to
      • moderate comments.
      • approve topics and subtopics.
      • delete reported or inappropriate comments.

      3.1.3. Admins

      Admins are able to
      • modify categories.
      • administrate users.
      • assign moderators.
      • ban or suspend moderators by looking at their last login dates.

      3.2. Non-Functional Requirements

      3.2.1. Performance

      A system should have a response time of average 5 seconds to have a consistent user experience.

      3.2.2. Usability

      • System and user interface should be easy to understand and use.
      • Users should be able to use all functions with ease.
      • Users should be able to access the main page from any page.
      • All pages should refer to a default theme and layout.
      • An additional tutorial or help page should be available for users in need of help or guidance.

      3.2.3. Capacity

      • The database should be able to consist of large amounts of data.
      • High numbers of Users, Categories, Topics, Subtopics, Comments, and Comments of Comments should be able to be kept in the database.

      3.2.4. Reliability

      • System service should be up and online 24/7 and 365 days except for scheduled maintenance.
      • The system should be able to perform the given tasks without fail.
      • If a task fails situation should be logged and recovery should be performed as fast as possible without keeping the user waiting.

      3.2.5. Security

      • A system should provide user authentication and data privacy.
      • For authentication procedure system will use unique user id and password per user.

      3.3. Constraints (Pseudo Requirements)

      • MySQL will be used as the Structured Query Language.
      • PHP and javascript will be used for frontend and backend development.
      • Ajax will be used as the connection between database and javascript to get and modify data from the system.

      4. Limitations

      • Moderators can only moderate or approve comments subtopics and topics that he or she was assigned. e.g. Moderator who approves Dog Topic cannot approve a comment in Science Topic/Subtopic.
      • When a user account is banned or suspended he or she cannot log in to the system during his/her ban/suspend time.
      • When user’s account is terminated/deleted her or her account info, all of his or her comments, likes, topics, subtopics will be deleted.
      • Users cannot report the same comment again in predefined time interval e.g. the user cannot report a comment two day in a row.
      • A user can only add 1000 comments to their favorite.
      • Comment can include up to 4 images/gifs.
      • Comment can only be up to 5000 characters.
      • A user can add images to comments which are smaller than 1920 x 1080 as resolution and 5 MB as size.
      • Moderator cannot create or modify categories.

      5. Conclusion

      This project is a social discussion website which is inspired by sites like vBulletin, Reddit, and Quora. In this website, people can interactively discuss a particular topic for which they feel interested in and share their opinions and knowledge with other users as well. The system that we intend to build tries to capture the specifications and the relations between the users, administrators, the categories, topics, subtopics and the comments given in a hierarchical manner.

      This proposal tries to explain the implementation of the system as a whole, how each part is used and why it is considered as a separate part and not as an embedded attribute. This is going to be important for the later implementation of the system since this report gives the conceptual design and takes into consideration the difficulties that we might face when implementing it. All the non-functional requirements and limitations presented above contribute to the later implementation of the system as well. Any further development of our project will be given in our web link.

      To download Source Code and report, please contact us at

      Social Network for Check-In PHP source code for free

      - No comments

      Social Network for Check-In PHP source code for free for BE, BTech, MCA, BCA, Diploma and MSc

      Social Network for Check-In PHP source code for free

      1. Introduction

      In modern days social networks like Facebook, Instagram, Snapchat have become a very common part of our everyday life and are widely used throughout the world, some counting more than 500 million users of different ages. 35% of adult internet users now have a profile on an online social network site whereas, for teenagers, the numbers jump to 65%. There is a large variety of the purpose these social networks serve, but despite their differences, they are similar in one main aspect. All of them have a vital need for a database management system which will deal with the continuous growth in size and complexity. Since the number of users, new features, and general complexity of every social media application changes rapidly, the design of the database should be able to efficiently store and support the data.

      For this course, we are going to develop a database for a “Social Network for Check-ins”. As the name suggests our social network will be mainly focused on finding interesting venues and areas inside a certain range of the user’s current location and “checking in” in each of them. The locations will be categorized and the user will easily find what he is looking for and will have the opportunity to rate and recommend each location. Together with this, each user will have his own profile in which he can store different information regarding his preferred locations and being in a social network he will be able to communicate and share them with his friends.

      2. Problem Definition

      The main issue of our system is that there will be lots of venues and users with many attributes each. The old check-ins, comments, messages, likes, and suggestions of each user need to be stored together with the user information and preferences so that they can be displayed again. This means that we have to store everything in our database from the simple birth date of the user up to his/her first check-in.

      Another reason why we need the database system is a large number of friends a user can have and the messages with them. Since the user can only follow another user, friends will be called only the users who follow each-other respectively. The database system will also be responsible for the storage and organization of the information regarding the venues and its subcategories. Due to this organization of the database the user will be able to access information more efficiently. These problems that arise during the design of an application can only be handled if it has the support of a very well organized database management system.

      3. Project Description

      The basic and fundamental idea of the system is to socialize people with each other and discover many interesting places easily. The system will be accessed by 2 different types of users: simple users and managers. Simple users will be able to create their accounts, to search for different venues and places, check-in, rate the locations, recommend them and update their profile. Being a social network they will also be able to communicate and connect with their friends. Managers will be able to update information regarding the venue they are managing such as hotel, restaurant etc, with photos and different information. However, they will not be able to remove the comments made by users, in order to guarantee transparency.

      Users will be able to search different locations which will be organized into categories and subcategories in order to facilitate the searching process. Beside via categories and subcategories, users can search based on different features such as parking facilities, credit card acceptance etc. Due to this organization, the searching process will be very efficient and users will be able to find everything they need within seconds.

      Being a social network, users will be able to complete their profile and add preferences to it which will enable him to see in his news feed information related to his preferences. He will also be able to connect and send messages with other people sharing his experience and also make a different list of locations he has already visited or that he wishes to do so. The application will also be very user-friendly so that the users familiarize themselves much easier to the system and that they start using it more often.

      4. Requirements

      The system has 3 Operational Roles: User, Manager, and Administrator. Each of them will have different UI and their personalized options related to the permission allowed to them.

      4.1 Functional Requirements

      • Users can sign up and create their own accounts by using their email.
      • Users will be divided into three categories with different privileges (administrator, manager and simple user).
      • have their unique profiles with their personal information and preferences.
      • Users login into an application using their unique email and password.
      • Venues have their unique profiles.
      • Venue’s accounts will be under manager’s control.
      • Users can follow each other.
      • Users can check-in in different venues.
      • can review the venues and affect their overall rating by liking or disliking them.
      • Users can send suggestions to the Venues.
      • Users can send messages to their friends.
      • can like and comment on the check-ins and reviews of the people whose profile is public or of their friends.
      • Users can view the ratings and reviews of the venues.
      • Users can create a list of venues that they are planning to check-in.
      • have their own preferences and favorite venues (Newsfeed will be sent to them according to them).
      • Users can search based on categories or subcategories.
      • Users can search for a particular venue.
      • can search based on some preferred features.
      • Users can search for venues in a particular city, state, and country.
      • Users can update the information of their profiles.
      • will have a list of all their check-ins in their profile.
      • Users can recommend a particular venue to a friend.
      • Admins can edit and check the whole information of the application.

      4.2 Non - Functional Requirements

      • The system will be scalable and won’t be affected by a number of users working simultaneously.
      • The user interface of the application will be user-friendly.
      • The website will be responsive for mobile devices.
      • Confidentiality is another thing that system will deal by protecting sensitive data and allowing only authorized access to the data.
      • The system will be maintainable and easy to find and fix faults.
      • The system will be easily modified and expand its processing capabilities to support system growth.

      4.3 Pseudo Requirements

      • MySQL will be used for the database.
      • Javascript, HTML5, and CSS3 will be used to create the frontend side.
      • node.js will be used to create a server which would handle database and frontend communication.

      5. Entity Relationship (ER) Diagram

      6. Limitations

      •  Each kind of user has its own specific characteristics regarding access on the application.
      • Users can edit only their own information; not the information of any other user.
      • Managers can edit only the information of the Venues that they manage; not the information of the users or other venues.
      • Check-ins of public accounts are shown to everyone, while check-in of private account is shown only to the friends.
      • Users can have only one unique profile.

      To download Source Code and report, please contact us at

      - No comments

      Car Sharing System in PHP Free Source Code For BE, BTech, BCA, MCA, Diploma and MSc Students

      1. Project Description

      Car Sharing System is an application where people going in the same direction to share their cars. The aim of this system is to bring people together on the same platform and provide safe, cheap and effective ways to share cars. With this system, drivers can create a trip saying which location they are going to go at a specific time and through which route they are going to do so. The passengers can enter a location and see all the relevant trips destined to that location. Passengers need to make a reservation for a trip to participate in that trip. The driver has the option to accept or decline the passenger.

      After a trip is done, the passengers can rate the drivers and other passengers and the driver can rate their passengers. Both can also write reviews about them anonymously. The payments are done beforehand and can be refunded if the driver does not show up or the passenger cannot attend due to some reasons. The system has a customer service which helps the customers to solve their problems with the trips and the refunds. The information of the customers are protected.

      People can only see the reviews and rates of each other before making a reservation. After the reservation is done and the passenger is accepted by the driver, their contact information becomes available to each other. There are multiple locations a passenger can get in or get out and will be charged accordingly. The driver can set up mid stops on the route and charge those stops differently. Also, the driver is responsible for estimating the trip’s time and will set up a price for the trip according to the estimated time and trip length.

      2. Why/How a Database is going to be used

      The aim of this project is to provide a database application for the Car Sharing System to make data management easy. As this is a complicated system, a well designed database is needed. There are many passengers, drivers, ratings, reviews, trips, vehicles, locations, routes, time and cost information to manage, therefore an automated database system is needed for this Car Sharing System. This database application is going to handle query operations, data entries, and updates.

      3 Requirements

      3.1 Functional Requirements

      3.1.1 User

      Users should be able to
      • modify their personal information
      • register their car and become a driver.
      • search for trips with specific start and end location.
      • search for trips within the specific time frame.
      • make a reservation to a available seat in a posted trip.
      • cancel their reservation.
      • see driver’s personal information such as phone number after their registration is approved by the driver.
      • rate drivers and other passengers if they have been in a same trip.
      • see driver’s rating before making a reservation to the trip.
      • see trip information such as car information, stop locations, other passengers.

      3.1.2 Driver

      Drivers should be able to
      • modify the information of their car.
      • post a trip with specific start and end location and start and end time.
      • determine the price for their trip
      • see reservation requests for their trip and approve or cancel the reservations.
      • see passengers’ personal information such as phone number after approving their registration.
      • rate the passengers if they have been in a same trip.
      • see passengers’ ratings if they have made a reservation request.

      3.1.3 Customer Service

      Customer service should be able to
      • see drivers car information.
      • user’s personal information
      • search for trips with specific start and end location.
      • search for trips with a specific time frame.
      • see a trip’s information

      3.1.4 System Requirements

      System should be able to
      • block reservations after the capacity of a trip is full.
      • block reservations 1 hour before the starting time of a trip.
      • verify user's email.
      • limit the unverified users’ functionality with the only search for trips.

      3.2 Non Functional Requirements

      3.2.1 Quick Response Time & Scalability

      • The system should be able to fast and scale able. Since there will be searches and posting new data, the system should be able to handle searches and database modifications as fast as possible.

      3.2.2 User Friendliness

      • The system should provide a easy-to-use interface.
      • The system should guide new users and show the features of the system.

      3.3 Pseudo Requirements

      • MySQL is used for the database.
      • PHP will be used for the backend.
      • HTML ,CSS, JavaScript will be used for web page.

      4.0 Limitations

      • People can search for trips but they need to login to their user account in order to reserve a trip or host one.
      • Only the users with a validated car, a car that is registered on their name, can host a trip. This information will be collected from the traffic database.
      • A driver needs to accept a passenger’s reservation in order to confirm the reservation.
      • A driver needs to specify where he is going and where he is willing to stop (to pick up people) when creating a new trip.
      • When a vehicle’s capacity is filled users cannot reserve a place for that trip.
      • Drivers can only write reviews about passengers they drove, Passenger can write a review about the driver and the passengers they took a trip with.
      • Users will have different reviews for their driver and passenger behaviours.
      • When a user is deleted his/her vehicle will also be deleted.

      To download Source Code and report, please contact us at