Tele Health Non Functional Requirements

Question: Discuss about the Tele Health for Non Functional Requirements. Answer: Introduction With the modernization and advent of technology cloud based mobile solutions are increasingly becoming the need and requirement for the day to day functioning of many organizations and individual alike. These solutions are being delivered as per the specifications and requirements. This report explores pros and cons of cloud based solutions and mobile solutions. While these means certainly adds to the productivity of any organization, it is very important to ensure that these are implemented properly with right measures in place for information and data security. SDLC- Software Development Life Cycle is also explained in this report. Mobile Based Solutions While internet is an important part and aspect of mobile based solutions, it is not always necessary to utilize these. There are the solutions for its users to make the information and means to access connected to them on their go. With the help of Mobile based solutions event geographical hurdles can be overcome easily. There are a set of components which are used to have access to the Mobile Based Solutions. The first requirement would be Wireless Data Network that is used for the services and solutions, which needs network got the exchange of information between different locations and devices. Next requirement would be wireless data modems, which is needed to connect to any wireless network with no cables. An appropriate mobile device as per the requirements are also needed to on which the solutions can be accessed over or run over. Another important device is middleware that sits between the network and the device. Cloud Solutions Any technological or computing solution which uses cloud solutions uses a grid for the purpose of data storing, data handling and data managing instead of a local machine. These solutions make use of models for growth, planning and distributions. The most common and standard model used is explained below: Software as a Service (SAS): Under this model every facility and the uses are supplied by the solution provider and are them made available to the users over a grid. Grid in most cases is internet. The solution provider, with their services, brings along a set of features and benefits for their clients. Some the features and benefits are explained below: APIs (Simple Application Programming Interface) for incorporation Clients dont need to worry about or arrange for any improvements needed in present or in future Single-to-many model is implemented Centrally-located zone for control of the software Convenient availability of the facilities over web Service Platform Under this model, its comparatively simpler for the client to get the facilities and applications. System upkeep and maintenance is taken care by the service provider and the client dont need to worry about these. There are many feature and benefits of a service platform which are mentioned below: Tool for growth load balancing Multiple tools for facilitation of billing and for payments management Multiple designs for tenant, which offers the ability for all stakeholders to utilize the progress application process. Tools for consumer interaction are established over the internet and these are easy to build, implement and alter multiple UI situations Mutual levels for incorporation of users, facilities and databanks Infrastructure as a Service Under this model cloud computing are provided by subcontracting various tools and devices like hardware, storage, productivity and contribution together along with the grid parts. This model brings, along with it, many remarkable benefits and features. Some of which are mentioned below: Properties for this model are dispersed as a service Price may vary in this scenario basis various factors Active increase is permitted and is made simple Utilizes two or more consumers on one machine or a hardware Cloud and mobile based solutions Data security While the technology has been growing at much faster pace today, threats to data and system security is also growing along with it. Cloud and mobile based solutions are also today exposed to a number of threats from the predators of data and information. Data security issue today has become one of the main issues of discussions and concerns for cloud and mobile based solutions. Access, authorization and authentication control The service provider and the users of these services need to decide clearly regarding the admission, endorsement validation. These are important to ensure reliability and secrecy in the system. For example, if data encryption is part of the security feature then sharing of community keys, mutual keys and personal keys also needs to be decided as well as their security requirements needs to be resolved. Data Ownership and Authority If there are multiple or more clients and owners are involved there might be some problem or issue with the proprietorship its assessment. This needs to be sanctioned along with various data package. Shared Access In cloud based system its fairly common to have Multi-tenant design, which means that there will be many authorized consumers, who will be sharing among themselves various usages means like hardware, storage and memory. This presents itself with a potential exposure risk to the pooled resources and the personal data stored over the cloud. Availability Acceptance of accessibility and errors is a service that all service providers claim to provide. But, there is still a long way to go for these services to be robust. It is still not completely secure. Data Accessibility is one of the most pressing security hazards today. Cloud and mobile based solutions - Strengths Interface: One of the great strength of the mobile and cloud based solutions is the interface as the interface required for the development as well as the one on deployment has strong technology behind it. Maintainability and manageability: These requirements can be easily achieved with the cloud and mobile based solutions. These can be managed easily and these also have a defined structure that doesnt need much maintenance. Portability: There are the solutions for its users to make the information and means to access connected to them on their go. With the help of Mobile based solutions event geographical hurdles can be overcome easily. Reliability: With managed solutions and services, reliable services are something that comes easy through these solutions. Cloud and mobile based solutions Weaknesses Both the cloud and mobile based solutions have safety constraints which affect the data security and also presents with the users, network and device threats. Authorization controls, authentication, defined encryption and access control are the issues that need to be focused upon and prioritized. Denial of service, account hijacking, malware attacks, data loss and data breach are some of the security issues, which are very common with cloud and mobile based solutions. Strength weaknesses basis the Non-functional Requirements - evaluation Non-functional requirements explain the overall attributes and qualities of the resulting system. Restrictions are applied by non-functional requirements on products which are in process of development or are developed. Each and every external constraint that the product needs to meet is specified by the non-functional requirements. Examples of non-functional requirements are: safety, performance, security, reliability and usability. Non-Functional Requirements They are divided into below classifications as per the IEEE: Resource Requirements Quality Requirements Safety Requirements Acceptance Requirements Maintainability Requirements Reliability Requirements Portability Requirements Documentation Requirements Verification Requirements Operational Requirements Interface Requirements Performance Requirements They are also divided into External, Product and Process Requirements. External Requirements consists of Interoperability Requirements, Economic constraints and Legal constraints. Product requirements comprise of Safety, Reliability, Usability and Efficiency Requirements. Efficiency requirement is further divided into performance and capacity requirements. Process requirements comprise of Standard, Implementation and Delivery Requirements. Product Requirements: These are the requirements in which all features, which is required to be possessed by system are clearly mentioned. NFRs play an important role in Critical Systems. Following are key principles of Critical Systems: Safety Critical Systems - There is a danger to human life. Business Critical Systems - Failure has caused significant economic damage. Mission Critical Systems Abortion of mission is allowed Following are the requirements for Critical Systems: Security: There needs to be security requirements to ensure that any unauthorized users are denied access and no unauthorized data accesses or transfer is allowed. It also ensures that the data is completely safe from any accidental damage or malicious attack. Performance: This mainly is reflection of the processing speed of operations of a system. Performance requirements comprises of Availability, Throughput and Response Requirements. Availability Requirements ensures that the system is accessible to the services which are requested by the end-users. Throughput requirements define how much accomplishment has been done by the system within a time interval. Response requirements describes how an efficient system should respond to the input. Usability: These requirements discusses about the ease for the user to learn how to interpret output of the system, how to prepare inputs. Error messages, well-formed graphical interfaces, helping facilities and well-structured user manuals are included in Usability Requirements. Safety: These requirements are the requirements where non-safe situations are not considered from all possible systems solution. Reliability: Reliability is defined as performance of function in specific and defined conditions in particular interval of time. Predictive SDLC With the help of SDLC- Software Development Life Cycle proper steps to develop software is defined. Predictive SDLC is a organized approach. It defines the following steps: Planning Requirement gathering and analysis Design Development and Deployment Testing and Debugging Reporting Maintenance (Okoli, 2016) There are a few pros and cons which are associated with this approach. Following are the advantages that this approach extends: Commonly known and found issues are tested before corrective actions are taken It offers stability. This due to the fact that any next step is begun only once the previous one is completed Covers all of the requirements, which are defined properly Good fit for mission critical functionality Focus on structure There are a few disadvantages that are with this methodology. Following are the disadvantages mentioned: Objectives need to be defined in advance All requirements need to be in place else it cannot function well Here testing is carried much later during finishing stages which creates space for error in initial stages. Adaptive SDLC It is a methodology, which executes the software development on the ad-hoc basis. It doesnt follow any structured approach. It is a plan which is driven in nature instead of structure driven. Following are the advantages of adaptive SDLC: Feedback is actively considered and applied Represents a rapidly changing industry Has flexible timeline It is easily adaptable to the changes There are a few disadvantages as well with the adaptive SDLC, which are mentioned below: The project may easily go off track if the customer representative isnt sure of what exact outcome that they are looking of. Lack of emphasis on documentation and designing It is difficult to evaluate the effort required in the project Conclusion Mobile and cloud based solutions are very common in the present era and have the set of advantages and disadvantages. These are reliable and portable solutions but suffer from the drawbacks of safety and security in terms of the data protection and information security. Adaptive software development life cycle has been suggested to develop the mobile and cloud based solutions as it is plan driven in nature and can adapt to the changes of the industry. References Iskwiki.upd.edu.ph. (2016). Mobile Solutions - iskWiki!. [online] Available at: https://iskwiki.upd.edu.ph/index.php/Mobile_Solutions#.VzXsXTB97IU [Accessed 13 May 2016]. Okoli, C. (2016). 1st ed. [ebook] Available at: https://chitu.okoli.org/media/pro/research/pubs/OkoliCarillo2010IJAESD.pdf [Accessed 13 May 2016]. Grimes, R. (2016). The 5 cloud risks you have to stop ignoring. [online] InfoWorld. Available at: https://www.infoworld.com/article/2614369/security/the-5-cloud-risks-you-have-to-stop-ignoring.html [Accessed 13 May 2016]. SearchCloudComputing. (2016). What is SPI model (SaaS, PaaS, IaaS)? - Definition from WhatIs.com. [online] Available at: https://searchcloudcomputing.techtarget.com/definition/SPI-model [Accessed 13 May 2016]. Staff, V. (2016). Top 10 cloud computing risks and concerns. [online] V3.co.uk. Available at: https://www.v3.co.uk/v3-uk/news/2343547/top-10-cloud-computing-risks-and-concerns [Accessed 13 May 2016]. Support.rackspace.com. (2016). Understanding the Cloud Computing Stack: SaaS, PaaS, IaaS. [online] Available at: https://support.rackspace.com/white-paper/understanding-the-cloud-computing-stack-saas-paas-iaas/ [Accessed 13 May 2016].