System Analysis PG - Review of cloud-based solutions

Requirement

This is the final part of the Tele-Health project. You need to answer these questions within the context of that project.
Mobile and cloud based solutions should be investigated. Furthermore, data security also needs to be further investigated, which includes data ownership, data security in the cloud and who has access permission, and to what level of access, etc.
Non-Functional Requirements
• This sets out the critical system qualities, system interfaces, user interface requirements, and system constraints. 
• Use to ‘FURPS+’ acronym as reference, and ensure you at cover the non-functional aspects of the acronym, Usability, Reliability, Performance and Security.
Review of cloud-based solutions
A review of strengths and weaknesses of cloud based solutions. Taking into consideration the environment in which the solution would be deployed.
SDLC Approach
Write brief description of the Pros and Cons of approaching the project using the ‘Predictive’ SDLC, then the Pros and Cons to approach the project as an ‘Adaptive’ SDLC. Then recommend either Predictive or Adaptive to the SDLC for the project and briefly describe why.

Solution

NON FUNCTIONAL REQUIREMENTS

The non-functional requirements of the system that will be covered are:

1.    Interface requirements

  • a.    There should be a login screen for the medical experts and other staff

  • b.    There should be form for filling up patient info and other medical service details

  • c.    There should also be form to add data about the employees

  • d.    The interface should be user friendly and use general English language.

At Allassignmenthelp.com the students can get the best computer network assignment help. Our team of professional experts has expertise in providing the best programming assignment help. Whenever a student places an order on our website we make sure that he or she gets high-quality assignment writing.

2.    Quality requirements: these ensure that the product is of good quality and provide optimum results and on time.

  • a.    Reusability of system components

  • b.    Higher response time

  • c.    Flexibility 

  • d.    Interoperability

  • e.    Adaptability to technological changes

  • f.    Advancement with the new technology 

  • g.    Refined and concise results

3.    FURPS requirements 
a.    Security

  • i.     There should be different access levels for each type of user like admin and employees and the medical staff. Each user must have a unique user id.

  • ii.    Passwords must be of minimum 8 characters and must contain a number and special character. 

  • iii.    There should be sessions that should be timed out so as to avoid exploitation of the resources.

b.    Auditing of the data

  • i.    The patient reports and medical service to be provided should be regularly audited so that to keep a check on whether they are getting the help and solution or not.

c.    Performance

  • i.    Response times of the application should be high because thelocations are remote and there may be emergencies at times.

d.     Query and Reporting times – the system should be able to handle complex queries for patient requirements. 
e.    Reliability: the application should be reliable enough to handle the failures that may occur. For example server failure, network failure, application failure and revert back in minimal time say max 2 hours. Or can handle multiple user requests say 100 to 1000 users at a time.

f.    Recovery: the recovery will done from the backup data. The data on server will be backed up every day so as to avoid any natural calamities or human damages.

  • i.    The recovery time will depend on the data size.

  • ii.    And the backups will be created by the system admin that is, the copy of all the data will be saved.

g.    Compatibility

  • i.    Compatibility with shared applications – it should be compatible with applications like Skype, so that patients can interact with the doctors. 

  • ii.    Compatibility on different operating systems – it should be compatible with OS like MAC or windows.

  • iii.    Compatibility on different platforms – it should be compatible with tablets, phones, desktops etc. 

h.    Documentation: there should be documentation for all types of users so that they can learn to operate the application and other documents for the developers.

  • i.    SRS to record initial requirements: for developers

  • ii.    Technical manuals: for software experts

  • iii.    User manuals: for the staff.

  • iv.    Software visual designs: for software developers

  • v.    Code backup files: for developers

  • vi.    Database design: for database developers

  • vii.    Help guide: for patients and doctors.

REVIEW OF CLOUD BASED APPROACH

Cloud based approach is an approach where the cloud space is integrated with the product or the application. This is done to provide support for various data and space needs, functionality needs, connectivity needs etc. we can say that it provides an internet infrastructure which enables the user to access computing resources anytime from anywhere. Some of the advantages of cloud computing are:

  1. Cost-saving: this refers to the cost saving related to the storage space. The expenses related to capital and operational processes are reduced up to a large extent. Since the infrastructure is online, the cost related to electricity and other operations are also reduced.

  2. Reliability: this platform is much more reliable than any other physical platform present. These provide 24/7/365 and 99.99% availability. Moreover there is support for safeguarding against the failure. That is there are multiple servers so that if one fails or a cluster fails, the other cluster can fulfill the requirement.

  3. Manageability: this means that there will be lesser maintenance at the user end and rather the service provider will be responsible for all online resources. The user can just handle the GUIs and not worry about the network or data storage. Hence making the entire product more manageable.

But along with advantages it has some disadvantages as well. They are:

  1. Downtime: since there are multiple users of the cloud space hence there may be situations where the technical outrages might occur. This can result in taking down the business processes for short spans but yet affecting the processes. Apart from that if the ISP is not available at any time, the resources may not be accessible.

  2. Security: as we can see during our research that the cloud vendors provide agreements for best security yet there are certain risks attached to it. We will have to provide the access to the confidential or important data to the vendor so that they can maintain the data online. Here the security is compromised. Apart from that there can be online intrusions on the data since everything will be on the internet. Or even the loopholes in the system can also be exploited. Although the chances are very less yet there exists these risks. 

  3. Limited control: the actual user will have limited control over the cloud infrastructure because it will be owned and managed by the vendor itself. The user can only access and manage the data, services and the applications but not the backend of the application. So this is also a drawback.

