Developing An Online Railway Reservation System For Eutopia

Requirement Analysis

Railway is one of the major forms of transportation for human beings all over the world. It connects various parts of a country and carries more than billions of people all over the world. The native system that is used since ages asks the passengers to visit the rail stations and collect their train tickets by paying for it (Profillidis 2016). Humongous queues of people are observed before the railway ticket counters in the rush hours. It is certainly necessary but hectic in the same time. However, with the advancement of time, human life is tending to become faster. Wasting a minute in queue can cost tremendously in the long run. Therefore, it is necessary to realize the situation and come out of the traditional ticket booking approach as soon as possible (Suki and Suki 2017). Several countries and their railway agencies have already sorted a way out of all these hustle and bustle. According to modern trends, going online is the key to success. Taking any form of customer interactions online seems to have vigorously enhanced the life of many which includes both the business holders and the clients. In case of a railway reservation system, an online platform can greatly help in the growth of the nation and its transportation (Ghosal et al. 2015).

Eutopia is fast-growing nation with a very busy passenger railway network that runs through the country. This extensive railway network is operated by the Eutopian government railway agency. As stated earlier, similarly, the passengers here has to buy tickets for their rail journeys by visiting the ticket counters and paying for the tickets. They can also make telephonic call to the railway customer service and then make draft payment, in which case the tickets sent to them over the post. However, having realized the need for an online railway reservation system, the Eutopian railway agency wants to implement a web application into the ticket booking system. This would include a web application that will be used by the customers through any web browser, online. The customers will use this system to view railway time-tables, view ticket availabilities and also book tickets for their journeys. Once purchased, the customers may choose to either receive these tickets via mail post or they may also choose to collects the tickets by visiting the ticket counters, physically. The users will also be provided with other added features to make their travelling experience more enhanced.

Functional Requirements

This report aims at throwing light into the depths of website development by outlining and explaining all the necessary steps that are needed in the process. This will include the listing of all functional and non-functional requirements for the website. Furthermore, the report will present the use case diagrams and their detailed explanations alongside the class diagrams that will help the readers to read the system details with better understandability. The system design will adhere to the Object Oriented Programming principles and other necessary principles (Coad, Yourdon and Coad 2012).

Functional requirement listing is a software engineering procedure that lists down and explains all the detailed functionalities of a computer system or its components. The functions are described based on the types of inputs and outputs for the system (Wiegers and Beatty 2013). Here, the functional requirements that will describe the core details of the Eutopian railway ticket booking web application are as follows:

1. Customers must be able to sign up into the system using their personal details.
2. Each new customer will have a unique ID.
3. The web application must be able to allow customers to view train time-table.
4. The web application must allow customers to view available train tickets.
5. The web application must be able to allow customers to set reminders or save their upcoming plans for journey and be notified via mail.
6. The application must give a detailed listing of all the available stations along with route details, which the customers must know before they proceed with the booking (Molchanova et al. 2015).
7. The web application must allow customers to book tickets according to their choices by selecting the proper source and destination stations and finally the trains they would like to book for.
8. Each new ticket will have a unique ID.
9. The application must allow users to view the booking status of their last booked ticket.
10. Different price charts must be presented for adult and child tickets.
11. Customers must be allowed to view the bookings they made before payment procedure.
12. The customers are to be allowed to make payments using their valid VISA or MasterCard credit cards.
13. Options must be presented to the customers in order to choose between postal deliveries for their tickets or counter collection.
14. If the customer chooses to get their tickets delivered via post, the customer’s address must be validated by the system.
15. An option must be presented for the user to cancel bookings or report errors in the booking after the payments have been made.
16. A helpline module must be implemented into the website via email assistance or FAQ.
17. After logging in into the system, the system will allow the users to view their ticket booking history.
18. Logged in users must be allowed to access their favorite or most visited train destinations.
19. Administrator login must be allowed to update necessary information in the website’s backend.
20. The backend database must allow access boundaries for the various types of users.

Explanation

