Conduct Functional Communication Training -Myassignmenthelp.Com

Question: Discuss About The Conduct Functional Communication Training? Answer: Introduction The project of Telehealth was eventually started for the better development of admittance to the health care in almost all the services in healthcare and hospitals that are not present in urban areas (Henderson et al., 2013). This causes a major problem for any patient, as they are unable to contact to the health experts or hospitals. The professionals or the experts of the healthcare are often separated by the long distances and this particular feature makes the situation absolutely tough for all the patients from reaching out to the particular hospitals or doctors and nurses. It is considered as one of the most common problems in the rustic areas that for the issues in communicating with any hospital or health expert, the patient has significant problems for the completion of their treatments (Wacker et al., 2013). This project of Telehealth was started for this significant reason so that their treatment could be completed without going to any health expert or hospital. The entire initiative was treating the patients by means of tools. This particular report will give a proper explanation on the entire Telehealth project. The report will be helping to understand the various requirements that are non-functional for the project. The major non-functional requirements of Telehealth project are the functionalities, usability, reliability, performance and finally security (Phillips et al., 2016). The project of Telehealth may consider a cloud based solution and the different types of clouds will be described here, which will eventually include all the merits and the demerits of the suggested cloud. The SDLC approach with specific details will also be described here. Non-Functional Requirements of the System Any particular situation can be easily judged with the help of the non-functional requirements of any system. There are various non-functional requirements in Telehealth project (Chen Zhao, 2012). The major non-functional requirements of the Telehealth project are known as FURPS. The full form of FURPS is Functionality, Usability, Reliability, Performance and lastly Security. Functionality The first non functional requirement of Telehealth is Functionality. This is extremely important for the Telehealth project as it describes the complete functionalities of the system (Chung et al., 2012). This particular system requires the basic functions of daily updates and proper data access. The user, who is accessing the data, will be able to understand the entire problem of the patients, only by viewing the data stored in the system. Therefore, this particular requirement is extremely vital. Usability The second non-functional requirement of Telehealth project is usability. This requirement eventually refers to the effortlessness of learnability and proper utilization of any tool or object (AlZain et al., 2012). The important benefit of the project is the simple utilization with excellent efficiency. The project of Telehealth never considers the problem in communication within any health expert or patient. Reliability Reliability is the third most important non-functional requirement of this specific project, namely, Telehealth. The entire system of Telehealth is absolutely reliable and can be easily trusted as all the experts of healthcare and hospitals are real. These professionals are eventually hired for completing the treatment of any patient (Chung et al., 2012). This treatment of the patients is done by audio-visual conferences. The system of patient treatment can be improvised with the help of this requirement. Performances The fourth non-functional requirement of FURPS is the performance. This performance requirement is the most significant criteria for any project (Galibus Vissia, 2015). Since the treatment will be completed with the help of talented healthcare experts it is evident that the entire performance of this Telehealth project would be much better than the system of traditional treatment. Security The last non-functional requirement of FURPS is the security (Jain Nandakumar, 2012). This is again one of the most important needs for any system as if a system is not secured; it is evident that the data or information stored within it is not secured. Telehealth project is extremely secured and there is no chance that the data would be lost. Biometric is the best option for Telehealth. Comparison and Contrast between Functional Requirements and Non-Functional Requirements of the System The functional requirements of any typical project mainly involve those requirements that are related to the functions of the projects (Kulkarni et al., 2012). The calculations, the functional activities, the details of technology, manipulation of data and many more are considered as the functional requirements of a project. Data processing is also considered as the functional requirement. Mostly, the functional requirements are expressed as use case diagrams. The non functional requirements of any project mainly deals with those requirements that are utilized for the judgment of any operation of a particular system. These requirements are often considered as the quality attributes of any system (Chung et al., 2012). The most significant examples of the non functional requirements of a project are accessibility, functionality, performance, operability, usability, portability and many more. The project of Telehealth cannot consider the functional requirements. However, the non functional requirements will be considered. Selection of Cloud Cloud computing is the best technology for transfer of data from one particular location to another. The project of Telehealth was started by a specific group of doctors and nurses for treating the patients, residing in rustic areas (Li et al., 2013). This significant amalgamation of ICT and medical technology will be absolutely useful for the patients. The solution for the project of Telehealth can be improvised with the help of cloud deployment models. Significantly, four specific kinds of cloud deployment models can be utilized. The four kinds of cloud deployment models are private, public, hybrid and community. Private cloud can be defined as the type of cloud that allows data access amongst a restricted group of users. Public cloud, on the other hand, allows data access within no restrictions (AlZain et al., 2012). Amalgamation of private and public clouds is known as a hybrid cloud. Community cloud can be utilized when a restricted group of users having same requirements, is ac cessing the data. The perfect cloud solution for this project of Telehealth is the deployment model of hybrid cloud. Since this particular cloud is the amalgamation of public and private clouds, it has each and every characteristic of these two mentioned cloud deployment models (Li et al., 2015). Telehealth project will be improvised with the help of hybrid cloud. Strengths of Selected Cloud Solution Cloud computing is the safest mode of data transfer via Internet. Each and every kind of deployment model has their own characteristics (Galibus Vissia, 2015). Hybrid cloud has various merits and demerits. The most significant merits of a hybrid cloud deployment model are as follows: i) Security: The important merit of hybrid cloud is security. Transfer of data or confidential information is absolutely safe in hybrid cloud. Most of the popular organizations, utilize hybrid cloud for their data migration (Kulkarni et al., 2012). Moreover, hybrid cloud deployment model is scalable and flexible in nature. ii) Cost Effectiveness: The second important benefit of hybrid cloud is the cost effectiveness. This particular merit or benefit makes this cloud very popular for all the small and medium enterprises or organizations (Chen Zhao, 2012). Moreover, the operational cost of hybrid cloud is extremely small and thus the operations or functions can be claimed as cost effective. Weaknesses of Selected Cloud Solution There are various demerits or disadvantages for hybrid cloud as well. They are as follows: i) Integration of Application: The main weakness of hybrid cloud is the lack of integration of the applications and data. This creates a significant problem when the application is in private cloud and the data is in the data centre, the entire integration of data and application becomes tough (Li et al., 2015). Often it causes data loss and the data cannot be recovered if recovery plan is not present. ii) Compatibility: The second most significant demerit of this hybrid cloud is lack of compatibility. This compatibility across the infrastructure of the hybrid cloud is very difficult in comparison to the private cloud and public cloud. System Development Life Cycle Approach The systems development life cycle approach or the SDLC approach divides the entire cycle of all software into several significant stages (Mahalakshmi Sundararajan, 2013). It is utilized in software engineering for the purpose of describing the planning, testing and implementation of a system. Predictive SDLC approach and adaptive SDLC approach are the two probable approaches for Telehealth project. Description of Predictive Approach The predictive approach of software development life cycle can be defined as the approach that is taken before completing any project. There are various pros and cons of predictive approach and they are as follows: i) Project plan is made perfectly. ii) Project time and scope are properly understood to every member (Balaji Murugaiyan, 2012). i) Alteration of the plan of project is absolutely impossible. ii) Client feedback is never considered. Description of Adaptive Approach The reciprocal of adaptive approach is known as SDLC predictive approach (Balaji Murugaiyan, 2012). This approach is mostly beneficial for the long term projects. There are various pros and cons of predictive approach and they are as follows: i) The plan of the project is modified in every step. ii) Feedback of clients are considered (Mahalakshmi Sundararajan, 2013). i) Predictive SDLC approach is extremely costly. ii) The project scope and the time is not specified. Hence, for the project of Telehealth, the best approach is the predictive approach (Weinstein et al., 2014). Conclusion Therefore, from the report, conclusion is drawn that, the project namely, Telehealth was started with the mission of providing better access to each and every healthcare unit that are present in rustic areas. All the healthcare experts or hospitals are separated by the long distance between patients and them. This has become a major problem for all persons to contact to the health experts and hospitals. It is considered as one of the most common problems in the rustic areas that for the issues in communicating with any hospital or health expert, the patient has significant problems for the completion of the treatments. This project of Telehealth was started for this particular cause so that the patients can be treated easily without any complexities and without even going to the health centres. The application of this project was extremely straightforward that the system will be able to treat every patient by means of technology. This report has provided major details about the non f unctional requirements like security, usability, performance, functionality and usability. Hybrid cloud will be the best solution for this project. Hybrid cloud has several strengths and weaknesses within itself. These strengths and weaknesses will be useful for the project to choose which type of cloud deployment model would be better. The selection of the best SDLC approach is also mentioned here. 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. Henderson, C., Knapp, M., Fernndez, J. L., Beecham, J., Hirani, S. P., Cartwright, M., ... Doll, H. (2013). Cost effectiveness of telehealth for patients with long term conditions (Whole Systems Demonstrator telehealth questionnaire study): nested economic evaluation in a pragmatic, cluster randomised controlled trial.Bmj,346, f1035. Jain, A. K., Nandakumar, K. (2012). Biometric Authentication: System Security and User Privacy. IEEE Computer, 45(11), 87-92. 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 MethodologyA Comparative Study.International Journal of Emerging Technology and Advanced Engineering,3(6), 192-196. Phillips, V. L., Vesmarovich, S., Hauber, R., Wiggers, E., Egner, A. (2016). Telehealth: reaching out to newly injured spinal cord patients.Public health reports. Wacker, D. P., Lee, J. F., Dalmau, Y. C. P., Kopelman, T. G., Lindgren, S. D., Kuhle, J., ... Waldron, D. B. (2013). Conducting functional communication training via telehealth to reduce the problem behavior of young children with autism.Journal of developmental and physical disabilities,25(1), 35-48. Weinstein, R. S., Lopez, A. M., Joseph, B. A., Erps, K. A., Holcomb, M., Barker, G. P., Krupinski, E. A. (2014). Telemedicine, telehealth, and mobile health applications that work: opportunities and barriers.The American journal of medicine,127(3), 183-187.