Conclusions
In this section, state conclusions made by the team at the close of the project. Also state and describe limitations and improvements for future direction. Limitations and improvements can be action steps through which additional, more effective, or less costly project work can be conducted.
Final Project Report Dynamite Database Itec 485 Group 1: Christinah Adeyemi Robert Trevillian Dalton Obima Malik Herbert Ansula Banjade The Executive Summary will serve as a summary and introduction to the report, while the following four sections will explain each aspect of the project in more detail. The final section should be an appendix, which provides support for the project. More specific information on each section is listed below. NOTE: Be sure to add graphs, tables, and images to your report in case that they contain SIGNIFICANT information and place them where the section is RELEVANT. All figures/tables/images should include captions and numberings. Sections 2-5 make up the body of the report and together should be no more than 10 pages in length. Font style is Times New Roman, size is 12 and single spaced. Executive Summary The start of this semester we were given the project to create a MYSQL database for a car dealership. This car dealership sells cars of all makes and models and the inventory can change very frequently. The goal of this project is to store the current cars on the lot in a database that can be updated and managed by the dealership. Purpose and Objectives This section should include information about the need(s) the project is addressing the sponsor involved in the project. Include information about the existing technology or science involved in addressing the need(s). (If there is no information available, explain why and how your team is making its research on the needs) Organization and Approach Group text messaging was used weekly to communicate information between all members. This was very helpful to have since everyone could understand their role and get there part of the project done. We also used google docs to implement the scripts for the database before we entered them into the MYSQL program. Christianah was the team leader and gave each of the members a role in the project. Since some of the MYSQL technologies were new for some members we had a lot of testing to do to make sure this software would work. Database Defined requirements and considerations: · Product research · Informal user survey for simulated client rental or purchase entries · Task delegation for DB management and entry maintenance · Platform comparison and consideration for cross platform functionality between our group members · Scrum methodology practices and documentation of activities within time frames · Risk Identification and Mitigation strategies for protection of our internal systems; these will be FIPS compliant and adhere to the NIST SP 800-53 publication Delivered Solutions The desired outcome and goal of this project was to create a database that would be able to receive, store, manage, and retrieve data records catered to the needs of the user. The database created (Dynamite Database) was centered around car dealerships and information that would be found within a database. The database is successfully able to accept new records, manage current records, and retrieve information within the database by using unique statements specified by the user as shown by the example screenshots below. The screenshot above shows the script that created the database and the tables within it. On the left side is the schema that shows that the database has been created. The screenshot above shows the records that have been successfully inserted into the “Car” table of the database. The screenshot above shows the records that have been successfully inserted into the “Customer” table of the database. The screenshot above shows the records that have been successfully inserted into the “Employee” table of the database. The screenshots above show the data that has been inserted into both the “Service” and “Payment” tables. This screenshot shows the first example of pulling data from the database. With the shown script, the user can see the number of sales associates that are in the company. From the example, within the employee table, there are 3 sales associates. This screenshot shows the second example of pulling data from the database. With the shown script, the user can see which cars in the database are from the year 2021. From the example, within the employee table, there are 3 cars that were made in 2021. This script can be modified by the user to see any car made in any year by changing the value of ‘year’. This screenshot shows the third example of pulling data from the database. With the shown script, the user can see the information of the customers who paid for their cars in cash. From the example, within the customer table, there are 3 customers who paid in cash. This script can be modified by the user to see any customers’ payment by changing the value of ‘cash’. This screenshot shows the fourth example of pulling data from the database. With the shown script, the user can see the name of the customers listed in alphabetical order by last name. This screenshot shows the fifth example of pulling data from the database. With the shown script, the user can see the make and model of the cars listed in order by price from greatest to least. Conclusions In this section, state conclusions made by the team at the close of the project. Also state and describe limitations and improvements for future direction. Limitations and improvements can be action steps through which additional, more effective, or less costly project work can be conducted. Appendices Work Breakdown Structure Tasks Completed by Team Members: Christianah - Robert - Executive summary, Database entries, WBS, and organization and approach. Dalton - Malik - Ansula - Conclusion,