Itc548 Systems Science And Engineering Assessment Answers

This assessment aligns with learning outcomes

 

1. be able to compare and contrast the different methodologies of systems analysis and evaluate their appropriateness for different and complex situations;

2. be able to distinguish between requirement gathering techniques and combine these appropriately to apply to a real scenario;

3. be able to evaluate development requirements and prepare a feasibility proposal based on multi-disciplinary (financial, human resource, technological) analyses;

4. be able to formulate and justify system requirement models based on evaluation of given situations;

5. be able to assemble the components of a requirements model using the tools and techniques of object oriented or structured systems modelling.  

Answers:

Introduction

My health record system is one type of software that is used to keep the records of the patients as well as of the entire organization which is necessary to maintain for a better retrieval of data as and when required by anyone belonging to that particular organization. The software is necessary in order to maintain the information system which is very much important for any organization to perform any types of activities. The software has several features that help the patients and the other members of the hospital to access the details within less period of time. This helps the Australian people to enhance their data record system in their respective hospitals or healthcare (El-Hajjar & Hanzo, 2014).

The report that is mentioned below contains the necessary details about the actors, stakeholders and the managers those who are involved in the process of accessing the software. The software helps to get the emergency details of the patients as well. The report of this software contains the dealers who are externally connected with the software through the entire phase. As per Fry, et al, the stakeholders are considered as the hero for the software, and provide the necessary information that is quite helpful for the patients as well as for the managers (Fry, et al., 2014). The details of the software are different for everyone. The level of accessing the details varies from each person. The patients are not allowed to access the details of the mangers and the same applies to the other members of the organization. The access level is set for the different levels of the members.  

Non-functional requirements

For the better retrieval of the information out of massive amounts of data, an organization needs the multi-talented web-based solution or else software which can manage the entire information system of the hospital without showing any type of faults or errors (Grinspan, et al., 2015). The software is the collection of the millions of numbers of data, program and services management whose primary is to:

1. Streamline and advance the processing speed of the software for those who are visiting the hospital and to provide the full basket of community and home-based care and services.
2. Programs and planning services that can appropriately address the emerging needs of the clients.
3. Supports the human resource management.
4. Measure the performance or efficiency of the user while accessing the data through the software.  

Critical system qualities, system interfaces, and user interface requirements, and system constraints

The critical system requirements are defined as the complex integrated requirements of the system whose performance depends on the quality and efficiency of the larger system. As per Hemsley, et al, the data that are stored in the hospital's database is huge, so it is important to consider the hardware-related aspects as well as the obsolescence of the components. Therefore my health record system software maintains the critical system while designing the software keeping the priority on the number of tasks and on the components of it (Hemsley, et al., 2017).  The system interface of the software is highly reliable that helps to transform the input into the output without taking much time.

The collection of the inputs and the outputs from the other sources are often defined as the interface. The interface of this software is highly effective and user-friendly. The user-interface is identified during the requirement phase regardless of the methodology. In my health record system, the user interface has been considered while designing the software in the requirement phase. The UI helps to give the detailed information about the software design, details about the product as well as the implementation of the software (Lau & Haut, 2017).

With the help of the UI in this software, the database and the other program specifications are properly maintained that enables the user to access the data in a better way. The system constraints of this software help to filter the supporting capabilities like the group modulation, refining and the explanatory on the large-scale information systems of the organization. With the use of the system constraints, the software is capable of identifying the replication on the user access and maintains the data competency against the storage requirements.

The features of the functional and non-functional requirements

The non-functional requirements of the software describe the functioning of the software with the help of the usability, reliability, performance, and supportability. The usability of this software is very high as the number of data is more.

The functions are properly tested on eth usage patterns. The reliability of the software can be trusted as the information are always in the backup state for long years without changing the system that helps in better software performance (Li, et al., 2014). The performance of the software is usually high that releases the stress of the user while accessing the system. The software "my health record system" is highly cost-effective and maintains diverse levels of documentation.

According to Linares-Flores, et al, the functional requirements of the software deal with the description of the system and whereas, the functional requirements of the system describes how the system really works (Linares-Flores, et al., 2015). The functional part covers the records of the client management, case management, client delivery system, about the scheduling functions and human resource management. The functional part covers the performance, usability, reliability, and accuracy of the software.

Cloud-based approach

Strength and weakness of the cloud platform

From the last few years, the cloud computing has been emerged as one of the dominant factors in the IT infrastructure, in case of the hospitals and healthcare, educational institutes and much more. It offers the flexibility, cost-effective and on-demand access to the users to a wide pool of resources and functions. Leveraging it varies from the type of services, diverse user communities as well as adopts the cloud paradigm that offers the low-cost burden to the user and reduces operational complexity (Muñoz, Cowling & Birt, 2016).

The cloud platform is used as it provides the unlimited storage, best backup, and recovery to the data, cost-efficient, automatic software integration, easy to access the information and faster deployment. The disadvantages of the cloud platform are like the technical issues, the security system on the cloud platform and the platform are prone to attacks. The entire connection of the cloud services are based on the internet, so the services suffer from frequent downfall or slow speed which is not at all reliable for the business.

Whether the cloud platform is secure or not when the third party is involved?

The mental health data which are generally massive in number can be stored in the cloud platform. Despite the rise in the public cloud platforms, the entire data of the organization are stored in the cloud. Building the own energy-hungry data centers are always time-consuming and expensive on part of the managers of the organization. So, it is quite difficult to manage the hundred software application of the software "my health record system" (Nazi, 2013).

