Journal Of Emerging Technology Engineering -Myassignmenthelp.Com

Question: Discuss About The Journal Of Emerging Technology Engineering? Answer: Introduction The project Telehealth is introduced to improve the quality of the healthcare services of the patients in the rural areas. In rural areas, the professionals are separated by long distance making it tough for them to deliver health related process. The project Telehealth aims at linking the emergency departments of the nearby hospitals to deliver healthcare services via videoconferencing. The project is decided to be implemented in a cloud-based solution. The report discusses the non-functional requirements of the system, the use of hybrid cloud environment and the chosen SDLC approach for the implementation of the Telehealth project is discussed in the following paragraphs (AlZain, et al., 2012). Non-Functional Requirements The non-functional requirements of the system are necessary to consider for proper implementation of the project as it helps in enhancing the system performance. The non functional requirement of the Telehealth project is evaluated on basis of FURPS+ acronym and is described in the following section. Functionality The Telehealth project is to be developed for linking the emergency departments of the hospital and providing the healthcare services through videoconferencing. The major non-functional requirement of the project associated with the functionality of the system is real time data availability. Another major non-functional requirement of the system is considering the throughput of the system that is to be developed (Jain Nandakumar, 2012). This is essential as the system is being developed for providing emergency healthcare services to the patients in the rural areas. Usability The system to be developed should be easy accessible to the people of the rural areas as it aims to serve the patients in the emergency. The major non-functional requirement of the system is easy accessibility of the system. For this, the user interface should be simple. Therefore, designing an easy user interface should be a major non-functional requirement of the system. Reliability The system should be reliable enough to provide management services to the patients of the rural areas. Therefore, incorporating a report option in the system is a major non-functional requirement of the project (Steele Lo, 2013). This will help in identifying and eliminating the bugs from the system. Performance Since the project is to be implemented for providing emergency services to the patients, it is essential for the system to have a high performance rate. Therefore, the system should have a minimum response time for reducing the time for information flow. Therefore, this can be considered as another major non-functional requirement of the system. Supportability The major non functional requirements of the system associated with the supportability of the system is the presence of certain features in the system, such as scalability, testability and configurability. These features are essential to consider as a major non-functional requirement of the system as it will help in modifying or upgrading the system in future (Krupinski Bernard, 2014). Along with these significant non-functional requirements, there are certain secondary non-functional requirements of the project as well. These include a proper design of the system, identifying the physical and software requirements for project. Functional Vs Non Functional Requirements The functional requirements of a system mainly describe the essential functionality of the system, while the non-functional requirements specify the overall characteristics of the system. These characteristics of the system can in enhancing the function or performance of the system. The functional requirement of the system is essential to consider as without these features the system will fail to perform (Chung et al., 2012). Without the non-functional requirements, the system will fail to perform at the optimum level. This is therefore, a major difference between the functional and non-functional requirement of the system. The functional requirement of the Telehealth project includes the developing a secure system for saving the confidential data of the hospitals and the patients. This is associated with enforcement of proper authorization levels and authentication. This requirement is therefore essential to include in the project or else the project will fail. The non-functional requirement of the system on the other hand deals with the different characteristics of the system that is capable of enhancing the system performance. These features include presence of an easy user interface, report button and so on. Absence of these features may decrease the performance level of the system. Therefore, it can be said that both functional and non-functional requirement of the system is essential to consider in this project. Cloud Solution: Use of hybrid Cloud The project has been decided to be deployed in a cloud environment for easier storage and access of the data stored in the system. It is therefore essential to evaluate which cloud environment would be appropriate for deployment of the system. There are three basic cloud environments on which the project can be implemented, which are public cloud, private cloud and hybrid cloud. Out of which, the hybrid cloud environment has been chosen for implementation of the Telehealth project (Li et al., 2013). This is because the hybrid cloud environment has a numerous advantage over the public and private cloud. Public cloud is a cost effective solution and is easy to implement. However, there are number of issues associated with the public cloud environment. One of the major issues with the public cloud environment is that it is vulnerable to attacks (Chen Zhao, 2012). This is because the public cloud can be accessed by anyone, which increases its vulnerability level. This project cannot be implemented in the public cloud environment, as it is associated with the storage of the confidential data of the customers and hospitals. The private cloud environment although eliminates the privacy and the security risk associated with the data storage, it cannot be consider for the project implementation. This is because the private cloud environment limits the accessibility of the data (Galibus Vissia, 2015). Only the specified people are able to access the network of private cloud. Furthermore, the implementation of the system in private cloud is costly as it includes use of a dedicated network. Furthermore, the use of private cloud environment will constrict the reach of the Telehealth system to the people of rural areas. Therefore, it is recommended for the Telehealth project to implement the system in hybrid cloud environment. This is because the hybrid cloud incorporates the features of both public and private cloud environment. The public cloud is furthermore secure enough to store the confidential data of the patients and hospital. The public zone of the hybrid cloud environment helps in easier access of data from the system (Li et al., 2015). The strength and weakness of the hybrid cloud environment are discussed in the following section. Strength of Hybrid Cloud The strength of hybrid cloud and implementing the system in hybrid cloud environment are as follows- The cost of implementation of the system in hybrid cloud environment is comparatively low as the public zone of this cloud environment can be leveraged from a third party vendor. The hybrid cloud environment provides secure data storage and data access thus helping in maintaining the privacy and confidentiality of the data stored (Kulkarni et al., 2012). Organization agility is another major strength of the hybrid cloud environment. The leveraging of the public cloud environment helps an organization in reducing the cost of implementation of the system. The use of hybrid cloud increases the accessibility of the data stored in the system and therefore it will be easier for the patients in the rural areas to use the system. Weakness of Hybrid Cloud The different weakness or disadvantages of implementing the Telehealth project in a hybrid cloud solution are as follows- The hybrid cloud environment has features of both public and private cloud environment. However, the movement of data in and out of the public and private cloud environment is vulnerable to the attacks. This is a major disadvantage of implementing a system in a hybrid cloud environment. Designing the network of the hybrid cloud environment is complex. SDLC Approach The software development life cycle (SDLC) helps in identifying the methodologies a project will be using for its successful implementation (Balaji Murugaiyan, 2012). The SDLC approach systematically describes the planning, process and the testing phase of development of software. The following section discusses the two broad SDLC approaches, predictive SDLC and Adaptive SDLC. Predictive SDLC The predictive SDLC approach is a process of software development in which all the phases of the project implementation is pre determined. The project follows a planned approach in predictive SDLC. In predictive SDLC, the entire project is divided into number of phases. Successful execution of one phase leads to the commencement of another (Rittinghouse Ransome, 2016). An example of predictive SDLC approach is waterfall methodology that deals with systemic development of a software. The strength and weakness of predictive SDLC are as follows. Strength/Pros The project scope remains clear and fixed throughout the project implementation phase. The project is completed within a schedule time in predictive SDLC. The resource estimation is done before the implementation of the project and therefore, there is a very less chance of budget revision in projects implemented by the predictive SDLC. Weakness/Cons The major weakness of using predictive SDLC is that the project cannot be modified after the start of the implementation phase. Furthermore, since the testing phase is executed at the end of the project, project improvising becomes impossible (Mahalakshmi Sundararajan, 2013). Adaptive SDLC Adaptive SDLC is completely different from the predictive SDLC approach. In adaptive SDLC, the project phases are not pre planned and does not follow a set approach. In this approach, the project is implemented according to the project requirements. Strength/Pros The major strength of implementing the project with adaptive SDLC is that the project can be improvised even in the implementation phase. Furthermore, proper and regular testing helps in fixing the bugs before the project release (Tuteja Dubey, 2012). Weakness/Cons There is no fixed schedule of project completion. Possibilities of change in scope may alter the entire project plan and budget allocated for the project. The Approach Chosen: Predictive Since the scope of the project, Tehealth is clear, it is recommended to implement the project in a predictive SDLC approach. This will ensure timely delivery of the project within the approved budget. Furthermore, the size of the project is not very large and therefore, it is better to implement the project using predictive approach. Conclusion Therefore, it is deduced that idea of implementation of the project Telehealth in a cloud environment is an effective idea, as it will increase the accessibility of the data stored in the system. The report gives an overview of the non-functional requirements of the system. The report discusses the different cloud environments and recommends the usage of hybrid cloud for project management. The report further recommends the use of predictive SDLC approach for ensuring project completion within the scheduled time. References AlZain, M. A., Pardede, E., Soh, B., Thom, J. A. (2012, January). Cloud computing security: from single to multi-clouds. In System Science (HICSS), 2012 45th Hawaii International Conference on (pp. 5490-5499). IEEE. Balaji, S., Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30. Chen, D., Zhao, H. (2012, March). Data security and privacy protection issues in cloud computing. In Computer Science and Electronics Engineering (ICCSEE), 2012 International Conference on (Vol. 1, pp. 647-651). IEEE. Chung, L., Nixon, B. A., Yu, E., Mylopoulos, J. (2012). Non-functional requirements in software engineering (Vol. 5). Springer Science Business Media. Galibus, T., Vissia, H. E. R. M. (2015). Cloud storage security. Proc NSCE, 2014, 123-127. Jain, A. K., Nandakumar, K. (2012). Biometric Authentication: System Security and User Privacy. IEEE Computer, 45(11), 87-92. Krupinski, E. A., Bernard, J. (2014, February). Standards and guidelines in telemedicine and telehealth. InHealthcare(Vol. 2, No. 1, pp. 74-93). Multidisciplinary Digital Publishing Institute. Kulkarni, G., Gambhir, J., Patil, T., Dongare, A. (2012, June). A security aspects in cloud computing. In Software Engineering and Service Science (ICSESS), 2012 IEEE 3rd International Conference on (pp. 547-550). IEEE. Li, J., Li, Y. K., Chen, X., Lee, P. P., Lou, W. (2015). A hybrid cloud approach for secure authorized deduplication. IEEE Transactions on Parallel and Distributed Systems, 26(5), 1206-1216. Li, Q., Wang, Z. Y., Li, W. H., Li, J., Wang, C., Du, R. Y. (2013). Applications integration in a hybrid cloud computing environment: Modelling and platform. Enterprise Information Systems, 7(3), 237-271. Mahalakshmi, M., Sundararajan, M. (2013). Traditional SDLC Vs Scrum psychologyA Comparative Study.International Journal of Emerging Technology and Advanced Engineering,3(6), 192-196. Rittinghouse, J. W., Ransome, J. F. (2016). Cloud computing: implementation, management, and security. CRC press. Steele, R., Lo, A. (2013). Telehealth and ubiquitous computing for bandwidth-constrained rural and remote areas.Personal and ubiquitous computing,17(3), 533-543. Tuteja, M., Dubey, G. (2012). A research study on importance of testing and quality assurance in software development life cycle (SDLC) models. International Journal of Soft Computing and Engineering (IJSCE), 2(3), 251-257