need to create a web application and use database, mvc and several operations for a health care centre application. All those are mentioned in the attached file and even the rubricAssignment Workbook CSCE 5430: Software Engineering Project Workbook Fall 2022 Revision History Date Issue Description Author September 6, 2022 Project1-Phase1 Adding Glossary (Question 4) September 6, 2022 Project1-Phase1 Adding system actors (Question 6.1) September 6, 2022 Project1-Phase1 Adding system use cases (Question 7.1) September 6, 2022 Project1-Phase1 Adding use case diagram (Question 8.1) September 25, 2022 Project1-Phase2 Produce a list of candidate classes September 25, 2022 Project1-Phase2 Filtering the list of candidate classes September 25, 2022 Project1-Phase2 Produce a potential class diagrams September 25, 2022 Project1-Phase2 Identified potential class attributes September 25, 2022 Project1-Phase2 Revised the diagrams September 25, 2022 Project1-Phase2 Update the glossary October 9, 2022 Project1-Phase3 Adding sequence diagram for “Authenticate Uesr” use case October 9, 2022 Project1-Phase3 Adding sequence diagram for “Assign Patient” use case October 9, 2022 Project1-Phase3 Adding sequence diagram for “Display My Board” use case October 9, 2022 Project1-Phase3 Adding State Chart diagram for “PatientRecord/TreatmentRecord” object October 9, 2022 Project1-Phase3 Adding a description for the state Chart diagram ( CSCE 5430: Software Engineering Issue: Fall 2022 Assignment Workbook Issue Date: October 9, 2022 ouda_CSCE5430_000_Workbook.docx ) ( Confidential ) ( Page 10 ) Table of Contents ICARE SYSTEM GLOSSARY4 INTRODUCTION4 GLOSSARY4 ICARE SYSTEM ACTORS5 ICARE SYSTEM USE CASES6 ICARE SYSTEM USE CASE DIAGRAM8 LIST OF CANDIDATE CLASSES9 POTENTIAL ICARE CLASSES10 POTENTIAL ICARE CLASS DIAGRAMS (ENTITY CLASSES ONLY)14 REVISED ICARE UML CLASS DIAGRAM17 POTENTIAL ICARE SEQUENCE DIAGRAMS23 ICARE STATE CHART DIAGRAM26 1.1 Introduction iCARE System Glossary This document is used to define terminology specific to the problem domain, explaining terms, which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information. 1.2 Glossary The glossary contains the working definitions for the key concepts in the iCARE System. Term definition Authentication Authentication is the process of determining whether someone or something is, in fact, who or what it is declared to be. User account A user is a person who uses iCARE system. Each user should have an account in order to be identified by iCARE. To login to an account, a user is typically required to authenticate himself/herself with a password or other credentials for the purposes of accounting, security, logging, and resource management. User friendly interface It is a computer application screen that makes it easier for novices to use this application. Menu- driven programs, for example, are considered more user-friendly than command-driven systems. Graphical user interfaces (GUIs) are also considered user-friendly. Physicians A physician is a professional who practices medicine, which is concerned with promoting, maintaining or restoring human health through the study, diagnosis, and treatment of disease, injury, and other physical and mental impairments. Digital ink Refers to technology that digitally represents handwriting in its natural form. In a typical digital ink system, a digitizer is laid under or over an LCD screen to create an electromagnetic field that can capture the movement of a special-purpose pen, or stylus, and record the movement on the LCD screen. The effect is like writing on paper with liquid ink. The recorded handwriting can then be saved as handwriting or converted to typewritten text using handwriting recognition technology. UI component UI stands for User Interface. It is a junction between a user and a computer program. An interface is a set of commands or menus through which a user communicates with a program. PDF Document Portable Document Format (PDF) is a file format used to present and exchange documents reliably, independent of software, hardware, or operating system. Pen-based document Any document that is created using tablet and stylus as pointing devices in addition to handwriting recognition capability. Windows-based desktop computers A desktop computer is a personal computer powered by Microsoft Windows operating system in a form intended for regular use at a single location desk/table due to its size and power requirements. Tablet PCs A tablet PC, commonly shortened to tablet, is a mobile computer with a touchscreen display, circuitry, and battery in a single device. iCARE System Actors The first useful step to analyze the system functionality is to look in the problem statement at the things that interact with the system. In UML use case analysis, these external things are called actors. Actors are identified based on the following: · Actors are always external to the system – they are therefore outside our control. · Actors interact directly with the system. · Actors represent roles that people and things play in relation to the system, not specific people or specific things. · Each actor has a unique name and description. Actor Description iCARE User A general user interacting with iCARE system. This general user can be a doctor, a nurse, or the system administrator. We will use the name “worker” to refer to a doctor or a nurse. In order to this general user to use iCARE, he/she needs to successfully login to the system. iCARE Admin A special type of iCARE User who is responsible for ensuring around-the-clock technical maintenance and support. This normally includes maintaining workers accounts and the connectivity issues with the drugs management system. iCARE Worker A special type of iCARE User who wish to use iCARE system to automate the paper-based processes and to speed up its data entry related tasks. iCARE System Use cases Use Case Description Authenticate User iCARE shall provide a functionality to authenticate its user by using a pen only. The user taps his name and can "ink" his password in the box. The user can of course also type (typically using the on-screen keyboard) into the box if desired. Once the user has logged in, the set of controls dynamically changes to match the permissions of this account. Note that, each user should be successfully authenticated before using any of iCARE functionalities. Manage Worker Account iCARE shall provide the functionality for the system administrator to create user accounts for doctors and nurses to use iCARE according to a set of access controls predefined for each user type. The administrator account itself is shipped with the system. Display iCARE Board iCARE shall provide the functionality for its workers to show a list of the existing patients corresponding to the geographic unit view. Assign Patient iCARE shall provide the ability for its workers to browse through the provided list of patients exist in the iCARE Board, select one or more patients and assign himself to them. Display Palette Display Palette UC shall provide a graphical user interface GUI to help simplify the choosing of documents among large number of potential documents. It's one tablet screen in size so the user can see all choices in one view which consists of a series of buttons for the user to tap on. The Palette shall be able to manage larger number of document choices than can fit on one screen. Display My Board iCARE shall provide the functionality for its workers to show only the active patients list of the logged on worker, and hence My Board view can be different for doctors and nurses. Manage Document iCARE shall allow the workers to create a new document. It is a text based document and the works shall be able to modify its contents. This document will be saved in a PDF format and will be tagged with the patient’s a metadata. This metadata includes Patient ID, Date of creation/imported, the user ID of the creator/importer, Modification date, the user ID of the modifier, Brief description. This UC includes two UCs Manage Text Insertion and Recognize Drug names. Manage Text Insertion This is a supplier UC for the Manage Document UC that shall allow the workers to insert different types of text into the new and/or the old documents created by the base UC. This text can be any paragraph that describes treatments, drug orders, or prescriptions. Recognize Drug Names This is a supplier UC for the Mange Document UC that shall allow iCARE to recognize generic and brand drug names during the text insertion process to help auto completion capability. This information will be extracted from a common repository managed by the Drugs Management System. Import Images This UC provides a tool to import images using a scanner or by browsing the internal stored image files into the application. These imported files will then be converted to PDFs, to become a part of the iCARE documents repository. Manage Patient Record This UC shall allow the workers at iCARE to maintain (add, modify) patient records. Patient’s record includes (but not limited to) the following information: ID, name, address, date of birth, height, weight, bloodGroup, BedID, Treatment area. Each patient record will be associated with zero or more treatment records and a set of digital documents. iCARE System Use case Diagram List of Candidate Classes pen user his name his password box set of controls account iCARE Board My Board patient the geographic unit Worker Palette documents tablet screen text treatments drug orders prescriptions images scanner application PDFs documents metadata Patient ID Date of creation/imported user ID the creator/importer Modification date Brief description administrator doctors nurses records Treatment area treatment records digital documents Potential iCARE Classes Class name Type Brief Description UserAuthenticationForm Boundary The UserAuthenticationForm will be displayed by the iCARE system asking the user to ink or enter its username and password to be authenticated. iCAREUser Entity The common information of the iCARE works and the iCARE admin such as User ID and User name will be maintained by this entity class. iCAREWorker Entity iCAREWorker is a specification class inherits the iCAREUser class and add specific information about the worker such as the profession name and type. iCAREAdmin Entity iCAREAdmin is a specification class inherits the iCAREUser class and add specific information about the system administrator such as the starting and ending date for the admin responsibility. UserPassword Entity The UserPassword class store the iCARE user account information that include a password related information like an encrypted password of a user, the day the password expires, whether or not the password has to be changed from time to time, the minimum and maximum time between password changes, etc. UserAuthenticationController Control A control class to accept and validate the iCARE username and its corresponding password. It takes the decision whether the iCARE user is allowed to access the iCARE services or not. ManageAccountsForm Boundary iCARE displays the ManageAccountsForm when the system admin initiate the process for adding/modifying iCARE user account. This form will help the admin to inter the user general information like name and addresses and the secret information like password and the associated access roles. UserRole Entity UserRole class maintains a list of all available iCARE access roles and the related permissions. For example, System administrator who has a privilege