A Scheduling Application How many times have you forgotten about an assignment that was due the next day? Or missed a dentist appointment because it slipped off your mind? These things happen often. It is human nature to forget important dates and appointments because our brain can only hold so much information. So, my proposal for a suitable software engineering project is a scheduler application. The problem it will solve is a fundamental one: It will help us manage our time more efficiently by recording dates of important tasks, projects, and appointments. Furthermore, the program will remind us a few days beforehand when a major event is coming up. This application will allow students to keep track of important assignments. All they need to do is enter in the description of the assignment, the due date, and the filename of any document(s) associated with the assignment. If the student wishes to view all tasks that need to be done, he/she has several options. The student can choose to search for undone tasks within a certain time period. He can just view all the unfinished tasks in a huge list. Or he can view the tasks that need to be done in a specific month, day, or week. Secondly, the application will enable people to change or view the status of a particular task. When an assignment is done, one just needs to mark the assignment as done, and the status of it will be changed in the application. The user can set an assignment to any status from the following: Researching, Working, Quit, Complete. The additional functionality of displaying the filename of documents with the due date is important because the user can easily open the document he was working on without searching for it in his hard drive. Lastly, when a student is done with a huge project/assignment, he can go back and see how many hours he worked on the project, how many hours an assignment was in a particular status and assess whether he should've spent more or less time. The application, overall would store deadlines to appointments, tasks, projects, or assignments, and can give vital statistics on how time was used.

Here is what you need to do.

1. Using scenarios like in figure 4.14, write one scenario of your choice.

Figure 4.14

INITIAL ASSUMPTION: The patient has seen a medical receptionist who has created a record in the system and collected the patient's personal information (name, address, age, etc.). A nurse is logged on to the system and is collecting medical history. NORMAL: The nurse searches for the patient by family name. If there is more than one patient with the same surname, the given name (first name in English) and date of birth are used to identity the patient. The nurse chooses the menu option to add medical history. The nurse then follows a series of prompts from the system to enter information about consultations elsewhere on mental health problems (free text input), existing medical conditions (nurse selects conditions from menu), medication currently taken (selected from menu), allergies (free text), and home life (form). WHAT CAN GO WRONG: The patient's record does not exist or cannot be found. The nurse should create a new record and record personal information Patient conditions or medication are not entered in the menu. The nurse should choose the other option and enter free text descibing the condition/medication. Patient cannot/will not provide information on medical history. The nurse should enter free text recording the patient's inability/unwillingness to provide information. The system should print the standard exclusion form stating that the lack of information may mean that treatment will be limited or delayed. This should be signed and handed to the patient. OTHER ACTIVITIES: Record may be consulted but not edited by other staff while information is being entered. SYSTEM STATE ON COMPLETION: User is logged on. The patient record including medical history is entered in the database, a record is added to the system log showing the start and end time of the session and the nurse involved