Compute Electronics Electrical Technologies -Myassignmenthelp.Com

Question: Discuss About The Compute Electronics Electrical Technologies? Answer: Introduction Telehealth project is introduced for enhancing the quality of health services in rural areas and the public hospitals of the rural regions by overcoming the challenge of long distance. Telehealth can provide convenient, cost-effective and real-time healthcare services. Telehealth project aims to enhance the patient outcomes (Steele Lo, 2013). Cloud based solutions will provide on-demand services and resources over the Internet in a cost-effective manner. This report discusses the non-functional requirements of Telehealth, strengths and weaknesses of cloud based solutions. It also suggests an SDLC approach for the project after discussing the pros and cons of predictive and adaptive SDLC approach. Non-Functional Requirements of the System Non-functional requirements can be considered to be the main qualities that need to be possessed by the system. It also specifies the constraints of the system. Non-functional requirements of a system focus on the system behaviour and how it works (Ameller et al., 2012). The Telehealth project has certain non-functional requirements that are discussed below. Functionality Functionality is one of the main requirements of the Telehealth project that identifies user needs and preferences. Telehealth should be able to improve the healthcare quality in the rural regions by providing high quality health services with the help of the cloud platform. It should overcome the issues that are faced by healthcare professionals as well as consumers such as time, cost and long distance via remote patient monitoring over the cloud platform. Telehealth project should create links among urgent health care centres in the rural areas with emergency departments at the hospitals through video conferencing. Flexibility and robustness are also included in the functionalities of Telehealth. Usability Usability can be considered to another main non-functional requirement of the Telehealth project. It can be considered to be the ease with which the healthcare professionals and the patients will be able to learn about the cloud based system of Telehealth and operate it. Accessibility, consistency and interface aesthetics are the main usability requirements of the Telehealth project. Telehealth cloud platform should be able to eliminate the communication gap that exists in the healthcare services by developing user-friendly and interactive cloud based portals that can be used by the patients and healthcare professionals in an effective manner (Chung et al., 2012). Telehealth project should eliminate the problem of distance via video conferencing and cloud platforms. Reliability Reliability of Telehealth will depend on its recoverability, accuracy and availability. Reliability is one of the most important non-functional requirements because Telehealth will deal with the lives of the patients. Telehealth cloud based system should have less possibility of failure, low downtime and should quickly recover in case of a failure. The Telehealth system should produce consistent result and improve the healthcare services via video conferencing and mobile patient monitoring. Telehealth system should be able to quickly recover health related data from the cloud storage during any emergency and should backup data on a regular basis. Performance Performance of Telehealth will depend on its throughput and response time (Chung et al., 2012). The After-Hours Urgent Healthcare Telehealth project should aim at providing uninterrupted high quality emergency services to the users. Telehealth services such as video conferencing should have a fast response time. Telehealth system should provide high quality real-time telecommunication facility to the patients and the healthcare professionals. The performance of Telehealth will be high when its cloud platform will have high throughput with quick response time. Security Security is an important non-functional requirement of the Telehealth project. Telehealth devices and cloud platforms will be used for conducting video conferences and remote patient monitoring. Any unauthorized access to the patient details and health records can adversely affect the treatments of the patients. Security policies and authorization process should be used for protecting the Telehealth devices and cloud platforms. The patient health details should be protected by implementing biometric authentication and passwords. Constraints Telehealth project will also have certain constraints. Project deadline is the main constraint of this project. Another constraint of Telehealth project will be the decision regarding choosing an appropriate cloud platform. Functional Requirements and Non-Functional Requirements Non-functional requirements deal with the system behaviour but functional requirements focus on the functions that should be performed by the system. Functional requirements mainly deal with the technical specifications of the system without which a system cannot be developed. One main functional requirement of Telehealth will be that the cloud platforms must be able to store voice records along with written documents. Authentication as well as authorization is an important functional requirement that allows the healthcare professionals to access the information of various patients but allows the patients to access only their own details (Kvedar, Coye Everett, 2014). Biometric authentication will enable users to access data based on their details. Non-functional requirements judge the system after delivering to the clients but functional requirements gives a description of the services of the system. It helps the systems to operate in smoothly. Functional as well as non-functional r equirements are required for proper implementation of the system. Cloud based solution of the Telehealth Project: Hybrid Cloud The Telehealth project focuses on enhancing the quality of healthcare services by overcoming the issue of long distance and providing after-hours urgent healthcare services in case of any emergency. The deployment environment chosen for Telehealth is the hybrid cloud deployment model because of the additional benefits that it provides over the public and private deployment environments. Hybrid cloud environment combines a public as well as a private cloud environment. Public cloud platforms are accessible to all the people without any restrictions. One of the major concerns of public cloud deployment model is the security (Chen Zhao, 2012). Telehealth system will deal with sensitive data of the patients and their health records. Urgent care centres will be able to link different emergency units of the nearby hospitals through video conferencing (AlZain et al., 2012). Public cloud will cause leakage of the confidential data. Therefore, a public cloud deployment environment would not be a suitable solution for the Telehealth project. Private cloud deployment model has several advantages. It also has certain constraints such as high deployment cost and vendor lock-in. To deploy the Telehealth project in the rural areas and across the state the cost of implementing private cloud environment will incur high cost. It would not be a feasible solution. The urgent care services will be provided only in case of emergency situations. If the after-hours urgent healthcare services are not required regularly due to reduction in the rate of emergency cases then the private cloud system would remain under-utilized and incur huge loss (Jadeja Modi, 2012). Therefore, optimizing the resource utilization would become a challenge for the Telehealth project. Vendor lock-in is another issue that would not allow Telehealth to migrate to another vendor. Therefore, private cloud deployment is not a suitable solution for the Telehealth project. Strengths Hybrid cloud is considered to be a cost-effective solution for organizations. It reduces the ownership cost and also improves the cost efficiency of the organization (Goyal, 2014). The hybrid model will enable the Telehealth services to use a pay-per-service model and save its cost. Hybrid cloud environment can securely store and access sensitive data. It can maintain data confidentiality and integrity (Li et al., 2015). The Telehealth project needs to maintain integrity and confidentiality of the health records and patient details. Therefore, Telehealth system will get benefitted from the improved security features of the hybrid cloud. Hybrid cloud will enable the Telehealth system to overcome technical barriers and minimize trade-offs. It will be able to improve the performance of the system (Garrison, Kim Wakefield, 2012). The mix of public cloud will enhance the scalability of the hybrid cloud environment. Hybrid cloud environment enhances the flexibility of the business. Weaknesses One of the main challenges of a hybrid cloud environment is ensuring that the private and public cloud services are complying with the security policies of organizations. Hybrid cloud environments are vulnerable to external attacks (Goyal, 2014). The movement of data occurs between the private and public cloud. An unauthorized access during the transmission of data between the private and public cloud can cause loss of confidentiality, privacy and integrity. Cost of implementing hybrid cloud models is expensive due to the presence of private cloud. It requires more cost as compared to the cost of implementing public cloud models. The presence of private and public cloud increases the networking complexity in an organization. Organizations are dependent on their internal IT infrastructure in case of outages. SDLC Approach SDLC or software development life cycle approach can be considered to be a conceptual model for describing various phases that are required for software development. There are several SDLC models such as waterfall and spiral models. The SDLC approach starts with feasibility analysis and ends with system testing. Predictive SDLC Waterfall models falls under the category of predictive SDLC approach. Predictive SDLC approach is used in developing projects where the project aim and phases are clearly defined. This approach is appropriate for developing similar systems where no new requirements will be needed (Balaji Murugaiyan, 2012). The project requirements and phases are clearly defined and fixed. Pros of Predictive SDLC It has an organized structure that will ensure project completion as per the project plan and schedule. Possibility of project delay is low in a predictive SDLC approach (Sakul-Ung Chutimaskul, 2017). The pre-determined phases of the projects will ensure effective tracking of project activities. It will also help in tracking the progress of a project. The project failure risk is low as the project aim and requirements are clear. Cons of Predictive SDLC It is not a flexible approach. Additional features cannot be added as it will cause disruption of the existing project plan (Mahalakshmi Sundararajan, 2013). Movement from one phase to a previous phase is not possible in a predictive SDLC approach. Absence of feedback mechanism can cause system failure leading to huge loss. Adaptive SDLC Adaptive approach is suitable for new projects where the project aim and requirements are not clearly defined. This approach does not need to follow sequential steps. There is scope for adding new features as per the change in requirements. Pros of Adaptive SDLC It is a flexible approach. It is capable of adapting to changing project needs (ztrk, 2016). Presence of a feedback mechanism helps in improvising the project plan and the system. There is less possibility of incurring huge loss due to system failure as the phases and project plan can be modified with the changing demand and need of the project. Cons of Adaptive SDLC Lack of proper documentation process causes issue in tracking the project activities and the project progress. Lack of pre-determined phases and plans can cause delay in the project completion. Recommendation The Predictive SDLC approach will be suitable for the Telehealth project because the project scope and requirements are clearly defined. The organized structure of the predictive approach will help in completing the project within a specified time. Conclusion This report concludes that the Telehealth project must implement a hybrid cloud environment as it is cost-effective and provides better security to the data. Furthermore, the project is suggested to be implemented by using a predictive SDLC approach for ensuring completion of the project without any delay. 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. Ameller, D., Ayala, C., Cabot, J., Franch, X. (2012, September). How do software architects consider non-functional requirements: An exploratory study. InRequirements Engineering Conference (RE), 2012 20th IEEE International(pp. 41-50). 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. InComputer 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. Garrison, G., Kim, S., Wakefield, R. L. (2012). Success factors for deploying cloud computing.Communications of the ACM,55(9), 62-68. Goyal, S. (2014). Public vs private vs hybrid vs community-cloud computing: A critical review.International Journal of Computer Network and Information Security,6(3), 20. Jadeja, Y., Modi, K. (2012, March). Cloud computing-concepts, architecture and challenges. InComputing, Electronics and Electrical Technologies (ICCEET), 2012 International Conference on(pp. 877-880). IEEE. Kvedar, J., Coye, M. J., Everett, W. (2014). Connected health: a review of technologies and strategies to improve patient care with telemedicine and telehealth.Health Affairs,33(2), 194-199. 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. Mahalakshmi, M., Sundararajan, M. (2013). Traditional SDLC Vs Scrum MethodologyA Comparative Study.International Journal of Emerging Technology and Advanced Engineering,3(6), 192-196. ztrk, V. (2016). Flexible and Adaptive Life Cycle Framework for Software Development.JSW,11(9), 943-951. Sakul-Ung, P., Chutimaskul, W. (2017, February). A predictive model for successful software development projects with information technology strategic alignment. InProceedings of the 6th International Conference on Software and Computer Applications(pp. 39-45). ACM. Steele, R., Lo, A. (2013). Telehealth and ubiquitous computing for bandwidth-constrained rural and remote areas.Personal and ubiquitous computing,17(3), 533-54