Web Application And MongoDB Analysis Report

Web Application Report
Student’s name
Institution Affiliation(s)

Table of Contents
5.2 Database Design....................................................................................................................................2
6.2 Backend API...........................................................................................................................................3
6.2.1 Login module..................................................................................................................................3
6.2.2 Student...........................................................................................................................................4
6.2.2.1 API for viewing approved topics..............................................................................................6
6.2.2.2 API for selecting preferences...................................................................................................7
6.2.2.3 API for showing allocated topics and groups...........................................................................9
6.2.3 Admin...........................................................................................................................................10
6.2.3.1 API for adding topics..............................................................................................................10
6.2.3.2 API for publishing approved users.........................................................................................13
6.2.3.3 API for viewing preferences...................................................................................................14
6.2.3.4 API for viewing Allocations....................................................................................................14
6.2.3.5 API for publishing allocations.................................................................................................14
6.2.4 Supervisor.....................................................................................................................................14
References.................................................................................................................................................15
1

5.2 Database Design
The above code snippet is the code that was used to connect the JavaScript web application to
the mongo database. The try and catch block has been included where the try statement allows
the program to test a block of code for errors and the catch statement lets the program handle the
error. Everything done on mongoose database is based on a schema where each schema is
mapped to a mongoDB collection that is responsible for defining and shaping the documents
within that collection.
For this web application the try and catch block will try the code for errors and return ‘error’
while the catch block will handle the error and if successful the database will be connected to the
application. When the user logs out of the system, the status will change to ‘disconnected’.
Mongodb was used as the preferred database. MongoDB can be explained as a database program
that is both document-based and can be used in various platforms.
2

MongoBd features such as ACID properties that allow for multi-document transactions,
MapReduce properties for JavaScript execution, sharding which allows MongoDB to scale
horizontally and replication are some of the main reasons why I choose to use MongoDB.
MongoDB is a NoSQL type of database.
NoSQL
6.2 Backend API
6.2.1 Login module
The login module recalls the user details for the already existing users from the database. Users
will be required to type in their email and their password after which the try and catch block will
3

be executed to validate the credentials. If both the email and the passwords match with the
existing user details then the user is allowed to login successfully.
6.2.2 Student
The above snippet is the code that enables students to create their account and login after
creating an account. As is with JavaScript and JSON, the code is initialized and then the critical
libraries are imported. Then all the data types that will be required are initialized and their
conditions such as the minimum length of the data and whether it is required or it can be skipped
are determined. For this case, the email is a string data type and only a min of four characters are
allowed. The password on the other hand, must be unique for every user, a string data type and
4

only a minimum of six characters are accepted. The system uses timestamps to be able to know
at what time the student logged in the system.
For the above code, a jwt is generated after creating and account and login in. After setting up
the account with an email and a password, the above code uses a try, catch and throw method of
error handling. As indicated earlier, the throw statement allows the program to notify the student
using customized error messages. In addition, the try statement tests the code for errors while the
catch statement handles it.
5

An if else statement has been used in the above code to ensure that the code executed as long as
the password and the email match with the data that is stored in the database. If the password and
the email are collect, the student logs in the system successfully. The throw statement is
constantly used in this particular segment of the code to ensure that the system remains user
friendly thus improving usability. When a student or any other user for that matter is notified of
what the system is doing along the way, then they fell more comfortable while using the system.
6.2.2.1 API for viewing approved topics
6

6.2.2.2 API for selecting preferences
7

8

6.2.2.3 API for showing allocated topics and groups
9

6.2.3 Admin
The admin is responsible for overseeing the whole system as well as maintenance. For this
particular web application, the admin have roles such as adding topics, publishing approved
users, viewing student’s topic preferences, and viewing and publishing topic allocations. The
following sections explain the various APIs for the admin.
6.2.3.1 API for adding topics
10

In the first segment of the above code snippet, the topic is initialized and all the required libraries
imported. JavaScript models are also used in reference to the libraries. The second part of the
code is where the admin creates a new topic. At this point, the system uses a try and catch block
to validate and make sure that only topics that are new can be added to the system. The last
segment in the above snippet is the code that the admin use when checking for topic details to
ensure they have been added to the system successfully.
11

This part of the API has two segments where the admin is able to both update and delete topics
from the system. While updating the topics, the admin a try, throw and catch block have been
used the try block tests the code segment for any errors. The throw block allows the admin to
receive customized error messages from the system. The same procedure have been used for the
delete segment of the code where a throw statement have been added to notify the admin when
the select an invalid topicID. Additionally, the try and catch statement tests the code and handles
it respectively. An if statement have been used for both segments of the code and allows either
segments to be executed as long as certain conditions hold true.
This is the final segment of the add topics API for the admin where the classes are closed and the
module exported for use by modules that have referenced them.
12

6.2.3.2 API for publishing approved users
13

6.2.3.3 API for viewing preferences
6.2.3.4 API for viewing Allocations
6.2.3.5 API for publishing allocations
6.2.4 Supervisor
14

References
15