Systems Analytics and Enterprise Management 4
System development document 1
System development document And concept map 13
Easy Health Care access Software
System development document
And concept map
Name
Institution
Date
Table of Contents Introduction 3 Context diagram 4 System development document 4 General Overview and Design Guidelines/Approach 5 General Overview 5 Assumptions/Constraints/Risks 6 Assumptions 6 Constraints 6 Risks 6 Design Considerations 7 Goals and Guidelines 7 Development Methods & Contingencies 7 Architectural Strategies 8 Performance Engineering 8 System Architecture and Architecture Design 8 Hardware Architecture 9 Software Architecture 9 Information Architecture 10 Data 10 Internal Communications Architecture 10 System Architecture Diagram 11 System Design. 11 Database Design 11 Data Conversion 12 References 13
Introduction
A context diagram is developed and used to show the context and boundaries of the systems which are modelled (Sonwane, 2017). Where the things are outside and inside of the modelled system also the relationship of the system from the external entities. The context diagram also called the 0 level data flow diagram will be used to show the role and relationship of the professor according to the case study. It will be used to identify the flow of information between the external entities and the professor and their role.
The study has developed a concept diagram pertaining to the easy health care system. This system is scheduled to be developed with an aim of reducing the strain that patient go through so that they can access the health care. The system will be used by the user who is the patient to access health care services.
Context diagram
System development document
The system development document role is to show the functional and non-functional requirement of the system. The SDD will also provide the preliminary user oriented functional design. In other words the SDD will record the high level system design and the low level detailed design specification (Chen, 2019). The whole purpose of the system development document is to document the easy health care accessibility system. This system will enable the user who is a patient needing medical care to access the services just by a click of a button. The system will also enable the health care provider source client through the connection of the client and the health care provider through the system support. The system will have three interface which include the input interface which is more so the client interface, the control interface which is the system administration and the output interface which is the service provider interface. The system will comprise of high level design and low level design which will work together to complete the system function (Bohnes, 2019). High level will comprise of the system architecture, description of the data design which is associated o the system and the human machine interface. The high level system will decompose of the low level detailed design for every system component which will include the following the internal communication, hardware, software, system integrity control and external interface (Allen, 2016). The high level system design will be the primary input for the preliminary design review while the low level detailed design is the input of the detailed design review
General Overview and Design Guidelines/Approach
In this section the principle and strategies used will be review along with the guideline for designing and implementation the system
General Overview
The easy medical health access software system will seek to bind the gap between the medical health provider and the patient. According to the WHO data of 2019 28% of total deaths in United States were caused by health condition which would have been cured if the victim had received effective medical services on time. Due to accessibility is often difficult to have a specialist at your service when you need them this the system will ensure that their user have medical services when they need it. Through the input interface the client will develop their profile using their detail highlighting the medical condition they might have and whether they may need help. The second interface is the health care provider. Their role in the system is to provide their services for a fee. They will create their profile and list the time when they are free and the location, cost and specialty. This way the client can be connected to their services by the control. The control is the third interface whose role is provision of a connection between the user and service provider, they will also solve a technical dispute when one arises. The system will operate on a fee which will be charged form the specialist side when the receive an patient through the system.
Assumptions/Constraints/Risks
Assumptions
The system is developed on the assumption that the client will have some technical or health need while registering the software. Also the project is developed under the assumption that the information by the health officer is truthful and it can be relied upon,
Constraints
The system contrail is that first it requires internet connectivity to operate and this the system will need the client to have an internet connected device. Second constrain is that the doctor and other specialist will have to pay some percentage of the cost of health care to the company for the client and connectivity that has been done.
Risks
The risk that is associated with the system is that the health care specialist may oppose its use. This is because first they will be monitored easily and second most health care workers may not have great understanding of use of computer (Henry, Murray-Rust, & J. Whitaker, 2017). Some of the cause of opposition may be cause by the fact that the lectures feel the need to still use papers in healthcare management (Levin, 2015). To mitigate the opposition risk, the system will be used in a simple and interpretative form which will be easy to use by the healthcare workers. Second the lecturers will be informed the importance of use of the system to enhance their embrace the system.
Design Considerations
In this section the issues in complete designing of the system will be address to complete the design documentation of the system.
Goals and Guidelines
Goals of designing- the sole goal of system designing is to ensure that the system reach all the expected requirement (Lowry, 2018). The design which is the form of the model as shown in the diagram above will show how the system will be and key features of the system.
Guideline- according to the OIT Unified SDLC has set for policies which will be used in the system development (Ronaniello, 2018). The policies include the risk management, security management and the quality of the system and procedure policies.
Development Methods & Contingencies
The approach to system development which will be used include structure system development approach. This approach will enable the study observe important features of the system, develop flow chart and concept diagram, data flow and entity relationship in the system (Ronaniello, 2018). Through the structured design of system development it is clear to understand how the system will operate before the development of the system thus the developer can understand the improvement needed.
Architectural Strategies
This system development will use the macroscopic system strategy, in this strategy the system will use a higher level abstraction of the software system which will constrict of the computation components and connectors which will interact with the components (Sonwane, 2017). The decision on use of the system will be made by the higher management of the system however the implementation will depend on the availability of the health care provider and the client who are the patient. The system functioning is the utmost requirement of the project, it is in this need that the system will be developed and the abstraction will be based on the need of the client and the user (Saltzer & e, 2015). The system will be developed according to JAVA programming language and use the commercial off the shelf product
Performance Engineering
The performance requirement of the system is the accepting the input by the client according to the health care need they request which will be marched with the healthcare provider who is available. This connection will be fostered by the management of the system (Amaechi, 2018). The system should also process the information provided by the client pertaining to the urgency of the service as well as the location in order to connect the client with the closest service provider according to location and urgency.
System Architecture and Architecture Design
The system will have a serve with which all the user will be linked by the software which will be installed in their devices. The channel of connectivity is through the software and at this point that the user will interact with either their colleagues, the administration or their department (Whitten, 2017). The data is passed from one user to the other or department through the interaction box. The system will be divided into three section which is the user or the input, control or management and the output which is the information received. The easy healthcare access system will provide continuity of patient record and clinical communication between the doctor or any other health care provider and the client. This will ensure a well-coordinated health care service delivery.
Hardware Architecture
The system hardware of the organization will include the various hardware which will be required to host the system (David, 2020). This will include the computer system which will serve as the system server, and all the computer devices which will be used by the users to access the system (David, 2020). The number of the hardware will depend on the number of the user in the system. The system will use a control which will be installed in the devices and latter be used to access the system.
Software Architecture
The system software will be the means of connecting the user to the system. The software will be developed along the system (Chen, 2019). Due to the role of the software and the system, they are not complicated to develop as they do not perform a complex role. However there is need to establish safety protocol like fire wall which will be use along with the system. the software version will be window 8 operating system chisch will include an Apache (A), Perl (P) (XAMPP), MySQL (M) or Cross-platform(X) can be used to host the database and also foster the running of the system on local host. Additionally a complicated test editor the sublime text editor will be used in quick response as well as cording as code generator. This will be used to provide a fast response to the staff and patient for security accessibility purposes.
Information Architecture
The system will store the client data and the health care provider data. The data will pertain to the personal information of the user, the health information of the user and service record of the user (Bryan, 2016). This data will be used in service delivery and understanding the kind of services the client needs, the data will also be used to understand the kind of specialist who need to be invited to the system to provider their professional services.
Data
The data will be stored in three former the CSV format for the list of health care and their specialty, list of the client and their information including the health services they require, pdf format for other personal information pertaining to the client (Bryan, 2016). All the document will be electronic and will be sourced from the administration, department and the individual lecture as highlighted in the input section of the system.
Internal Communications Architecture
The system will provide a communication channel between the stake holders. The first communication will be through the system where the user can select the receiver of the message and through the system they can text the message which will be sent to their profile in the message section (Bohnes, 2019). Second way is through email, this will be the methord of signing in, and according to the organization credential and the institution email the user can send their email to the receiver as long as they have the receiver email.
System Architecture Diagram
System Design.
Database Design
The system will use the relational database design which will contain numerous tables of data that are related to one another through the special key (Amaechi, 2018). The reason is because this design of the database structure allows deletion of data, update of the data and reading and creating new data. This is ideal for the system as new data will come in the system every data. The system will further use the structured query language for database interaction. All data will be stored according to the source of the data (Alshemali, 2020). This mean that the database will have three section for the three sources of information. The data will store the name of the source of data, the length of the data, type and element (Allen, 2016). Additionally there is need for validation of the data to avoid future error of retrieval thus data which are not subject to viruses will be verifies and also complete data.
Data Conversion
Through explicit and implicit data to the database will be converted from excel and word to CSV and pdf format in order to retain the integrity (Akomolafe, 2016).
In conclusion, the study started with the concept diagram which highlighted the system and the study continued to develop the system development document. The SDD has considered a number of fact that are effective to address according to the requirement of the system. Other section of the SDD have been left out to avoid repetitiveness as the system is not complicated as such I need a SDD which will only suit the need of the system.
References Akomolafe, D. T. (2016). Using Database Management System To Develop and Implement an Automated Motor Vehicle Management System. European Scientific Journal, 10(24), 313–322. Allen, J. H. (2016). The CERT Guide to System and Network Security Practices. Boston, MA: : Addison-Wesley. Alshemali, B. &. (2020). Improving the reliability of deep neural networks in NLP: A review. Knowledge-Based System. New York: Springers. Amaechi, J. C. (2018). Design and Implementation of a Hospital Database Management System (HDMS) for Medical Doctors. . International Journal of Computer Theory and Engineering, 10(1), 1–6. anik, A. B. (2016). Exploring Energy Efficiency of Lightweight Block Ciphers. IOT security system , 12(9), 178–194. Bohnes, F. A. (2019). Life cycle assessments of aquaculture systems: a critical review of reported findings with recommendations for policy and system development. . Reviews in Aquaculture, 11(4), 1061-1079. Bryan, B. A. (2016). Quantifying and exploring strategic regional priorities for managing natural capital and ecosystem services given multiple stakeholder perspectives. Ecosystems, 13(4), 539-555. Chen, J. X. (2019). System development and environmental performance analysis of a solar-driven supercritical water gasification pilot plant for hydrogen production using life cycle assessment approach. Energy conversion and management, 18(4), 60-73. David, D. a. (2020, April 10). infomrtaion system for business and beyond. charpter 4: data and database. Retrieved March 28, 2020, from https://bus206.prssbook.com/chapter/chapter-4-data-and-databases/ Gates, A. F. (2017). Building a high-level data flow system on top of map-reduce . Proceedings of the VLDB Endowment,, 2(2), 1414-1425. Hamamura, J. (2018). The impact of an information linkage system on a firm’s organization structure, transfer price, and profit. Asia-Pacific Management Accounting Journal, 13(1), 131-152. Henry, Murray-Rust, P., & J. Whitaker, B. (2017). The Application of network designing in infomation system . Journal of computer science, 38(6), 976–982. Levin, M. (2015). Modular system design and evaluation. New York: Springer. Lowry, P. W. (2018). performance management in production process. communication of the association for infomation system, 17(6), 14. Ronaniello, A. A. (2018). A connected world; A systematic literature review of the internet effects on society. issues in information system , 19(3), 17. Saltzer, J., & e. (2015). End-to-End arguments in System Design. ACM Transactions on Computer Systems, 12(4), 277–288. Sonwane, A. v. (2017). Identity and policy based network security and management system and method. USPTO patent full text and image database, 12(4), 42. Spagnoletti, P., & A., R. (2017). The duality of Information Security Management: fighting against predictable and unpredictable threats. Journal of Information System Security, 4(3), 46–62. Whitten, J. L. (2017). System analysis and design methods. New York: Springer.