An Overview Of Spare Parts Car Computer Science Essay

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Design and implement a computer-based spare parts management system which will allow users of the Omani privet company to find out easily which spare part wants to sale and the commercial value that company has. Also where the spare parts are kept. In addition to sales and order entry, customer's, material's and supplier's details, search about the availability of items, accounts receivable and payable, provide different type of reports and bills, adding new items and reduction in the warehouse, counting the profit and lost.

The current situation

The user stores the details of customers, materials and companies in the registration books. They face difficulty to get information quickly from those books so the user spends a lot of time to get some information from those books. That means the customers have to wait long time or the employee will not record some details when he/she busy with many customers.

Warehouse stores a lot of materials, which need hours or in some cases days to be checked. Also, employee need to compare the details in books and which is available in the warehouse. So the staff spends time to check and audit. Also, this checking is not accurate since it is done manually.

The details of the customers, companies and items need to be checked and updated. This means the company has to spend the time to check the details of those manually and search from a lot of files and books to change the details.

Thousands of items are available with the company and staff confuse with sales of similar type of items. The staff will guess the price of item or he/she will check the price from several files and make the user wait for long that Lose the customer because of waiting and make him deal with other company that gives fast service, buying cheap item with expensive price, sell expensive item in cheaper price.

At the end of each month the owner wants to know the balance, the profit and loss that company mad. So, the user will check thousands of bills and writes a long report which is cost extra time and effort.

The proposed new system

A computer-based management system could aid the administration and identification of the location of spare parts, improving the situation for the users.

A computer-based system would also allow for different ways of identifying items of interest. For example, by associating keywords with a categories, it would be possible to search by keyword to find items which include many bills on the category suggested by the keyword.

In addition, if the system was readily accessible, e.g. via the web, it could also be made available to the employees and the company owner so that they also could make use of this valuable resource.

The company therefore requires a system which will enable the efficient storage, maintenance, search and retrieval of information about the items bills reports owned by the company, keywords and staff.

Functional requirements

Employees in the company should be able to

  • query, view and print information about spare parts sale information, bills and any reports belongs to the system;

  • retrieve, view and print information about the location of the spare parts;

  • update their own contact and location information;

  • change their own password.

  • Search, add, update and delete items and orders from files in the database.

  • Search, add, update, remove for customer and companies details.

  • Prepare order report: This function allows the user to show or print the daily system order

In addition, Owner of company should be able to:

  • add a new spare parts items - inputting information about them, its keywords its category;

  • add a keyword to the list of authorised keywords;

  • add a member to the user's list;

  • amend or remove existing records of the employee , e.g. change the employee, update staff details;

  • Add price amount to the items or give a special discount.

  • Count the total of each type of items.

  • Produce bills.

  • Reduction of the used items in the store.


Incremental model :

I choose an Incremental mode because it is an evolution of waterfall model. The product is designed, implemented, integrated and tested as a series of incremental builds. It is a popular model software evolution used many commercial software companies and system vendor.

Incremental software development model may be applicable to projects where:

  • Software Requirements are well defined, but realization may be delayed.

  • Generates working software quickly and early during the software life cycle.

  • More flexible - less costly to change scope and requirements.

  • Easier to test and debug during a smaller iteration.

  • Easier to manage risk because risky pieces are identified and handled during its iteration.


Interviewing the Manger of Alhadeth company (Mr Ibrahim Mohamed).

Lecture note from moodle .

Appendix 1: Methodologies

A development methodology comprises a model of how the development will proceed, and includes design, testing, and completion, as well as a manner, or method, of verifying that the process in proceeding as it should

  1. The software production process may follow different methods of software development

  2. There are many methods such as the follows:

    • The waterfall model.

    • Incremental model.

    • The prototyping model.

    • The Spiral model

The waterfall model

for systems development was popularized in the 1970's and permeates most practices. It is also called the phased model because of sequential move from one phase to another. This phased model segments the software life cycle into a series of successive activities. It has the following seven phases of development:

  • Conception.

  • Initiation.

  • Analysis.

  • Design.

  • Construction.

  • Testing.

  • Implementation and maintenance.

The Prototyping model

also known as the evolutionary model came into SDLC because of certain failures in the first version of application software. To avoid a failure of SDLC, the concept of Prototyping is used. A prototype is built to understand the requirements. The prototype is built using known requirements by viewing or using the prototype; the user can actually feel how the system will work. It gives a feel of how the real system will look. The prototype is a working model that can be used for several purposes such as:

  • Validating user requirements.

  • Performing a feasibility study of a complex system.

  • Arriving at the functional specifications for a system.

  • Establishing a starting point for further evolution.

The Spiral model :

Deal with the risks that may be faced during project development. It was first presented in 1986.each phase in the Spiral model is split into four sectors of major activities. These activities are as follows:

  • Objective setting.

  • Risk analysis.

  • Engineering.

  • Customer evaluation.

This model is inappropriate if the problem domain is well understood and no major risks exist. It is difficult and time-consuming to search for risks where none exist.

Unless the prototyping model which is expensive and the analyst may compromise on the quality of the system in order to gets the prototype working quickly. And spiral has lack of explicitly process guidance in determining objectives, constraints and alternatives. Also, there is a lack of risk assessment expertise.

APPENDIX 3: Non-functional requirements

Usability (user interface) requirements

The company requires a system to have an appropriate user interface, accessible from the desktop of every potential user. It should have a simple structure, and be self-explanatory and consistent for all types of potential user.


The system should be robust, and should minimize the possibility of incorrect input by validating input and pointing out errors to the user.


The company requires a system with authorisation for different levels of access to the system. It should provide the necessary authentication and security of information through enforcing a login and password system with different privilege categories (the latter to allow different levels of access, e.g. company owner will have admin rights, employees/staff could have rights to amend certain items of data.

Interface requirements

This system is not required to interface to any other computer system just now, although it may be useful in the future for the items information to come from a centrally held database rather than being held and maintained separately within this system.

Implementation requirements

The system should be developed on the company intranet using standard facilities, with a view to being run on the same system. The implementation language should be Oracle, to allow for greatest portability.


The company currently has thousands of items, around 30 employees. The list of keywords does not currently exist. Each category could have ten or more, although there will be some overlap.

Potential developments and reusability

The number of spare parts rise rapidly, and the list of keywords could grow to contain many hundreds of words.

Although the system is currently required by the company for management of sales spare parts, the system could be used by other companies and disciplines. In addition, the system could possibly be adapted so that it could be used for a similar companies which have the same activities. This should be born in mind when designing the system.