Project of a malfunction.The major task are listed down
Project Scope:Insulin/glucagon pump simulator has been designed keeping the fundamental aspects of a critical system such as safety, reliability, and availability in mind. The major function of this pump is to measure the correct amount of dose required by the diabetic patient’s body corresponding to his or her body’s current level of blood sugar.The pump showcases three point of views. We can look at the working of the simulation from theperspective of a patient, a doctor and admin. We have implemented the safety and security functions like proper error and warning messages, alarming the responsible person in case of system shut down etc in case of a malfunction.The major task are listed down below.Develop a software simulation of an Insulin/Glucagon pump.The system should be able to monitor blood glucose 24×7. The simulator should work faster than real-time (i.e. it should not wait 10 minutes between sensor readings) and the simulator displays should replicate the displays on the Insulin/Glucagon pump system.The systems falls under a safety critical system as too little blood glucose can be fatal.Major software functionsSimulate Insulin/glucagon dose to a diabetic patient.Monitor the blood sugar level of the patient.Monitor insulin/glucagon levels in the reservoirs.Maintain reliable and safe simulation Diabetes History : Requirement AnalysisThe proposed system simulates the functioning of a basic insulin/glucagonpump. It controls the blood sugar level of a diabetic patient by monitoring changes in patient blood glucose level and based on this it calculates and administers the required dose of insulin/glucagon.This simulation has two modes – automatic and manual. The default setting is to run the pump in automatic mode. The dosage is injected automatically in auto mode.In manual mode patient can inject his own dose. Functional Requirements:Simulation of biological system for measuring Glucose level >Determine the blood sugar level >Display the blood sugar level in a graph >Determine which hormone and amount of dose to be injectedConfiguration of the device >Monitor the insulin and glucagon reservoirs. >Doctor can only configure the manual operation for patient based on dementia status >Monitor battery level Mode of operation >Automatic mode >Manual modeGraphical User Interface for admin/user >Doctor manages and observe patient history and condition >Patient can enter his carbs intake and raise alarm.Patient history database >Maintain user history >Maintain user daily and weekly dose historyNon-Functional Requirements:Security: Only authorized personnel can accessSafety: Display the appropriate error and warning messages when requiredAccessibility: the GUI is easy to operate and user-friendlyReliability: The pump has recharge buttons for the battery, insulin and glucagon reservoirsAgile methodology is used for software development life cycle. It is very effective where Client frequently changes this requirement. Since it has more iteration so you can assure a solution that meets client’s requirement. More than one builds deployment for a project. It involves more client interaction and testing effort..Agile software development is based on an incremental, iterative approach and no in-depth planning at beginning of the project. As Agile methodologies encourages constant feedback from client ; it is open to changing requirements over time. Cross-functional teams work on iterations also called as sprint cycle of a product over a period of time, and the work is organized into a backlog that is prioritized based on business or customer value.Agile Lifecycle The agile lifecycle is fairly simple. Even though there are various approaches tofollow an agile model we preferred to stick to the four step cyclic method for our project development.The project was broken down into short iterations of two weeks each called sprints. The lifecycle ofeach sprint includes:1. Planning – The team did scrum every day to decide the set of goals to be achieved during the sprint. Each member was assigned their tasks for the sprint.2. Execution – Everybody worked on their task for the sprint and raised the difficulties they facedwhile development at a common platform. In this way we were able to help one another quickly by providing alternate solutions and continuing progress.3. Review – The team met after end of each sprint to review the work done during the sprint.4. Rinse & Repeat – Feedbackst and new requirement were incorporated before starting new sprint cycle.