We write custom essays and can help you with

The essay examples we publish have been submitted to us by students. The essays are the student's work and are not examples of our expert essay writers' work. READ MORE


See how we can help

Need help with your essay?

Specialized in car sales business

SYSTEM DESCRIPTION

INTRODUCTION

DMC is a Dedicated cars company that is specialized in Car sales business, and it was established Four years ago in 7th May 2005, and its main name stands for Dedicated Motor Cars and its main division is in Tripoli - Libya, it is a company with many high workers and skilled employees working on it as they are sharing the same ambition, and always aiming for the best in their business, in both to improve their employees skills and also to provide the best services to their dear customer.

DMC is really working hard to achieve a new improvement in their business every year, also to get the most popular and successful cars to get them, and for the best prices to its customers, as they are also filling their case show with a good collection in each month.

As for this month they got a very promising collection of new cars that just released this year, and old ones but got well comments from millions of people who tried them, this collection will be for this year as in this time it's the company's season time for the business.

The current system of my company is going like this, each day we are improving, and as I can see now we are well known as 1 of the top 20 Private companies in Libya, and we are also known in the other continents as well.

We are also not restrict with only 1 nationality as we are offering jobs, because our company contains employees from different nationality as we have some of them in the main division and some other are in our different offices around the globe.

DMC has a good budget as overall, and it is improving, also the customers are so pleased with our services in general, and our economical prices.

That includes that we are always taking care of our employees in terms of payment and to keep them improving by sending them to take courses in different kind of fields.

Although we are doing a pretty good job in this business field and improving by a good rate percentage every year, but we are really facing some of the major problems in our business, the main problem is that we are facing a new changes and new challenges in our business, also we have other competitors companies in the countries we are doing this business and selling our cars and making our different services.

So our main problem actually includes semi problems that we should take care of them so we can solve the main problem, which is we really need to move on with our services with the technology we are facing these days in doing those kind of business to make it better, faster, and easier.

And 1st of all is our own system in the company, because it is still not well organized as an strong infrastructure and we also need a well studied design model for this infrastructure for our company.

That's where I planned to made a Special database system to our company, which will be including our employees, our daily customers for each season, and our sales of cars on this season on as well covered by the invoice section of the company, and some specific information about our shipment idea and its fee and coverage services.

The good thing is that with this new system we will be able to make a clear and direct relational between all the sections mentioned above and make a really strong infrastructure for the company plus to be able to store information and data more sufficiently.

In this segment I would like to give you an idea about the goals and aims that we are aiming to achieve and they are:

  1. Improve the business even much further, to reach a new level of development.
  2. Reduce the paper work as we had a lost of some data from time to time.
  3. To always keep up with the other contenders companies so we won't lose our customers.
  4. Secure our data in a sufficient way.
  5. Provide a system where it is easy to get data for any of our customers.
  6. Improvement of production to satisfy the customers needs.
  7. Easy access to database and information used by employees.
  8. Remove barriers to widen its production by improving sales procedure and reducing costs.

BUISNESS ACTIVITIES & OPERATIONS

BUSINESS ACTIVITIES

This section describes the operations of DMC Company which is as I mentioned before but in more specific it deals with car sales that the company get from other retailers which recently built up a really strong relationship with DMC and are getting the best deals to expand our business.

So mainly DMC deals with customers with services, and we do car sale business, also we are very restrict with our system and the invoice we made are very clear for every car, further our employees are doing their best in every deal been made for each car.

And more to mention here for our upcoming infrastructure design is that we are going to build a new design system model that contains Cars, Employee, Invoice, Shipment, and Customer.

Those Five elements that I mentioned above will be our main focus on this database design, as it is in general what DMC is is all about.

For that matter here we are going to explain in details every Element we have for our Design Model, been explained by including its Attributes and a brief description about its main purpose.

And every element will be known later on in the database description as Entity.

Invoice Entity

This entity's main purpose is to keep track of the sales, and for every deal that have been soled by whom as an employee and for whom as a customer, also it will display all the data necessary about the product (Car) AND ITS Unique ID, plus other major information such as total price and the invoice reset number, what's more is this entity acts as the main entity related to all the other entities as it is also related to the (Shipment) entity as it also saves the shipment number in the invoice paper.

The Attributes that have been made for this Entity are: Invoice_Number, Customer_ID, Employee_ID, Shipment_Nmber, Total_Price, and Car_ID, and we will be talking about all the attributes for every entity in more details later on.

Cars Entity

This entity deals with all the cars that the company DMC stores, and contains all its details such as the car brand name, its color and the car ID, and the shipment number for every specific shipment that been made, along with the most important attribute for all the customers which is: the car's price.

Employee Entity

This entity here will be busy of containing the Employee_ID, Name, Age, Nationality, and Date of Birth, it will be also including two separated types of employees and they are: Part Time, and Full Time.

Customer Entity

