Project Research and Investigation Report Online Transactions

Question: Describe about the Project Research and Investigation Report for Online Transactions. Answer: Introduction Development of an OTP system is an important part of secure online payment methods. The system is developed based on some requirements or future insights that may enable the online transactions popular among regular subscribers because of useful and time saving applications (Yigitbas et al. 2016). The main objectives of development of this system are to enhance the security and accuracy of the online payment methods without involving real cash. The OTP system requires a number of features the payment method and the details are to be shown clearly so that the subscriber can understand properly; the interface should be user friendly and less time consuming, so that more users are interested in using the system. In this report, a project suggestion has been provided for the development of a OPT system by selecting the most suitable methodology. Project Research and Investigation: A Report on One Time Password (OTP) Project Existing Systems There are many existing systems where OTP is currently used. Some of these are as follows. Banking Transactions and ATMs Nowadays, One Time Password system is widely used in online transactions that involve the users bank account. The user buys some product from an online retail shop and the payment mode is online. Hence, the user will pay online using his credit / debit cards serial number (Tandon et al. 2013). However, without any authentication, the payment cannot be done. Hence, the bank sends a One Time Password (OTP) to the users registered mobile number that he must enter during the last stage of payment so that the process can go ahead. However, this password has a short life span (about 5-10 minutes) after which, it expires and the transaction fails. This is also applicable during withdrawal of cash from an ATM. Password Authentication in Emails and other Online Accounts OTP is also widely used in authentication of passwords in emails and other online accounts. During a time, a user may chose to change his password of his account. However, this can also be done by an unethical user. Hence, for authentication, the website sends an OTP to the users personal email or mobile number for authentication. Generally, this type of OTP does not have a short life span but failure to use it for authentication may result in temporary lock of the account (Huang and Huang 2013). The same procedure is also followed while creating a new account. For example, a user chooses to start an account in Facebook. Accordingly, he does by using his email account and / or mobile number. For authentication, Facebook will send him an OTP to his mobile number or email account that he will have to use to authenticate and get started with his account. Security Token Nowadays, OTP is also used for authentication of security tokens. Security tokens are electronic key for access to something that is protected. In this process, a user registers his fingerprint or retina scan that will be the authentication method for access (Devi et al. 2014). However, in order to authenticate whether the right person is giving the scans, an OTP is sent to the phone number of the user. Using this, he can confirm his identity and verify his access. Methodologies There are different methodologies available for software development. Some of them are as follows. Agile Software Development Methodology Agile Software Development Methodology is conducted through a series of iterations for the execution of large scale software development projects. Each iteration is actually taken as a miniature project as it takes a lot of steps and if one error occurs, the iteration is repeated (Weber 2016). This is why, agile methodology is an extremely lengthy process that takes up huge amount of time and resources. However, the main advantage of this methodology is that the outcome is always error-free. Due to its lengthy process and change of internal coding, this is not suitable for user interface development. Dynamic Systems Development Model Methodology This methodology is a modification of agile methodology in which the iterations are modified and changed with the changing demands of the system or client. For this purpose, the overall development project is divided into several parts, each having a particular deliverable (Eason 2016). At the successful completion of one iteration, that deliverable is quickly released from the overall project structure. Hence, the products from the project are delivered faster that agile methodology. Extreme Programming (XP) Methodology This is special kind of methodology that is specifically used in unstable environments. This is because, this particular methodology provides a lot of flexibility support and hence, developments can be done in unstable environments (Park, Kim and Jeong 2013). However, the main issue of this methodology is that the change in requirement in the last stages of development inflicts a very high amount of cost as the deliverables are pre-set in this methodology. Joint Application Development (JAD) Methodology The Joint Application Methodology or JAD is a methodology that is conducted through joint venture of the vendor and the client. In other words, the client and the vendor management team go through some meeting sessions to clarify the exact requirements of the clients (Despa 2014). After that, a series of workshops are conducted for preparation of the project plan. In these workshops, the project deliverables are prepared in the available technical setup and the developers prepare themselves for final development. Hence, this methodology is more business oriented rather than technical and hence, it is applicable for user interface designs. Rapid Application Development (RAD) Methodology This methodology is emphasized on the planning of the processes to be conducted rather than on the planning of the project (Dissanayake et al. 2014). Hence, once the deliverables are set, the project planning documentation is prepared and the methods to be used for executing the methodology is followed from the documentation. Justification for Chosen Methodology The chosen methodology is Joint Application Development (JAD) Methodology as it is the most suitable methodology for the development of the user interface system. This methodology is based on the client requirements rather than the functions proposed by the company. The project planning of the development using JAD is developed through a series of workshops (Gilbert 2016). When the company (vendor) comes in a mutual agreement with the client regarding the user interface, the development is initiated. As the deliverables is set by mutual agreement with the client, the development can be done with a specific end goal and it is the most suitable methodology for user interface development. Technologies and Resources Required The JAD methodology can be easily conducted in the latest technical setup available to the developers. However, without some workshops, execution of the methodology is not possible. In the workshops, the project is planned using documentation, worksheets, diagrams, and props that are useful for documenting and planning the flow of work using this methodology (Eason 2016). After analyzing the client requirements, the developers need to go through some workshops for preparation of the project plan. In these workshops, the project deliverables are prepared in the available technical setup and the developers prepare themselves for final development. The JAD methodology significantly reduces the cost and time required for preparation of the system for developing user interface. Moreover, changes of wrong iterations are reduced as workshops are conducted prior to the actual development. The resources required for the JAD methodology are as follows. Resource Function Technically Updated Computers For the development of the user interface according to requirement Interface Tools For creating and adding different elements in the designed interface Debugging Softwares For identifying and removing bugs in the user interface System Firewall For protecting the system from loss of work due to external and internal attacks Testing Systems For testing the developed interface in different systems and software environments Conclusion From the discussion in the report, it can be concluded that the best methodology for OTP development is Joint Application Development (JAD) Methodology as it is the most suitable methodology for the development of the user friendly and secure system. The OTP system requires a number of features the payment method and the details are to be shown clearly so that the subscriber can understand properly; the interface should be user friendly and less time consuming, so that more users are interested in using the system. One Time Password system is widely used in online transactions that involve the users bank account. OTP is also widely used in authentication of passwords in emails and other online accounts. During a time, a user may chose to change his password of his account. However, this can also be done by an unethical user. Hence, for authentication, the website sends an OTP to the users personal email or mobile number for authentication. Nowadays, OTP is also used for authenticati on of security tokens. Hence, the most suitable methodology must be chosen in order to develop the OTP system. JAD methodology is based on the client requirements rather than the functions proposed by the company. The JAD methodology can be easily conducted in the latest technical setup available to the developers. In the JAD workshops, the project is planned using documentation, worksheets, diagrams, and props that are useful for documenting and planning the flow of work using this methodology. References Despa, M.L., 2014. Comparative study on software development methodologies.Database Systems Journal BOARD,5, p.3. Devi, D.S., Thilagavathy, K., Vaghula Krishnan, S., Harish, S. and Srinivasan, R., 2014. Integrating OTP authentication service in openstack. InAdvanced Materials Research(Vol. 984, pp. 1309-1317). Trans Tech Publications. Dissanayake, N.R., Dias, G.K.A., Al-Shalfan, K.A. and Al-Shalfan, K.A., 2014. What does the AJAX Rich Internet Applications need to Support the Rapid Application Development?.A Vision System for Vehicle Driving Safety Assistance, p.1. Eason, O.K., 2016. Information Systems Development Methodologies Transitions: An Analysis of Waterfall to Agile Methodology. Fischer, H., Yigitbas, E. and Sauer, S., 2015, September. Integrating Human-Centered and Model-Driven Methods in Agile UI Development. InINTERACT 2015 Adjunct Proceedings: 15th IFIP TC. 13 International Conference on Human-Computer Interaction 14-18 September 2015, Bamberg, Germany(Vol. 22, p. 215). University of Bamberg Press. Gilbert, A.L., 2016. 25 Information Technology Transfer: The Singapore.Technology Transfer in the Developing Countries, p.320. Halbrgge, M., Quade, M., Engelbrecht, K.P., Mller, S. and Albayrak, S., 2016, September. Predicting user error for ambient systems by integrating model-based UI development and cognitive modeling. InProceedings of the 2016 ACM International Joint Conference on Pervasive and Ubiquitous Computing(pp. 1028-1039). ACM. Huang, C.H. and Huang, S.C., 2013, October. RFID systems integrated OTP security authentication design. InSignal and Information Processing Association Annual Summit and Conference (APSIPA), 2013 Asia-Pacific(pp. 1-8). IEEE. Khaddam, I., Barakat, H. and Vanderdonckt, J., 2016. Enactment of User Interface Development Methods in Software Life Cycles. InROCHIINTERNATIONAL CONFERENCE ON HUMAN-COMPUTER INTERACTION(p. 26). Min, R., Patern, F., Arrue, M. and Abascal, J., 2016. Integrating adaptation rules for people with special needs in model-based UI development process.Universal Access in the Information Society,15(1), pp.153-168. Park, G.Y., Kim, Y.M. and Jeong, C.H., 2013. Development of Testing Platform for Digital I and C System in Nuclear Power Plants. Rambhia, A., Syed, H. and Doran, E., Microsoft Technology Licensing, Llc, 2015.Contextual search using natural language. U.S. Patent Application 14/875,143. Tandon, A., Sharma, R., Sodhiya, S. and Vincent, P.D.R., 2013. QR Code based secure OTP distribution scheme for Authentication in Net-Banking.International Journal of Engineering Technology, pp.0975-4024. Weber, E.V., 2016. Performance Learning of Agile Methodology Using Paired Courses of Systems Analysis and Design and Web/Mobile Programming. InProceedings of the EDSIG Conference ISSN(Vol. 2473, p. 3857). Yigitbas, E., Kern, T., Urban, P. and Sauer, S., 2016, June. Multi-device UI Development for Task-Continuous Cross-Channel Web Applications. InInternational Conference on Web Engineering(pp. 114-127). Springer International Publishing.