This is to certify that ______CHOONG WIN SHEN___ (ID No: __18ACB01717 ) has completed this final year project/dissertation/thesis* titled “_HOSTING AND MEETING MOBILE APPLICATION____” under the supervision of ___MS. I declare that this report entitled “MOBILE APP FOR HOSTING AND GATHERING MEET UP” is my own work, except as indicated in the references. This project is a mobile application development project that makes it easy for users to meet a stranger.
Some of the problems with the traditional dating app can be solved by this proposed project, where the user can find it easy to use the app and easily meet others in real person. There will be several features that help the user in planning and starting a meeting, such as host, join or accept a meeting application. This project was developed with the Extreme Programming methodology, which will be easier for an individual or a small team.
INTRODUCTION
- Problem Statements and Motivations
- Objectives
- Project Scope
- Impact, Significance and Contribution
- Report Organization
It is difficult to schedule meetings due to the lack of built-in support function. As mentioned above, there is no dating function for users to facilitate the entire dating process. Therefore, there is a motivation to build an application that enables the user to host a meeting that allows other interested users to join together.
One of the main objectives of this project is to develop an application that enables the user to interact with other users personally through hosting meeting functions and features. The scope of this project is to develop and deliver a social networking and scheduling application that allows the user to host a meeting to meet other users in person. The host must close the meeting registration to create a group chat room with other connected users.
LITERATURE REVIEW
Existing Applications Review .1 Tinder
- Bumble
- Tantan
Bumble also has an account verification feature that allows a user to upload a one-time selfie to verify themselves. The male user has to wait for the female user to start a conversation, which in the worst case will be automatically terminated by the match after 24 hours. Its photo verification allows the user to upload a selfie for self-verification and after verification, they will receive a badge.
This can help another user identify whether the user they liked is a real person or not. It does not force the user to take photo verification functions which creates a loophole for bots and fake accounts. Its left and right swipe feature is the only way for the user to connect with others, which is a disadvantage for those who don't upload attractive photos.
Methodologies Review
- Rapid Application Development (RAD)
- Agile Methodology – Extreme Programming (XP)
- Spiral Methodology
This can be easily accomplished in Agile as it is an iterative and incremental model approach. It is suitable for low or small budget projects as the XP team requires less human resources [18]. It does not require fully defined user requirements in the early stage as it is an iterative approach where user requirements can be specifically increased [25].
Time and cost must be analyzed in each iteration during the risk analysis phase, as this is one of the important criteria for determining project risk [26]. The success of the project is highly dependent on the accuracy of the experts' risk analysis, as this is the main focus of this methodology. It is also not suitable for low-risk projects or small projects aimed at a low budget.
SYSTEM METHODOLOGY/APPROACH 3.1 System Design Diagram
Use-case Diagram a) Normal User Module
Prerequisite(s) User wants to write a review for company or user Prerequisite(s) User is logged in. Prerequisite(s) User wants to see reports of own, other users or business users Prerequisite(s) User is logged in and has landed on the profile page. Assumption(s) User has received application from other users. Prerequisite(s) User is logged in and on the meeting page Post condition(s) The user has landed on the application page.
Assumption(s) User wants to view message logs and chat with users Prerequisite(s) User is logged in. Assumption(s) The User has responded to the booking requests before the Prerequisite User is registered on the home page. Assumption(s) User wants to view review of own users or other users Prerequisite(s) User is logged in and logged in profile page Requirement(s) Post User is placed on review page.
Activity Diagram .1 Log in
User Interface (UI) Design .1 Sign up and Login
SYSTEM DESIGN 4.1 System Block Diagram
System Components Specification Classes and Objects Specification
In this system, several Java libraries and classes are used to build the functionality of the application. The activity and fragment lifecycle will control the switching of pages and content of the application. For example, there are some supported callbacks to monitor state changes, such as onCreate() - the system creates, onStart() - the system starts, onDestroy() - the system process is destroyed.
For example, it is used in the feature to answer friend requests in this app, where there will be a rectangular modal popup at the bottom of the screen with some button options. For example, this is useful for allowing users to swipe right to see more profile pictures. It is a class dedicated to holding and storing the data controlled by a lifecycle.
Other classes like Client – contains the getClient() method for the message service to retrieve the current client, DataMessage class – a model for the message, FCMToken class which contains getToken() – to get the token for granted service, Response class – indicates the success or failure of the service, Sender class – to create an instance of the sender of the message. ConstraintLayout is also often used as the basic layout of the screen, as it allows to position children's display in a flexible way by setting the constraint weight. For example, there are 4 pages - Home, Chat, Notification and Profile that can be switched by users at the bottom of the screen, held by this BottomNavigationView.
There is a header that is mainly used across the application for pushback function and to display the title of the pages. This is a custom ToolBar view that contains all the necessary view that shows the title of the pages. Whenever users land on a particular page, the Toolbar will handle which title view to show at the top of the page.
Sometimes it is also useful to display a hard-pressed back button to the left of the Toolbar to allow the user to navigate to the previous page.
Components Design System Flow Chart Diagram
There is an important component that is designed to control the flow of multiple connected fragments. It is a navigation component supported by Android that allows the user to navigate through different fragments in the application. For example, since the application process is divided into several pages, these pages can be grouped together using a navigation chart to help navigate from one to the other.
As shown in the picture below, this is a Navigation Graph for the recording process, where a fragment can be navigated to another fragment as a destination and back or forth.
System Components Interaction Operation Log in and sign up
User editing description User uploads photos User successfully registered Table 4.1 Log in and register. User check shows up and found it completed. Table 4.4 Meet up is accepted, completed or closed. The user clicked on the profile icon in the bottom navigation bar and visit own user profile page.
User clicked Hosted or Affiliated tab, user cannot view meeting details. Table 4.9 Normal user views different user profile. User clicked the History tab User clicked on one of the bookings on the home page and went to the booking detail page.
SYSTEM IMPLEMENTATION 5.1 Hardware Setup
- Software Setup
- Setting and Configuration
- System Operation Normal user
- Concluding Remarks
There is only one simple setting which is to turn on either Wi-Fi or mobile data as it required the user to be online to use this application. This section covers the setup, device requirements as well as a simple user guide to guide the interested user in using the application. However, if the user wants to use this application in Android Studio, there is a built-in emulator provided by Android Studio, and the user can drag the application file into the emulator.
A brief user guide is provided in this section to guide the user in using the main function of the application.
SYSTEM EVALUATION AND DISCUSSION 6.1 System Testing and Performance Metrics
- Testing Setup and Result Functional Testing
- Implementation Issues and Challenges
- Objectives Evaluation
- Concluding Remark
It is needed to ensure that the user can access a particular screen and return to the previous screen seamlessly and smoothly. This goal is achieved as the user can host a meeting in the app by setting relevant information such as title, description, date and time of gathering, number of guests and also location.
CONCLUSION AND RECOMMENDATION 7.1 Conclusion
Recommendation
In the next version, it is suggested that only those users who participated in a meeting together will have the privilege to rate and review each other. It is suggested that security instructions be given to the host and convenors for the meeting. Gavrilă, “Influencing factors for choosing a software development methodology”, in Accounting and Management Information Systems, Jan.
Adapting XP Practices to Large-Scale Projects," in Proceedings of the 37th Annual Hawaii International Conference on System. Öztürk, "Selecting Appropriate Software Development Life Cycle Using Fuzzy Logic," in Journal of Intelligent & Fuzzy Systems, May. West, "A Comparison of Software Project Architectures: Agile, Waterfall, Spiral, and Set-Based," in Massachusetts Institute of Technology, Jan.
Alarabeyyat, "A Review of Risk Management in Different Software Development Methodologies," in International Journal of Computer Applications, May.
FINAL YEAR PROJECT WEEKLY REPORT
WORK DONE
WORK TO BE DONE Enhance notification
PROBLEMS ENCOUNTERED
PROBLEMS ENCOUNTERED None
SELF EVALUATION OF THE PROGRESS Good in progressing
WORK TO BE DONE
POSTER
PLAGIARISM CHECK RESULT
The originality parameters required and the restrictions approved by UTAR are as follows: i) The overall similarity index is 20% and below, and. ii) Match of individual sources listed must be less than 3% each and (iii) Matching texts in continuous block must not exceed 8 words. Note: Parameters (i) – (ii) will exclude quotes, bibliography and text matching that are less than 8 words. Note The Supervisor/Candidate(s) must/are required to provide the Faculty/Institute with a full copy of the complete set of originality report.
UNIVERSITI TUNKU ABDUL RAHMAN FACULTY OF INFORMATION & COMMUNICATION
TECHNOLOGY (KAMPAR CAMPUS)