This Entity is busy with giving the full information needed about the customers we are dealing with such as their Customer_ID, Name, Age, Contact_Number, and these information will be helpful in many facts in our company such as in making our invoices and assigning a specific car for a certain customer.

Shipment Entity

Shipment entity is one of the services that made our company earn its name in such a short time, as this service allow a full shipment service for as much as needed for cars for our customers viewed with its price, and a unique Shipment_Number, also the Country attributes as it tells the destination for each shipment services and the Fee attribute to tells the price for each country shown on the list.

OPERATIONS

Operation Name: Assign an Employee to handle a certain invoice.

Description: This operation handles the fact that when we are having a new invoice table, we hand it over to a certain employee, and a (certain) employee means that he/she is not busy with another invoice or another operation in the moment.

Input: The assigned Employee must appear his/her unique ID number, along with his name, and should be clear to read.

Output: The Employee will be responsible for that invoice, and handle its full data.

Operation Name: Check the Country of the Customer to make a delivery shipment service for his/her order.

Description: This operation handles the action when the Customer wants to make a shipment service for his current order and to make it to a certain country.

Input: The Customer must give information about the destination (Country) area where he/she wants to deliver the order.

Output: The Customer will be given an information about the shipment service such as the fee that known for that country.

Operation Name: Adding an Employee to the company.

Description: As DMC expanding greatly in the past years, we are making this issue more than usual lately, and it is about recruiting a new employee to the company, further adding his information to the database.

Input: For this operation we need to have the new Employee Name, Age, Nationality, and his/her Date of Birth to be able to add him/her to our database.

Output: The new Employee will be added to our database, and will be given a Unique ID number to be known as one of DMC employees.

Operation Name: Assign a Unique ID to a Customer.

Description: This operation deals with having a new customer and need to be having his/her information in our database to be given an ID number for easily checking the customer status when he/she makes more orders in the future.

Input: To make this operation successful, we need to have basic information yet helpful for us such as Name, Age, and Contact number.

Output: The Customer has been given a unique ID number.

INITIAL E.R

DESIGN SPECIFICATION

Entity Specification

Entity Name: Invoice

Entity Description: To be used as a reference of all the sales of the company.

Attribute of the Entity: Invoice_Number, Customer_ID, Car_ID, Employee_ID, Shipment_Number, Total_Price.

Entity Type: Independent.

Primary Key: Invoice_Number.

Entity Name: Customer

Entity Description: To be shown the customer basic information, along with his/her unique ID number.

Attribute of the Entity: Customer_ID, Name, Age, Contact_Number.

Entity Type: Independent

Primary Key: Customer_ID

Entity Name: Employee

Entity Description: To be shown the Employee private data inside the database.

Attribute of the Entity: Employee_ID, Name, Nationality, Date of Birth.

Entity Type: Independent (Supertype)

Primary Key: Employee_ID

Entity Name: Cars

Entity Description: To be shown the Car basic data, along with the car's price and its shipment number.

Attribute of the Entity: Brand_Name, Color, Car_ID, Shipment_Number, Price.

Entity Type: Independent

Primary Key: Car_ID

Entity Name: Shipment

Entity Description: To be shown more specific information about the shipment service, such as the countries that are available for the service, plus the fee.

Attribute of the Entity: Shipment_Number, Country, Fee

Entity Type: Independent

Primary Key: Shipment_Number

Entity Name: Full Time

Entity Description: To be shown more specific information about the Full Time employees, such as the Salary for the Full Time employees section, and the administration section which shows each full time employee and hi/her related administration division, along with the Employee ID.

Attribute of the Entity: Employee_ID, Salary, and Administration.

Entity Type: Independent (Subtype)

Primary Key: Employee_ID

Entity Name: Part Time

Entity Description: To be shown more specific information about the Part Time employees, such as their Salary as well, and the Part time employees time shifting for their work time, and for sure their employee ID..

Attribute of the Entity: Employee_ID, Salary, and Time Shifting.

Entity Type: Independent (Subtype)

Primary Key: Employee_ID

RELATIONSHIP SPECIFICATION

1. Assign

Name: Assign

Degree: 2

Type: Non-Identifying

Entities Involved: Invoice and Shipment

Connectivity: One to Many (1:M)

Direction: Arbitrary

Existence: Invoice can exist without Shipment, so it is a Optional relationship, while the Shipment cannot exist without the Invoice which is Mandatory.

Description: This is a relationship between the entity "Invoice" and the other entity "Shipment".

2. Contain

Name: Contain

Degree: 2

Type: Non-Identifying

Entities Involved: Invoice and Cars

Connectivity: One to One (1:1)

Direction: Arbitrary

Existance: Invoice cannot be made without having a Car for sale, therefore the existence of the Invoice depends on the Car, which makes it a Mandatory relationship, while the Car can exist whether there is an invoice or not, which is optional relationship.

Description: This shows the relationship between the "Invoice" entity and the "Car" entity.