• User Registration and login: One of the most basic features of any software or web system is the ability of the user to sign up into it using their personal details. Similarly, the Eutopian Railway Web application must also allow new users to sign up for their account in the website. This account must store the basic identity details of the personality including their name, password, email id, contact details, address, date of birth and a social identity card number. The system administrators must ensure that these data are well preserved. Details on the security of the system will be discussed in a later section of the report under the non-functional requirements (Kaufman 2009). Furthermore, the registration process must verify the identity of the personal by sending a verification link to the individual’s mail account. The user will then be required to login into their provided mail id and then click on the link to verify the account. This process helps the system to reject any registration requests that comes from users who try to register with false or inactive email accounts. Once signed up for the website, every step taken by the user within the website will be saved under their own profile and hence this increases reliability of the system. This makes it easier for the system to distinguish between various profiles and their bookings and other whereabouts. Finally, the users can therefore login into the system once their account is verified and created. In addition, the system should also allow provisions to allow users to gain access to their accounts if they have supposedly forgotten their password. The system should send an email to the registered mail id of the individual and ask him or her to visit the mail inbox to change their password. Features should also be presented for the users to edit and update their provided information at any point of time. However, proper validation measures must be taken. This sign-up/login option should be displayed on top of every webpage within the website application to allow users to login whenever they feel like. Also, a logout option is to be presented for the already logged in users.
• Time-Table: It is always necessary for any railway reservation system to allow their customers to view the train timetables with keen details that will allow them to make their reservation or journey plans. This feature will allow the customers to view the time-table of the trains. The time-table data will be taken from a backend database which can be updated by the system administrator according to needs and situation. This will help the system to remain updated in real-time. The feature can also include a search box that will allow the users to search for a particular destination and accordingly gain train information for the same.
• Tickets availability:This is a very crucial feature that will help the passengers who are planning for long rides. This will allow them to view the number of tickets that are remaining for a particular train. This can be done in two ways. A graphical representation of the booked seats and the un-booked seats can be presented to the user. This will allow the user to get a better understanding of the actual booking status for the train that they are going to book. This will also help them to choose the seats with better precision. However, it must be made sure that the ticket availability option is not presented to those customers or passengers who are willing to book a ticket for a local train journey. Through this feature, the passengers must also be allowed to search for trains by their preferable journey times and or other categories.
• Journey Reminders:This option will allow the web application to notify the users with their upcoming ticket bookings a day prior to the scheduled date and 6 hours prior to the time. This will help the passengers to not miss their trains or bookings. The users are to be notified via an email or messaging service that will contain the ticket code, the date/time of booking and the status of ticket collection. This option shall also allow the users to set their own customized journey reminders. Another interesting feature of this application will be to inform the willing passengers when there is a ticket available for a train they enquired about. This is a very necessary feature and must be a key implementation in the process.
• Location Listings: The web application must have the features to allow its users to view the cities or towns that the railway routes connect. Through this the passengers will be able to choose their boarding and departing stations from a presented list. This will also avert the chances of erroneous input into the system like when a passenger enters a wrong station name and the ticket is wrongly generated. A distance calculator should also be displayed that will display the distance of the total journey to be made for the particular booking between the mentioned locations. If a passenger wishes to book tickets based on the search results for particular trains, the journey routes must also be displayed in a textual or graphical map visual. This will prove to be a very useful user interface feature for the application.
• Booking status:According to (Mohapatra 2013)This is one of the most important feature of any e-commerce application. To view the status of the ordered products is a basic necessity for any customer centric e-commerce website. Here, the passengers must be offered the chance to view the status of the tickets that they have booked currently. They must be presented with all the detailed information about their bookings. If the user chooses postal servicing for obtaining the tickets then the order status must be updated on the user’s portal at dispatch, en-route and delivery instances. For passengers who have got their tickets in waiting list must also be notified with updates about their booking status. Booking status is a method that helps to keep the client content at hours of mistrust or order complications. If the customer feels that he is being cheated or a delivery is being late, this feature will allow the users to view the real-time status and gain comfort about the same.
• Price Charts: The price-chart of the entire train routes must be displayed on the web portal when a user logs in. This will help them to plan their long journeys according to the price. The price chart should have two different sections. First where the distance to and from a particular station to another shall be depicted alongside the price for the tickets. This will include price for both the children and the adults. In addition, a price calculator can be added that will allow the system to calculate the net price of the bookings made under a particular profile. This will keep track of the number of tickets bought by the individual, the price of each depending on the number of adults or minors (Hetrakul and Cirillo 2014).
• Booking confirmation:Through this feature, the customer must be made aware of the bookings they made just before they proceed with the payment procedure. This will help them to confirm that they have not made any mistake while in the process.
• Ticket collection and delivery options: The application should decide whether the user is eligible for choosing the ticket delivery by post option. This shall be done by taking into consideration the address of the customer. Ticket delivery by post can only be availed by those passengers who live in Eutopia. For the rest they will have to collect their tickets by visiting the railway counters. Eutopians can also avail this option if they wishes so.
• Payment: This is another very important feature of the system that must be presented with utter precision and security. In the words of Ur Rehman and Coughlan (2013), the security aspects of the system regarding payment and other modules are extremely important and must be considered with utmost priority. A trusted 3^rdparty payment gateway should be implemented into the system that will allow the users to make hustle-free payments. The gateway must allow the users to choose between their VISA and MasterCard for making the payments (Roy and Venkateswaran 2014). Furthermore, the validity of the cards must be judged. The rest will be taken care of by the responsible gateway. Finally, a printable invoice of the tickets should be presented to the user.
• Ticket cancellation or escalation: Through this option, the passengers who have already booked their tickets, will have the ability to cancel their tickets or escalate mistakes that might have been made during the process. The application should provide all necessary details to the user before they proceed with this option. On cancellation of a ticket, the ticket must be made available for the rest to buy, keeping in mind that there is no other individual with a “waiting” ticket status. In such case, the ticket will be assigned to the first person in the waiting queue. For escalated bookings, the management will be informed and they can have the liberty to get back to the client as soon as possible to amend the changes.
• Helpline system: Every computer application must be presented with a well defines set of help options for the clients to communicate with the administrators whenever they face a difficulty. Similarly here, all sorts of options that might be able to help a customer at their hour of doubts and need must be presented. These include an online chat system, where the user can chat with an admin personal and convey their discomforts and gain instant solutions. In addition to that, the use can avail the e-mail help option through which the customer will be given the liberty to mail their issues or feedbacks to the Eutopian Railway authority. Aziz, Kamaludin and Sulaiman (2013), states that in order to provide prompt answers to the most general problems that a new user might face with the application, an FAQ section must be present in the website. This will contain pre-written answers to the most predictive problems that one may face on this website. Finally, the helpline numbers and the links to the social media handles of the website must also be provided. The users can call the respective numbers to discuss their grievances and get prompt solution to their queries. The social media handles will provide a discussion forum for the railway authority. The passengers will be able to share their thoughts openly in these platforms. The authority can make notes of these and then proceed on with the needed changes in their application. This will not only help in the process of improving the website but will also attract more visitors to use the online system for booking their tickets.
• Ticket booking history: All logged in users would be presented with the option to view their ticket booking history. This will include the entire set of tickets that they have booked under the respective profile.
• Favorite Destination: To make bookings simple and more agile, the users can be given the opportunity to add their source and destination stations directly from the list of favorites they have. The list of favorite can be auto generated by the application based on the frequency of the station choices made by the users on a daily basis. This will not only save time for the user but will also provide interface supremacy to the application.
• Administrator Operations: The administrators must be able to login into the backend system and make necessary amendments. These might include price changes, changing the train timings, ticket quantities or may be editing the ticket records of required individuals.
• Access Specifications: Being and open-end application that will be used by both the general customer-end users and the administrators as well, it must have a detailed layout of the access level for each set of entity who are allowed to login into the system. A customer can only book tickets, view train details and enjoy other front end operations, whereas an administrator should have all the prior said operations in addition to making amendments to the underlying information.

The set of requisites that define how a system is supposed to work is known as the non-functional set of requirements. This highlights the overall requirements of any application system. According to Chung et al. (2012), the non-functional requirements of a system helps to understand the reliability, sustainability and security features of a system. The basic non-functional requirements of the Eutopian Railway application are as follows:

1. Accessibility
2. Security
3. Usability
4. Performance

Explanation

• Accessibility: Accessibility defines the reach out features of any website application. Better accessibility means users from all around can access the website aloof of all the versatilities involved. This brings the users closer to the application both emotionally and functionally. An application with improved accessibility traits will preferably remove all barriers that prevent interaction with, or access to websites for the users with disabilities. When sites are correctly designed, developed and edited, all users have equal access to information and functionality. Through this, visually weak people will have a proper opportunity to use the application without much difficulty. The graphics used can be used in one such way that enhance the visibility. Fonts and buttons can be made respectively bigger in size and other graphical design changes can be made.

Technological and geographical accessibility is another concept that must be kept in mind while developing the application. This means that instead of the technological adversities that prevail, people must be able to access the website. The website must not be adhered to any technological barriers. Geographical accessibility should be maintained by allowing the website to be accessed globally irrespective of caste, race or religion. People must be made aware of the presence of the application and be allowed to visit and use the website, whenever and from wherever possible.

