Content: Title
Content: Title
Content: Title
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.
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.
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.
(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 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.
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 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.
(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 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.
(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 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 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.
6
1.3 DESCRIPTION OF EXISTING SOLUTION
Da taflo w di agram
DETAILS OF MOTORCYCLES
+
VISIT THE SHOWROOM SALE DETAILS
MOTORCYCLE DETAILS
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
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:………………………………………………………
DATE RECEIVED:…………………
NAME OF COMPANY:……………………………………………………
ADDRESS:…………………………………………………………………
………………………………………………………………………………
REMARK:…………………………………………………………………..
………………………………………………………………………………..
………………………………………………………………………………..
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……………...
…………………………………………………………………………………………..
MAKE:……………………………………………………
MODEL:………………………………………………….
COLOUR:………………………………………………...
ENGINE NO:…………………………………………….
ENGINE CAPACITY:……………………………….CC
CHASSIS NO:……………………………………………
REGISTRATION NO:…………………………………..
SIG:…………………………….. SIG:………………………………
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).
MAKE Make of motorcycle.
MODEL Model of 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 company manager’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): …………………………
……………………………………………………………………………….
………………………………………………………………………………..
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.
16
Ally Motors
51, ANTHELM MNT ROCHE
Tel: 2170096 Fax: 2481234
HEREBY CERTIFY HAVING SUPPLYING MOTORCYCLES
BEARING NO………………………………………….TO ……...…………………..
AT…………….......................................................................................................……..
MAKE:……………………………………………………
MODEL:………………………………………………….
COLOUR:………………………………………………...
ENGINE NO:…………………………………………….
ENGINE CAPACITY:……………………………….CC
CHASSIS NO:……………………………………………
REGISTRATION NO:…………………………………..
SIG:…………………………….. SIG:………………………………
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).
MAKE Make of motorcycle.
MODEL Model of 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 company manager’s signature.
SIG The supplier’s manager’s signature.
SIG The company manager’s signature.
18
PURCHASE BOOK
INVOICE NUMBER: ……………………
…………………………………………………….………………………….
TELEPHONE NUMBER:………………………………………………….
………………………………………………………………………………..
MODEL:…..………………………………………………………………...
ENGINE CAPACITY:…………………………CC
CHASSIS NUMBER:..…………………………………………………….
YEAR:……………………………COUNTRY:…………………………...
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:………………………………………………………………….
…………………………………………………………………………………………..
QUANTITY:……………………………………………………………………………
…………………………………………………………………………………………..
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:……………………………………………………………….
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
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.
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.
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.
29
MOTORCYCLE
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)
31
Make interface will be created where the user will be able to
handle details about makes.
TASK ST AR TED END RELA TED
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)
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
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
34
5.0 P AS SW OR D
A password will be implemented to prevent unauthorized
users to get access to confidential information.
TASK ST AR TED END RELA TED
DATE DATE OBJECTIVE
S
CREATION OF PASSWORD: 16/05/07 16/05/07 7
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
∞
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.
FIELD N AME DATA TYP E FIELD SI ZE
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.
FIELD N AME DATA TYP E FIELD SI ZE
makeid Autonumber Long Integer
make text 20
stockquantity number Long Integer
regionstatus text 20
remarks text 20
Primary key: makeid
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.
FIELD N AME DATA TYP E FIELD SI ZE
purchaseid Autonumber Long Integer
supplierid number Long Integer
productid number Long Integer
makeid number Long Integer
date_bought date/time
cost currency
invoicenumber text 20
Primary key: purchaseid
38
saleid Autonumber Long Integer
custimerid number Long Integer
productid number Long Integer
makeid number Long Integer
datesold date/time
cost currency
discount currency
netpay currency
Primary key: saleid
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
EVENT PROCEDURE On lost focus
4 TEXTBOX NAME Region
EVENT PROCEDURE On lost focus
5 TEXTBOX NAME Telephonenumber
EVENT PROCEDURE On lost focus
6 TEXTBOX NAME Contact
EVENT PROCEDURE On lost focus
7 TEXTBOX NAME Faxnumber
EVENT PROCEDURE On lost focus
8 COMMAND BUTTON NAME cmdsave
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
9 COMMAND BUTTON NAME CMDFNDREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTFREC
0
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
41
11 COMMAND BUTTON NAME GTLREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCANREC
2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDDELREC
3
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME cmdadd
4
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME GTPREC
5
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTLREC
6
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCLOFRM
7
EVENT PROCEDURE On click
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
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
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:-
(i)Yes a message will be displayed saying that it cannot go to a specified
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
# TYPE PROPERTIES VALUE
1 TEXTBOX NAME customerid
2 TEXTBOX NAME nameofcustomer
EVENT PROCEDURE On lost focus
3 TEXTBOX NAME surname
EVENT PROCEDURE On lost focus
4 TEXTBOX NAME address
EVENT PROCEDURE On lost focus
5 TEXTBOX NAME region
EVENT PROCEDURE On lost focus
6 TEXTBOX NAME mobile
EVENT PROCEDURE On lost focus
7 TEXTBOX NAME nid
EVENT PROCEDURE On lost focus
8 COMMAND BUTTON NAME cmdsave
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
9 COMMAND BUTTON NAME CMDFNDREC2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
10 COMMAND BUTTON NAME CMDGTFREC2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
52
11 COMMAND BUTTON NAME CMDGTPREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
12 COMMAND BUTTON NAME CMDCANREC2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
13 COMMAND BUTTON NAME CMDDELREC2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
14 COMMAND BUTTON NAME cmdadd
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
15 COMMAND BUTTON NAME CMDGTNREC2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
16 COMMAND BUTTON NAME CMDGTLREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
17 COMMAND BUTTON NAME CMDCLOFRM2
EVENT PROCEDURE On click
CAPTION Close Form
53
ADD NEW RECORD, VALIDATE AND SAVE PROCESS
START
CLEAR ALL
TEXTBOXES
INPUT
REQUIRES
DETAILS
VALIDATE
YES DISPLAY
ERROR?
MESSAG
E
NO
SAVE RECORD
CUSTOMER
DISPLAY
MESSAG
E
END
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
MOVE TO 1ST RECORD PROCESS
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
MOVE TO PREVIOUS RECORD PROCESS
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
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 customer table will be displayed.
57
CANCEL PROCESS
START
END
CANCEL PROCESS
1. When the user clicks on the “Cancel button” all text boxes are cleared.
58
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
CUSTOMER
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:-
(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
MOVE TO NEXT RECORD PROCESS
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
1. When the user clicks on the “Go to next 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 next record from the customer table will be displayed.
60
MOVE TO LAST RECORD PROCESS
START
MOVE TO LAST
RECORD CUSTOMER
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.
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
# TYPE PROPERTIES VALUE
1 TEXTBOX NAME makeid
2 TEXTBOX NAME Make
EVENT PROCEDURE On lost focus
3 TEXTBOX NAME stockquantity
EVENT PROCEDURE On lost focus
4 COMBO BOX NAME status
ROW SOURCE TYPE On lost focus
ROW SOURCE
COLUMN COUNT
5 TEXTBOX NAME remarks
6 COMMAND BUTTON NAME CMDSAVREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
7 COMMAND BUTTON NAME CMDFNDREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
8 COMMAND BUTTON NAME CMDGTFREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
9 COMMAND BUTTON NAME CMDGTPREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
63
1 COMMAND BUTTON NAME CMDCANREC
0
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
11 COMMAND BUTTON NAME CMDDELREC
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDADDREC
2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTNERC
3
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDGTLREC
4
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCLOFRM
5
EVENT PROCEDURE On click
CAPTION Close Form
64
ADD NEW RECORD, VALIDATE AND SAVE PROCESS
START
CLEAR ALL
TEXTBOXES
INPUT
REQUIRES
DETAILS
VALIDATE
YES DISPLAY
ERROR?
MESSAG
E
NO
SAVE RECORD
MAKE
DISPLAY
MESSAG
E
END
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
MOVE TO 1ST RECORD PROCESS
START
MOVE TO 1ST
RECORD MAKE
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to 1st record button” the first record is
Displayed from the make table.
67
MOVE TO PREVIOUS RECORD PROCESS
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
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 will be showed from the make table.
68
CANCEL PROCESS
START
END
CANCEL PROCESS
1. When the user clicks on the “Cancel button” all text boxes are cleared.
69
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
MAKE
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:-
(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
MOVE TO NEXT RECORD PROCESS
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
1. When the user clicks on the “Go to next 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 next record will be showed from the make table.
71
MOVE TO LAST RECORD PROCESS
START
MOVE TO LAST
RECORD MAKE
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.
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
# TYPE PROPERTIES VALUE
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 TYPE Table/Query
ROW SOURCE Status-product
COLUMN COUNT 1
7 TEXTBOX NAME stockquantity
8 TEXTBOX NAME model
9 COMBO BOX NAME year
ROW SOURCE TYPE Table/Query
ROW SOURCE year
COLUMN COUNT 1
1 TEXTBOX NAME country
0
EVENT PROCEDURE On lost focus
11 TEXTBOX NAME txtdate
1 TEXTBOX NAME txtcost
2
1 TEXTBOX NAME remark
3
1 COMBO BOX NAME makeid
4
ROW SOURCE TYPE Table/Query
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 TYPE Table/Query
ROW SOURCE Supplier
COLUMN COUNT 3
1 TEXTBOX NAME nameofcompany
8
1 TEXTBOX NAME contactperson
9
2 COMMAND BUTTON NAME cmdsave
0
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDFNDRECORD
1
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTFREC
2
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTPREC2
3
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
75
2 COMMAND BUTTON NAME CMDCANREC
4
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDADDREC
6
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTPREC
7
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTLREC
8
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDCLOFRM
9
EVENT PROCEDURE On click
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
UPDATE MAKE
MAKE STOCK
77
END
PURCHASE AND UPDATE STOCK PROCESS
78
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
PURCHASE
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
purchase 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 purchase 79
table.
MOVE TO 1ST RECORD PROCESS
START
MOVE TO 1ST
RECORD PURCHASE
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to 1st record button” the first record is
displayed from the purchase table.
80
MOVE TO PREVIOUS RECORD PROCESS
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
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 will be showed from the purchase table.
81
CANCEL PROCESS
START
END
CANCEL PROCESS
1. When the user clicks on the “Cancel button” all text boxes are cleared.
82
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
PURCHASE
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:-
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
MOVE TO NEXT RECORD PROCESS
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
1. When the user clicks on the “Go to next 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 next record will be showed from the purchase table.
84
MOVE TO LAST RECORD PROCESS
START
MOVE TO LAST
RECORD PURCHASE
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.
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
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
# TYPE PROPERTIES VALUE
1 TEXTBOX NAME saleid
2 COMBO BOX NAME customerid
ROW SOURCE TYPE Table/Query
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
EVENT PROCEDURE On lost focus
9 TEXTBOX NAME netpay
1 COMBO BOX NAME makeid
0
ROW SOURCE TYPE Table/Query
ROW SOURCE make
COLUMN COUNT 3
11 TEXTBOX NAME make
1 TEXTBOX NAME stockquantity
2
1 COMMAND BUTTON NAME cmdsave
3
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
87
1 COMMAND BUTTON NAME CMDSREC
4
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
PICTURE Bitmap
1 COMMAND BUTTON NAME GTFREC
6
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDCANREC
7
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
1 COMMAND BUTTON NAME CMDDELREC
8
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
88
1 COMMAND BUTTON NAME CMDADDREC
9
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDGTNREC
0
EVENT PROCEDURE On click
CAPTION
PICTURE Bitmap
2 COMMAND BUTTON NAME CMDCLOFRM
2
EVENT PROCEDURE On click
CAPTION Close Form
2 COMMAND BUTTON NAME Command 25
3
EVENT PROCEDURE On click
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
(C) 91
DISPLAY
NET PAY
(C)
UPDATE PRODUCT
PRODUCT STOCK
END
92
SEARCH PROCESS
START
ENTER THE
SEARCH
CRITERIA
SEARCH RECORD
SALE
NO
HAS RECORD
BEEN
YES
ERROR
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
sale table if the details have:-
(i) Not been found, an error message will be displayed saying that
the record has not been found. 93
(ii) Been found, the record will be displayed from the sale table.
MOVE TO 1ST RECORD PROCESS
START
MOVE TO 1ST
RECORD SALE
DISPLAY
DETAILS
END
1. When the user clicks on the “Go to 1st record button” the first record is
displayed from the sale table.
94
MOVE TO PREVIOUS RECORD PROCESS
START
VERIFY IF NOT
ALREADY AT THE
END OF FILE
DISPLAY END OF
MESSAGE FILE?
E
SALE
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 will be showed from the sale table.
95
CANCEL PROCESS
START
END
CANCEL PROCESS
1. When the user clicks on the “Cancel button” all text boxes are cleared.
96
DELETE PROCESS
START
DISPLAY
CONFIRMATIO
N
MESSAGE
SELECT OPTION
DISPLAY NO DELETE
MESSAG ?
E
YES
DELETE RECORD
SALE
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:-
(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
MOVE TO NEXT RECORD PROCESS
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
1. When the user clicks on the “Go to next 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 next record will be showed from the sale table.
98
MOVE TO LAST RECORD PROCESS
START
MOVE TO LAST
RECORD SALE
DISPLAY
DETAILS
END
MOVE
CLOSETO LAST RECORD PROCESS
PROCESS
1. When the user clicks on the “Go to last record button” the last record is
Displayed from the sale table.
START
CLOSE FORM
CLOSE PROCESS
100
LIST OF CUSTOMERS
SURNAME
ADDRESS
REGION
NAME OF CUSTOMER TELEPHONE NUMBER NATIONAL ID
101
MENU PURPOS E: SWI TCHING FR OM ON E MENU T O
ANO THER.
MAIN MENU
SALE EXIT
EXIT
102
WELCOME TO UNITED MOTORS
FORMS
REPORTS
EXIT
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
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.
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.
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.
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:
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
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.
The followings field names are:
1. makeid (This field name has been used as primary key)
2. make
3. stockquantity
4. status
5. 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
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.
The followings field names are:
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
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.
4. A command button has been added by wizard to be able to
search for a particular supplier details.
5. A command button has been added by wizard to be able to
save a new supplier details.
6. A command button has been added by wizard to be able to
navigate to 1st record.
7. A command button has been added by wizard to be able to
navigate to previous record.
8. A command button has been added by wizard to be able to
cancel any edit or new entry record.
9. A command button has been added by wizard to be able to
navigate to next record.
10. A command button has been added by wizard to be able to
navigate to last record.
11. A command button has been added by wizard to be able to
close the form.
OBJECTIVE MET: YES
115
Objectiv e 3 (b). De veloping supplier interf ace with
rela ted buttons.
The objective has been implemented by designing a form using wizard in
MS ACCESS 2002/03 based on supplier 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 supplier.
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.
4. A command button has been added by wizard to be able to
search for a particular supplier details.
5. A command button has been added by wizard to be able to
save a new supplier details.
6. A command button has been added by wizard to be able to
navigate to 1st record.
7. A command button has been added by wizard to be able to
navigate to previous record.
8. A command button has been added by wizard to be able to
cancel any edit or new entry record.
9. A command button has been added by wizard to be able to
navigate to next record.
10. A command button has been added by wizard to be able to
navigate to last record.
11. A command button has been added by wizard to be able to
close the form.
116
Objectiv e 3 (c). De veloping mak e interf ace with r ela ted
button s.
The objective has been implemented by designing a form using wizard in
MS ACCESS 2002/03 based on make 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 make.
2. From the make interface a user an edit any required textboxes.
3. A command button has been added by wizard to be able to
delete a make details.
4. A command button has been added by wizard to be able to
search for a particular make details.
5. A command button has been added by wizard to be able to
save a new make details.
6. A command button has been added by wizard to be able to
navigate to 1st record.
7. A command button has been added by wizard to be able to
navigate to previous record.
8. A command button has been added by wizard to be able to
cancel any edit or new entry record.
9. A command button has been added by wizard to be able to
navigate to next record.
10. A command button has been added by wizard to be able to
navigate to last record.
11. A command button has been added by wizard to be able to
close the form.
117
Objectiv e 3 (d). De veloping pur chase interf ace with
rela ted buttons.
The objective has been implemented by designing a form using wizard in
MS ACCESS 2002/03 based on purchase 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 purchase.
2. From the purchase interface a user an edit any required
textboxes.
3. A command button has been added by wizard to be able to
delete a purchase details.
4. A command button has been added by wizard to be able to
search for a particular purchase details.
5. A command button has been added by wizard to be able to
save new purchase details and update stocks after purchase.
6. A command button has been added by wizard to be able to
navigate to 1st record.
7. A command button has been added by wizard to be able to
navigate to previous record.
8. A command button has been added by wizard to be able to
cancel any edit or new entry record.
9. A command button has been added by wizard to be able to
navigate to next record.
10. A command button has been added by wizard to be able to
navigate to last record.
11. A command button has been added by wizard to be able to
close the form.
118
Objectiv e 3 (e). De veloping sale interf ace with r ela ted
button s.
The objective has been implemented by designing a form using wizard in
MS ACCESS 2002/03 based on sale 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 sale.
2. From the sale interface a user an edit any required textboxes.
3. A command button has been added by wizard to be able to
delete a sale details.
4. A command button has been added by wizard to be able to
search for a particular sale details.
5. A command button has been added by wizard to be able to
save new sale details and update stocks after sale.
6. A command button has been added by wizard to be able to
navigate to 1st record.
7. A command button has been added by wizard to be able to
navigate to previous record.
8. A command button has been added by wizard to be able to
cancel any edit or new entry record.
9. A command button has been added by wizard to be able to
navigate to next record.
10. A command button has been added by wizard to be able to
navigate to last record.
11. A command button has been added by wizard to be able to
close the form.
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.
120
OBJECTIVE MET: YES
Objectiv e 4 (d). Cr ea ting valida tions on pur chase
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.
4. Range Check.
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 9. S ecurity .
A logging password has been implemented.
OBJECTIVE MET: YES
122