3. Transport

Name: Transport

Degree: 2

Type: Non-Identifying

Entities Involved: Shipment and Cars

Connectivity: Many to Many (M:N)

Direction: Arbitrary

Existence: Shipment entity cannot exist without Cars entity which is a Mandatory relationship, while the Cars entity can exist without the Shipment entity which makes it an Optional relationship.

Description: This shows the relationship between the two entities "Cars" and Shipment".

4. Belong 2

Name: B2

Degree: 2

Type: Non-Identifying

Entities Involved: Invoice and Customer

Connectivity: One to Many (1:M)

Direction: Arbitrary

Existence: The Customer can exist without the Invoice, which makes this relationship "Optional", while the Invoice cannot exist unless it belongs to one and only one Customer, which makes this relationship "Mandatory".

Description: This shows the relationship between "Customer" and "Invoice".

5. Handle

Name: Handle

Degree: 2

Type: Non-Identifying

Entities Involved: Employee and Invoice

Connectivity: One to Many (1:M)

Direction: Arbitrary

Existence: The Employee can exist without the Invoice, which makes this relationship "Optional", while the Invoice cannot exist unless it is been handled by one and only one Employee, which makes this relationship "Mandatory".

Description: This shows the relationship between the two entities "Employee" and "Invoice".

CONSTRAINTS SPECIFICATION

- Generalization hierarchy on an Employee.

Description:

This hierarchy assigns the Employee entity as Supertype, and Full Time, Part Time as Subtypes, and since the both subtypes have many similarities, the Supertype have the ttributes in common to the subtypes and they are: Employee_ID, Name, Nationality, Date of Birth.

The subtypes cannot be one in another, means the Full Time employee cannot be a Part Time employee, and therefore this generalization hierarchy is of the type disjoint.

Type: Disjoint

Super type Entity: Employee

Super type Primary Key: Employee_ID

Common Attributes: Employee_ID, Name, Nationality, Date Of Birth.

Full Time: This subtype entity shows certain data about the Full time employees in the company and their related information which is needed to our database.

As for the attributes for this entity: Employee_ID, Salary, Administration.

Part Time: This subtype entity shows the data the other type of employees which is the part time employee type.

As for the attributes for this entity: Employe_ID, Salary, Time shifting,

BUSINESS RULES

In this section we will be listing DMC company's main rules in its business, as for our customers for an example they are able to buy as much cars as they can with no any problems but for our cars in the stock we cannot offer to sell the car for more than one and only one customer, also with our employees as any 1 of our employees can deal with more than just one car, but for the cars they should be dealt with only one employee to make the sell process.

And as for these examples here we will be listing all the business rules for our company to make sure to be followed as it is:

  1. For every Shipment service that been made, it has to be assigned into an invoice that is related to it and that is a MUST.
  2. Every Car in stock can have one invoice specialize for it; same goes for the invoice as we made only one car can fit in each invoice rather than more than just one to make the business more flexible.
  3. Every Car can have a shipment service depends on the customer's need, and as for this shipment service, it can be done for more than just one car as well, but it should be made for at least one car for this service to be available.
  4. For every single customer, he/she can belong to more than just one invoice depends on the orders he/she made and how many cars been bought, and in the other hand for the invoice it can only belong to one and only one customer, means we cannot include two customers buying the same car model in one invoice because they sold the same car model.
  5. Every employee can handle more than just one invoice when making the selling process, he/she can serve more than just one invoice, but for the invoices, every invoice should be handled by only one employee.
  6. Also we have to make sure that we won't start the buying process for our customers unless we have their personal data in our database system.
  7. For our new employees, we cannot let them start working in active business unless the process of having their personal information inside our database is done.

CONCLUSION

Critical Appraisal

As I can see from this scheme that been made, along with the other information followed by the basic and final design for my company's database, and how to provide a reasonable relationships to all the tables "Entities", I realized that with this work I have come up to a point where I did reached almost 90% of the objectives needed to be achieved, and get the goals that DMC was aiming for through this scheme.

Further more if we will be considering those steps to be done before any new system or a project to be made for the company, I'm sure that DMC will reach more heights, and the company's system will keep on being reliable, flexible, and compatible even if it is gotten bigger in business data, as for new employees, or more customers and of coarse a lot of brand new cars ever season.

And more extensive testing should have been carried out on the surface as functional testing and usability, I also would like to mention that from this project course I've really gained a far better understanding and knowledge on certain aspects of database designing and how to deal with the tables known as entities along with their attributes and the primary and foreign keys inside every entity, further more which is really helpful to our diagram design is how to normalize to 3rd normal form, also few more relational database techniques such as generalization which was really helpful to my project.

Need an essay? You can buy essay help from us today!







Request the removal of this essay.

Find out how UKEssays.com can help you with your Essays

Get help with your essay

Sign up and be the first to receive our latest offers: