ASSIGNMENT QUESTION
You are required to select ONE (1) menu-driven application in any of the domain that given
below:
(i) Student Management System
(ii) Library Management System
(iii) Pharmacy Management System
(iv) Bank Management System
(v) Employee Management System
The application selected must be developed based on TWO (2) of the selected data structure
concepts below by the approval from the lecturer:
(i) Stack
(ii) Queue
**The data structure concept chosen must be implemented using linked list representation.
You are required to write C++ program to implements the selected application. The requirements
for the system are as listed below.
Requirements:
1) Suitable class(es) to represent the information using the data structure selected and
information to be stored.
2) Constructor
3) Destructor
4) Login() and exit() functions to allow only one authorized admin to access the system
5) InsertNew(...) {...}
6) DeleteRecord()
7) SearchRecord(...) {...}
8) UpdateRecord(...) {...}
9) SortRecord()
10) DisplayAll()
11) ClearAll()
However, you need to be creative to include TWO (2) more additional functionalities that meet
the usability and efficiency of the chosen domain of application.
You have to present your assignment solution and answers to the lecturer during Q&A session
that will be conducted after hand-in date.
DOCUMENTATION
The documentation should include the following:
Format:
Type face: Times New Roman. Bold face, italic & lines can be used for
emphasizing and to enhance readability.
Font size: 12(except titles and headings) and
Spacing: 1.5 lines between texts of a paragraph.
Binding: APU standard for Level 2
Cover page, your cover page should contain the following items
» Your Name and ID.
» Intake code.
» Subject.
» Project Title.
» Date Assigned (the date the report was handed out).
» Date Completed (the date the report is due to be handed in).
» APU logo
Recommended Content
Table of Contents
» The table of contents should have the topic title and reference page
number attached to each topic.
1.0 Introduction
» This section introduces the aim of your program.
2.0 Objectives
» This section stated the objectives of the program.
3.0 Functionalities
» This section stated all the functionalities of the program.
4.0 Interfaces
» This section contains the code snippet and the explanation of each
function/selection in the program.
5.0 Conclusion
» This section contains the conclusion.
6.0 References
» This section contains the list of related references in case if you use some
code which has been taken or adapted from another source (book,
magazine, internet, forum, etc.).
» It must be cited and referenced using Harvard Referencing Style Failure to
reference code properly will be treated as plagiarism.
SUBMISSION
The complete C++ program and project documentation (softcopy) in the form of a CD-
ROM.
The project documentation (hardcopy).
MARKING CRITERIA
The program submitted will be evaluated according to the following performance criteria:
Distinction (90% and above)
Program compiles and executes perfectly
At least 90% of the required functionalities are correctly implemented
Efficient data structures and\or algorithms are used in the implementation
Clear coding style and structure, and code is properly commented
Functionalities are fully tested/validated in program execution
Credit (70% – 89%)
Program compiles and executes
Between 70% and 90% of the required functionalities are correctly implemented
Implementation uses a data structure or algorithm that is not most efficient
Clear coding style, and code is properly commented
Functionalities are not fully tested/validated in program execution
Pass (50% - 69%)
Program compiles perfectly and executes
Between 50% and 70% of the required functionalities are correctly implemented
Implementation uses inefficient data structures or algorithms
Unclear coding style, or code is not properly commented
Functionalities are not full tested/validated in program execution, or produce errors in
some cases
Marginal Fail (30% - 49%)
Program does not compile or run, but coding logic is almost correct
Between 30% and 50% of the required functionalities are correctly implemented
Implementation uses inefficient data structures or algorithms
Unclear coding style, and no comments provided
Functionalities are not tested/validated in program execution
Fail (below 30%)
Program is not given
Program does not compile or run
Less than 30% of the required functionalities are implemented
Implementation uses very inefficient data structures or algorithms
No proper code structure and no comments provided