Therefore, the organization can outsource the data to the third party who can expand the services by reducing the level of risks and fulfill the demands of the users by saving money as well as time. The cloud provides the best services in managing the risks and controls the data to someone else by using the various data centers (Phillips, et al., 2015).

System development life cycle

As per Willers, the SDLC approach is used to create the hardware, a software system or the combination of the both by using the six phases of the life cycle. The system is defined as the integration of the whole which can be used for various industries (Willers, 2013).

The phases of the software are integrated with the other components of the software to create the whole system. Without a proper SDLC approach, it is quite difficult to design software as the work will be divided into teams where each team has some specific work to do. It includes the planning, designing, testing, coding, and maintenance.

Pros and cons of the predictive SDLC approach

The predictive approach helps to know the parameters in designing the phase that is known to the developer. It also focuses on the parameters so that they will not change throughout the process. The precise and detailed outline highlights the functionalities of the resources include the non-functional and functional elements. It also provides the legal guidelines and procedure to follow the implementation of the procedure while developing the software for the storage and access of the data (Zhang, Kong & Yu, 2016).

The sequential approach helps to maintain the framework without any deviation. The multiple forms of the predictive modeling like the decision analysis, optimization, transaction profiling, modeling as well as the predictive search helps the managers to influence the sales, development of the software and manufacturing optimization.

Sometimes the data-driven approach needs to have the access to the substantial data from a wide range of data, and sometimes from the big data set that is difficult to do. The human behavior and algorithms fail to consider the variables and might influence the customer accessing process. The software needs a regular update with the predictive approach otherwise the behavior of the software will change.

Pros and cons of the adaptive SDLC approach

The adaptive approach carries the necessary task and activities as per the demand of the project. The process is quite flexible and easily adopts the changes in the requirements (Phillips, et al., 2015). The process generally divides the implementation process into steps that help in faster execution and reduces the development stress and time. The approach helps to reach the final step of developing the software within a short period of time if the steps are properly executed and maintained throughout the project.

The approach needs the resource-intensive model and the estimation of the timeline is not easy as it takes time when the changes are introduced in between developing the software. The process is not acquainted with the sudden changes in the environment (Linares-Flores, et al., 2015).

Recommendation

Both the models are useful in the respective fields, but for developing the software "my health record system" predictive method is feasible and relevant. The approach considers the existing the model and easily make the changes that are introduced in the architectural design. It also helps to resolve the prevailing problems that are faced during the designing of the software.

Conclusion

The report presents the detailed knowledge about the software, its storage capacity as well as the approach used while designing it. Both the functional as well as the non-functional areas have been covered that provides the necessary information about the cases and issues raised while developing the software. The main intention of the software is to show the efficiency when the storage is based on the cloud platform and the accessibility of it through the software application.

References

El-Hajjar, M., & Hanzo, L. (2014). EXIT charts for system design and analysis. IEEE Communications Surveys & Tutorials, 16(1), 127-153.

Fry, C. L., Spriggs, M., Arnold, M., & Pearce, C. (2014). Unresolved Ethical Challenges for the Australian Personally Controlled Electronic Health Record System: Key Informant Interview Findings.

Grinspan, Z. M., Hafeez, B., Haridas, B., & Patel, A. D. (2015). The Pediatric Epilepsy Emergency Risk Score (peer): Predicting Frequent Ed Use with Data From an Electronic Health Record System. Annals of Neurology, 78, S155.

Hemsley, B., McCarthy, S., Adams, N., Georgiou, A., Hill, S., & Balandin, S. (2017). Legal, ethical, and rights issues in the adoption and use of the “My Health Record” by people with communication disability in Australia. Journal of Intellectual & Developmental Disability, 1-9.

Lau, B. D., & Haut, E. R. (2017). Computerized Clinical Decision Support Systems for Prevention of Venous Thromboembolism: Why Can’t My Electronic Health Record Be More Like Netflix, Amazon, Google, and Apple?. JAMA surgery.

Li, H., Gupta, A., Zhang, J., & Sarathy, R. (2014). Examining the decision to use standalone personal health record systems as a trust-enabled fair social contract. Decision Support Systems, 57, 376-386.

Linares-Flores, J., García-Rodríguez, C., Sira-Ramírez, H., & Ramírez-Cárdenas, O. D. (2015). Robust backstepping tracking controller for low-speed pmsm positioning system: Design, analysis, and implementation. IEEE Transactions on industrial informatics, 11(5), 1130-1141.

Muñoz, J. C., Cowling, M. A., & Birt, J. (2016). Using gamification and mixed reality visualization to improve conceptual understanding in ICT system analysis and design.

Nazi, K. M. (2013). The personal health record paradox: health care professionals’ perspectives and the information ecology of personal health record systems in organizational and clinical settings. Journal of medical Internet research, 15(4).

Phillips, C. L., Nagle, T., Brickley, J., & Chakrabortty, A. (2015). Digital Control System Analysis & Design. Pearson Higher Ed.

Willers, C. J. (2013). Electro-Optical System Analysis and Design: A Radiometry Perspective (p. 385). SPIE Press.

Zhang, J., Kong, X., & Yu, P. S. (2016). Badge system analysis and design. arXiv preprint arXiv:1607.00537.