l have exam database on Tuesday 8:00am NYC time zone( will start after 6 hours from now). Topic will be included entities and relationships, determinacies and normalizationThere will be QBE,SQL and relational algebra and calculusWill you be able to help me out with those topics?exam duration time: 2 hours.l attached old exam l already took and hw problem...so when my exam will start i will send you pics, you need to solve and send me back within 2 hours.

Question 1 250 to 300 words with references Topic: Using Information Technology to assist in treating Ebola Not all information technology projects are equal when it comes to testing and soliciting feedback; for example, a software application may go through code reviews and rigorous white-box testing before delivery; an information security risk management plan may go through security testing; and a network simulator may be used to test a new network infrastructure. For your initial post, describe strategies you will use to test your project. In a real business setting, stakeholder feedback will be important. Their feedback will help you know whether you have hit the mark with their needs and how well the solution fits within the existing operating environment. Also describe the strategies you will use to get feedback from those stakeholders impacted by implementation of this project. Question 2 3 to 4 pages with references  Submit a draft of your project report that addresses the following sections: Topic: Using Information Technology to assist in treating Ebola 1. Project Implementation. If you implemented your project, describe the implementation. If your project was not implemented, how would you implement it? As you work on the project each module, the status of the project will be updated in this section. Describe the status of the implementation to date. 2. Project Test Plans and Results. If you implemented and tested your project, describe how you tested your project. If your project was not implemented or tested, how would you test it? Project Overview If you are able to implement your solution, include a summary of your implementation and testing in your report. If you are not able to implement your solution, you may develop a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project. In this case, in your report you should include a plan for implementation and testing. Your report must provide clear evidence that your project was implemented and tested (or is implementable and testable). This can be achieved by documenting a demonstration of the project in use or documenting an explanation of the model, simulation, or prototype. Consider using video or screenshots to demonstrate and explain your project. If the implemented project is to be supplied to the instructor, you could provide a user manual that explains how to install, configure, and run the software. You are encouraged to submit artifacts of the project including diagrams, software applications, database designs, process documents, etc. Make sure to include clear instructions for accessing and using these artifacts. The design and development of your project solution should demonstrate professional-level knowledge and skills. Your project report should include at least one recommendation for future enhancements. Explain what you might add to the project if you had more resources? What risk(s) would you need to consider before the enhancement was implemented at some future point in time? What would have to happen first before the future enhancement was even considered seriously?

PLEASE READ AND REVIEW ATTACHED FILE ON APEX ONLINE BANKING SYSTEMSection 9: Quality ChecklistCreate a table that includes the following:List 10–12 deliverables that would be required throughout the entire software development life cycle.Include a key statement that describes the quality review definition.This would be used as a running list of deliverables and will review the criteria for the entire project. It should contain 4 columns:Phase, or area of methodology where this deliverable is createdDeliverable nameDeliverable descriptionDescription of qualityInclude an introductory paragraph describing what the reader is looking at, and how to use the table.Section 10: Maintenance and SupportDescribe the maintenance and support plan for this software application. Indicate the following:Show how the changes will be dealt with, whether they are defects or enhancement requests. Create a diagram showing the flow.Create an overall maintenance release schedule that shows the next 4 releases and indicates the cut-off dates for changes, etc.Write 1–2 paragraphs detailing the user support plan. This should indicate what the users can count on regarding support. Include any documentation that the users may have available to them, as well as detailing first- and second-level support procedures.