GUJARAT TECHNOLOGICAL UNIVERSITY Chandkheda, Ahmedabad Affiliated GYANMANJARI INSTITUTE OF TECHNOLOGY BHAVNAGAR A Project report On Online Virtual Exhibition Platform Under Subject Of PROJECT B.E, Semester – VIII (Information Technology Branch) Submitted By Team Id: 93452 Sr.No. Name of Student Enrolment No. 1. 2. Bhayani Parth Bhungaliya Nirav 171290116007 171290116008 3. 4. Godhani Kaushik Vaghasiya Aniket 171290116020 171290116052 Prof. Dhaval R Chandarana (Faculty Guide) Prof. Chirag S Bhalodia (Head of Department) Academic Year 2020-2021 I GYANMANJARI INSTITUTE OF TECHNOLOGY BHAVNAGAR DEPARTMENT OF I.T. ENGINEERING CERTIFICATE This is to certify that the basic process and framework has been satisfactorily carried out by 1. Bhayani Parth 171290116007 Under my guidance in the fulfillment of the course PROJECT during the academic year 2020-2021. Date of submission: Faculty In-Charge Internal Examiner External Examiner II GYANMANJARI INSTITUTE OF TECHNOLOGY BHAVNAGAR DEPARTMENT OF I.T. ENGINEERING CERTIFICATE This is to certify that the basic process and framework has been satisfactorily carried out by 2. Bhungaliya Nirav 171290116008 Under my guidance in the fulfillment of the course PROJECT during the academic year 2020-2021. Date of submission: Faculty In-Charge Internal Examiner External Examiner III GYANMANJARI INSTITUTE OF TECHNOLOGY BHAVNAGAR DEPARTMENT OF I.T. ENGINEERING CERTIFICATE This is to certify that the basic process and framework has been satisfactorily carried out by 3. Godhani Kaushik 171290116020 Under my guidance in the fulfillment of the course PROJECT during the academic year 2020-2021. Date of submission: Faculty In-Charge Internal Examiner External Examiner IV GYANMANJARI INSTITUTE OF TECHNOLOGY BHAVNAGAR DEPARTMENT OF I.T. ENGINEERING CERTIFICATE This is to certify that the basic process and framework has been satisfactorily carried out by 4. Vaghasiya Aniket 171290116052 Under my guidance in the fulfillment of the course PROJECT during the academic year 2020-2021. Date of submission: Faculty In-Charge Internal Examiner External Examiner V Student Information Name Of Student: Enrollment NO.: Contact No.: Email Id: College Name/Code: Branch/Sem.: BHAYANI PARTH 171290116007 +91 7698760332 parthbhayani2000@gmail.com Gyanmanjari Institute of Technology [129] Information Technology / 8th Name Team Members: Er. No. Nirav Bhungaliya 171290116008 Kaushik Godhani 171290116020 Aniket Vaghasiya 171290116052 Student’s sign: VI Name Of Student: Enrollment NO.: Contact No.: Email Id: College Name/Code: Branch/Sem.: BHUNGALIYA NIRAV 171290116008 +91 90331057387 niravbhungaliya2000@gmail.com Gyanmanjari Institute of Technology [129] Information Technology / 8th Name Team Members: Er. No. Parth Bhayani 171290116007 Kaushik Godhani 171290116020 Aniket Vaghasiya 171290116052 Student’s sign: VII Name Of Student: Enrollment NO.: Contact No.: Email Id: College Name/Code: Branch/Sem.: GODHANI KAUSHIK 171290116020 +91 9427748208 kaushikgodhani2218@gmail.com Gyanmanjari Institute of Technology [129] Information Technology / 8th Name Team Members: Er. No. Nirav Bhungaliya 171290116008 Parth Bhayani 171290116007 Aniket Vaghasiya 171290116052 Student’s sign: VIII Name Of Student: Enrollment NO.: Contact No.: Email Id: College Name/Code: Branch/Sem.: VAGHASIYA ANIKET 171290116052 +91 7817812518 aniket.vaghasiya.007@gmail.com Gyanmanjari Institute of Technology [129] Information Technology / 8th Name Team Members: Er. No. Nirav Bhungaliya 171290116008 Kaushik Godhani 171290116020 Parth Bhayani 171290116007 Student’s sign: IX Acknowledgement I have taken efforts in this project. However, it would not have been possible without the kind of support and help of many individuals and organizations. I would like to extend my sincere thanks to all of them. I am highly indebted to Prof. Dhaval R Chandarana and Prof. Chirag S Bhalodia for their guidance and constant supervision as well as for providing necessary information regarding the project & also for their support in completing the project. I would like to express my special gratitude and thanks to faculties for giving me such attention and time. My thanks and appreciations also go to my colleague in developing the project and people who have willingly helped me out with their abilities. Every project big or small is successful largely due to the effort of a number of wonderful people who have always given their valuable advice or lent a helping hand. I sincerely appreciate the inspiration; support and guidance of all those people who have been instrumental in making this project a success. I would also like to thank all the faculty members of I.T. department for their critical advice and guidance without which this project would not have been possible. Last but not the least I place a deep sense of gratitude to my family members and my friends who have been a constant source of inspiration during the preparation of this project work. Thank you. X Abstract The invention relates to Online Virtual Exhibition Platform which provides a huge interactive platform to clients and to event organizers as well. In the current scenario there are too many problems we face in every exhibition we wanted to attend. This platform enables organizers to organize the event virtually which can reduce the time to organize the event and also be cost effective. This platform will provide a client or user module.This module is highly interactive for users.where they can virtually feel to attend the live events or exhibition of trade expo. The other module is the Organizer module which has the ability to manage the event and the products will be exhibited in this exhibition. They can manage different types of business types like B2B, B2C etc. There is one more module named sub-admin module in this platform which handles event organizers and clients. XI INDEX Sr. No. 1 2 3 Content Name Introduction 1 1.1 Project Summary 1.2 Project details 1.3 Project Specification 1.4 Literature Review 1.5 Technology 2 2 2 3 3 Project Management 5 2.1 Feasibility Study 2.1.1 Technical Feasibility 2.1.2 Time Schedule Feasibility 2.1.3 Operational Feasibility 2.1.4 Implementation Feasibility 2.2 Project Planning 2.2.1 Project Development Approach and Justification 2.2.2 Milestone & Deliverables 2.2.3 Roles & Responsibilities 2.2.4 Group Dependencies 2.3 Project Scheduling 2.4 Risk Management 2.4.1 Risk Identification 2.4.2 Risk Analysis 2.4.3 Risk Planning 6 6 7 7 7 7 7 9 9 10 10 10 10 11 11 System Requirement Study 12 13 13 13 13 14 14 14 14 14 14 14 14 15 3.1 Study of Current System 3.2 Problems and Weakness of Current System 3.3 User Characteristics 3.4 Hardware and Software Requirements 3.5 Constraints 3.5.1 User Interface 3.5.2 Communications Interface 3.5.3 Hardware Interface 3.5.4 Criticality of the application 3.5.5 Safety and Security Consideration 3.6 Assumption and Dependencies 3.6.1 Assumptions 3.6.2 Dependencies 4 Page No. Requirements of Proposed System 4.1 Main Module of the System 4.2 Module Descriptions 16 17 17 5 6 7 8 9 10 System Design 18 5.1 Architecture Design 5.1.1 E-R Diagram 5.1.2 Use Case Diagram 5.1.3 Class Diagram 5.1.4 Activity Diagram 5.1.5 DFD Diagram 5.2 Data Dictionary 19 19 20 21 22 23 24 Snapshots 6.1 Exhibitor-Admin View 6.2 WebAdmin View 6.3 Sub-Admin View 6.4 Company-Admin View 6.5 Event Organizer-Admin View 6.6 Client View 6.7 Other Functionality 35 36 38 41 44 46 48 58 Implementation 59 7.1 Implementation Environment 7.2 Program Specification 7.3 Security Features 7.4 Coding Standard 60 60 60 60 Testing 8.1 Testing Plan 8.1.1 Design Testing 8.1.2 Implementation Testing 8.1.3 Product Testing 8.2 Testing Strategy 8.3 Testing Methods 8.3.1 Unit Testing 8.3.2 Integration Testing 8.3.3 Validation Testing 8.3.4 Storage Testing 8.4 Test Cases 62 63 63 63 63 64 65 65 65 65 65 66 Limitation And Future Enhancement 69 9.1 Limitation 9.2 Future Enhancement 70 70 Conclusion And Discussion 71 72 72 72 73 73 74 10.1 Project Liabilities 10.2 Problem Encountered And Possible Solution 10.3 Summary Of Project Work 10.4 References 10.5 Work Experience 10.6 Appendix LIST OF FIGURES Figure No. Figure Name Page No. 1 Iterative Waterfall Model 8 2 E-R Diagram 19 3 Use Case Diagram 20 4 Class Diagram 21 5 Activity Diagram 22 5.1 User’s AD* 22 5.2 Web Admin AD* 23 5.3 Exhibitor Admin AD* 24 5.4 Company Admin AD* 25 5.5 Event-Organizer Admin AD* 26 6 DFD Diagram 27 7 Data Dictionary 28 8 Snapshots 35 6.1 Exhibitor view 36 6.2 Web Admin view 38 6.3 Sub Admin view 41 6.4 Company Admin View 44 6.5 Event organizer Admin view 46 6.6 Client’s view 48 6.7 Other Functionality 58 AD* : Activity Diagram LIST OF TABLES Table No. Table Name Page No. 1 Schedule 10 2 TCT* Login 66 3 TCT* Dashboard 66 4 TCT* Registration 67 5 TCT* Length Validation 67 6 TCT* OTP Validation 68 7 TCT* Email Validation 68 TCT* : Test Case Table CHAPTER 1 INTRODUCTION 1.1 Project Summary 1.2 Project details 1.3 Project Specification 1.4 Literature Review 1.5 Technology 1 Chapter 1: Introduction 1.1 Project Summary: The project provides a kind of network virtual exhibition method and system, its fundamental purpose is to overcome traditional exhibition waste of manpower, material resources, financial resources and the shortcoming of time, the present invention also aims to overcome the virtual exposition that has the web page browsing formula now web page browsing and reservation Web conference only are provided, and can't realize carrying out between the exhibitor staff shortcoming of real-time interactive. 1.2 Project Details: In this project we build platform where exhibitor can represent their item and user access from anywhere so, not necessarily in suitable place, the suitable time just in time has and the exhibition of this specific products, thereby must drop into certain energy and go to note the exhibition held all over the world about various products, notice that it holds time and host place, to arrange own exhibition stroke rightly, may miss many good business opportunities like this. The present project adopts following technical scheme: A kind of network virtual exhibition method may further comprise the steps: 1) user interface of a virtual exposition is provided in client, is used for and user interactions, the real-time information of the virtual exposition that reciprocal process is produced is sent to the server.[client-server-exhibitor connection] 2) server receives the real-time information from the virtual exposition of client, and the configuration information that is translated into virtual exposition is stored in the database, according to the configuration information of the virtual exposition in the database, sends the graphic file display order to client.[exhibitor pre-set all data, graphics to the server] 3) The client is according to the graphical display order that the server sends, and the graphic file that calls the virtual exposition in the library shows.[user access data, graphics from server] 1.3 Project Specification: The present project relates to be specially for exhibition, in this project we build web applications for exhibitors and for users they can access remotely. 2 1.4 Literature Review and Prior Art Search: Literature Name: Virtual exposition system Abstract: A virtual exposition system is provided in which Web pages of a virtual exposition are transmitted from a WWW server to a user's PC terminal connected with the Internet so that particular merchandise information can be easily collected from the displayed Web pages. The exhibition data from the exhibitors are edited in the same format. The industrial fields are classified into a plurality of categories. Description: Web page of a virtual space exhibition from a WWW server to a personal computer terminal of a user connected to the Internet, and easily collects specific product information from the display screen. About the system to do. Background art A conventional case of collecting information on a specific product will be described below. Here, when collecting information on the characteristics and prices of studless tires of each brand and company with a specific product as a studless tire, in the past, a specialized exhibition on studless tires was first searched. Exhibitions with limited products such as J are rarely held. Conclusion: Make a website for the virtual exhibition which is more suitable for global users an d for organization also that the prior exhibition wastes mass manpower, material resource, financial resource and time in order that exhibitors can exchange and communicate in real time and the users can fully see a real-time exhibition in the client. References: ● ● https://patents.google.com/patent/WO2001040994A1/en https://www.on24.com/ 1.5 Technology: 1 Platform : PHP 7.2.0 2 Client OS : Windows 10, Mac-Os, Android 4 Client Authoring : XHTML, JavaScript,CSS 5 Code Behind : Java script, PHP, HTML, Ajax, MySql 3 6 Web Server : Xampp Server 7 Version & Source Control : GitHub 8 Back-End Tools : MySql Server 5.7.21 9 A&D/UML : Ms office world, Wowslider Using above mentioned tools we make a web-application for the virtual exhibition which is more suitable for global users and for organization also. 4 CHAPTER 2 Project Management 2.1 Feasibility Study 2.2 Project Planning 2.3 Project Scheduling 2.4 Risk Management 5 Chapter 2: Project Management 2.1 Feasibility Study • Feasibility studies aimed to objectively uncover the strengths and Weaknesses of an existing tracking applications, opportunities and threats present in the resources required to carry through, and ultimately the prospects for success. • A feasibility study evaluates the project's potential for success; therefore, perceived objectivity is an important factor in the credibility of the study. 2.1.1 Technical Feasibility • At this level, the concern is whether the proposal is technically feasible. • The technical feasibility assessment is being focused on gaining an understanding of the present technical resources, and their applicability to the expected needs of the proposed system. It is an evaluation process of the hardware and software and how it meets the need of the proposed system. Front-end selection: • It must have a graphical user touch interface. • Flexibility • Front end must support some popular back-end like PHP, MySql According to above stated features we selected Web as our front end for developing the project. Back-end selection • Multiple user support • Efficiency in data handling • Efficient data retrieval and data store procedure. • Easy to implement with Front-end. • OS compatible According to above stated functions we selected Php, MySql as our backend for developing the web-application.According to above stated selections and statements, this project is Technically Feasible. 6 2.1.2 Time Schedule Feasibility • Time schedule feasibility is a measure of how reasonable the project development time period is. A project will fail if it takes too long to complete. It is necessary to determine whether the deadlines are desirable. • Time schedule feasibility makes sure that a project can complete before the project or technology becomes obsolete or unnecessary. Our project can easily develop within 7 to 8 months using 4 manpower. So, we can say that this project is Feasible to schedule. 2.1.3 Operational Feasibility • The Operational Feasibility is the measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development. • Our app will cover almost all features and it will satisfy requirements identified in the analysis phase. So, we can say that our project is operationally feasible. 2.1.4 Implementation Feasibility • There is no any ambiguity in project planning, and our requirements are very well-defined and stable. So, we can say that our project is feasible to implement. 2.2 Project planning Project planning is a part of project management. Every new project requires understanding of the science behind the project, the techniques involved and the elements to be handled to give the end result. Hence, the initial period was spent in surfing a number of sites. We need to do domain study for better understanding of the project and preparing project synopsis. 2.2.1 Project development approach and justification • To solve real problems in an industry setting, a software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods and tools layers and generic phases. This strategy is often called a process model or a software engineering model or project development approach. 7 • A process model for software engineering is chosen based on the nature of the project and application, the methods and tools to be used, and the controls and deliverables that are required. • Our project is based on the iterative waterfall model. This software development approach is described as below. ITERATIVE WATERFALL MODEL [Figure 1: Iterative Waterfall Model] Explanation: • Iterative waterfall model is by far the most widely used model. • The principle of detecting errors as close to its point of introduction as possible is known as phase containment of errors. • Phase containment of errors can be achieved by reviewing after every milestone. • The iterative waterfall model provides a feedback path from every phase of model to its preceding phases. • When errors occur at a later phase, with the help of a feedback path one can correct errors committed by programmers during any phase. • Feedback paths allow programmers to rewrite or change the code of some phase, and they are reflected at later phase.How it is suitable for our system? • As this project’s Requirement is well specified and clear so it is suitable for it. • It gives the feedback path to earlier phases, it makes our task easy, if any error occurs. • It divides complex tasks to smaller subtasks so it is suitable for it. 8 • As this model is simple and easy to understand and use so it is easy to follow and implement in this project. 2.2.2 Milestone and Deliverables • Milestones are checkpoints throughout the life of the project. The project team defines the milestones during project planning in order to identify the appropriate project activities to be accomplished; and to set planned targets. Milestones can indicate the completion of key project tasks, the commencement or conclusion of the plan. • A deliverable is a measurable and verifiable outcome or object that a project team must create and deliver according to the terms of an agreement. • First Milestone: Analysis of the application and the technology which we are using. Industry definition problems will be submitted to the college and to the university. • Second Milestone: In this milestone we have done the technology analysis and we will fixed the software designing approach and which model will be used and what are the basic functionality will be required for the development and analysis. • Third Milestone: In this milestone till decided the project approach and designing (Comparatively) and modules will be there. Which module will be handling by who can decided in this module. And finally, the database designing will be done in this milestone. • Fourth Milestone: In this milestone the database designing is ready so that the time estimation for coding and developing the modules can be calculated here. • Fifth Milestone: In this milestone the coding will be done. • Sixth Milestone: The testing of the application will be done here. 2.2.3 Roles & Responsibilities • Roles - generally, roles are the positions team members assume or the parts that they play in a project. • Responsibilities - responsibilities are the specific tasks or duties that members are expected to complete as a function of their roles. They are the specific activities or obligations for which they are held accountable when they assume, or are assigned to a role on a project or team. • During these all stages the guidance will be provided by our internal guide Prof. Dhaval R Chandara. 9 2.2.4 Group Dependencies • There will not be any kind of group dependency in this project. • All the developers and designers can work as they want. • It means the work will be done in a sequential manner but there is no dependency between users. 2.3 Project Scheduling Task Expected Days Analysis 30 days Design 25 days Coding 180 days Testing 25 days [Table 2.1: schedule] 2.4 Risk Management • Project risk management is the process of identifying, analyzing and then responding to any risk that arises over the life cycle of a project to help the project remain on track and meet its goal. • Managing risk isn’t reactive only, it should be part of the planning process to figure out risk that might happen in the project and how to control that risk if it in fact occurs. • A risk is anything that could potentially impact your project’s timeline, performance or budget. Risks are potentialities, and in a project management context, if they become realities, they then become classified as “issues” that must be addressed. • So, risk management is the process of identifying, categorizing, prioritizing and planning for risks before they become issues. 2.4.1 Risk Identification • Risk Identification determines which risks might affect the project and documents their characteristics. 10 • The objective of risk identification is the early and continuous identification of events that, if they occur, will have negative impacts on the project's ability to achieve performance or capability outcome goals. They may come from within the project or from external sources. • We can identify risks by reviewing previous documents, and by observing similar projects. 2.4.2 Risk Analysis • It is the action of reviewing the risks associated with a particular event or action. • It maps the risk, and makes an estimate of impact of the risk on the project. • It has two approaches: first qualitative and second quantitative. • Qualitative Approach: it is a technique in which probability of risk is discovered based on the occurrence of risk events and the impact of the risk, if it occurs. • Quantitative Approach: it is a technique in which impact of the risk is converted into numerical forms, and these numerical data is frequently used to estimate the cost and time contingencies of the project. 2.4.3 Risk Planning • It includes strategies and plans to compete with the risk, and manage its impact on the project. • We can handle risk by four ways: avoid, Mitigate, Transfer, and Accept. • At the time of risk occurrence, it’s worthless to do something about it. That’s why one has to plan for risk management from early stages of the project management and keep continuing this task during the whole project development process. 11 CHAPTER 3 System Requirement Study 3.1 Study of Current System 3.2 Problems and Weakness of Current System 3.3 User Characteristics 3.4 Hardware and Software Requirements 3.5 Constraints 3.6 Assumption and Dependencies 12 Chapter 3: System Requirement Study 3.1 Study of Current System We studied the current system and other related systems to this project, in conclusion we were aware about the knowledge of what are the things in the system and how one can process it for development. Future more we found some problems, rather changes to be done in the current system. We have better understood that functionalities can be added or modified in current systems for providing efficiency in usage of current systems. 3.2 Problems and Weakness of Current System • Manual work. • Managing large data. • Managing large entries of users. 3.3 User Characteristics Analyzing user characteristics is an important aspect of any project. It allows us to clearly define and focus on who the end users are for the project. Also, it allows us to check the progress of the project to ensure that we are still developing the system for the end users. Mainly two type of user comes into picture: 1. Users 2. Organizations In this application the users are users and organization. Users log into to find their product expo where organizations use to show their product to global users and other organizations. 3.4 Hardware and Software Requirements • Hardware Requirement o Development Side: Minimum required, Pentium IV processor (2 GHZ or higher is recommended), RAM with minimum 512 Mb, Disk space: 1 GB, Mouse and keyboard are needed as input and a monitor. o Deployment Side: Most compatible Domain which is provided us at least 1gb virtual storage and also give support of MySQL v.5.7 And php v.7.2 13 • Software Requirement o Development side: Php v.7.2, Windows, MacOs, Mysql o Deployment side: Domain 3.5 Constraints 3.5.1 User Interface We are providing interactive UI to both users. 3.5.2 Communication Interface An Organization gives notification of their product via mail to remind them to join the event. 3.5.3 Hardware Interface The current constraints on the project are related to the provision of hardware resources to implement and test a high-performance cluster, smart android device or computer required for running web applications with hardware & software specification. 3.5.4 Criticality of the project Not works with slow internet connection, requires hardware to support software application with above given specifications. 3.5.5 Safety and Security Consideration Access of the system is strictly restricted by the username and password that has been provided uniquely to the user of an application. Unauthorised users cannot see the expo event of any other products. 3.6 Assumptions & Dependencies 3.6.1 Assumptions • A user of an application may have knowledge of operating any supported device. 14 • We are assuming users may have basic knowledge of web applications. 3.6.2 Dependencies • Device dependency • Operating system dependencies • Internet availability 15 CHAPTER 4 Requirements of Proposed System 4.1 Main Module of the System 4.2 Module Descriptions 16 Chapter 4: Requirement of Proposed System 4.1 Main Module of the System Our vision is to provide the best and reliable system where users can attend any exhibition of any product from anywhere and other hand any organization or individual can represent their product to their global user with minimum human power, money and reach upto globe. As of our project plan we divide into main four module: 1. User interface 2. Exhibitor 3. Admin 4. Sub-Admin 4.2 Module Description ● Exhibitor connect with Admin: When exhibitors decide to exhibit their product or prototype to their users, they connect to our site main admin and get permission to exhibit. ● Exhibition process: Exhibition handled by exhibitors and with Sub-admin support and real time representation also exhibitors share invitations with their users. ● User interface: The user interface of a virtual exposition is provided in client, is used for and user interactions, the real-time information of the virtual exposition that reciprocal process is produced is sent to server. 17 CHAPTER 5 System Design 5.1 Architecture Design 5.2 Data Dictionary 18 Chapter 5: System Design 5.1 System Architecture Design 5.1.1 E-R Diagram [Figure 2:E-R Diagram] 19 5.1.2 Use Case Diagram [Figure 3: Use Case Diagram] 20 5.1.3 Class Diagram [Figure 4: Class Diagram] 21 5.1.4 Activity Diagram [Figure 5.1: User’s Activity Diagram] 22 [Figure 5.2: Web Admin Activity Diagram] 23 [Figure 5.3: Exhibitor Admin Activity Diagram] 24 [Figure 5.4: Company Admin Activity Diagram] 25 [Figure 5.5:Event-Organizer Admin Activity Diagram] 26 5.1.5 Data Flow Diagram [Zero level data flow diagram] [First level data flow diagram] [Figure 6: Data Flow Diagram] 27 5.2 Data Dictionary Customer [Table 5.2.1] Contact Us [Table 5.2.2] 28 Exhibition Company [Table 5.2.3] Exhibition details [Table 5.2.4] 29 Exhibition Company User [Table 5.2.5] Exhibitor Admin [Table 5.2.6] 30 Exhibition user [Table 5.2.7] Products [Table 5.2.8] 31 Request demo [Table 5.2.9] Web Admin [Table 5.2.10] 32 Website General COnfig [Table 5.2.11] Subscription details [Table 5.2.12] 33 Payment details [Table 5.2.13] Login history [Table 5.2.14] Newsletters [Table 5.2.15] 34 CHAPTER 6 SnapShots 6.1 Exhibitor-Admin View 6.2 Web-Admin View 6.3 Sub-Admin View 6.4 Company-Admin View 6.5 Event-Organizer-Admin View 6.6 Client’s View 6.7 Other Functionality 35 Chapter 6: Snapshots 6.1 : Exhibitor-view [login page for Exhibitor] [exhibitor's Dashboard, here exhibitor can see details about sales, company registry etc.] 36 [exhibitor’s profile details with last login logs] [Registered Company information and status] 37 6.2 : WebAdmin-view [WebAdmin's dashboard, here webAdmin can see subAdmin, visitors details etc.] [Newsletter page in WebAdmin's dashboard, in this page show subscribed users] 38 [webAdmin page, here webAdmin can add, delete or update subAdmin's details] [Here, webAdmin see all the users details and also see status of user] 39 [Web configuration details to show personalize data] [Subscription price and other related details] 40 6.3 : Sub-Admin-view [subAdmin's dashboard, here subAdmin see all subscribed user and their details] [contact page, here subAdmin can find all the subscribers details] 41 [Request-demo page, here find all the request for demo by user] [Exhibitor-details page, here subAdmin can see all details about exhibitor] 42 [More details about demo requests and contact information] 43 6.4 : Company Admin View [company admin can view here about their products and related details] [View of product with status of product availability and admin can change in their catalog] 44 [View about product inquiries made by company customer and their contact details] [Other security informations] 45 6.5 : Event Organizer Admin View [Registered companies details] [Live Exhibition details Modification form] 46 [Price settlement by exhibitor admin] [company’s detail information] 47 6.6 : Client-View [Homepage, here exhibitor and visitors can find overview of our services] 48 [OurServices page, here exhibitor and visitors can find more details about over services] 49 [ContactUs page, through this page any user can direct contact with our team] 50 [RequestDemo page, through this page any user can schedule demo of exhibition] 51 [User’s signup page] 52 [Without login/signup user can see one demo product] 53 [Exhibition page here all the running and upcoming events details present to user] 54 [Exhibition organized by companies] 55 [Exhibited product detailing page] 56 [Inquiry details Made by customer] 57 6.7 : Other Functionality [Mails for username/password, OTP and Welcoming message] [Exported data tables for product, company and product inquiry] 58 CHAPTER 7 IMPLEMENTATION 7.1 IMPLEMENTATION ENVIRONMENT 7.2 PROGRAM/MODULE SPECIFICATION 7.3 SECURITY FEATURES 7.4 CODING STANDARDS 59 CHAPTER 7: IMPLEMENTATION 7.1 IMPLEMENTATION ENVIRONMENT: To develop this project we setup our development environment like: Web Server − PHP will work with virtually all Web Server software, including Microsoft's Internet Information Server (IIS) but then most often used is freely available Apache Server, and we also used Apache Server. Database − PHP will work with virtually all database software, including Oracle and Sybase but most commonly used is freely available MySQL database. And we also used MySQL database. PHP Parser − In order to process PHP script instructions a parser must be installed to generate HTML output that can be sent to the Web Browser. We use to develop this project is Chrome standard browser and use Microsoft Edge some time for debug the program. 7.2 PROGRAM/MODULE SPECIFICATION: Four main modules are dealing with the website: ● Users ● Exhibitor Admin ● Sub Admin ● Web Admin ● Company admin ● Event organizer admin The administrator module is the primary module in our project. There are different attributes allocated to their tasks like exhibitor admin is also a client for us, but they manage their exhibitory product and product information and connection with their customer also. Sub admin acts as a live support for exhibitor admin and also they manage contact us messages and demo requests, where web admin is master of this project they can manage all the details and connection between admins and customers also. Event organizer admin can handle live event and price for event or particular products and company admin can handle request for inquiries and live event and their product etc. And the user is the end customer or exhibitor shows initially users of our customer before subscription, from the front site of the web user see live exhibition and connect with sub admin or exhibitor admin. 7.3 SECURITY FEATURES: Since our project saves data online, some customers or users might be worried about security. However, security is a top priority for online. In addition, the online connection makes it easy to participating event, link up with organizations. We create OTP based registration for security purposes. Also, we maintain strong folder structure. 60 7.4 CODING STANDARDS: Developers’ work is much easier if they use the right tools, and this definitely includes automated coding standards checkers and fixers. It makes the learning process much smoother for new members of the team, helps to keep code consistent and easy to read, and last but not least, enables the team to focus on important issues during development and code review. ● ● ● ● ● PHP tags: One must use the PHP standard tags (), rather than the shorthand tags () to delimit the PHP code. Commenting: Use commenting style i.e., (//) – for single line and (/* */) – for multi-line, is highly encouraged in PHP environment. Line length & Indentation: It is a standard recommendation to not exceed more than 7585 characters in a single line of code. One must not use tabs for indentation instead use 4 spaces as it is the standard indenting method in most of the programming languages. Structuring the control flow statements: The control flow or conditional statements must be written in such a way so that it could be differentiated from function call statements. While writing if, for, while, switch and other control flow statements there must be one space between the keyword and the opening parenthesis. Function Calls: While writing a function call statement, there must be no space between the function name and the opening parenthesis. Above mentioned all Coding standard followed in our project. 61 CHAPTER 8 TESTING 8.1 TESTING PLAN 8.2 TESTING STRATEGY 8.3 TESTING METHODS 8.4 TEST CASES 62 CHAPTER 8: TESTING In this chapter is aimed to provide a brief account of testing the software. There are two principal motives of testing the software: 1. To rectify the error in execution 2. To check the viability of software The testing ensures that the software is according to the required specification standards and performs the task meant for it. The testing is done by our team members that act as novice users and test the project with all possible way to find the bugs and error as well as check validation. 8.1 TESTING PLAN: Testing is carried out at the following three stages: 1. Design 2. Implementation 3. Coding 8.1.1 Design Testing: This Testing apply after designing stage to verify product design.At this stage we test our project’s all designing schema like class diagram, E-R diagram and UI/UX design also. 8.1.2 Implementation Testing: This testing is not a proper structural testing but every time check the program after writing some code of particular function, programmer check their code by testing some edge case to check reliability of code.This testing perform during implementation of project. 8.1.3 Product Testing: Product testing is last stage of testing, Here We tested our project’s end to end customer Satisfaction. In this testing we use black box and white box testing techniques to check technical and practical View of project. 63 8.2 TESTING STRATEGY: A technique for programming testing coordinates programming experiment structure strategy into an all-around arranged arrangement of steps that outcome in the effective development of the product. The system gives the guide that depicts the means to be led as a piece of testing. We have tried our entire project utilizing bottom up testing technique. Bottom up testing includes incorporating and testing the modules to the lower levels in the chain of importance, and afterward stirring up progression of modules until the last module is tried. Bottom up testing procedure demonstrates how genuine testing is to be finished with the entire project yet it doesn't demonstrate any insight concerning every module testing. For every module testing, we have chosen to test each lower level module with white box testing system. When all modules are tried effectively then I will move to one stage up and proceed with white box testing technique. When all modules will be tested successfully then I will integrate those modules and try to test the integrated system using black box testing strategy. Why Black Box Testing in my Project? In our project whatever we have implemented was going to be tested by Aniket(our team member)knowing bit of code, so there was a black box testing involve directly. Why White Box Testing in my Project? During the project we were making the website, we knew how it should proceed internally; all the team members done the white box testing for individual portion of project. Why interface Testing in our Project? In this testing mainly focused on Interface view. In this testing we tests some basic GUI functionality, some of tested functionality is: 1) Testing the Screen Control for its position And Side. 2) The Position and Related Marks for All Control were checked 3)Validations for all input were done. 4) Whether the system prompts the user with appropriate message as and when invalid information is entered. 5) All required fields aren’t left blank. 64 8.3 TESTING METHODS: 8.3.1 Unit Testing: The unit testing is intended for testing the littlest unit of programming. There are two methodologies to be specific: bottom-up and top-down. In bottom up methodology the last module is tried and after that moving towards the principal module while top down methodology switches the activity. In present work we select the first. 8.3.2 Integration Testing: The integration testing is intended to test every one of the modules at the same time since it is conceivable that every one of the modules may work accurately when tried separately. However, they may not work by and large and may prompt unforeseen results. 8.3.3 Validation Testing: Validation can be defined in many ways but a simple definition is what a validation succeeds when software functions in a manner that can be reasonably accepted by the user. 8.3.4 Storage Testing: The database of the system has to be stored on the hard disk. So, the storage capacity of the hard disk should be enough to store all the data required for the efficient running of the system. 65 8.4 TEST CASES: TEST CASE ID: TC_Login_01 NAME: User Login TESTING STRATEGY Black Box and White Box Testing PURPOSE Checking the authenticity of the user INPUT: Username, password TEST DATA: txtUserName, pwdPassword EXPECTED O/P: If user name and password are correct then user is allowed to enter in to the system UNBEHAVIOURABLE O/P: N.A. STEPS: 1. After user enters username and password it is going to be verified with database 2. It matches the username and password and get access system if both matches correctly. [Table 8.4.1.1: Test Case Table Login] TEST CASE ID: TC_Login_02 NAME: User’s dashboard TESTING STRATEGY Black Box and White Box Testing PURPOSE Checking the authenticity of the user INPUT: Username, password TEST DATA: txtUserName, pwdPassword EXPECTED O/P: After the login user can access the features and Functionalities of the system. UNBEHAVIOURABLE O/P: N.A. STEPS: 1. After user enters username and password it is going to be verified with database 2. It matches username and password and get his user rights 3. As per assigned rights relevant action will be enabled [Table 8.4.1.2: Test Case Table dashboard] 66 TEST CASE ID: TC_Login_03 NAME: Registration [username already exist] TESTING STRATEGY Black Box and White Box Testing PURPOSE Creating new user INPUT: username, password, confirm password TEST DATA: txtUserName, pwdPassword EXPECTED O/P: User is not created if username already exists. UNBEHAVIOURABLE O/P: N.A. STEPS: After the admin enters the username and password it is verified with the database. If already exist then alert message will be show [Table 8.4.1.3: Test case Table Registration] TEST CASE ID: TC_Login_04 NAME: Length Validation TESTING STRATEGY Black Box and White Box Testing PURPOSE Validating length of input components INPUT: input components of all web pages TEST DATA: Inputted data EXPECTED O/P: Validation occurs . UNBEHAVIOURABLE O/P: N.A. STEPS: Length of password should not be greater than 30 characters. [Table 8.4.1.4: Test Case Table Length Validation] 67 TEST CASE ID: TC_Login_05 NAME: Test Case Table OTP Validation TESTING STRATEGY Black Box and White Box Testing PURPOSE To validate OTP of the user INPUT: OTP TEST DATA: otp EXPECTED O/P: Validation of otp UNBEHAVIOURABLE O/P: N.A. STEPS: 1. Check whether OTP is previously inserted or not. 2. Checking for the correct OTP format. [Table 8.4.1.5: Test Case Table OTP Validation] TEST CASE ID: TC_Login_06 NAME: Test Case Table email verification TESTING STRATEGY Black Box and White Box Testing PURPOSE To validate email for newsletter INPUT: Mail Id TEST DATA: Mail address EXPECTED O/P: Validation of mail id UNBEHAVIOURABLE O/P: N.A. STEPS: Checking for the correct email id format. [Table 8.4.1.6: Test Case Table email Validation] 68 CHAPTER 9 LIMITATION AND FUTURE ENHANCEMENT 9.1 LIMITATION 9.2 FUTURE ENHANCEMENT 69 CHAPTER 9: LIMITATION AND FUTURE ENHANCEMENT Though we tried our best in developing this system but as limitations are mere parts of any system so are of our system. 9.1 LIMITATION: In this project exhibition goes in virtual mode, but there are many product that can impress customer using product real touch & feel and some time scent also. So in virtually mode there no possible to give customer real feel about that type of product. In real exhibition’s customer connect with product presenter to directly and clear their doubt or negotiation about product and make deal real time, in our platform currently C2B and B2B connection made through other platform but In future we have plane to overcome this limitation by giving real time chat option or other media to make connection. 9.2 FUTURE ENHANCEMENT: The future upgrades will have a few updates in the project. We will incorporate to give product inquiries or any other type of deal made through over site by giving chat option to connect each other. And giving more option to our customer/exhibitors to give dynamic detail to make more personalize view for any company or product specific by giving dynamic mail template and dynamic product exhibiting page etc. 70 CHAPTER 10 CONCLUSION AND DISCUSSION 10.1 PROJECT VIABILITIES 10.2 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTIONS 10.3 SUMMARY OF PROJECT WORK 10.4 REFERENCES 10.5 WORK EXPERIENCE 10.6 APPENDIX 71 CHAPTER 10: CONCLUSION AND DISCUSSION 10.1 PROJECT VIABILITY: By doing analysis we get some advantage and project viability as per below: Global outreach Cost-effective & Speed to marketing of product Flexibility of timing Connect with stack-holders and many more… 10.2 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTIONS: Problem: When we began creating the site we confronted the functionalities issue while creating code, errors like syntax error, connection error, database query error etc. Solution: We learned PHP and MySQL and created the working functionalities of the system. 10.3 SUMMARY OF PROJECT WORK: ● ● ● ● ● ● After doing this project, we have learned numerous things and we might want to thank all the concerned people who have added to our valuable learning. We have likewise comprehended the significance of naming traditions and coding traditions being developed procedures. As our inclination of the venture we were following appropriate strides of improvement legitimately. In the first stage, we have figured out how to set up the necessity inventory utilitarian determination, plan detail, project improvement life cycle. We went on numerous sites and applications which are giving the same offices as our venture to see genuine case situations. In the following stage we have an entire web portal to create which ought to be easy to use and simple to utilize. We have likewise comprehended the significance of naming traditions and coding traditions being developed procedures. Despite the fact that the undertaking was taking excessively long and we confronted numerous challenges which had been settled by the viable direction of educators and our outer guide. We are certain that we can perform better and better as we venture up on the stepping stools of the experience. 72 10.4 REFERENCES: Websites: ● https://www.w3schools.com/html/html_form_input_types.asp ● https://www.w3schools.com/html/html_form_input_elements.asp ● https://www.javatpoint.com/html-table ● https://www.w3schools.com/js/js_ajax_php.asphttps://www.freeprojectz.com/ ● https://www.tutorialspoint.com/ajax/ajax_database.htm ● https://www.tutorialspoint.com/php/index.htm ● https://dev.mysql.com/doc/mysql-tutorial-excerpt/8.0/en/ ● https://www.tutorialspoint.com/php/php_and_mysql.htm ● https://www.tutorialspoint.com/php/php_file_uploading.htm ● https://www.w3schools.com/css/css_form.asp' ● https://www.php.net/manual/en/function.base64-encode.php 10.5 WORK EXPERIENCE: We had begun our work for the report on the "Online Virtual Exhibition Platform" in the beginning of the semester. The time length for this report is several months this semester. We have a decent encounter at work. This helped us to think about the distinctive things which ought to occur in the business or in the genuine work. In this time term our employee helped us particularly to finish this undertaking. Our venture director Prof. Dhaval Chandarana gave us great information about the theme and about the report. In the end I like to state that this experience gave us incredible comprehension and great learning about our point. 73 10.6 APPENDIX: 1. AEIOU FRAMEWORK: AEIOU framework is developed to analyze the world project. To observe each and every part of the activity done by the users while developing the framework. All the activities which the users do while using the application or the users can use the application while doing other activities.Environment perspective is also important for the project in many conditions our project gets failed. It is essential to be aware of the environment needed for the application. It includes power failure and also in many weather conditions can’t be used. [Aeiou Framework] 74 2. IDEATION CANVAS: In this canvas the activities play the major role. Four possibilities are defined in this which are the people, the activities, the related situation based on the activities, the context or the location based on the activities. The possible solutions are also given or the objects which are used while implementing the project. The basic analysis is done from the ideation canvas and the needs of the users and their requirements are also defined from this sheets the one can easily identify the basic things about the projects which would be useful. [Ideation canvas] 75 3. PRODUCT DEVELOPMENT CANVAS: The product development canvas is done for getting the information about the main objective of making the application. In this, the purpose for why the product is developed and how it would be benefited to the people is described. After using the product the experience of using is given by the user. The functions which are applied in the product while making the product. The features which are added by the admin in the product and the components used while developing. After using the product the expected features which are added more for comfort are obtained from the reviews and if the redesigning is possible then that feature is added or else it would be in rejected mode. [Product Development Canvas] 76 4. EMPATHY Summary: Empathy summary is used to find various challenges occurring in the project. The given from the AEIOU framework and the activities are also obtained from that framework.The main five challenges which the admin faces while making the project or which would be helpful and needed for the users. Then the exact problem is carried out so by that functionality after adding the users would use the application. [Empathy Canvas] 77 5. BUSINESS MODEL CANVAS: The Business Model Canvas is utilized to approve the market criticalness of items and administrations, taken up for the undertaking for this situation. Innovation ventures are frequently arrangements or procedures that take care of a specialized issue. Anyway, the execution for the market of such arrangements additionally necessitates that the issue arrangement is structured. ● ● Not just to defeat not simply the specialized barriers But likewise, to market-and-business related boundaries of costs, client reach and Collaborations. In this manner a plan of action canvas can be utilized to envision and advertise issues and client desires. This activity will expand the market potential and entrance of innovation products and ventures. This will make them increasingly successful in the market. [Business Model Canvas] 78