1 APU CSLLT Assignment
1 APU CSLLT Assignment
Instructions:
1. No marks will be awarded for the entire assignment if any part of it is found to be copied
directly from printed materials or from another student.
2. All submissions should be made on or before the due date.
3. Any late submissions after the deadline will not be entertained.
4. Zero (0) mark will be awarded for late submission, unless extenuating circumstances are
upheld.
Scenario
Application for Eelectronic Cash Register
Many well-known companies, such as S&M Supermarket and Costume Jewellery outlets,
Tampin Shopping Centre, 7-Eleven, Chakri Thai Restaurants, Picnic Food Court-KLCC, Food
Junction-Mid Valley, Victoria Station, Sri Ayuttaya, Kim Gary Restaurant, The Piazza Courtyard and
Restaurants have chosen custom designed application in the electronic cash register (ECR) to enable
products to be sold at a retail outlet. ECR helps large and small retail outlets track sales, minimize
register errors, collect inventory data and much more.
Assume, you are currently working for Naros Pvt Ltd software house and your project manager
assigned you to develop a simple apps to manipulate cash counter receipt in-line with Malaysian
government GST, your apps should serve customers in their daily food operation. This apps will be
utilized by Modesto Chain Restaurants at Asia Pacific University Sdn Bhd.
At Modestos Chain Restaurants you have to identify the available food, calculate the delivered
food item, and maintain the stocks etc. For the inventory, the restaurants required to follow the
arithmetic operations (addition, subtraction, multiplication and division) for ordering and delivering
food. Your application will be uploaded in the ECR upon completion.
1. Elaborate in detail about the uses of low level programming languages in security and
forensic also provide the self-reflections with justification.
2. Design main menu in your programming and list down the name of the foods and provide
necessary code to perform basic arithmetic operations (+, -, *, / ) to find out the total sum.
3. You are expected to demonstrate creativity in develop an application using assembly
language prototype that can deal with the requirements of the developer as well as addressing
(if necessary) any other aspects of control of the main menu of the application.
4. You have to work on the prototype individually.
5. You are permitted to make assumptions where necessary. These assumptions are expected to
be logical and must be appropriate for the situation at hand.
6. There will be a presentation towards the submission date of the project. You are expected to
demonstrate how your system is capable of addressing the requirements of the developer.
7. The submission of your project should entail the following items:
a. Main hardcopy documentation highlighting the following:
i. How the requirements have been addressed by the developing language, uses of
low level programming languages in security and forensic also provide the self-
reflections with justification
ii. System Design.
b. Softcopy user manual or guide that can explain how your system works. This will be
based on your system application.
The Assesment
This assignment will contribute 50% towards the module marks, as mentioned in the Student
Assessment & Information sheet. This assignment will be evaluated based on the following criteria.
Marks will be awarded based on:
Criteria Weight in
Pecentage
Discussion and analysis of the process that takes place based on the 20
scenario given.
This includes no runtime error, syntax errors etc. Source codes are 30
consistent, clean, modular and follows programming logic.
Submission requirements
1. Your report must be typed using wordprocessor with Times New Roman font size 12, with 1.5
spaces.
2. The report has to be well presented and should be typed. Submission of report that is unprofessional
in its outlook (dirty, disorganised, inconsistent look, varying coloured paper and size) will not fare
well when marks are allocated.
3. The report should have a one (1”) margin all around the page as illustrated below:
1 inch 1 inch
1 inch
1 inch
1 inch
1 inch 1 inch
4. Every report must have a front cover. A transparent plastic sheet can be placed in front of the report
to protect the front cover. The front cover should have the following details:-
a) Name
b) Intake code.
c) Subject.
d) Project Title.
5. All information, figures and diagrams obtained from external sources must be referenced using
the Harvard referencing system accordingly.
6. Plagiarism is a serious offence and will automatically be awarded zero (0) marks.
7. Produce the hardcopy of the above report and enclose a softcopy of the report together with the
program source code in a secondary storage media.
8. You have to hand in your hardcopy assignment on time with the Course Work Submission and
Feedback Form.
9. Please be informed that presentation is compulsory and if any student refusing to attend the
presentation, the grade will be considered as fail.
Performance Criteria:
The following guidelines indicate the standard that will be expected for each grade.
Documentation will be followed high standard with flow of statements. The elaboration of working
programmes at least based on one machine level language. The analysis and evaluation and
comparison of various processor architectures need to be clearly discussed.
Referencing and comments in the source code are very clear and followed the standard; readability of
source code follows the W3 standard. The presentation and application demonstration is good and
answers provided for any questions are completed.
Document referencing and code comment is complete and the code is following standard to achieve
readability.
Documentation is limited or not to an acceptable standard. The inappropriate referencing and poor
source code comment.
Fail (0 - 39%)
Demonstrate poor understanding of the CSLLT concepts, documentation incomplete and poor
explanation during demonstration. The development of machine language programs are weak or
incomplete, the documentation has very minimum of coding and unable to run properly. The analysis
and evaluation of assembly level language and differences between various processor architecture is
not properly delivered. Referencing / code comments are very poor or do not have proper referencing
/ comments.