Professional Documents
Culture Documents
A workshop in Malaysia is providing express car maintenance services. Types of services the
workshop offers are those simple maintenance tasks which can be done in short time using
simple tools, without requirement for highly skilled workers. The mission of the company is
to provide low cost and speedy car maintenance service for customers. There are two type of
express service fees offered by the workshop – the normal charges and urgent charges. For
the normal charges, the customer need to wait for their turn – to be called by the service
technician. For the urgent fee, customer will be served immediately – in a way, to allow
queue cutting.
When a customer visits the workshop requesting service, the staff at the counter will record
information about the customer and the requested service using your program.
You are required to write a program to manage the diary operation of the workshop by
providing the following functional features:
• Display a menu of services provided by the shop with other details as shown in the
above table.
• Record the customer and service information:
o Customer Name
o Service Date
o Car Registration number
o Service needed – by service number, as listed in the selection.
o Type of Service (Normal/Urgent)
o Service fee
• Upon completion of the above, an On-Screen invoice will be generated with an auto
generated, sequential Invoice Number. The invoice will contain information such as
customer name, Car Registration Number, Service Date, Type of Service and Service
Fee.
• Each individual invoice will be also be saved in a file in text format (.txt). You can
design your own invoice format, but information included in the invoice need to be in
proper structure.
2.0REQUIREMENTS
i. You are required to carry out extra research for your system and document any
logical assumptions you made after the research.
ii. Your program should use symbolic constants where appropriate. Validations need
to be included to ensure the accuracy of the system. State any assumptions that
you make under each function.
iii. Your program must be modular, user-friendly using programming techniques that
you have learnt. You may include any extra features which you may feel relevant
and that add value to the system. The menus could be modified in order to
facilitate more options.
iv. Graphical User Interface is NOT needed in this program. The marking scheme for
the assignment has been provided so that you clearly know how the assessment
for this assignment would be done.
v. You should include the good programming practice such as comments, variable
initialisation, naming conventions and indentation.
3.0DELIVERABLES
iv. Submission
- The documentation and codes must be submitted online before/on the due
date stated, latest by 7.00 p.m.
4.0ASSESSMENT CRITERIA
5.0PERFORMANCE CRITERIA
Credit (65%-74%)
This grade will be assigned to work which is considered to be of good standard and meets
most of the requirements stated in the question. The program runs smoothly when executed.
There is clear evidence and application of C concepts up to at least intermediate level. The
program solution is unique with good coding styles and validation. The program
implemented maps well against the design (pseudo code and flowchart) as seen in the
documentation. The design of the solution varies in styles and has unique logic with minor
errors / omissions. The documentation does not have any missing components. Sample
outputs documented with some explanation. All work is referenced according to Harvard
Name Referencing convention but with some minor errors / omissions. Student must be able
to provide good explanation of the codes and work done, answer most questions posed with
mostly accurate / logical answers / explanation. Overall a good assignment submitted.
Pass (50%-64%)
This grade will be assigned to work which meets at least half of the basic requirements
(approximately 50%) stated in the questions. The program runs smoothly when executed.
There is clear evidence and application of C concepts at basic level. The program solution is
common with basic coding styles and validation. The program implemented somewhat maps
with the design (pseudo code and flowchart) as seen in the documentation. The design of the
solution is average in terms of logic and style with some errors / omissions. The
documentation has some missing components. Sample outputs documented but without any
explanation. Did some referencing but not according to Harvard Name Referencing
convention and with some minor errors / omissions. Student must be able to explain some
codes and work done and able to answer some questions posed with some accurate / logical
answers / explanation. Overall an average piece of work submitted.