• Security: Schäfer and Kummer (2013), saysthat probably the most important non-functional aspect of any online-based platform is its security. Any platform should be judged on the basis of its security measures with utter priority. A web-based platform or any o0ther application that is connected to the internet if not protected with proper security measures can be open to threats from online hackers, spammers and what not. To keep the system protected, several security aspects of the website must be scrutinized and prevented from being illegally accessed. The security threats that are prevalent in this scenario are as follows:

1. Hacking: Hackers all around the world, are trained professionals who have the quality to hack into other’s computers, networks or databases and steal important information which was otherwise meant to be kept private. In this case, several passengers will have their basic identity details and journey routes stored in the website’s database. If this system is compromised to the hackers, billions of individual’s information will be at stake. It is the same case for any public service website (Coleman 2012).
2. Spamming: In this case, spammers can create numerous fake accounts of themselves in the website and tend to use these accounts for illegal purposes. They can prohibit the proper functioning of the website by ignorantly purchasing all tickets for a train journey and then further cancelling them. This is done to spread mockery and humiliation (Spirin and Han 2012).
3. DDOS attacks: Wang  et al (2015), says that this is one such case where the hacker will not tend to rob the website off anything, however they will jam their servers and prohibit user access. DDOS or Distributed Denial of Services attack involves several connected online devices that are collectively called botnets that are used to overwhelm a target website with fake traffic. This overburdens the website server and the website needs to be taken down. Nobody can access the website or the database unless the issue is resolved and the server is made online (Gasti et al. 2013).

Therefore, as it can be seen from the above mentioned that the application and the users’ information can be at great risk. Proper security measures shall hence be implemented before making the website go live. Robling (1982), says that cryptography is one of the main technological procedure that can be used to store the data in the database in an encrypted format.

• Usability: Aziz, Kamaludin and Sulaiman (2013), says usability means how the website is presented to its clients. The user interface and the basic front-end functionalities comes under the banner of usability features of any application. It must be made sure that the application accommodates perfectly in the visibility aspects when accessed from a computer or a mobile device. This suggests that the website must be responsive. A responsive website is the need of the hour for any online business forum (Natda 2013). Moreover, it must the designed must be confined to the use of suitable color and fonts that are soothing to the eye and the theme of the website, keeping in mind the accessibility constraints that must also be addressed. The application should be able to handle erroneous data entry and not lose user’s data at any cost.
• Performance: The application should not startle in its course of execution. All inputs and outputs that have been mentioned in the functionality requirements must be well addressed and tested before being released for the public to use. Testing is a very crucial stage of software or web development (Haanperä and Nieminen 2013). It helps to spot the possible bugs and failures in the developed product and gives a scope for improvement. The website should be tested for its performance during high load and for all types of user interaction. The website should be so designed and developed that the data fetching time for the website is minimum. This will require adequate architecture modelling and the use of proper programming concepts like Object Oriented Programming (Coad, Yourdon and Coad 2012). The type of database must also be determined based on the type of data that is needed to be stored. A relational database can be used to store the basic train related data whereas the customer information alongside the ticket sales data must be stored in NoSQL database for better storability and analysis.

1) New Registration: Users are allowed to create their accounts on the website using their respective identity details. They will also have the option to add their Google accounts to the website by choosing to login into the website using their Google ID and password. However, in this case the website will send a link to the added Gmail address in order to verify the account. The user will need to click on the link and verify their account. The user can also choose to login manually. In this case, the profile details needs to be entered by the user manually. In this case the email verification can be done using any kind of email id and not just a Gmail account. However, in both cases the user must enter their Social Identification ID details. An additional ID verification will take place. Furthermore, in order to verify the Social Identity Number, the website shall check the government databases to verify the number.

Non-functional Requirements

2) Login: The user will be allowed to login into the website system using their already created account. If they have a profile that is connected to their Google account, they will require to login using their Gmail address and password, otherwise they will require to login using the mail id that they had entered manually and the profile’s respective password generated. After logging in they will be provided access to the internal features of the website, otherwise they will only be able to browse the home page of the website. Nevertheless, if the user has supposedly forgotten his or her password, the individual can request for a password change option by clicking on the ‘Forgot Password’ button. This will mail the user with the password and will also prompt the user to change the password for security purposes.

As depicted by the use case diagram, the admin will have access to both the above said features as a backend user. The administrator will have the freedom to add new customer data into the database and will also have the option to login himself and finally forward password change mails to the users, on request.

