design an Ms access information system

Ms Access database will be used by the car vendors to store data and generate reports as specified,then when doing so a user manual have also to be generated from Ms Access database

Auto Parts Vendor Information System The aim of this project is to design and develop an Information System for an Auto Part Vendor shop. The shop is selling car parts of Renault, Fiat, Mercedes and BMW to automobile repair/mechanic shops and other individual customers. Specifications: A list of parts should be stored. Information on parts should be stored Information on factories that the shop order parts from Information on customers should be stored . Quantity of each part should be stored. Payment conditions and debts of customers should be stored. Information on parts ordered from factories. Information on back-ordered parts should be stored. The system should be able to print at least the following list of reports (This is just a recommended list, please don't forget that every additional report implemented by the project team will affect their ranking in the class): List of parts List of back-ordered parts . the class): o List of parts List of back-ordered parts O o List and status of orders List of customers with problems (such as late payments including the number of days it is overdue) A reminder letter to be issued to a customer on a specified time (near to the due date for payment). And etc... o The system should be able to perform and reply at least the following on-line queries (This is just a recommended list, please don't forget that every additional query implemented by the project team will effect their ranking in the class): Communication information about a customer. Status of a certain part. Number of parts on back-order. Number of parts purchased by a certain customer. Name of the customers who purchase a certain part, etc. o O e Project Requirements: Design a database to store all necessary data User interface on Access Tables Queries Forms o Reports You should draw: Context Diagram Level 1 and Level 2 Data Flow Diagrams (DFD) o Entity-Relationship (E-R) diagram I It should be designed as a Relational Data Base and implemented such that it can be used on a single PC with an accompanying printer. All input data should be entered into screen forms and all modifications should be done on screen forms. Cognitive ergonomic features of The User Interface should be taken into account. The written report should include a USER MANUAL. The report should be neatly written with proper content. o O