Week 7 Assignment: Database Management System (DBMS) Implementation Assignment Content 1

Subject:Computer SciencePrice:18.89 Bought3

Share With

Week 7 Assignment: Database Management System (DBMS) Implementation Assignment Content 1. The implementation phase is where you install the Database Management System (DBMS) on the required hardware, optimize the database to run best on that hardware and software platform, and create the database and load the data. The initial data could be either new data or existing data imported from your SQL scripts. You also establish database objects this week and give the users that you've identified access applicable to the database requirements. Keep in mind that you are going to present your DBMS at the final project presentation day. The following are steps for the implementation assignment: 1. Install the DBMS. 2. Tune the setup variables according to the hardware, software, and usage conditions. 3. Create the database and the tables. (Every table must have a primary key, which uniquely identifies rows in the table and validation rule). 4. Establish relationships between tables. 5. Load the data into the tables. 6. Create at least three forms (splash screen and Main switchboard are optional). 7. Create at least four transaction requirement Queries. (from week 5). 8. Create data views and reports. If it is necessary for your DBMS, all transactions can be handled by SQL scripts. Submit a document report essay with screenshots and any additional files. Format your write-up in an APA-style essay and include APA-style references (if applicable). You do not need to include a title page for this assignment. Grammar, spelling, and quality will influence your grade. Week 8 Assignment: Final Project Presentation Week 8 Assignment: Final Project Presentation Assignment Content 1. For this week you need to submit your final project presentation. Include in your presentation a summary of every final project assignment: o Conceptual Modeling Design o Entity Relationship Diagram (ERD) o Logical Modeling Design o Relational Schema o Physical Modeling Design o Structured Query Language (SQL) o Database Management Systems (DBMS) o Database Management System (DBMS) Implementation Your presentation should consist of at least 12 slides, not including the title or reference slides, and be between 5-10 minutes in length. Your presentation should be engaging and provide a thorough review and summary of all components of your written final project study case. Slides should be concise and uncluttered. Use various graphics and visual enhancements when appropriate. Be sure to provide APA-style citations for any references and images used. Use an online presentation tool such as Loom to record your presentation (see these options for recording your narrated presentation). Present yourself professionally and be aware of your demeanor and appearance, as well as that of your surroundings. Your presentation should be professional and academic. Submit both your presentation slides and video recording link for your assignment submission. Please compare your work to the grading rubric before submitting it. DBMS Proposal for Hotel Booking System Name Omitted University of the People 7th August 2021 Introduction Hotel booking is complicated since it entails a lot of variables such as keeping track of users accommodated, attendants, check-in, and check-outs. The interest in the proposed system stems from the fact that hotels have grown out of filing papers in cabinets. There is a real need to keep track of the huge numbers of visitors in a database. The proposed system will make it easier for clients to book online, as well as make inquiries and cancel reservations via their phone. The acceptance and adoption of enterprise software in the travel and tourism industry have created the opportunity to develop a DBMS product to assist with hotel operations. A computerized reservation system can improve the service delivery of the hotel. Description of the Proposed System The proposed DBMS system will be named the Hotel Reservation System. The proposed system will utilize a MySQL database system and will be web-based using PHP. It will require the first and last name of the client. Other essential attributes for the entity include a valid address, phone number, and email address. The client will be identified using a unique client ID number. The system will record the attendants’ details too. The attendants will be responsible for the facilitation of customer room booking by retrieving information about available rooms. The system should have rooms as entities to ease the query transactions of suitable accommodation. The proposed system will incorporate several transactions including making a room reservation, adding customer details, canceling a reservation, check the availability of rooms, and edit room pricing. Each time a reservation is made, the status of the room is updated with the customer details occupying it. The transaction is recorded in the database. The proposed system will provide a report based on the transactions daily. It should give a customer a receipt after booking a room. The proposed system should be compatible with systems like Amazon RDS for MySQL. The deployment support in virtualized environments makes it easy for users to transfer MySQL data to a SQL Server using AWS Database Migration Service; however, it is important to consider the architectural differences between MySQL and SQL Server during the migration (Moore, 2018). Challenges of Proposed System Some of the challenges that are anticipated include maintaining the data integrity when concurrent users utilize the system. Another challenge is that troubleshooting can be delayed because MySQL logging is disabled by default thus a lack of real-time visibility. The reason for the default setting is the high costs involved. High connection churn is brought about by high concurrency among users of the proposed system since valuable server resources can be fully utilized. Uncontrollable cache invalidation can make it difficult to handle high volumes of workload. When frameworks are used in the graphical user interface, the development time of the proposed system may exceed the time budgeted. The reason is that scaling the frameworks are hard to optimize the master/slave setups where replication conflicts may emerge disrupting the data consistency (Branson, 2017). Due to scheduling problems, the check-out and payment aspects of the room reservation system will not be included. Solution The use of database load balancing software when scaling the proposed system could solve the identified challenges and keep the hotel up and running without a hitch. The load balancing facilitates read/write split to leverage readable replicas without changing the code. Response time is boosted through an intuitive approach that prevents downtime during database failovers (Branson, 2017). Conclusion The proposed system will solve the problem of paper filing systems by easy access to the database server that maintains the client and room entities' information. The querying process when booking at the hotel will be faster thus enhancing customer satisfaction. References Branson, T. (2017). The 5 Best Reasons to Choose MYSQL – And its 5 Biggest Challenges. Retrieved from: https://dataconomy.com/2017/04/5-reasons-challenges-mysql/ Moore, L. (2018). MySQL. SearchOracle. Retrieved from: https://searchoracle.techtarget.com/definition/MySQL Content 50% of total grade Meets or Exceeds Expectations provided all the required information and details required within the presentation. 85 - 100% Approaching Expectations provided some details on the required information for the assignment within the presentation but is not complete. 70 - 84% Does Not Meet Expectations Does not provide the required information or details required in • Organization 20% of total grade Meets or Exceeds Expectations Information presented in logical, interesting sequence. 85 - 100% Approaching Expectations Presentation is difficult to follow at times. Sequencing is not clear in places or is disjointed. 70 - 84% Does Not Meet Expectations Presentation is difficult to follow. Sequencing is not clear and/or is disjointed. 0 - 69% • Graphics & Screen Design 10% of total grade Meets or Exceeds Expectations Includes a variety of graphics, text, and animation that exhibits a sense of wholeness. Creative use of navigational tools and buttons. Explain and reinforce screen text and presentation. 85 - 100% Approaching Expectations Includes combinations of graphics and text, but buttons are difficult to navigate. Some buttons and navigational tools work. Occasionally uses graphics that rarely support text and presentation 70 - 84% Does Not Meet Expectations Either confusing or cluttered, barren or stark. Buttons or navigational tools are absent or confusing. Uses superfluous graphics or no graphics 0 - 69% APA formatting & Grammar 20% of total grade Meets or Exceeds Expectations Rules of APA, grammar usage and punctuation are followed; spelling and word choices are correct. 85 - 100% Approaching Expectations Presentation contains few APA formatting, grammar, punctuation, spelling, and word choice errors. 70 - 84% Does Not Meet Expectations Presentation contains numerous APA formatting, grammar, punctuation, spelling, and word choice errors. 0- • Organization and Reasoning 35% of total grade Meets or Exceeds Expectations Clear introduction and conclusion. The writing is logical, orderly, internally consistent, and well developed. Ideas are well synthesized. Topic, ideas and arguments are clearly stated for the intended audience. Shows planning and preparation. 85 - 100% Approaching Expectations The writing is logical and orderly. Effort is made to synthesize ideas. Ideas and explanations are supported by evidence. Topic, ideas and arguments are mostly clear but lack definite focus and consistency. Some effort in planning and preparation is evident. 70 - 84.99% Does Not Meet Expectations Writing is illogical, disordered, and without a professional tone. Inferences are unsupported by evidence. Topic, ideas, and argument are not stated. Poor or lack of introduction/ conclusion. Poor effort at synthesizing ideas from different sources. A lack of effort is apparent. 0 - 69.99% • Content 45% of total grade Meets or Exceeds Expectations Work demonstrates a theoretical and applied understanding of the topic. Demonstrates a synthesis of ideas and concepts. References are used appropriately to support ideas. 85 - 100% Approaching Expectations Work demonstrates a basic operational understanding of the topic and requested content details. Poor effort at synthesizing ideas from different sources. 70 - 84.99% Does Not Meet Expectations Work demonstrates a little understanding of the topic and requested content details. Poor effort at synthesizing ideas from different sources. 0 - 69.99% • Paper Mechanics 20% of total grade Meets or Exceeds Expectations Scholarly style. Appreciation to reader’s perspective is obvious. Quotations and paraphrasing are minimal and well integrated with original writing. Proper APA style. No spelling/grammar/ punctuation errors. Professional tone. Appropriate selection and use of references. 85 - 100% Approaching Expectations Shows awareness of reader’s perspective. Occasional quotations and paraphrasing that are integrated in original writing. Minor errors in APA style. Few spelling/grammar/ punctuation errors. Most references are appropriate at this level. 70 - 84.99% Does Not Meet Expectations Informal writing style with an unprofessional tone. Lacks awareness of reader’s perspective. Overuse of quotations and paraphrasing. Major errors in APA style. Many spelling/grammar/punctuation errors. References not appropriate to this level of writing. 0 - 69.99% Week 3 Assignment: Logical Modeling Design & Relational Schema Below is a logical model representing a sub domain proposed. Various entities have been identified with their attributes. Both foreign and primary keys are represented. The design also contains different cardinality. One to one and one to many relationships is applied between a doctor and a patient. A one to one and a one-to-many cardinality also exist between a doctor and a drug. The same relationship is also applied between patient and drug. Below are the entities and attributes used in this sub domain. doctorID, doctorName, DoctorEmail and DoctorPhoneNumber. Patient entity. PatientID, PatientName, PatientAge, and PatientLocation Drug entity. DrugID, DrugName, DrugType and ExpDate 1 Physical Modelling Design and SQL This assignment involves writing SQL code to create and populate the proposed tables present in week 3 assignment. Below is an SQL code which creates these tables. Data types and constraints are used in the code. To create the table doctor, the SQL code below is used: CREATE TABLE doctor ( DoctorID int (11) NOT NULL PRIMARY KEY AUTO_INCREAMENT, DoctorName Varchar (100) DoctorAge int (3) NOT NULL, NOT NULL, DoctorEmail Varchar (50) DoctorPhoneNo int (10) NOT NULL, NOT NULL ); To create table patient, the SQL code below is used. CREATE TABLE patient ( PatientID int (11) NOT NULL PRIMARY KEY, PatientName Varchar (100) PatientAge int (3) PatientPhoneNo int (10) ); NOT NULL, NOT NULL, NOT NUL 2 To create table drug, the following SQL code is used CREATE TABLE drug ( DrugID int (10) NOT NULL PRIMARY KEY, DrugName Varchar (50) NOT NULL, DrugType Varchar (50) NOT NULL, ExpDate DATE (8) NOT NULL ); 1 Most of the hospitals around the globe have failed to keep their data. Most of them are using manual methods to record information. It has been observed that files held as records are either lost or quickly demolished in case of fire or other accidents (Tripathee, 2016). Since most hospitals lack backups about the manual files kept, they end up losing meaningful information of either drug, patients, doctors, or other people present within their scope. Because of these problems, there comes a need to develop a hospital database system that can help them store their information in the cloud. This proposal is all about developing a hospital database system. The main reason for this is to help hospitals keep their records well. With a well-developed strategy, hospitals can capture doctors' information. The hospital's management team can retrieve and update any information related to them (Tripathee, 2016). Apart from recording doctors’ sensitive data, the hospital management can also capture patients’ data. Both incoming and outgoing patients can be caught, thus keeping track of them. The DBMS is needed to help the hospital keep track of its drugs. With this DBMS, all information about drugs can be captured and recorded. The proposed system users include doctors, hospital system administrators or IT experts, and the senior management team. The subdomain of a hospital database system is used on this occasion. The subsystem only contains doctors, patients, and drugs as its major entities (Amaechi James, Agbasonu & Nwawudu, 2018). Under doctors, data such as name, age, email, phone number will be captured. For the case of drugs, information such as drug name, drug id, drug type, and the expiry date of a prescription will be recorded. Patient information such as patient id, name, age, and phone number will also be recorded. 2 References Amaechi James, C., Agbasonu Valerian, C., & Nwawudu Sixtus, E. (2018). Design and Implementation of a Hospital Database Management System (HDMS) for Medical Doctors. International Journal of Computer Theory and Engineering, 10(1). Tripathee, D. (2016). Hospital Database Management System. IJCSMC, 5(4), 71-73. 1 Step 1 The entities available in the Hospital database project include: Doctor, Patient and Drug Step 2 This step is all about determining relationship that exist between entities. The table is used to determine this relationship. It is as shown below: Doctor Patient Drug Doctor Patient From the table above, different relationship exists. This includes a relationship between: Doctor and a patient where one doctor can attend to many patient Doctor and a drug Patient and a doctor Patient and a drug 2 Step 3 Below is an ER diagram indicating all the relationships, functions, and sizes which exits among various entities. Description of the ER Diagram drawn. The ER diagram represents a hospital database system (Amaechi, Agbasonu & Nwawudu, 2018). The system has various entities. These entities include: Doctor entity. The hospital employs various doctors to help attend to patients. This entity stores information about doctorID, doctorName, DoctorEmail and DoctorPhoneNumber. Patient entity. Since the hospital admits and attends to patients, some meaningful information has to be captured. This information includes PatientID, PatientName, PatientAge, and PatientLocation Drug entity stores information about DrugID, DrugName, DrugType and ExpDate 3 References Amaechi James, C., Agbasonu Valerian, C., & Nwawudu Sixtus, E. (2018). Design and Implementation of a Hospital Database Management System (HDMS) for Medical Doctors. International Journal of Computer Theory and Engineering, 10(1).