But as we analyse, we can see that the advantages can easily overcome the disadvantages and makes it suitable for products that have large amount of data and require remote access. Hence cloud based approach is one of the best methods which can be used with the product. As we see nowadays that the products should be interoperable on different platforms to reach the remote locations and access remote data. As we see in the scenario that the location is a remote area so it is one of the best options to use the cloud approach. Thus we will be able to provide various health benefits to the customer, interact with them and help them in emergency situations that is, fulfilling the mainpurpose of the product. Moreover it will provide security to the data, integration of the data from varied location on to the cloud space, support for ever increasing data as the customer base increases, support for storing varied data files etc. we can use a public cloud space or even can buy a private cloud for use. 

SDLC APPROACH

The ‘Predictive’ SDLC approach uses the methodology of defining all the requirements at the first stage and then moving to the next stage then. In other words, it is like a build and fix approach where everything is firstly predicted and then fixed into the model. One of the most common model that uses this approach is waterfall model. In this model every step and its prerequisites are pre-defined and followed step by step. The steps that waterfall model follow are:

  • Step 1: Requirements Capture (Business and Software)

  • Step 2: Design (Business and Software)

  • Step 3: Construction

  • Step 4: Integration

  • Step 5: Testing and debugging

  • Step 6: Installation

  • Step 7: Maintenance

Every next phase is dependent on the previous phase for all the information and documents and development as well. Each phase has to be completed in order to begin with the next one. Everything is clear and defined. This type of model are used in the fields where the growth of requirements is minimal. For example: 

  • 1.    Companies that have order processing system.

  • 2.    Small or stable business projects where no frequent changes will occur.

  • 3.    Organization where large number of developers work together. 

  • 4.    Critical software where the requirements are set and will never change. 

Thus this model has some pros and cons as well. It cons are:

  • 1.    No reusability

  • 2.    High cost in redevelopment or adding of features

  • 3.    Unadaptable to changing requirements

  • 4.    The phases have interdependence

  • 5.    Inflexible

  • 6.    Requires reverse engineering to remodel that is doesn’t fit real life scenarios where user requirements change every now and then. 

Place Order For A Top Grade Assignment Now

We have some amazing discount offers running for the students

Place Your Order

But the pros of the model are:

  • 1.    Each phase is complete and consistent

  • 2.    Low development cost

  • 3.    Holistic approach

  • 4.    Lesser cost than the agile approach

  • 5.    Requires just regular maintenances.

  • 6.    Everything is documented.

Next we have ‘adaptive approach or we can say the ‘agile approach’. As the name says, this approach is used for scenarios where the requirements keep on changing every now and then. This approach makes the model more adaptive to the real world scenarios where the user has a new requirement every day. Some of the examples are Scrum and extreme programming. The rules that agile follow are:

  • choosing the Individual views and interactions over software processes and tools

  • prefer working on a software rather than focusing on the comprehensive documentation

  • believes in using customer collaboration rather than doing contract negotiation

  • helping to understand the user needs better and then responding to follow a change rather than following a plan

So as we see that this methodology is more bent towards understanding what the user need rather than what the developer wants to develop. The customer is priority in every aspect rather than the need to just deliver the fixed product. It is more of an interactive approach used for software development. Some of the pros of agile or we can say that the principles that the agile follow are:

  • Customer satisfaction is a priority.

  • Rapid software delivery but it should be a useful one as well.

  • Changes can be easily adapted.

  • Communication with users regularly to add up new requirements.

  • Easy to build new versions

  • Simplicity of design

  • Flexibility

  • Reusability

  • Lesser cost for redevelopment.

  • Developed at a faster speed 

But with pros, there are some cons to the methodology as well. They are:

  • Each rebuilding will have some cost

  • Requires large number of skilled developers

  • Not easy to document every change because they are frequent.

  • Increases the size of the software with time.

So for the Tele-health scenario, we would say that the agile methodology will be best suited because the software will be designed for a large number of users and will require addition of features every now and then as the technology changes because it is technology dependent.
 Moreover, this product requires frequent changes as the number of users increase and the advancement occurs in the field of medicine. So we need a software or a product that is reusable and flexible in nature and can provide varied functionality on different platform like tablets, phones, laptops etc. so considering the features and pros of this method, it is best suited for the development of the product. 

REFERENCES

  • Anonymous. (2011). Opportunities and Challenges of Cloud Computing to Improve Health Care Services. J Med Internet Res. Retrieved from www.ncbi.nlm.nih.gov: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3222190/

  • Anonymous. (n.d.). Advantages and Disadvantages of Cloud Computing. Retrieved from www.levelcloud.net: http://www.levelcloud.net/why-levelcloud/cloud-education-center/advantages-and-disadvantages-of-cloud-computing/

  • Arshdeep Bahga, V. K. (2013). A Cloud-based Approach for Interoperable Electronic Health Records (EHRs). IEEE Journal of Biomedical and Health Informatics , 894 - 906. Retrieved from http://ieeexplore.ieee.org/document/6497443/

  • Johnson, D. W. (2010). Waterfall or Agile? Differences between predictive and adaptive software methodologies. Retrieved from searchsoftwarequality.techtarget.com: http://searchsoftwarequality.techtarget.com/tip/Waterfall-or-Agile-Differences-between-predictive-and-adaptive-software-methodologies

Get Quality Assignment Without Paying Upfront

Hire World's #1 Assignment Help Company

Place Your Order