A​‌‍‍‍‌‍‍‌‍‌‌‍‍‍‌‍‌‌‌‍​fter you have completed the readings, identify an actual or fictional business scenario that needs modeling. Think about clinical scenarios that you are aware of or believe need to exist in the healthcare environment. The scenario can revolve around a clinical scenario such as the monitoring of patients with specific acute care conditions and the tracking of their conditions (sepsis, heart failure), or a workforce management issue such as the onboarding and retention of hospital employees, or perhaps even a business problem such as supply chain order management of medical supplies for units across the healthcare organization. Be creative with what you come up with! The component of the work completed this week will serve as a foundation for the work that continues across the course. The below components are the requirements for the assignment “Project Part One”. You will submit your Part One assignment to the instructor by 11:59ET at the end of Week 2. 1. Describe the actual or fictional business scenario that needs to be modeled. 2. Articulate the high-level mission for the system. For example, “This system will be used to capture…, so that…”. 3. Detail a list of requirements of the system, specifically a list of must-haves, should-haves, and wants. For example, “Must be able to capture (or track)…”. 4. Convey the most important features for the success of your database design.​‌‍‍‍‌‍‍‌‍‌‌‍‍‍‌‍‌‌‌‍​5. Select the ideal database design for your actual or fictional business scenario using substantiating support from this week’s readings. 6. Create a list of ten questions that you would ask potential end-users during your requirements gathering specifically focusing on the “how” of the system. These non-functional requirements elicitation questions should revolve around system performance, usability, maintainability, reliability, and security. 7. Create a list of ten questions that you would ask potential end-users during your requirements gathering specifically focusing on the “what” of the system. These functional requirements elicitation questions should revolve around the expected value delivered to the end-user and specific pain points they expect to solve by using the software within their workflow. 8. Create three detailed use cases for the proposed database. Include the goals, summary, end-users (primary/secondary actors), normal flow using a use case diagram (today/without the technology), expected flow using a use case diagram (with the technology), and any additional notes that someone reviewing the script would need to know. The use cases should come from the perspective of an identified persona (e.g. physician, nurse, administrator, unit manager, supply chain manager, human resources manager, etc.). These detailed use cases should closely follow the notes contained within Slide​‌‍‍‍‌‍‍‌‍‌‌‍‍‍‌‍‌‌‌‍​ 7 of the Module 2 PowerPoint