Content: Title

Content
Title Page
1.0 Analysis.............................................................................................1-27
1.1 Description of problem.........................................................................2
1.2 Objectives...........................................................................................3-5
1.3 Description of existing solution......................................................6-23
1.4 Evaluation of existing solution...........................................................24
1.5 Description of other possible solution..........................................25-26
1.6 Evaluation of other possible solution.................................................27
2.0 Design............................................................................................28-106
2.1 Plan....................................................................................................1-33
2.2 Description of method of solution...............................................34-103
2.3 Hardware....................................................................................104-106
2.4 Software..............................................................................................106
3.0 Implementation...........................................................................107-119
3.1 Method of solution described in specific details relevant to problem
.............................................................................................................107-108
3.2 Accurate method of solution......................................................109-119
4.0 Testing...........................................................................................120-226
4.1 Test Strategy.................................................................................120-226
4.2 Test Result....................................................................................120-226
5.0 Documentation............................................................................ 227-352
5.1 Technical Documentation............................................................227-329
5.2 User Documentation....................................................................330-352
6.0 Evaluation...................................................................................... 353-
6.1 ............................................................ -
6.2 ............................................................ –
7.0 Technical Skills.............................................................................. -
7.1 ............................................................ -
1.0 A NALYSIS
1.1 DESCRIPTION OF PROBLEM
The company name is United Motors and its owner is Mr. George
Koenig. It has been inaugurated the 13 July 1997. The company is situated
in Royal Road Port-Louis. It is involved in the buying and selling of
motorcycles. The company started with only 3 employees.
The business has evolved to 9 employees that means it has been

increased thrice the number of staff at the start of the business over the
last 10 years. Now the company offers more services as warranty, a
showroom is now available and has also different new models from Japan
and other countries.
Because the company is well centered, prices are low and the
company sells very good quality of motorcycles, there has been a
tremendous increase in customers during the 3 past years. Now the
company is facing some problems to manage some parts of it. There is lots
of duplication when purchases of motorcycle are made the same details
have to be written in different books and the same thing happens when
sales are made. We have some difficulty to manage the stock. Due to this
problem motorcycle are not ordered in time. When customer enquires
about a particular model of motorcycle we lose lots of time in looking for
the particular information requested in the product book therefore
customer lose patience.
We lose lots of time when reports need to be done. We have to look

for the information in different books and we have to write the report
manually. We sometime make mistakes while calculating the prices during
sales. Sometimes employees do make mistake while entering details in
different books and hence we most of the time have invalid information.
2
1.2 OBJECTIVES
COMPUTER RELA TED T ERMS
1) Creating a database.
2) The following tables will be developed:
(a) Customer table will be developed in order to store details
about customers.
(b) Supplier table will be developed in order to store details about
suppliers.
(c) Make table will be developed in order to store details about
makes of motorcycles.
(d) Product table will be developed in order to store details about
motorcycles.
(e) Purchase table will be developed in order to store details
about motorcycle purchases.
(f) Sale table will be developed in order to store details about
motorcycle sales.
3) The following interfaces will be developed:
(a) Customer interface will be developed where the user will be
able to:
(i) Add new customer details in the database.
(ii) Edit customer details in the database.
(iii) Delete customer details from the database.
(iv) Save customer details in the database.
(v) Cancel any entries at anytime.
(xi) Close form at any time.
There will also be navigation button on the interface where the user
will be able to:
(vi) Go to 1st record by clicking on a command button.
(vii) Go to next record by clicking on a command button.
(viii) Go to previous record by clicking on a command button.
(ix) Go to last record by clicking on a command button.
(x) Search any customer record from the database.
3
(b) Supplier interface will be developed where the user will be able
to:
(i) Add new supplier details in the database.
(ii) Edit supplier details in the database.
(iii) Delete supplier details from the database.
(iv) Save supplier details in the database.
will be able to:
(x) Search any supplier record from the database.
(c) Make interface will be developed where the user will be able
to:
(i) Add new make details in the database.
(ii) Edit make details in the database.
(iii) Delete make details from the database.
(iv) Save make details in the database.
(v) Cancel any entries at a.
(xi) Close form at any time anytime.
will be able to:
(x) Search any make record from the database.
4
(d) Purchase interface will be developed where the user will be
able to:
(i) Add new purchase details in the database.
(ii) Edit purchase details in the database.
(iii) Delete purchase details from the database.
(iv) Save purchase details in the database.
will be able to:
(x) Search any purchase record from the database.
(e) Sale interface will be developed where the user will be able to:
(i) Add new sale details in the database.
(ii) Edit sale details in the database.
(iii) Delete sale details from the database.
(iv) Save sale details in the database.
will be able to:
(vi) Go to 1st record by clicking on a command button by
clicking on a command button.
(x) Search any sale record from the database.
5
4) Appropriate validation checks will be introduced on different
interfaces:
(i) Type check.
(ii) Length check
(iii) Presence check.
(iv) Range check on required fields.
5) Calculation will be made automatically when a customer will buy a

product on the sales interface.
6) Whenever a purchase or a sale will be made, the stock will be

automatically updated on purchases and sales interface.
7) A password will be implemented to prevent unauthorized user to

have access to the database.
8) Report list of:
a) Customers will be automatically generated.
b) Suppliers will be automatically generated.
c) Products will be automatically generated.
d) Makes will be automatically generated.
9) A main menu will be developed in order to facilitate the switching

from one form to another.
BUSSIN ESS RELA TED TERMS

1) Better management of stock.
2) Money will be saved on filling cabinets and paperwork.
3) Decision can be made from valid information.
4) Confidential information will be protected from unauthorized users.
5) Better service to customers.
6
1.3 DESCRIPTION OF EXISTING SOLUTION
Da taflo w di agram
REQUEST DETAILS LOOK FOR REQUESTED

ABOUT A PRODUCT DETAILS
Customer 1 REQUEST
M1 Product Book
Handle Request
DETAILS OF MOTORCYCLES
+
VISIT THE SHOWROOM SALE DETAILS
MOTORCYCLE DETAILS
RELATED DOCUMENTS SALE DETAILS

+ 3 Payment M2 Sale Book
PAYMENT
Calculate Cost for
Customer Sale M3 Receipt Book
RELATED
DOCUMENTS + MOTORCYCLE SALE DETAILS
REORDER
4 REORDER PRODUCTS TO BE ORDERED
Supplier LIST
Prepare Purchase LOOK FOR A SUPPLIER
Unit M4 Supplier Book
INVOICE NUMBER
+
RECEIPT + MOTORCYCLES RECORD NEW PRODUCTS
5 PAYMENT M1 Product Book
Calculate Supplier RECORD PURCHASE

PAYMENT Payment M5 Purchase Book
LOOK FOR DETAILS

IN ALL BOOKS
REQUEST M1 Product Book