1) Book Tickets: This use case describes how the user is allowed to use the website in order to buy tickets or make changes to the group of tickets bought in the process. The user will have the freedom to search for trains and book tickets on them. This will further check if the train actually has the number of tickets ordered, available. The users can also choose to add new tickets to their already existing list or remove tickets which they already thought of purchasing.

2) Confirmation: If the tickets are actually available, the user will be provided with a confirmation page about the tickets that they have selected, the number of each and the net price of the same. From here too, they can choose to edit the content of their ticket cart and finally proceed to make the payment.

3) Ticket collection method: The customer will need to choose a method that they would opt in order to collect the tickets as the Eutopian railways currently does not provide e-ticket printing facilities. The users will be given the choice to either get a postal delivery of the tickets or they can opt for the counter collection. In case they choose the postal delivery option, they will require to put in the delivery address. The system will further check the entered address and confirm if the address is from Eutopia. If the address is not from Eutopia, the user will be informed of the same and only the collection at counter option will be presented and activated. In both cases, the user will have to produce the ticket ID and the receipt that has been provided before collecting the tickets from the respective individuals.

Registration/Login Use Cases

4) Payment: The customers will need to make their payments online using the payment gateway portal that the website is to offer. Here the user will enter the payment details and the gateway will take care of the other details of the payment. The system will check if the card details is of a VISA or a MasterCard type. Furthermore, the amount to be paid against the bill will be deducted and the user will be provided an e-receipt. The receipt will consist of all the respective details of the booked tickets. The user can print this receipt and produce them before the respective officials and collect their actual tickets (ur Rehman and Coughlan 2013).

1) Timetable: The users will have the option to view the timetables of various trains that are operated by the Eutopian Railways, daily. The users can set reminders on specified date and times and the website will send emails to the users when the reminder time has arrived.

2) Price Chart and Calculator: This option allows the user to view the various prices that are offered for different journeys, trains and as per routes or distances. The users can opt to view the route maps of the trains and visualize the price according to the distance. A price calculator will also be provided for the user to enter two destinations of their choice and predict the net fare, beforehand (Hetrakul and Cirillo 2014)..

3) Booking history: The customers will have the option to view their ticket booking history whenever they wish, just by logging into the system. They will be provided with the detailed information about all the bookings that they have made in the past from that particular account (Molchanova 2014).

4) Help: The users or customers can seek for administrator help. They will be able to state their problems to the website administrator by posting their queries on the web portal. The query along with all other details will be forwarded to the administrator’s mail id and the user will be replied back with a solution as soon as possible. Users can also choose to study the available FAQs and tutorial information that shall be hardcoded into the web application.

The following classes have been selected using the noun analysis method, to represent a real life instance of the Eutopian Railway Web system:

• Eutopian Railway
• Users
• Customers
• Admins
• Registration
• Login
• Tickets
• General ticket
• Long journey tickets
• Station
• Source Stations
• Destinations
• Payment
• Payment methods
• Ticket Collection
• Counter collection
• Postal Delivery
• Ticket booking history
• Train
• Train time table
• Local Train
• Express train
• Route

Analyzing the above produced candidate class list based on the nouns that are involved in the process, a generalized list can be obtained, which are the essential classes that are finally selected to represent the design under the Object Oriented Programming concept (Coad, Yourdon and Coad 2012). The selected classes and their explanation are as follows:

• Eutopian Railway: The driver class that will initiate the program. The registration and login functions can be implemented through this class instead of designating them as separate classes.
• User: This class will be the parent class that will represent all sorts of users involved with the system.
• Customer: The passengers who will create an account with Eutopian Railways through their website. This will inherit the basic properties of the User class.
• Admin: The administrators, who will have access to all the backend functionalities of the system. This will inherit the basic properties of the User class.
• Booking: This class will keep record of all bookings.
• Ticket: The parent class for all types of ticket.
• General ticket: This will represent the local tickets and will have respective set of members.
• Express Ticket (long-journey): This will represent the express tickets and will have respective set of members.
• Station: A class that will hold the data about all stations.
• Payment: The class that will carry out the payment methods for the customers.
• Delivery: This class will hold the basic delivery information about the tickets being bought by respective customers.
• Postal delivery: Inherit basic values from the Delivery class and implement requisite methods for postal delivery of tickets.
• Counter collection: Inherit basic values from the Delivery class and implement requisite methods for counter collection of tickets.
• Trains: Consist of basic data about the trains enrolled in the system, in general.
• Local trains: Consist of data about the local trains enrolled in the system. It inherits basic data from the Train class.
• Express trains: Consist of basic data about the express trains enrolled in the system. It inherits basic data from the Train class.

