Data Flow Diagram

Defining the process view is when an IT system relates information from one system to another. The technical process is needed so that IT systems can communicate. The model in the process view helps us to understand a system that is currently in place, and being able to consider what is needed for a new or future. The more information that a model is supposed to give, then the more detailed and difficult it can get, making it difficult to convey and confusing. The solution to this problem is to simply state that the different types of information are like using individual maps. You can see how all of these views are interconnected in many ways by the use of graphs or diagrams.

The objective is to put together a detailed diagram or view of the information and statistics concerning the projects progress. In the process view it will display the logical system which will give more detail about the system and the processes that the project team will be working on. By putting together the Data Flow Diagram (DFD), the system analyst can produce a view of the proposed system that will be ease to follow and understand.

The system analyst gathers the facts and are able to use the methodological knowledge they have obtained through collaborating with IT systems experts. These facts are shown in the DFD along with any documents have been prepared by the analyst. In order develop a DFD the analyst has to be able to master all of the technical details of the project. The DFD diagrams will give an overview of how system will function. Also, they will give a description of procedures and in which step they are processed and how they will interact. The diagram is especially useful when showing and illustrating sequence, system alternatives, and similar system events. The diagram will also help to communicate the sequence and order in which processes will follow. A data flow diagram is a good basis for data and information exchange with partners and customers. It is a good source to help relate the events and project progress information. ("Process View", n.d.).

Functional allocation modeling

Function allocation during the proposed process is deciding whether a particular function can be accomplished using technology hardware or software which project team members will be in charge of that area. The system analyst along with the project team manager will consider several different factors such as, possible error rates, costs, hazards, technological feasibility, security, ethical issues and the team of people to perform and work on the project.

The process of functional allocation is very useful in helping to decide the amount of automation that will be needed for the new a system. As we have seen technology improve, the function allocation tasks have changed to be able to take on complex details and to take advantage of new machine capabilities, such as, more advanced software, and increased intelligence. In the context of using analysis and task analysis, to help define and identify the task structure its demands, and the technical knowledge needed to perform the tasks, environmental constraints, any possible functional and safety requirements, and any other relevant issues.

As each task is being allocated there are several factors that will need to be addressed such as task cost, training, criticality and unpredictability along with knowledge requirements. Also there needs to be attention taken when looking at human workload, team support and individual differences in each user. In allocating tasks they should be based on factors such as individual responsibility, task variety, communication between users, and individual capability.

There can be some common issues that may also come up during the purposed process there can be a failure to monitor the system frequently or adequately and users may rely on the system to much. There has to be a constant backup to make sure that the system is continually checked and tested before moving on the next task. It is always a good idea to have or build a prototype of the system to evaluate function allocation and it can be included in the design process and can be used before the implementation of the system ("Function Allocation", n.d.).

Data Flow Diagram:

The Data Flow Diagram for the proposed systems begins at reception. The receptionist will input Patient check-in information at this point. This information includes the patient name, patient contact information, time of check-in, time of appointment, provider information, type of visit, and insurance information. The data then flows as the Nurse enters the patient’s vital statistics information obtained at the beginning of the visit. This information includes the patient’s heart rate, weight and height. Next the data flows as the Provider enters applicable information during the appointment. The provider can initiate a data flow again to either a specialty clinic or pharmacy (if necessary) and billing. If applicable, data will also flow from the specialty clinic or pharmacy to billing. From the provider, specialty clinic, and pharmacy, information will flow to the patient’s electronic record where it will be stored. The diagram represents processes in a square. Data flow is represented by an arrow while data store is indicated by a vertical line to the left of the label. The circle includes the automation system boundary.

Design trade-off approach

The hardware that should be requested for this task is: four central servers, two 802.11n wireless routers, and contract a bulk order of 802.11n usb’s for the company. The option of 802.11n network card is available. However, instead of upgrading all the cards I have decided to go with fresh out of the box new Dell Precision T5500 towers running windows 7 with remote systems administration capacity. These systems will all have Norton Anti-Virus introduced which will anticipate infections, worms, and other known endeavors at the systems level. The new systems will take into consideration speedier exchanges and correspondence to the POS server.

The new systems will be in consistent correspondence with the hand held stock system. This will give all representatives the capacity to look out for current costs, stock, and shipments progressively at whatever point they require without sitting tight for administration. The VoWLAN would supply a wireless signal to all the phones in the area and will act like a cell phone network located within the company. This will allow management and some employees with cell phones to connect to the WLAN network. This