Non-Functional Requirements
The Information Systems are the part of Information Technology that includes different applications, I/O devices, database and many more for carrying out organizational activities. The use of the information systems in the healthcare industry is done in a very large scale and it is continuously improving (Teixeira et al., 2014). One of the examples of Information Technology in this industry is EHR or electronic health record. EHR is responsible for storing the patient data. The cloud based systems are mostly popular for its ability to allow the user connect to the system database or function remotely. For implementing such system effective and successfully, a SDLC or System Development Life Cycle have to be used.
Within this study, the non-fictional requirements of the proposed My Health Record system along with the best cloud based solution for the system has been included. In addition to that, the study holds the information regarding the best approach for system development such as adaptive or predictive.
The non-practical necessities is thought to be the framework prerequisites that propose attributes that are utilized for judging the framework. The essential non-useful prerequisites that has been chosen for the framework are ease of use, unwavering quality, execution and security.
- Usability: It expresses the actualized framework will be anything but difficult to utilize. The clients of the My Health Record framework can utilize the framework to complete all the coveted operations, for example, information discovering, wellbeing information input and some more (Khan et al., 2016).
- Reliability:The dependability is the center of a viable framework. Keeping in mind the end goal to be solid, the framework will gather information through some approval conventions and give precise information to the client (Meulendijk et al., 2014). The framework will be kept up occasionally to guarantee that no blunder happens in its operation.
- Performance:The execution of the framework is exceptionally critical for giving the customer acceptable administration. The framework can perform a huge number of operations at the same time (Farzaneh et al., 2014). The framework capacities will be produced such that it will require the insignificant investment for executing.
- Recoverability:As far as cloud based framework, losing information is a typical term. The recoverability alludes to the way toward remembering lost information from an alternate information stockpiling. My Health Record application will be associated with an information reinforcement framework so that the lost information can be recuperated inside negligible time (Meulendijk et al., 2014).
- Security:The security is the term that characterizes how much the information of the client is sheltered inside the framework. The framework will have the capacity to avoid a large portion of the digital assaults (Slankas & Williams, 2013). As the framework will be sent inside cloud unique safety efforts will be viewed as.
- Environmental:The framework will be produced by taking after the distinctive conventions related with condition agreeable improvement. The framework operations will be done in such a way it will be eco-accommodating as.
- Capacity:The limit of the framework must be high regarding information stockpiling and demand taking care of. It is on account of the framework will store information from every one of the frameworks introduced in the facilities and those information will be gotten to by clients from everywhere throughout the states (Farzaneh et al., 2014).
- Manageability:The framework will be extremely perplexing as it will gather information progressively from various frameworks and security needs. Dealing with the framework will not be a simple errand. In any case, as the framework will be sent in the cloud, it is the migraine of the cloud merchants and the proprietor of the framework should do only support
The cloud based solution best suited for the system will be private cloud.
- Bandwidth:The cloud approach is basic for dealing with the framework transfer speed with the expansion or decline of client request. As the clients will not utilize the application much of the time, it will be productive to utilize low cloud limit (Wu et al., 2015). Be that as it may, if the data transfer capacity request expands then it can be rescaled.
- Remote Information Access: Using the distributed storage benefits, the framework will have the capacity to enable the clients to get to the information or data from wherever (Helo et al., 2014). The client must have an appropriate gadget and conventional web association.
- Automatic Software Update:The principle preferred standpoint of the could frameworks that the servers are off-start. The merchants deal with the application refresh, support and different operations. The sellers will consequently refresh the application when the updates come into the market.
- Disaster Recovery:It is basic for the associations that utilization IT frameworks for completing the business operations to put resources into debacle recuperation (Wu et al., 2015). The cloud merchants give the debacle recuperation highlight to the purchasers requiring little to no effort or for nothing.
- Collaboration:The joint effort among the medicinal services application will increment using the cloud approach.
- Technical Issue:The cloud based arrangement can prompt distinctive genuine brokenness. The cloud based frameworks are constantly watches out for various specialized issues, for example, blackouts. High upkeep norms cannot generally prompt keeping the specialized issues.
- Security:Clearly the cloud arrangement will be low secured, as the information will spill out of the gadgets to the framework through people in general web association (Kar & Rakshit, 2014). The greatest detriment as far as the proprietor viewpoint is that the merchant can get to the data.
- Prone to Attack:The cloud frameworks are less secured and the digital aggressors focus on these sorts of (Wang et al., 2014).
- Control:The framework stays in the control of the seller and it is a major hindrance regardless. The proprietor of the framework ought to approach its own particular framework regardless of what happens. Notwithstanding, for this situation, the cloud sellers takes the upper head and control the framework capacities, assets and numerous different angles. The main thing that proprietor can do is demand merchant to adjust the framework.
- Low amount of features:The greater part of the cloud merchants don’t give the greater part of the Could Features (Kar & Rakshit, 2014). It is not generally clear what operations the cloud sellers give.
Adaptive Approach:
Advantages: The advantages of iterative model are as following.
- Developing working functionalities is simple and rapidly inside the lifecycle of the approach
- The results of the approach can be picked up occasionally and early
- Planning parallel improvement is simple (Alshamrani & Bahattab, 2015)
- Measuring advancement of the improvement is conceivable
Disadvantage: The disadvantages are as following.
- In request to finish the venture extra assets are vital (Rastogi, 2015)
- Though the cost required for changing the framework is less, it is not reasonable to change the framework each time
- There may exist blemishes in the design of the framework as every one of the prerequisites are not accumulated toward the starting (Sahar et al., 2015)
- This venture is bad for the tasks that are little in scale
- The many-sided quality of the approach regarding dealing with the stages and exercises is high
- The ultimate result of the venture may not be constantly unsurprising
Advantages: The prescient approach basically gives the elements like control and departmentalization. It enables the venture supervisor to set due dates with respect to each of the prescient approach stages. The model permits the venture group to build up the item inside the booked due date through finishing the stages one by one. Alternate favorable circumstances of the prescient approach are the accompanying.
- The approach is anything but difficult to utilize and get it
- Each of the SDLC eliminates are worked and conveyed each one in turn
- The approach is effortlessly reasonable as a result of the unbending nature
- All the stages are guided through specific audit strategies and expectations
- The phases of the approach are characterized unmistakably
- Best for the littler and low complex activities
- Managing exercises inside the SDLC lifecycle are simple
- Good utilization of documentation all through the venture
- The greatest impediment of the prescient approach is that it doesn’t permit modification and reflection on the stages
- If the venture goes into the testing stage then it is practically difficult to change the item any more
- No application is produced until the venture is finished
- The approach contains a substantial number of instability and hazard
My Health Record venture is a major venture that incorporates application reconciliation, distinctive groups for various clients, approval level combination, database advancement, interfacing clinical frameworks and some more. Considering the venture estimate, the versatile approach is the best arrangement. The proposed venture is a perplexing one and requires add up to control over every one of the exercises. The venture incorporates a lot of elements that is should have been executed legitimately keeping in mind the end goal to make the venture fruitful. The versatile approach is reasonable for this situation. The venture trough must have control over every one of the stages legitimately. Without legitimate control, the venture chief cannot manage the venture exercises appropriately. The versatile approach does not give legitimate control over the stages where the prescient approach gives. The prerequisite social event process is followed in both the methodologies yet the prescient approach does not permit communicating new necessity inside the framework amid lifecycle. The prescient approach permits coordinating new prerequisites into the framework at any stage. At in the first place, it might appear that the cost of prescient approach is lower than the other however it is just conceivable when every one of the prerequisites are accumulated at the primary spot. From the above study, it can be suggested that the adaptive approach is the best solution in terms of SDLC.
Review of Cloud Based Approach
Conclusion:
From the above study it can be concluded that cloud based solution can be an easy choice for the project but may bring many issues that have to be faced in the long run. The study has properly provided all the information regarding non-functional requirements, SDLC approach and cloud based solution. However, a major thing in terms of cloud solution is the platform. It was needed to specify which platform (such as PaaS, SaaS and IaaS) is the best. Different cloud platforms are for different needs and proper analysis is required to select one. As the DDoS attacks are continuously increasing in the modern era and cloud vendors cannot do anything in front of a good DDoS attack, it is best to consider recruiting a third party security provider.
References
Alshamrani, A., & Bahattab, A. (2015). A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. International Journal of Computer Science Issues (IJCSI), 12(1), 106.
Farzaneh, M. H., Nair, S., Nasseri, M. A., & Knoll, A. (2014). Reducing communication-related complexity in heterogeneous networked medical systems considering non-functional requirements. In Advanced Communication Technology (ICACT), 2014 16th International Conference on (pp. 547-552). IEEE.
Helo, P., Suorsa, M., Hao, Y., & Anussornnitisarn, P. (2014). Toward a cloud-based manufacturing execution system for distributed manufacturing. Computers in Industry, 65(4), 646-656.
Kar, A. K., & Rakshit, A. (2014). Pricing of Cloud IaaS Based on Feature Prioritization-A Value Based Approach. In Recent Advances in Intelligent Informatics (pp. 321-330). Springer International Publishing.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: Dealing Non-Functional Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), 7-13.
Meulendijk, M., Meulendijks, E., Jansen, P., Numans, M., & Spruit, M. (2014). What concerns users of medical apps? Exploring non-functional requirements of medical mobile applications.
Rastogi, V. (2015). Software Development Life Cycle Models-Comparison, Consequences. International Journal of Computer Science and Information Technologies, 6(1), 168-172.
Sahar, S., Ayaz, S., Akram, M. U., & Basit, I. (2015). A Case Study Approach: Iterative Prototyping Model Based Detection of Macular Edema in Retinal OCT Images. In SEKE (pp. 266-271).
Slankas, J., & Williams, L. (2013). Automated extraction of non-functional requirements in available documentation. In Natural Language Analysis in Software Engineering (NaturaLiSE), 2013 1st International Workshop on (pp. 9-16). IEEE.
Teixeira, M. C., Monteiro, P. T., Guerreiro, J. F., Gonçalves, J. P., Mira, N. P., dos Santos, S. C., … & Madeira, S. C. (2014). The YEASTRACT database: an upgraded information system for the analysis of gene and genomic transcription regulation in Saccharomyces cerevisiae. Nucleic acids research, 42(D1), D161-D166.
Wang, L., Wang, X. V., Gao, L., & Vancza, J. (2014). A cloud-based approach for WEEE remanufacturing. CIRP Annals-Manufacturing Technology, 63(1), 409-412.
Wu, D., Rosen, D. W., Wang, L., & Schaefer, D. (2015). Cloud-based design and manufacturing: A new paradigm in digital manufacturing and design innovation. Computer-Aided Design, 59, 1-14.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
