In this segment, we'll take a more concrete look at our example project and the process of identifying user needs. You can see the project on the top right, the image guide in neurosurgery project. Our project here is this image guide in neurosurgery solution. Of course we're designing a solution with something for which a solution already exist. We're going to pretend that it doesn't. We're going to move back in time about 20 years, maybe 1999. I'm going to ask us, what is the situation that we're facing here? It's a little bit of a make-believe project, but it will illustrate the points we want to illustrate. What is the disease here? Well, in our case, we're dealing with epilepsy, is a particularly nasty disease, and surgery for epilepsy. The second question to ask is how do patients get to the point where then he surgery? Well, other treatments have failed, drug treatments have failed to cure patient from their epithelial seizures. We come to the point where we need surgery as an intervention. What happens prior to the surgery? Well, our patients have a set of images done, where we try to identify abnormal regions. They may well have had intracranial electrodes placed in their brain from a different surgery to identify the onset of seizure and all kinds of other neurophysiological testing. Again, we forecast attempt to identify where the seizures are coming from, what part of the brain is causing the seizures? What happens after the surgery? We need to know that. What are the pain point in this process. We're going to return to pain point multiple times this class, but what is it making the life of our surgeon difficult? How can we make it easier for them? How can make this procedure flow a little bit better? If you visit the operating room in the year 1999, so this is a drawing from AnMei that shows you a surgeon and a patient. This is me, coming up at the back of the room trying to see. What you would have seen, when I started working with epilepsy folks here, is that you see drawings attached to the wall with sketches of say, the brain, and this is what we're trying to do and this is where the electrodes were placed in the previous section. You may see images attached to the wall. What our surgeon is doing, is he's going to go back and fourth and look at the wall, to look at the images, and come back and look at the patient. They're going to try to integrate all this information on their heads. They are printers of medical images attached to the wall with tape, you think is the highest tech of high-tech, yet the piece of paper attach the wall with tape. The drawings on the wall showing how the police should be performed and the surgeon, as I mentioned, goes back and forth between working on the patient and looking at the images on the wall. In all of these, and this is part of the pain points, requires both significant experience in this procedures as well as mapping all this image to the patient mentally. This requires somebody from top of their game, has a lot of experience to do this. The surgeons who able to use procedures without image guide neurosurgery were very, very good at what they did because they had to there was no other way to do it. What is our neurosurgeon trying to do? That's the icons meant to represent a neurosurgeon there. The surgeon is trying to remove as much of the epileptogenic tissues as possible. Epileptogenic tissue is a tissue that's causing the seizure, while avoiding functional important zones and perhaps completing the procedure in the minimum amount of time possible. Let me show you an example of a functional important zone. This is a 3D rendering of a brain MRI from a particular person. If we cut through the top of the head here, there's a region called the motor cortex, is the central sulcus, and this is a part of your brain that controls motor function. This is the one that send signals to our hands and to your feet to cause movement of the hands and the feet. If this part of the brain is removed, there's a high chance that the patient is paralyzed, so we need to avoid places like this. Now, easy to say when I draw it on the screen. But if you have a patient that has had other procedures, other diseases, the motor failure may have shifted a little bit and we have to identify it. We do this by functional imaging and sometimes direct stimulation. But this is an example of something that needs to be avoided. What would she like to be able to do in addition, sometimes? We'd like to be able to see the location of the surgical tool on the images of the patient. This will eliminate the need to keep going back to the wall to look at the images. It will reduce the mental stress required to remember the information at all times. Maybe as such you may like to use functional images to define the zones to avoid. If we use functional images to define the motor area, then we can draw a circle and say, stay out of here. Maybe our session would like to create surgical plans ahead of time to guide the procedure and embed them into the software. Say, okay, well this is the line you're cutting, you getting close to the edge. This is the type of situation we would have encountered had we gone into the operating room 20 plus years ago and tried to identify what our users needs. In fact, this is what the systems they currently have in the operating room. Due to a large extent, obviously they're still open problems. But I would say that the basics are now well address and this systems are installed both in measure academic centers and also in community hospitals as well. With that, we conclude our discussion of user need. In the next few segments, we'll continue the story with the next step in the software lifecycle and we'll talk about the system requirements specification. Thank you.