Ticket Booking Use Cases

Conclusion

From the above documentation, it can be clearly stated that in order to design a web based application for a railway ticket booking system, several aspects of software designing and development shall be overviewed and implemented. The functional requirement analysis helps to sort out the important functionalities that must be implemented into the Eutopian Ticket booking website. The functionalities have been listed based on the basic needs of any such website, in the mentioned field. The non-functional requirements lists the overall requirements of the system that will help the system to be kept popular among the mass and secured at the same time. The use case designs and explanations assists the reader in a way that will generate a sense of clear understanding of how the system is supposed to work depending upon the underlying functionalities. Finally, the class listing helps the software developer to take up the project and implement the classes in a similar fashion to bring to life a real life entity of the entire project. The adaptation of the object oriented programming concepts are clear from the inheritance structures that have been used within the class designs.

References

Aziz, N.S., Kamaludin, A. and Sulaiman, N., 2013. Assessing web site usability measurement. IJRET: International Journal of Research in Engineering and Technology, 2(9), pp.386-392.

Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J., 2012. Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.

Coad, P., Yourdon, E. and Coad, P., 2012. Object-oriented analysis (Vol. 2). Englewood Cliffs, NJ: Yourdon press.

Coleman, E.G., 2012. Coding freedom: The ethics and aesthetics of hacking. Princeton University Press.

Gasti, P., Tsudik, G., Uzun, E. and Zhang, L., 2013, July. DoS and DDoS in named data networking. In Computer Communications and Networks (ICCCN), 2013 22nd International Conference on (pp. 1-7). IEEE.

Ghosal, S., Chaturvedi, S., Taywade, A. and Jaisankar, N., 2015. Android application for ticket booking and ticket checking in suburban railways. Indian Journal of Science and Technology, 8(S2), pp.171-178.

Haanperä, T. and Nieminen, M., 2013, July. Usability of web search interfaces for blind users–a review of digital academic library user interfaces. In International Conference on Universal Access in Human-Computer Interaction (pp. 321-330). Springer, Berlin, Heidelberg.

Hetrakul, P. and Cirillo, C., 2014. A latent class choice based model system for railway optimal pricing and seat allocation. Transportation Research Part E: Logistics and Transportation Review, 61, pp.68-83.

Kaufman, L.M., 2009. Data security in the world of cloud computing. IEEE Security & Privacy, 7(4).

Kreyszig, E., 1978. Introductory functional analysis with applications (Vol. 1). New York: wiley.

Mohapatra, S., 2013. E-commerce Strategy. In E-Commerce Strategy (pp. 155-171). Springer, Boston, MA.

Molchanova, V.S., 2014. The use of online service booking in tourist activity. European Journal of Social and Human Sciences, (2), pp.75-80.

Natda, K.V., 2013. Responsive web design. Eduvantage, 1(1).

Profillidis, V., 2016. Railway management and engineering. Routledge.

Robling Denning, D.E., 1982. Cryptography and data security. Addison-Wesley Longman Publishing Co., Inc..

Roy, S. and Venkateswaran, P., 2014, March. Online payment system using steganography and visual cryptography. In Electrical, Electronics and Computer Science (SCEECS), 2014 IEEE Students’ Conference on (pp. 1-5). IEEE.

Schäfer, K. and Kummer, T.F., 2013. Determining the performance of website-based relationship marketing. Expert Systems with Applications, 40(18), pp.7571-7578.

Spirin, N. and Han, J., 2012. Survey on web spam detection: principles and algorithms. Acm Sigkdd Explorations Newsletter, 13(2), pp.50-64.

Suki, N.M. and Suki, N.M., 2017. Flight ticket booking app on mobile devices: Examining the determinants of individual intention to use. Journal of Air Transport Management, 62, pp.146-154.

ur Rehman, S. and Coughlan, J., 2013, January. An efficient mobile payment system based on NFC technology. In Proceedings of World Academy of Science, Engineering and Technology (No. 78, p. 1680). World Academy of Science, Engineering and Technology (WASET).

Wang, B., Zheng, Y., Lou, W. and Hou, Y.T., 2015. DDoS attack protection in the era of cloud computing and software-defined networking. Computer Networks, 81, pp.308-319.

Wiegers, K. and Beatty, J., 2013. Software requirements. Pearson Education.