Managemen REPORT 6 REPORTS
M2 Sale Book
Preparing Reports
REPORTS M3 Receipt Book
M4 Supplier Book
7
1. When customers come to the showroom they usually ask for details
about for a specific motorcycle.
2. Then an employee looks for the information from the product book and
handles it to the customer and takes him for a visit in the showroom.
(Please see page 8 for an example of the product book)
3. If the customer is interested to buy a motorcycle, he gives to the
employee his identity card and other related documents.
4. The price and details of the motorcycle is checked from the product
book and then calculated if any discount is given. (Please see page 8 for an
example of the product book)
5. Then the employee makes two copies of a receipt using details in the
product book - one for the company and the other is for the customer.
When the client pays he is given the receipt and his documents. (Please
see page 8 for an example of the product book and page 10 for an example
of a receipt.)
6. At the end of each day the sale book is updated using the information in
the receipt. (Please see to page 12 for an example of sale book and page 10
for an example of a receipt)
7. When purchase needs to be done an employee look for products detail in
the product book and supplier details in the supplier book and then
prepare the reorder list. (Please see page 8 for an example of the product
book and page 14 for an example of the supplier book.)
8. The company then sends an invoice to the supplier. (Please see page 20
for an example of the invoice.)
9. On payment, a receipt is issued to the company along with the
motorcycles. Then the details of the new motorcycles are written in the
product book. (Please see page 16 for an example of the receipt and page 8
for an example of the product book.)
10. At the end of the day purchases are written in the purchase book.
(Please see page 18 for an example of the purchase book.)
11. Every week the management asks for a report.
12. Report is prepared using information from the supplier book, sale book,
product book and purchase book. (Please see page 14 for an example of
the supplier book, page 12 for an example of the sale book, page 8 for an
example of the product book, page 22 for an example of a report and page
18 for an example of the purchase book.)
8
PRODUCT BOOK
DATE BOUGHT:………………….
INVOICE NUMBER:………………….
MODEL:…………………………COLOUR:……………………………..
MAKE:…………………………...YEAR:…………………………………
C. OF ORIGIN:……………………………………………………………..
ENGINE CAPACITY:…………………….CC
ENGINE NUMBER:………………………………………………………..
CHASSIS NUMBER:………………………………………………………
BUYING PRICE: Rs……………SELLING PRICE: Rs………………
DATE RECEIVED:…………………
NAME OF COMPANY:……………………………………………………
ADDRESS:…………………………………………………………………
………………………………………………………………………………
REMARK:…………………………………………………………………..
………………………………………………………………………………..
………………………………………………………………………………..
DATE SOLD:………………(IF SOLD) SOLD TO:…………………………
PAGE ON SALE BOOK:………………… PAGE ON PURCHASE BOOK:………………
PAGE 1
9
DATA DICTION AR Y FOR PR ODUCT BOOK
NAME CONTENT
DATE BOUGHT Date on which the motorcycle has
been bought.
INVOICE NUMBER The number of the invoice sends to
the supplier by the company.
COLOUR Colour of the motorcycle.
MODEL Model of motorcycle.
MAKE Make of motorcycle.
YEAR Year of production of motorcycle.
C.OF ORIGIN The country where the motorcycle has
been produced.
ENGINE CAPACITY The capacity of the motor.
ENGINE NUMBER The motor serial number.
CHASSIS NUMBER The chassis serial number.
BUYING PRICE The buying price of the motorcycle.
SELLING PRICE The selling price of the motorcycle.
DATE RECEIVED The date that the company received
the motorcycle.
NAME OF COMPANY The name of the supplier.
ADDRESS The address of supplier.
REMARK Specific remark about the motorcycle.
DATE SOLD The date it was sold by the company.
SOLD TO To whom the motorcycle has been
sold.
PAGE ON SALE BOOK The page on which the sale details has
been written in the sale book.
PAGE ON PURCHASE BOOK The page on which the purchase
details has been written in the
purchase book.
10
United Motors
Royal Road Port-Louis
Tel:2414752 Fax:2480039
HEREBY CERTIFY HAVING SOLD A MOTORCYCLE
BEARIN NO………………………………………….TO Mr/Mrs…………………..
.........................................................................................RESIDING AT……………...
…………………………………………………………………………………………..
FOR THE SUM OF Rs………………………………………………………………...
WHICH ACKNOWLEDGE TO HAVE RECEIVED CASH.
THE PARTICULAR OF THE ………………………… ARE:
MAKE:……………………………………………………
MODEL:………………………………………………….
COLOUR:………………………………………………...
ENGINE NO:…………………………………………….
ENGINE CAPACITY:……………………………….CC
CHASSIS NO:……………………………………………
REGISTRATION NO:…………………………………..
DATED THE…………………………DAY OF …………………20………………...
UNITED MOTORS DIRECTOR PURCHASER
SIG:…………………………….. SIG:………………………………
I HEREBY CERTIFY THAT THIS ORIGINAL IS IDENTICAL TO THE

