The entities developed by Smith systems consulting require to be documented in the manner of an entity diagram since they did not develop a database. The overall goal of the project is to develop a fleet track maintenance database. An entity relationship diagram gets required to provide documentation of the process (Bagui & Earps, 2011). The entries got availed by Smith systems consulting.
The process starts off with a request by the IT project manager to the company directors. The IT project manager’s gets required to provide an accurate description of request. The IT manager describes the request as to develop a design for a fleet truck maintenance database. In the description, the IT project manager gets to provide the location for development of the database as all hub locations within the firm. The background of the project gets expounded further (Bagui & Earps, 2011). For this project, it gets explained that Smith system consulting developed entities and attributes for fleet truck maintenance but never developed the database. Resulting from the need of better documenting of the firm’s applications, entity relationship diagrams get required. The background should get connected to the expected results from the project (Bagui & Earps, 2011).
The background of the project helps to shade light on the main problem that resulted to the project. This helps to connect the background problem with the expected results for this relative project (Bagui & Earps, 2011). The expected results for this project get to be the creation of an entity diagram that shows the fleet truck maintenance database. After providing the background problem and the expected results, the IT project manager makes several change requests to the firm’s directors.
Reference
Sikha Bagui, R. E. (2011). Database Design Using Entity-Relationship Diagrams. New York:
CRC Press.
