Subscription Management System
Subscription Management System

Abstract

Accessing information in today’s world has leaped with the development in technology which has given way to the online system to be the new management system. The need for an online system has increased rapidly during these past years. The online method has been excellently eliminating the need for hard copies, spaces, protocols, and time. The online system indicates the connection between the users and the design.

 As one of the environments involving a large number of participants, information, and resources, UTP also tends to benefit from using a time-efficient online management system.

 Thus, the Subscription Management system is ideal since it provides the best solutions for the previous FYP management. This system is proposed to enhance the process and management system efficiency. This project will introduce a web-based software solution to provide a comfortable environment for FYP management. This system will be developed using software that is freely available to the public.

Introduction

The subscription Management system has played an essential role in my life by supporting my academic career. I have been using the Subscription Management system since I started my study. They have helped me remember assignment deadlines, group meetings, classes, exams, and, more importantly, subscriptions to other applications or sites, which are essential to my everyday life. In addition, they remind me of different activities, such as meetings and making purchases at shops. This study examines the usability of the Subscription Management system available from the Apple Store® and Google Play™. 

Subscription Management systems have several advantages, as people now use their smartphones and tablets to be reminded of future tasks. This study examines how and why users use the Subscription Management system, including whether they use them for analysis, sport, and other charges or whether they use it for one type. It also examines the functions and content that users need in the Subscription Management system. 

The choices people have for spending time and the multiple pressures on time have increased the interest in tools for helping people schedule and manage their tasks and remind them when assignments are due. With the ubiquity and constant proximity of personal mobile devices, many people are using the electronic Subscription Management system to assist them. There is a proliferation of such apps with diverse interfaces, features, and theoretical foundations. There is no one answer to fit all user needs. 

This begs the following questions: Which features are the most useful? How are users appropriating reminder apps? How can a user select from this snowballing diversity of apps to find one that suits them? This research addresses these questions by focusing on the usability of a set of standard Subscription Management systems and how people use them. Insights from this usability study will provide a basis for selecting a Subscription Management system, and it will guide the design decisions of future apps.

AIM of The Project

The main focus of this research is a usability study of the Subscription Management system available on smartphones and tablets that facilitate better app development, including better design and features that can address users’ needs. It is anticipated that the results from this research will help create guidelines for creating a Subscription Management system and identify the contents and functions that users need to remember for their future tasks. 

This research utilizes three combinations consisting of triangulation or quaternion of usability methods. The usability testing helps identify which contents and functions work and do not work in the Subscription Management system. Usability testing is the best method for this purpose because it directly studies the behavior of users at the time of use.

Problem Statement

It is done manually where all the registration, allocation, and markings are in hard copies and forms and then managed by FYP coordinators. While the coordinators are doing its job perfectly, this existing management system has several disadvantages:

  • It is time-consuming and requires more human resources to run the manual system; hence it is denoted as less efficient.
  • In communicating with all the participants, the committee also has problems and difficulties because there is no specific medium of interaction, and this will cause delays. 
  • There are also some problems aroused in storage and archiving. The previous data are hard to search and tend to be eliminated after some time. The manual system also uses much more storage for all the hard copies.

The Objective of The Project

The main objectives are: 

  • For the development of an online system that is systematic and comfortable 
  • To design the architecture of the subscription system and its functionalities 
  • To set up the platform and server environment 
  • To check the reliability of the system 

Scope of The Study

The scope of the Subscription Management system is complete terms of the management system. There are two parts to developing this project. This project will also involve the knowledge and experimentation based on:

  • Web design, setup, and development 
  • Database design and management
  • Server design and set up in this part will be focusing more on web and server design, setup, and development. 

Operating System

 The operating system is the essential thing in every computer, and it serves as the platform for all the programs to run and interact between the hardware and the software of the system. There are a lot of operating systems available to install, such as the Mac Operating system, Windows, and Linux.

System Requirements

Software Requirements

Operating system: Windows and Linus

Language: Java 2 Runtime Environment.

Databases: MySQL Server

Web Server: Tomcat7Software development kit: Java JDK 1.7 or above.

Hardware Requirements

RAM: 128GB

Monitor

Keyboard

Processor: Pentium III or above.

System Architecture