OTHER ORIGINAL WHICH IT HAS BEEN DULLY COLLATED.
UNITED MOTORS DIRECTOR PURCHASER
SIG:…………………………….. SIG:………………………………
11
DATA DICTION AR Y FOR RECEI PT BOOK
NAME CONT ENT
BEARING NO Invoice number.
MR/MRS Name of customer.
RESIDING AT Address of customer.
FOR THE SUM OF Price of motorcycle.
THE PARTICULAR OF THE Type (Autocycle/Motorcycle).
COLOUR The colour of the motorcycle.
ENGINE NO The motor serial number.
ENGINE CAPACITY The motor capacity.
CHASSIS NO The chassis serial number.
REGISTRATION NO The number that the motorcycle has
been registered.
DATED THE Date on which the motorcycle has been
registered.
DAY OF Day on which the motorcycle has been
registered.
20 The year on which the motorcycle has
been registered.
SIG The company manager’s signature.
SIG The purchaser’s signature
SIG The purchaser’s signature
12
`
SALE BOOK
SURNAME(BLOCK LETTERS):……………………………………………………..
NAME(BLOCK LETTERS):…………………………………………………………..
ADDRESS(BLOCK LETTERS):………………………………………………………
…………………………………………………………………………………………..
REGION(BLOCK LETTERS):………………………………………………………….
TELEPHONE NUMBER:……………………………………………………………….
NATIONAL ID:…………………………………………………………………………
PRODUCT MAKE:……………………………………………………………………...
MODEL:…………………………………………………………………………………
COLOUR:………………………………………………………………………………..
CHASSIS NUMBER:…………………………………………………………………...
ENGINE NUMBER:…………………………………………………………………….
YEAR:………………………DATE SOLD:……………………………………………
COST:……………………….DISCOUNT:……………………………………………..
NETPAY:………………………………………………………………………………..
PAGE 1
13
DATA DICTION AR Y FOR SALE BOOK
NAME CONT ENT
SURNAME The surname of the customer.
NAME The other name of the customer.
ADDRESS The address of the customer.
REGION The region where the customer lives.
TELEPHONE NUMBER The telephone number of the customer.
NATIONAL ID The national identity card number of the
customer.
PRODUCT MAKE The make of the motorcycle bought by
the customer.
MODEL The model of the motorcycle that the
customer has bought.
COLOUR The colour of the motorcycle that the
customer has bought.
CHASSIS NUMBER The chassis serial number of the
motorcycle that the customer has
bought.
ENGINE NUMBER The motor serial number of the
motorcycle that the customer bought.
YEAR The date of production of the
motorcycle that the customer has
bought.
DATE SOLD The date on which the customer bought
the motorcycle.
COST The cost of the motorcycle.
DISCOUNT The discount offered by the company (if
any).
NETPAY The price paid by the customer.
14
SUPPLIER BOOK
NAME OF COMPANY (BLOCK LETTERS): …………………………
……………………………………………………………………………….
ADDRESS (BLOCK LETTERS):…………………………………………
………………………………………………………………………………..
REGION:……………………………………………………………………
TELEPHONE NUMBER:………………………………………………….
FAX NUMBER:…………………………………………………………….
CONTACT PERSON:……………………………………………………...
………………………………………………………………………………..
PAGE 1
15
DATA DICTION AR Y FOR SU PPLI ER BOOK
NAME CONT ENT
NAME OF COMPANY The name of supplier’s company.
ADDRESS The address of the company.
REGION The region where the supplier company
is situated.
TELEPHONE NUMBER The telephone number of the supplier.
FAX NUMBER The fax number of the supplier.

CONTACT PERSON The name of the person in charge of the
supplier’s company.
16
Ally Motors
51, ANTHELM MNT ROCHE
Tel: 2170096 Fax: 2481234
HEREBY CERTIFY HAVING SUPPLYING MOTORCYCLES
BEARING NO………………………………………….TO ……...…………………..
AT…………….......................................................................................................……..
FOR THE SUM OF Rs………………………………………………………………...
WHICH ACKNOWLEDGE TO HAVE RECEIVED………………………………
THE PARTICULAR OF THE ……………………………………………………….

ARE:
MAKE:……………………………………………………
MODEL:………………………………………………….
COLOUR:………………………………………………...
ENGINE NO:…………………………………………….
ENGINE CAPACITY:……………………………….CC
CHASSIS NO:……………………………………………
REGISTRATION NO:…………………………………..
DATED THE…………………………DAY OF …………………20………………...
ALLY MOTORS DIRECTOR PURCHASER
SIG:…………………………….. SIG:………………………………
I HEREBY CERTIFY THAT THIS ORIGINAL IS IDENTICAL TO THE

OTHER ORIGINAL WHICH IT HAS BEEN DULLY COLLATED.
ALLY MOTORS DIRECTOR PURCHASER
SIG:…………………………….. SIG:………………………………
17
DATA DICTION AR Y FOR RECEI PT FR OM S UPPL IER
NAME CONT ENT
BEARING NO. Invoice number.
MR/MRS Name of customer.
RESIDING AT Address of customer.
FOR THE SUM OF Price of motorcycle.
THE PARTICULAR OF THE Type (Autocycle/Motorcycle).
COLOUR The colour of the motorcycle.
ENGINE NO The motor serial number.
ENGINE CAPACITY The motor capacity.
CHASSIS NO The chassis serial number.
REGISTRATION NO The number that the motorcycle has
been registered.
DATED THE Date on which the motorcycle has been
registered.
DAY OF Day on which the motorcycle has been
registered.
20 The year on which the motorcycle has
been registered.
SIG The supplier’s manager’s signature.
SIG The supplier’s manager’s signature.
18
PURCHASE BOOK
INVOICE NUMBER: ……………………
SUPPLIER NAME (BLOCK LETTERS)………………………………...
…………………………………………………….………………………….
TELEPHONE NUMBER:………………………………………………….
ADDRESS (BLOCK LETTERS):…………………………………………
………………………………………………………………………………..
MODEL:…..………………………………………………………………...
ENGINE CAPACITY:…………………………CC
CHASSIS NUMBER:..…………………………………………………….
YEAR:……………………………COUNTRY:…………………………...
DATE BOUGHT: ………………………………………………………….
REMARK:…………………………………………………………………
………………………………………………………………………………
………………………………………………………………………………
………………………………………………………………………………
PAGE 1
19
DATA DICTION AR Y FOR PUR CHASE BOOK
NAME CONTENT
SUPPLIER NAME The name of the supplier’s
company/Name of contact person.
TELEPHONE NUMBER The telephone number of the supplier.
ADDRESS The address of the supplier.
MODEL The model pf the product bought.
ENGINE CAPACITY The motor capacity of the motorcycle.
ENGINE NUMBER The motor serial number of the bought
motorcycle.
CHASSIS NUMBER The chassis serial number of the
bought motorcycle.
YEAR The year of production of the product.
COUNTRY The country of origin of the
motorcycle.
DATE BOUGHT Date on which the Motorcycle has
been bought.
REMARK Specific remark about the motorcycle
(ex any damage or second hand).
20
INVOICE
NO:……………………………
NAME OF PURCHASER:………………………………………….……...…………
………………………………………………………………………………………….
PRODUCT MAKE:.…………………………………………………………………...
…………………………………………………………………………………………..
PRODUCT MODEL:………………………………………………………………….
…………………………………………………………………………………………..
UNIT PRICE (INCLUDING DISCOUNT): Rs……………………………………

…
QUANTITY:……………………………………………………………………………
…………………………………………………………………………………………..
TOTAL PRICE: Rs……………………………………………………………………
21
DATA DICTION AR Y FOR INV OICE S ENDED BY TH E
SUP PLIER
NAME CONT ENT
NO The number of the invoice.
NAME OF PURCHASER The name of the company.
PRODUCT MAKE The make of the motorcycle.
PRODUCT MODEL The model of the motorcycle.
UNIT PRICE The unit price of only one motorcycle
calculated after discount.
QUANTITY The quantity commanded.
TOTAL PRICE The price of all the motorcycle bought
(quantity multiply by unit price).
22
PRODUCT REPORT
NO:……………………………………………………………….
NAME OF MAKE MODEL UNIT QUANTITY

SUPPLIER PRICE IN STOCK
1.4 EV AL UATION OF EXI STING S OL UTION

AD VANT AGES OF EX IST ING SY ST EM:
(i) The handling of the system is easy and requires no trained staff.
(ii) The existing system is less costly to run as it does not requires
electricity thus neither electrical circuit installation nor monthly
electricity bill to be paid.
(iii) The work can still be done if one employee is ill.
23
DATA DICTION AR Y FOR INV OICE S ENDED BY TH E
SUP PLIER
NAME CONT ENT
NO The number of the invoice.
NAME OF SUPPLIER The name of the supplier.
MAKE The make of the motorcycle.
MODEL The model of the motorcycle.
PRICE The unit price of motorcycle.
QUANTITY The quantity in stock.
24
1.4 EVALUATION OF EXISTING SOLUTION
AD VANT AGES OF EX IST ING SY ST EM:

(iv) The handling of the system is easy and requires no trained staff.
(v) The existing system is less costly to run as it does not requires
electricity thus neither electrical circuit installation nor monthly
electricity bill to be paid.
(vi) The work can still be done if one employee is ill.
DISAD VANT AGE S OF EXIS TING SY STEM:

1) There is duplication of information hence we lose lots of time in
writing the same information.
2) There are some problems to manage the stock and this leads to
failing of ordering of motorcycle in time.
3) It takes lots of time to search for particular information,
sometimes customers lose patience.
4) Lots of time is lost while making reports as it is done manually.
5) Sometimes mistakes are made while calculating the price when
sales are made and this leads to a lost of benefits for the
company.
6) Mistakes often happen while writing information in the different
books.
25
1.5 DESCRIPTION OF OTHER POSSIBLE SOLUTIONS
SOL UT ION 1 (MANU AL SY STEM ):
The first possible solution is to employ more people (about 3 persons)
(i) Helping to prepare reports.
(ii) Helping to search under demand of customer.
(iii) Helping in filling in different books.
AD VANT AGES OF S OL UTION 1:

(i) Solution is already available. People with minimum basic
qualification can be immediately being employed.
(ii) No training needs to be paid.
DISAD VANT AGE S OF SOL UT ION 1:

(i) It will cost lots in terms of salary and benefits.
(ii) Duplication will still need to be done.
(iii) Searching will improve but will still takes time.
(iv) Employees can still make mistake while entering information in
different books.
(v) Reports will still be done manually, hence will still take time.
26
SOL UT ION 2 (COMPUT ERIZED SY STEM):
The second possible solution is to create a computerized system to
manage transactions and records of database. This computer system will
comprise of a program including different interfaces which will ease in the
handling of transactions that takes place in the business, such as Sales
and Purchases of motorcycle.
AD VANT AGES OF S OL UTION 2:
(i) A computer cost only Rs 30,000 with no monthly payment.
(ii) No duplication will be needed.
(iii) Searching will not take much time.
(iv) Report will be automatically generated.
(v) Mistakes will be avoided as validation checks will be
implemented.
DISAD VANT AGE S OF SOL UT ION 2:

(i) Have to pay for the training of staff.
(ii) Electricity bill will need to be paid.
(iii) If the computer breaks down the work will no longer continue.
27
1.6 EVALUATION OF OTHER POSSIBLE SOLUTION
SOL UT ION 1 (MANU AL SY STEM ):
After having evaluated the two proposed solutions, it has been concluded
that the computerized (Solution 2) will be implemented the decision was
taken by considering the advantages and disadvantages of both solutions.
SCOPE OF PR OPOSED SO LUTION
1) In the long run the company will be able to get money invested back.
2) Since the system will be automated, there will be lots of facilities.
3) Search will be done faster.
4) Report will be automatically automated.
5) Calculations will be done automatically when a customer buys a product.
6) We will be able to handle details of make, products and customers.
7) Less error will be made while entering data due to validation checks.
8) When purchases and sales will be made the stock will automatically
updated.
9) Password will be implemented to prevent unauthorized users have
access to the database.
10) A menu will be developed which will include different interfaces and
make the handling of transaction that takes place such as sales and
purchases of new product more easily.
28
2.0 D ESI GN
2.1 PLAN
In order to solve the problem, it is intended to treat the different
modules separately using top down approach it involves breaking down an
over all task into a smaller one make it more easily manageable tasks
output and input screens will be designed.
USING MODULAR PR OGRAMMING

(i) Each problem will be treated as a separate module.
(ii) An algorithm will be developed for each module.
(iii) Each module and algorithm will be linked to the specific problems
already outlined so as to meet the aims and objectives.
(iv) All the forms will be presented in a united way on a menu.
HERE ARE THE REASON S WHY MODULAR PR OGRAMMING

WAS CHOSEN.
(i) Smaller modules are easier to write.
(ii) The complex task of testing and debugging becomes easier.
(iii) Development time is shorter.
(iv) Modules can be added or removed without affecting the whole system.
29
MOTORCYCLE
4.0 MAIN MENU

(5.0 PASSWORD)
DATABASE AND 2.0 INTERFACES 3.0 REPORTS

TABLES DEVELOPMENT DEVELOPMENT
1.0 D ATAB ASE AND TABLE S DEVEL OPMENT

A database called MOTORCYCLE.MDB will be created there at
all related tables will be created within their appropriate fields and
corresponding data type.
TASK ST AR TED END RELA TED
DATE DATE OBJECTIVE
S
CREATION OF THE DATABASE 08/05/07 08/05/07 1
CREATION OF TABLES: 2
(a) CUSTOMER 08/05/07 08/05/07 2(a)
(b) SUPPLIER 08/05/07 08/05/07 2(b)
(c) MAKE 08/05/07 08/05/07 2(c)
(e) PRODUCT 08/05/07 08/05/07 2(d)
(f) PURCHASE 08/05/07 08/05/07 2(e)
(g) SALE 08/05/07 08/05/07 2(f)
2.0 INT ERF ACES DEVEL OPMEN T

Customer interface will be created where the user will be able
to handle details about customers.
DATE DATE OBJECTIVE
30
S
DEVELOPMENT OF THE 10/05/07 10/05/07 3
CUSTOMER INTERFACE
ADD 10/05/07 10/05/07 3(a)(i)
DELETE 10/05/07 10/05/07 3(a)(iii)
CANCEL 10/05/07 10/05/07 3(a)(v)
SAVE 10/05/07 10/05/07 3(a)(iv)
CLOSE 10/05/07 10/05/07 3(a)(xi)
NAVIGATE TO 1ST RECORD 10/05/07 10/05/07 3(a)(vi)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(a)(ix)
SEARCH 10/05/07 10/05/07 3(a)(x)
NAVIGATE TO NEXT RECORD 10/05/07 10/05/07 3(a)(vii)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(a)(viii)
VALIDATE 10/05/07 10/05/07 4(i)-4(iv)
Supplier interface will be created where the user will be able to

handle details about suppliers.
TASK STAR TED END RELA TED
DATE DATE OBJECT IVE
S
SUPPLIER INTERFACE
ADD 10/05/07 10/05/07 3(b)(i)
DELETE 10/05/07 10/05/07 3(b)(iii)
CANCEL 10/05/07 10/05/07 3(b)(v)
SAVE 10/05/07 10/05/07 3(b)(iv)
CLOSE 10/05/07 10/05/07 3(b)(xi)
ST
NAVIGATE TO 1 RECORD 10/05/07 10/05/07 3(b)(vi)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(b)(ix)
SEARCH 10/05/07 10/05/07 3(b)(x)
NAVIGATE TO NEXT RECORD 10/05/07 10/05/07 3(b)(vii)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(b)(viii)
VALIDATE 10/05/07 10/05/07 4(i)-4(iv)
31
Make interface will be created where the user will be able to
handle details about makes.
DATE DATE OBJECTIVE
S
DEVELOPMENT OF THE MAKE 10/05/07 10/05/07 3
INTERFACE
ADD 10/05/07 10/05/07 3(c)(i)
DELETE 10/05/07 10/05/07 3(c)(iii)
CANCEL 10/05/07 10/05/07 3(c)(v)
SAVE 10/05/07 10/05/07 3(c)(iv)
CLOSE 10/05/07 10/05/07 3(c)(xi)
NAVIGATE TO 1ST RECORD 10/05/07 10/05/07 3(c)(vi)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(c)(ix)
SEARCH 10/05/07 10/05/07 3(c)(x)
NAVIGATE TO NEXT RECORD 10/05/07 10/05/07 3(c)(vii)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(c)(viii)
VALIDATE 10/05/07 10/05/07 4(i)-4(iv)
Purchase interface will be created where the user will be able

to handle details about purchases.
DATE DATE OBJECTIVE
S
PURCHASE INTERFACE
ADD 10/05/07 10/05/07 3(d)(i)
DELETE 10/05/07 10/05/07 3(d)(iii)
CANCEL 10/05/07 10/05/07 3(d)(v)
SAVE 10/05/07 10/05/07 3(d)(iv)
CLOSE 10/05/07 10/05/07 3(d)(xi)
NAVIGATE TO 1ST RECORD 10/05/07 10/05/07 3(d)(vi)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(d)(ix)
SEARCH BY INVOICE 10/05/07 10/05/07 3(d)(x)
NAVIGATE TO NEXT RECORD 10/05/07 10/05/07 3(d)(vii)
32
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(d)(viii)
VALIDATE 10/05/07 10/05/07 4(i)-4(iv)
UPDATE STOCK 10/05/07 10/05/07 6
Sale interface will be created where the user will be able to

handle details about customers.
DATE DATE OBJECTIVE
S
DEVELOPMENT OF THE SALE 10/05/07 10/05/07
INTERFACE
ADD 10/05/07 10/05/07 3(e)(i)
DELETE 10/05/07 10/05/07 3(e)(iii)
CANCEL 10/05/07 10/05/07 3(e)(v)
SAVE 10/05/07 10/05/07 3(e)(iv)
CLOSE 10/05/07 10/05/07 3(e)(xi)
ST
NAVIGATE TO 1 RECORD 10/05/07 10/05/07 3(e)(vi)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(e)(ix)
33
SEARCH 10/05/07 10/05/07 3(e)(x)
NAVIGATE TO NEXT RECORD 10/05/07 10/05/07 3(e)(vii)
NAVIGATE TO LAST RECORD 10/05/07 10/05/07 3(e)(viii)
VALIDATE 10/05/07 10/05/07 4(i)-4(iv)
AUTOMATIC CALCULATION 10/05/07 10/05/07 5
UPDATE STOCK 10/05/07 10/05/07 6
3.0 REPOR TS L IST

Report list will be automatically generated.
DATE DATE OBJECTIVE
S
CREATION OF REPORTS: 15/05/07 15/05/07
(a) LIST OF CUSTOMER 15/05/07 15/05/07 8(a)
(b) LIST OF SUPPLIER 15/05/07 15/05/07 8(b)
(c) LIST OF PRODUCTS 15/05/07 15/05/07 8(c)
(e) LIST OF MAKES 15/05/07 15/05/07 8(d)
4.0 MAIN M ENU

A main menu will be displayed on opening the software.
DATE DATE OBJECTIVE
S
CREATION OF MAIN MENU: 16/05/07 16/05/07
(a) BUTTON FOR FORMS 16/05/07 16/05/07 9
(b) BUTTON FOR REPORTS 16/05/07 16/05/07 9
(c) EXIT TO WINDOWS 16/05/07 16/05/07 9
34
5.0 P AS SW OR D
A password will be implemented to prevent unauthorized
users to get access to confidential information.
DATE DATE OBJECTIVE
S
CREATION OF PASSWORD: 16/05/07 16/05/07 7
2.2 DESCRIPTION OF METHOD OF SOLUTION

DATAB ASE AND TABLE S DESIGN
DATAB ASE USED I S MO TOR CY CLE.MDB .
RELATIONSHIPS
35
SUPPLIER ID
PRODUCT ID
SUPPLIER ID
MAKE ID
∞
1 1
∞
PRODUCT ID
MAKE ID
SUPPLIER ID
1
∞
∞
PRODUCT ID
CUSTOMER ID
CUSTOMER ID
1
1
∞
TABLE N AME: CUST OMER_T ABLE

TABLE PURPO SE: ST ORE DET AILS ABOUT CUS TOMERS.
FIELD N AME DATA TYP E FIELD SI ZE
customerid Autonumber Long Integer
36
surname text 10
nameofcustomer text 10
address text 50
region text 20
mobile text 7
nid text 20
Primary key: customerid
TABLE N AME: SUP PLIER_ TABLE
TABLE PURPO SE: ST ORE DET AILS ABOUT SU PPLI ERS.
supplierid Autonumber Long Integer
nameofcompany text 20
address text 30
region text 10
telephonenumber text 7
faxnumber text 7
contactperson text 20
Primary key: supplierid
TABLE N AME: MAKE_T ABLE
TABLE PURPO SE: ST ORE DET AILS ABOUT MAKES.
makeid Autonumber Long Integer
make text 20
stockquantity number Long Integer
regionstatus text 20
remarks text 20
Primary key: makeid
TABLE N AME: PR ODUCT_T ABLE

TABLE PURPO SE: ST ORE DET AILS ABOUT PR ODUCTS.
productid Autonumber Long Integer
37
makeid number Long Integer
supplierid number Long Integer
model text 10
cc text 5
year text 4
country text 10
colour text 10
chasisnumber text 20
enginenumber text 20
buyingcost currency
selling cost currency
date_received date/time
remark text 20
Primary key: productid
TABLE N AME: PUR CHASE_T ABLE
TABLE PURPO SE: ST ORE DET AILS ABOUT PUR CHASE S.
purchaseid Autonumber Long Integer
supplierid number Long Integer
productid number Long Integer
date_bought date/time
cost currency
invoicenumber text 20
Primary key: purchaseid
TABLE N AME: SALE_ TABLE

TABLE PURPO SE: ST ORE DET AILS ABOUT SALE S.
38
saleid Autonumber Long Integer
custimerid number Long Integer
productid number Long Integer
datesold date/time
cost currency
discount currency
netpay currency
Primary key: saleid
INT ERF ACES DEVEL OPMEN T

INT EFACE N AME: SUP PLIER_IN TEF ACE.
INT ERF ACE PURPOS E: HAN DLE DE TAILS OF SU PPLI ERS.
39
SUPPLIERS FORM
SUPPLIER DETAILS
SUPPLIER ID 1
NAME 2 8 9
ADDRESS 3
REGION 4 10 11 12 13 14 15 16
TELEPHONE NUMBER 5
CLOSE FORM17
FAX NUMBER 6
CONTACT PERSON 7
40
# TYPE PROPERTIES VALUE
1 TEXTBOX NAME Supplierid
2 TEXTBOX NAME Nameofcompany
EVENT PROCEDURE On lost focus
3 TEXTBOX NAME Address
4 TEXTBOX NAME Region
5 TEXTBOX NAME Telephonenumber
6 TEXTBOX NAME Contact
7 TEXTBOX NAME Faxnumber
8 COMMAND BUTTON NAME cmdsave
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
9 COMMAND BUTTON NAME CMDFNDREC
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTFREC
0
CAPTION
PICTURE Bitmap
41
11 COMMAND BUTTON NAME GTLREC
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCANREC
2
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDDELREC
3
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME cmdadd
4
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME GTPREC
5
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTLREC
6
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCLOFRM
7
CAPTION Close Form
42
ADD NEW RECORD, VALIDATE AND SAVE PROCESS
START
CLEAR ALL
TEXTBOXES
INPUT
REQUIRES
DETAILS
VALIDATE
YES DISPLAY
ERROR?
MESSAG
E
NO
SAVE RECORD
SUPPLIER
DISPLAY
MESSAG
E
END
When the user clicks on the “Add button”:-

1. All text boxes are cleared
2. The user input required details about the customers.
3. It is then validated on clicking on the “save button” if there is:-
(i) Any mistake a message will be displayed to the user and he will
need to correct the invalid information.
(ii) No mistake the record will be saved in the supplier table.
4. A message will appear in order to inform the user that the record has been
saved successfully.
43
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
SUPPLIER
NO
HAS RECORD
BEEN
ERROR
YES
MESSAG
E
DISPLAY
RECORD
END
SEARCH PROCESS
1. When the user clicks on the “Search button” he will be asked for the criteria.
2. When the criteria has been entered the details will be searched from the
supplier table if the details have:-
(i) Not been found, an error message will be displayed saying that the
record has not been found.
(ii) Been found, the record from the supplier table will be displayed.
44
MOVE TO 1ST RECORD PROCESS
START
MOVE TO 1ST
RECORD SUPPLIER
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to 1st record button” the first record in the
supplier table will be displayed.
45
MOVE TO PREVIOUS RECORD PROCESS
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAGE FILE?
E
NO SUPPLIER
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to previous record” the computer checks
if it is not already showing the last record if:-
(i)Yes a message will be displayed saying that it cannot go to a specified
record.
(ii)No the previous record from the supplier table will be displayed.
46
CANCEL PROCESS
START
CLEAR ALL TEXT

BOXES
END
CANCEL PROCESS
1. When the user clicks on the “Cancel button” all text boxes are cleared.
47
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
SUPPLIER
END
DELETE PROCESS
1. When the user clicks on the “Delete button” a confirmation message will
appear to him asking if he wants to delete the record if he clicks:-
(ii) No, another message will be displayed saying that the record has
not been deleted.
(iii) Yes, the record will be deleted in the supplier table.
48
MOVE TO NEXT RECORD PROCESS
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAG FILE?
EEE
NO SUPPLIER
MOVE TO NEXT
RECORD
DISPLAY
MESSAG
E
END
1. When the user clicks on the “Go to next record” the computer checks if it
is not already showing the last record if:-
record.
(ii)No the next record from the supplier table will be displayed.
49
MOVE TO LAST RECORD PROCESS
START
MOVE TO LAST
RECORD SUPPLIER
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to last record button” the last record is
displayed.
CLOSE PROCESS
START
CLOSE FORM
END
CLOSE PROCESS
1. When the user clicks on the “Close button” the form is closed.
50
INT EFACE N AME: CUST OMER_IN TEF ACE.
INT ERF ACE PURPOS E: HAN DLE DE TAILS OF CUST OM ERS.
CUSTOMERS FORM
CUSTOMER DETAILS
CUSTOMER ID 1
NAME 2 8 9
SURNAME 3
10 11 12 13 14 15 16
ADDRESS 4
REGION 5
CLOSE FORM17
ADDRESS 6
REGION 7
51
1 TEXTBOX NAME customerid
2 TEXTBOX NAME nameofcustomer
3 TEXTBOX NAME surname
4 TEXTBOX NAME address
5 TEXTBOX NAME region
6 TEXTBOX NAME mobile
7 TEXTBOX NAME nid
CAPTION
PICTURE Bitmap
9 COMMAND BUTTON NAME CMDFNDREC2
CAPTION
PICTURE Bitmap
10 COMMAND BUTTON NAME CMDGTFREC2
CAPTION
PICTURE Bitmap
52
11 COMMAND BUTTON NAME CMDGTPREC
CAPTION
PICTURE Bitmap
12 COMMAND BUTTON NAME CMDCANREC2
CAPTION
PICTURE Bitmap
13 COMMAND BUTTON NAME CMDDELREC2
CAPTION
PICTURE Bitmap
14 COMMAND BUTTON NAME cmdadd
CAPTION
PICTURE Bitmap
15 COMMAND BUTTON NAME CMDGTNREC2
CAPTION
PICTURE Bitmap
CAPTION
PICTURE Bitmap
17 COMMAND BUTTON NAME CMDCLOFRM2
CAPTION Close Form
53
START
CLEAR ALL
TEXTBOXES
INPUT
REQUIRES
DETAILS
VALIDATE
YES DISPLAY
ERROR?
MESSAG
E
NO
SAVE RECORD
CUSTOMER
DISPLAY
MESSAG
E
END

(i) Any mistake a message will be displayed to the user and he will
need to correct the invalid information.
(ii) No mistake the record will be saved in the customer table.
4. A message will appear in order to inform the user that the record has been
saved successfully.
54
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
CUSTOMER
NO
HAS RECORD
BEEN
ERROR
YES
MESSAG
E
DISPLAY
RECORD
END
SEARCH PROCESS
1. When the user clicks on the “Search button” he will be asked for the
criteria.
2. When the criteria has been entered the details will be search from the
customer table if the details have:-
(i) Not been found, an error message will be displayed saying that
the record has not been found.
(ii) Been found, the record will be displayed from the customer
table.
55
START
MOVE TO 1ST
RECORD CUSTOMER
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to 1st record button” the first record is
displayed from the customer table .
56
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAGE FILE?
E
NO CUSTOMER
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
record.
(ii)No the previous record from the customer table will be displayed.
57
CANCEL PROCESS
START
CLEAR ALL TEXT

BOXES
END
CANCEL PROCESS
58
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
CUSTOMER
END
DELETE PROCESS
(i) No, another message will be displayed saying that the record has
not been deleted.
(ii) Yes, the record will be deleted in the customer table.
59
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAG FILE?
EEE
NO CUSTOMER
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
(i) Yes a message will be displayed saying that it cannot go to a
specified record.
(ii) No the next record from the customer table will be displayed.
60
START
MOVE TO LAST
RECORD CUSTOMER
DISPLAY
DETAILS
END
displayed.
CLOSE PROCESS
START
CLOSE FORM
END
CLOSE PROCESS
61
INT EFACE N AME: MAKE_INT EFACE.
INT ERF ACE PURPOS E: HAN DLE DE TAILS OF SU PPLI ERS.
MAKES FORM
MAKE DETAILS
MAKE ID 1
MAKE 2 6 7
STOCK QUANTITY 3
8 9 10 11 12 13 14
STATUS 4
REMARK 5
CLOSE FORM15
62
1 TEXTBOX NAME makeid
2 TEXTBOX NAME Make
3 TEXTBOX NAME stockquantity
4 COMBO BOX NAME status
ROW SOURCE TYPE On lost focus
ROW SOURCE
COLUMN COUNT
5 TEXTBOX NAME remarks
6 COMMAND BUTTON NAME CMDSAVREC
CAPTION
PICTURE Bitmap
7 COMMAND BUTTON NAME CMDFNDREC
CAPTION
PICTURE Bitmap
CAPTION
PICTURE Bitmap
CAPTION
PICTURE Bitmap
63
0
CAPTION
PICTURE Bitmap
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDADDREC
2
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTNERC
3
CAPTION
PICTURE Bitmap
4
CAPTION
PICTURE Bitmap
5
CAPTION Close Form
64
START
CLEAR ALL
TEXTBOXES
INPUT
REQUIRES
DETAILS
VALIDATE
YES DISPLAY
ERROR?
MESSAG
E
NO
SAVE RECORD
MAKE
DISPLAY
MESSAG
E
END

a. Any mistake a message will be displayed to the user and he will need to
correct the invalid information(s).
b. No mistake the record will be saved in the make table.
4. A message will appear in order to inform the user that the record has
been saved successfully.
65
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
MAKE
NO
HAS RECORD
BEEN
ERROR
YES
MESSAG
E
DISPLAY
RECORD
END
SEARCH PROCESS
1. When the user clicks on the “Search button” he will be asked for the criteria.
2. When the criteria has been entered the details will be searched from the make
table if the details have:-
(iii) Not been found, an error message will be displayed saying that the
record has not been found.
(iv) Been found, the record will be displayed from the make table.
66
START
MOVE TO 1ST
RECORD MAKE
DISPLAY
DETAILS
END
Displayed from the make table.
67
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAGE FILE?
E
NO MAKE
MOVE TO NEXT
RECORD
DISPLAY
RECORD
END
record.
(ii)No the previous record will be showed from the make table.
68
CANCEL PROCESS
START
CLEAR ALL TEXT

BOXES
END
CANCEL PROCESS
69
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
MAKE
END
DELETE PROCESS
(i) No, another message will be displayed saying that the record has
not been deleted.
(ii) Yes, the record will be deleted from the make table.
70
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAG FILE?
EEE
NO MAKE
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
record.
(ii)No the next record will be showed from the make table.
71
START
MOVE TO LAST
RECORD MAKE
DISPLAY
DETAILS
END
displayed.
CLOSE PROCESS
START
CLOSE FORM
END
CLOSE PROCESS
72
INT EFACE N AME: PUR CHASE_IN TEF ACE.
INT ERF ACE PURPOS E: HAN DLE DE TAILS OF PUR CHASE S.
PURCHASES FORM
PRODUCT DETAILS MAKE DETAILS
PRODUCT ID 1
MAKE ID 14
COLOUR 2
MAKE 15
CHASSIS NUMBER 3
INVOICE DETAILS
ENGINE NUMBER 4
INVOICE NUMBER 16
ENGINE CAPACITY 5
STATUS 6
SUPPLIER DETAILS
SUPPLIER ID 17
STOCK QUANTITY 7
NAME OF COMPANY 18
MODEL 8
CONTACT PERSON 19
YEAR 9
COUNTRY OF ORIGIN 10
DATE BOUGHT 11
20 21
COST 12
REMARK 13 22 23 24 25 26 27 28
CLOSE FORM29
73
1 TEXTBOX NAME productid
2 COMBO BOX NAME colour
ROW SOURCE TYPE Table/Query
ROW SOURCE Colour
COLUMN COUNT 1
3 TEXTBOX NAME chasisnumber
4 TEXTBOX NAME enginenumber
5 TEXTBOX NAME cc
6 COMBO BOX NAME status
ROW SOURCE Status-product
COLUMN COUNT 1
8 TEXTBOX NAME model
9 COMBO BOX NAME year
ROW SOURCE year
COLUMN COUNT 1
1 TEXTBOX NAME country
0
11 TEXTBOX NAME txtdate
1 TEXTBOX NAME txtcost
2
1 TEXTBOX NAME remark
3
1 COMBO BOX NAME makeid
4
ROW SOURCE make
COLUMN COUNT 3
1 TEXTBOX NAME make
74
5
1 TEXTBOX NAME txtinvoicenumber
6
1 COMBO BOX NAME supplierid
7
ROW SOURCE Supplier
COLUMN COUNT 3
1 TEXTBOX NAME nameofcompany
8
1 TEXTBOX NAME contactperson
9
0
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDFNDRECORD
1
CAPTION
PICTURE Bitmap
2
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTPREC2
3
CAPTION
PICTURE Bitmap
75
4
CAPTION
PICTURE Bitmap

5
CAPTION
PICTURE Bitmap
6
CAPTION
PICTURE Bitmap
7
CAPTION
PICTURE Bitmap
8
CAPTION
PICTURE Bitmap
9
CAPTION Close Form
76
PURCHASE AND UPDATE STOCK PROCESS
START
CHOOSE
SUPPLIER &
MAKE SUPPLIER
MAKE ID
DISPLAY
SUPPLIER &
MAKE
DETAILS
ENTER
PRODUCT
DETAILS
DISPLAY
MESSAG
E YES VALIDATE
NO
ERROR?
NO
PRODUCT UPDATE STOCK
PURCHASE UPDATE PURCHASE
UPDATE MAKE
MAKE STOCK
77
END
PURCHASE AND UPDATE STOCK PROCESS

2. Then the user will need to choose a make id and supplier id then the
make’s and supplier’s details will be displayed.
3. Afterward he will need to enter the product details, on clicking the save
button the details will be validated. If the details are:-
a. Invalid an error message will be displayed and then the user has to re-
input details.
b. Valid the following table will be updated:-
(i) Product.
(ii) Purchase.
(iii) Make.
78
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
PURCHASE
NO
HAS RECORD
BEEN
ERROR
YES
MESSAG
E
DISPLAY
RECORD
END
SEARCH PROCESS
criteria.
purchase table if the details have:-
the record has not been found.
(ii) Been found, the record will be displayed from the purchase 79
table.
START
MOVE TO 1ST
RECORD PURCHASE
DISPLAY
DETAILS
END
displayed from the purchase table.
80
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAGE FILE?
E
NO PURCHASE
MOVE TO NEXT
RECORD
DISPLAY
RECORD
END
record.
(ii)No the previous record will be showed from the purchase table.
81
CANCEL PROCESS
START
CLEAR ALL TEXT

BOXES
END
CANCEL PROCESS
82
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
PURCHASE
END
DELETE PROCESS
2. No, another message will be displayed saying that the record has not
been deleted.
3. Yes, the record will be deleted from the purchase table.
83
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAG FILE?
EEE
NO PURCHASE
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
record.
(ii)No the next record will be showed from the purchase table.
84
START
MOVE TO LAST
RECORD PURCHASE
DISPLAY
DETAILS
END
displayed.
CLOSE PROCESS
START
CLOSE FORM
END
CLOSE PROCESS
85
INT EFACE N AME: SALE_IN TEF ACE.
INT ERF ACE PURPOS E: HAN DLE DE TAILS OF SALE S.
SALES FORM
SALES ID 1
CUSTOMER DETAILS MAKE DETAILS

CUSTOMER ID 2
MAKE ID 10
NAME 3
MAKE 11
SURNAME 4
STOCK QUANTITY 12
SALE DETAILS
PRODUCT ID 5 SEARCH 13 14
PRODUCT 23
COST 6
15 16 17 18 19 20 21
DATE SOLD 7
CLOSE FORM22
DISCOUNT 8
NET PAY 9
86
1 TEXTBOX NAME saleid
2 COMBO BOX NAME customerid
ROW SOURCE customer
COLUMN COUNT 3
3 TEXTBOX NAME nameofcustomer
4 TEXTBOX NAME surname
5 TEXTBOX NAME productid
6 TEXTBOX NAME cost
7 TEXTBOX NAME datesold
8 TEXTBOX NAME discount
9 TEXTBOX NAME netpay
1 COMBO BOX NAME makeid
0
ROW SOURCE make
COLUMN COUNT 3
11 TEXTBOX NAME make
2
3
CAPTION
PICTURE Bitmap
87
1 COMMAND BUTTON NAME CMDSREC
4
CAPTION
PICTURE Bitmap

5
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME GTFREC
6
CAPTION
PICTURE Bitmap
7
CAPTION
PICTURE Bitmap
8
CAPTION
PICTURE Bitmap
88
9
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTNREC
0
CAPTION

1
CAPTION
PICTURE Bitmap
2
CAPTION Close Form
2 COMMAND BUTTON NAME Command 25
3
CAPTION Search
89
SALE AND UPDATE STOCK PROCESS
START
CHOOSE
CUSTOMER CUSTOMER
DISPLAY
CUSTOMER
DETAILS
CHOOSE
MAKE MAKE ID
DISPLAY
MAKE
DETAILS
ENTER
PRODUCT
ID
VALIDATE
YES
DISPLAY NO
ERROR?
MESSAG
E (A) (B)
90
(A) (B)
SEARCH PRODUCT
PRODUCT DETAILS YES
NO
SOLD?
DISPLAY
PRODUCT
DETAILS
INPUT
DISCOUNT
YES VALIDATE
DISPLAY NO
ERROR?
MESSAG
E
CALCULATE NET PAY
(C) 91
DISPLAY
NET PAY
(C)
MAKE UPDATE MAKE STOCK
SALE UPDATE SALE TABLE
UPDATE PRODUCT
PRODUCT STOCK
END
SALE AND UPDATE STOCK PROCESS

2. Then the user will need to choose a make id , customer id and product id then
the customer’s and make’s details will be displayed.
3. If the product id is:-
(i) Not valid or has already been sold a message will be displayed and
the user will need to re-enter another product id.
4. Then the user will have to input discount if the discount offered is:-
(i) Invalid or out of range an error message will be displayed
therefore the user will have to correct the invalid information.
(ii) Valid the net pay will automatically calculated
5. On clicking the save button the record will be updated on the following tables:
(a) Make.
(b) Sale.
(c) Product.
92
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
SALE
NO
HAS RECORD
BEEN
YES
ERROR
MESSAG
E
DISPLAY
RECORD
END
SEARCH PROCESS
criteria.
sale table if the details have:-
the record has not been found. 93
(ii) Been found, the record will be displayed from the sale table.
START
MOVE TO 1ST
RECORD SALE
DISPLAY
DETAILS
END
displayed from the sale table.
94
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
DISPLAY END OF
MESSAGE FILE?
E
SALE
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
record.
(ii)No the previous record will be showed from the sale table.
95
CANCEL PROCESS
START
CLEAR ALL TEXT

BOXES
END
CANCEL PROCESS
96
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
SALE
END
DELETE PROCESS
(i) No, another message will be displayed saying that the record
has not been deleted.
(ii) Yes, the record will be deleted in the sale table.
97
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
YES
DISPLAY END OF
MESSAG FILE?
EEE
NO SALE
MOVE TO NEXT
RECORD
DISPLAY
DETAILS
END
record.
(ii)No the next record will be showed from the sale table.
98
START
MOVE TO LAST
RECORD SALE
DISPLAY
DETAILS
END
MOVE
CLOSETO LAST RECORD PROCESS
PROCESS
Displayed from the sale table.
START
CLOSE FORM
CLOSE PROCESS
1. When the user clicks on the “CloseEND

button” the form is closed. 99
REPOR T N AME: LI ST OF CUST OM ERS.
REPOR T PURPO SE: GEN ERA TE LI ST OF CUST OM ERS.
100
LIST OF CUSTOMERS
SURNAME
ADDRESS
REGION
NAME OF CUSTOMER TELEPHONE NUMBER NATIONAL ID
MENU N AME: MAIN M ENU .
101
MENU PURPOS E: SWI TCHING FR OM ON E MENU T O
ANO THER.
MAIN MENU
FORMS REPORTS EXIT
CUSTOMER LIST OF CUSTOMER
SUPPLIER LIST OF SUPPLIER
MAKE LIST OF MAKE
PURCHASE LIST OF PRODUCTS
SALE EXIT
EXIT
102
WELCOME TO UNITED MOTORS
FORMS
REPORTS
EXIT
MENU N AME: FORMS M ENU .
103
MENU PURPOS E: SWI TCHING FR OM ON E FORM T O
ANO THER.
CUSTOMER FORM
SUPPLIER FORM
MAKE FORM
SALE FORM
PURCHASE FORM
EXIT
MENU N AME: REPOR TS M ENU .
104
MENU PURPOS E: SWI TCHING FR OM ON E REPOR T T O
ANO THER.
LIST OF CUSTOMERS
LIST OF SUPPLIER S
LIST OF MAKES
LIST OF PRODUCTS
EXIT
105
PAS SW OR D US ED: AIRFOR CE.
PAS SW OR D PURPO SE: PR OTECTS D ATA FR OM
UN AUTHORIZ ED U SERS.
PASSWORD
ENTER DATABASE PASSWORD
Ok Cancel
106
2.3 HARDWARE
1. QWER TY k eyboar d
The keyboard will be used to key in information in the system.
Reason:
(i) Can easily be manipulated as some of the staff is already familiar with
typewriters.
(ii) Already available with the system.
2. Optical Mouse
The optical mouse will be used to enter data into the computer and also
select data from the system.
Reason:
(i) Is more sensitive, easier to handle and more accurate.
(ii) It will not be affected with dust.
3. 17” Inc hes Monitor

The monitor is used to view data from the system.
(i) The 17” inch monitor is big enough for the user to view ad the
information.
(ii) There is no much difference of price between 15” and 17” inches.
4. D VD write r driv e- 6×16 D VD +R

Data can be burnt to DVDs and CDs and can also be viewed form DVDs and
CDs.
Reason:
(i) It can be used for backup purpose and installation of programs.
5. Har d disk (80 GB)

The hard disk will be used to store data permanently.
Reason:
(i) Fast retrieval and reading of data.
(ii) Can store a large amount of data permanently.
107
6. Printer inkjet
The inkjet printer will be used to print reports.
Reason:
(i) Good quality picture.
(ii) Cheaper than laser printer.
(iii) Good speed of printing.
7. 512 MB of RAM
The RAM memory provides space for transactions currently being
executed.
Reason:
(i) To hold data temporarily.
(ii) Have a wider work place without freezing of the program.
(iii) What is actually available on the market.
8. PEN TIUM IV
To fasten the processing of data.
Reason:
(i) Allow to process data very quickly.
(ii) Though we do not need much speed now it will be needed as the
company evolves.
9. USB POR T
To connect different peripherals.
Reason:
(i) Can connect printer, scanner and external hard disk which can be used
in the future.
108
10. Scanner
To transfer documents into the system.
Reason:
(i) Sometimes people fail to do photocopies of their documents so scanner
will be helpful.
(ii) Sometimes we need to scan documents for administrative use and edit
the document.
2.4 SOFTWARE
1. W indo ws ser vice pac k 2
When we buy the system, we get an original copy of windows along with it.
Reason:
(i) It has a very good graphical user interface and users are familiar to the
environment and can easily manipulate.
(ii) The reason of windows is well protected against viruses and block
scripts which can be very dangerous.
2. Micr osoft Access

The system has been developed using Microsoft access.
Reason:
(i) It will be needed to execute the program.
3. T he softw ar e
The software has been developed to be run in the
Reason:
(i) To manage transaction.
(ii) To improve efficiency.
4. Anti vir us
Protect the system form viruses
Reason:
(i) In case of virus, the software will detect and remove the virus hence
protecting the data on the hard disk against viruses.
109
3.0 IMPLE MEN TATIO N
3.1 METHOD OF SOLUTION DESCRIBED IN SPECIFIC DETAILS
RELEVANT TO PROBLEM
Pr oblem 1. Duplica tion o f da ta.
This problem has been solved as the tables in the database
MOTORCYCLE.mdb are all linked together by relationship so it is
necessary to store the information only once and you can access that
particular information from several tables and interfaces hence avoiding
duplication of data.
Pr oblem 2. Dif ficulty to mana ge stoc k.

This problem has been solved by automatically updating the stock on
purchases and sales of product. Hence the company has an updated stock
and reports will be automatically generated to know the list of products
hence products are ordered in time.
Pr oblem 3. Losing time to pr epar e r epor ts.

This problem solved by automatic reporting hence lots of time is saved.
Pr oblem 4. Mistak e on Calcula tions.

This problem has been solved by automatic calculation. The net pay is
automatically calculated hence avoiding mistake.
Pr oblem 5. Mistak e w hile entering da ta.

This problem has been solved by adding validation on different fields
hence the user will be informed on any invalid input data.
Pr oblem 6.Losing time to sear ch f or pr oduct in for ma tion

reques ted by custome r s.
This problem has been solved by adding search button on each interface.
(Please refer to technical documentation for code listing)
110
TYPE S OF IMPLEM ENT ATION
Method of implementation of the new system Implementation is the stage
where my program will be introduced into the system. There are different
types of implementation namely:
(i) Dir ect Implementa tion

The system will be used from a specific date and the manual system is not
used anymore.
Disadvantages:
(a) If the system break down and need to be debug the business will be
affected.
(ii) P hased I mplementa tion

The system will be introduced in only one department and then will
continue until the whole business is computerized.
Disadvantages:
(a) Will take time to be completely introduced done.
(b) Not suitable as the company is a small one.
(iii) Par allel implementa tion

The system will continue running as a manual and the same thing will be
done on computer.
Disadvantages:
(a) Will take time to do the same job twice.
I ha ve c hosen par allel implementa tion

Reason s:
(i) Even though it is time consuming it will not affect the business if ever
the software reveals to be not yet on feet.
(ii) The software is not much trusty so it is preferable to do so.
(iii) The user will be allowed to adapt to the new system little by little.
(iv) Errors in the software will be then detected if there is any.
111
3.2 ACCURATE METHOD OF SOLUTION.
Objectiv e 1. Cr ea ting a da ta ba se.
This objective has been implemented using MS ACCESS 2002/03 to create
a database called MOTORCYCLE.mdb
OBJECTIVE MET: YES
Objectiv e 2 (a). Cr ea ting Customer T able.

In the database MOTORCYCLE.mdb, a table called customer has been
created using wizard in design view where the different field names, field
types and field sizes have been specified.
The followings field names are:
1. customerid (This field name has been used as primary key)
2. nameofcustomer
3. surname
4. address
5. region
6. mobile
7. nid
OBJECTIVE MET: YES
Objectiv e 2 (b). Cr ea ting S upplier T able.

In the database MOTORCYCLE.mdb, a table called supplier has been
types and field sizes have been specified.
1. supplierid (This field name has been used as primary key)
2. nameofccompany
3. address
4. region
5. telephonenumber
6. faxnumber
OBJECTIVE MET: YES
112
Objectiv e 2 (c). Cr ea ting Mak e T able.
In the database MOTORCYCLE.mdb, a table called make has been created
using wizard in design view where the different field names, field types and
field sizes have been specified some changed to combo box and the
related table and column count have been mentored.
1. makeid (This field name has been used as primary key)
2. make
3. stockquantity
4. status
5. remarks
OBJECTIVE MET: YES
Objectiv e 2 (d). Cr ea ting Pr oduct T able.

In the database MOTORCYCLE.mdb, a table called product has been
types and field sizes have been specified some change to combo box and
the related table and column count have been mentored.
1. productid (This field name has been used as primary key)
2. makeid
3. supplierid
4. model
5. cc
6. year
7. country
8. colour
9. chasisnumber
10. enginenumber
11. buyingcost
12. sellingcost
13. date_received
14. remarks
OBJECTIVE MET: YES
113
Objectiv e 2 (e). Cr ea ting P ur cha se T able.
In the database MOTORCYCLE.mdb, a table called purchase has been
types and field sizes have been specified some changed to combo box and
the related table and column count have been mentored.
1. purchaseid (This field name has been used as primary key)
2. supplierid
3. productid
4. makeid
5. date_bought
6. cost
7. invoicenumber
OBJECTIVE MET: YES
Objectiv e 2 (f). Cr ea ting Sale T able.

In the database MOTORCYCLE.mdb, a table called sale has been created
using wizard in design view where the different field names, field types and
field sizes have been specified some changed to combo box and the
related table and column count have been mentored.
1. saleid (This field name has been used as primary key)
2. customerid
3. productid
4. makeid
5. datesold
6. cost
7. discount
8. netpay
OBJECTIVE MET: YES
114
Objectiv e 3 (a). De veloping customer interf ace with
rela ted buttons.
The objective has been implemented by designing a form using wizard in
MS ACCESS 2002/03 based on customer table.
Appropriate textboxes have been used and with related buttons:
1. A command button has been added by wizard to be able to add
new customer.
2. From the supplier interface a user an edit any required
textboxes.
3. A command button has been added by wizard to be able to
delete a supplier details.
search for a particular supplier details.
save a new supplier details.
navigate to 1st record.
navigate to previous record.
cancel any edit or new entry record.
navigate to next record.
navigate to last record.
close the form.
OBJECTIVE MET: YES
115
Objectiv e 3 (b). De veloping supplier interf ace with
rela ted buttons.
MS ACCESS 2002/03 based on supplier table.
new supplier.
2. From the supplier interface a user an edit any required
textboxes.
delete a supplier details.
search for a particular supplier details.
save a new supplier details.
close the form.
OBJECTIVE MET: YES
116
Objectiv e 3 (c). De veloping mak e interf ace with r ela ted
button s.
MS ACCESS 2002/03 based on make table.
new make.
2. From the make interface a user an edit any required textboxes.
delete a make details.
search for a particular make details.
save a new make details.
close the form.
OBJECTIVE MET: YES
117
Objectiv e 3 (d). De veloping pur chase interf ace with
rela ted buttons.
MS ACCESS 2002/03 based on purchase table.
new purchase.
2. From the purchase interface a user an edit any required
textboxes.
delete a purchase details.
search for a particular purchase details.
save new purchase details and update stocks after purchase.
close the form.
OBJECTIVE MET: YES
118
Objectiv e 3 (e). De veloping sale interf ace with r ela ted
button s.
MS ACCESS 2002/03 based on sale table.
new sale.
2. From the sale interface a user an edit any required textboxes.
delete a sale details.
search for a particular sale details.
save new sale details and update stocks after sale.
close the form.
OBJECTIVE MET: YES
119
Objectiv e 4 (a). Cr ea ting valida tions on customer
interf ace.
Appropriate validations on textboxes have been added using VISUAL
BASIC language in order to check for:
1. Presence check.
2. Type check.
3. Length check.
The above validations will be checked on clicking on the save button.

Appropriate error message are given if there is any invalid data.
OBJECTIVE MET: YES
Objectiv e 4 (b). Cr ea ting valida tions on supplier

interf ace.
1. Presence check.
2. Type check.
3. Length check.

OBJECTIVE MET: YES
Objectiv e 4 (c). Cr ea ting valida tions on mak e interf ace.

1. Presence check.
2. Type check.
3. Length check.

120
OBJECTIVE MET: YES
Objectiv e 4 (d). Cr ea ting valida tions on pur chase
interf ace.
1. Presence check.
2. Type check.
3. Length check.
4. Range Check.

OBJECTIVE MET: YES
Objectiv e 4 (e). Cr ea ting valida tions on sale interf ace.

1. Presence check.
2. Type check.
3. Length check.
4. Range check.

OBJECTIVE MET: YES
Objectiv e 5. A utoma tic calcula tion on sale interf ace.

Codings in VISUAL BASIC have been added in order to calculate
automatically the net pay of a product automatically. The above calculation
will be calculated on command by clicking on a command button.
OBJECTIVE MET: YES
121
Objectiv e 6. A utoma tic upda te o f stoc k on sale and
pur chase interf aces.
Codings in VISUAL BASIC have been added in order to update the stock
while selling and purchasing a product. Stocks will be updated while
clicking on a command button.
OBJECTIVE MET: YES
Objectiv e 7. A utoma tic r epor ting.

1. List of Customers: this report has been developed using
wizard and customer table.
2. List of Suppliers: this report has been developed using wizard
and supplier table.
3. List of Products: this report has been developed using wizard
and product table.
4. List of Makes: this report has been developed using wizard and
make table.
OBJECTIVE MET: YES
Objectiv e 8. A ppr opria te Menu will be pr ovided.

This menu has been implemented in the form of a Switch Board.
OBJECTIVE MET: YES
Objectiv e 9. S ecurity .
A logging password has been implemented.
OBJECTIVE MET: YES
122

Content: Title

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Content: Title

Transféré par

Droits d'auteur :

Formats disponibles

Content

The business has evolved to 9 employees that means it has been

We lose lots of time when reports need to be done. We have to look

5) Calculation will be made automatically when a customer will buy a

6) Whenever a purchase or a sale will be made, the stock will be

7) A password will be implemented to prevent unauthorized user to

9) A main menu will be developed in order to facilitate the switching

BUSSIN ESS RELA TED TERMS

REQUEST DETAILS LOOK FOR REQUESTED

RELATED DOCUMENTS SALE DETAILS

Calculate Supplier RECORD PURCHASE

LOOK FOR DETAILS

REQUEST M1 Product Book

BUYING PRICE: Rs……………SELLING PRICE: Rs………………

DATE SOLD:………………(IF SOLD) SOLD TO:…………………………

PAGE ON SALE BOOK:………………… PAGE ON PURCHASE BOOK:………………

FOR THE SUM OF Rs………………………………………………………………...

WHICH ACKNOWLEDGE TO HAVE RECEIVED CASH.

THE PARTICULAR OF THE ………………………… ARE:

DATED THE…………………………DAY OF …………………20………………...

UNITED MOTORS DIRECTOR PURCHASER

I HEREBY CERTIFY THAT THIS ORIGINAL IS IDENTICAL TO THE

UNITED MOTORS DIRECTOR PURCHASER

ADDRESS (BLOCK LETTERS):…………………………………………

FAX NUMBER The fax number of the supplier.

FOR THE SUM OF Rs………………………………………………………………...

WHICH ACKNOWLEDGE TO HAVE RECEIVED………………………………

THE PARTICULAR OF THE ……………………………………………………….

DATED THE…………………………DAY OF …………………20………………...

ALLY MOTORS DIRECTOR PURCHASER

I HEREBY CERTIFY THAT THIS ORIGINAL IS IDENTICAL TO THE

ALLY MOTORS DIRECTOR PURCHASER

SUPPLIER NAME (BLOCK LETTERS)………………………………...

ADDRESS (BLOCK LETTERS):…………………………………………

DATE BOUGHT: ………………………………………………………….

UNIT PRICE (INCLUDING DISCOUNT): Rs……………………………………

TOTAL PRICE: Rs……………………………………………………………………

NAME OF MAKE MODEL UNIT QUANTITY

1.4 EV AL UATION OF EXI STING S OL UTION

AD VANT AGES OF EX IST ING SY ST EM:

DISAD VANT AGE S OF EXIS TING SY STEM:

AD VANT AGES OF S OL UTION 1:

DISAD VANT AGE S OF SOL UT ION 1:

DISAD VANT AGE S OF SOL UT ION 2:

USING MODULAR PR OGRAMMING

HERE ARE THE REASON S WHY MODULAR PR OGRAMMING

4.0 MAIN MENU

DATABASE AND 2.0 INTERFACES 3.0 REPORTS

1.0 D ATAB ASE AND TABLE S DEVEL OPMENT

2.0 INT ERF ACES DEVEL OPMEN T

Supplier interface will be created where the user will be able to

Purchase interface will be created where the user will be able

Sale interface will be created where the user will be able to

3.0 REPOR TS L IST

4.0 MAIN M ENU

2.2 DESCRIPTION OF METHOD OF SOLUTION

TABLE N AME: CUST OMER_T ABLE

TABLE N AME: PR ODUCT_T ABLE

TABLE N AME: SALE_ TABLE

INT ERF ACES DEVEL OPMEN T

ADD NEW RECORD, VALIDATE AND SAVE PROCESS

When the user clicks on the “Add button”:-