A brief outline of how the system works is shown in the Figures below refers to the architecture of a Three-Tier Client/Server. In contrast, the use case diagram shows the relationship between the client and server through a Use Case Diagram. In overview, the flow of the system can be described as follows. When a user enters the URL to access the Subscription Management system in the Web browser, the browser will send a request to the Web server to fetch an HTML page or execute a PHP script. A PHP script uses SQL queries to access the Subscription Management system database tables and sends dynamically generated HTML pages back to the client’s browser. One of the compelling reasons for developing a Subscription Management system is to provide a user-friendly Web environment for managing all the participants and projects. The system is made up of the following four main components: 

  1. Client-side
  2. Server-side
  3. Database backend and web-based administration tool
  4. Graphical front-end
System Architecture for Subscription Management System
System Architecture for Subscription Management System

Subscription Management system architecture is ordered into three tiers:

the user interfaces in the client browser, the Web server, and the database server. The working description of each tier in the system is as follows: 

  • First Tier: The Interface As viewed from the client’s web browser, the interface is built by HTML pages with JavaScript support.
  • Second Tier: Web Server For this system, an Apache web server is used with the PHP module to support the back ends in the third tier. The PHP scripts will process the user input, generate SQL queries to access the database and then the Apache will compile and execute the output as dynamically generated HTML pages. 
  • Third Tier: Database Server In the third tier, the MySQL database server will receive requests from the second tier to execute SQL statements. The server fetches the database files, retrieves the stored data, and then sends the required data back

Use Case Diagram

Using a case diagram is a graphical representation used to capture the dynamic aspect of a system. It consists of users, their use cases, and their relationships. Use a case diagram to describe how users interact with the proposed method. It is used to gather the requirements for the system and identify the external and internal factors that will influence the design.

When you will draw the diagram, the interactions and functionalities can be seen. In Figure, three actors represent the three groups of users for Subscription Management system users: Students, Lecturers/Supervisors/Examiners, and others. In the middle is the requirement of each group for the system.

Client-Side Architecture

The Subscription Management system is designed to exchange information between students and supervisors. For students, the system will have the position to view all the available topics of projects and supervisors, and 15 select the chosen one. Students may also view the supervisor’s profile and view the status of their submissions. As for the lecturers, supervisors, and examiners, uploading their projects and allocations of students is made easier with this system.

Use Case Diagram for Subscription Management System
Use Case Diagram for Subscription Management System

There will be no more hardcopy forms to be filled and submitted by hand. All will be done online. This group may also view students” profiles and give the students marks. The system is planned to be able to allow the educators to view the students” online submissions. The user will be granted full access to this system to manage the titles and allocations and assign the examiners. The user may view the subscription detail and will post any important announcement. The administrators will govern the system. The administrator will monitor the system, maintain all users’ access levels, and administer the site settings.

 The Subscription Management system is a Web-based application that uses any web browser to interact with the user. So, the critical component on the client-side is the web browsers (e.g., Internet Explorer, Mozilla Firefox, Google Chrome, etc.). After all the back-end processes, the HTML will generate dynamic web pages, and the JavaScript will validate user input. The scripting language used here is HTML with JavaScript enabled to ensure compatibility with the server-side. 

Server-Side Architecture On the server-side, the Subscription Management system will have several database tables where all the data and information are stored and some dynamically generated tables using MySQL database in the Linux environment. MySQL is used to compose the queries to access the database. The server will be running on PHP scripts with embedded questions to interact with the database.

Process Flow of The Project

Project Work shows the process flow of the project. Throughout the course, a lot of research had been done in studying operating systems, programming languages, SQL databases, and web servers until we decided which of each to use for this system. After that, the system design and architecture were discussed for use on the client-side and server-side of the Subscription Management system. The system has started to be developed since SMS and continues into SMSII.

Process Flow for Subscription Management System
Process Flow for Subscription Management System

Conclusion

A web-based software system Subscription Management system will be introduced to provide a comfortable environment for management. This project is a comprehensive solution to the problems faced by manual control. The success of the Subscription Management system will reduce the user’s weight, simplify the protocol and increase the performance of all the management. 

All the participants can interact with each other and exchange information online. The project’s feasibility is guaranteed, so this project should be developed and implemented. The Subscription Management system is hoped to perform very well in enhancing the quality of the Subscription management system.

Advantages and Disadvantages

We have already discussed all the advantages of the project above. However, one of the system’s main advantages is that it helps keep a tab over systems: subscriptions and many more.

One of the significant drawbacks of the system is the automatic payments system. As per the new government rules, People will have to make payments manually, which is one of the main disadvantages we faced while creating the design. Hence, the system is not entirely automatic but rather sends a notification regarding the same. And the user then has to make the payments. One of the features that we added was the storing of card details, but as per government rule, that system has also been withdrawn from the system.