C++The objective of this assignment is to refresh and enhance the skills of the students in problem solving involving functions, arrays, classes and others using the C++ programming language. Students MUST use the inheritance and polymorphism concepts in the OOP. Students are required to design a “Financial Monitoring System†that can perform the following functions:See attachment
INSTRUCTIONS
i. Efficiency
You should always try your best to minimize computations as much as possible. If a result can be achieved using less computation (expression evaluation), then it is usually a better solution. However, you must also take into consideration of modular design, ease of debugging and flexibility for future improvement etc.
ii. Accuracy
You should always test your program with all possible scenarios of how the program would be used. You need to make sure errors will not occur when it is used, especially in the case when the user enter an invalid input, in which case, the user must be prompted to enter a valid input.
ii. Robustness (Error-free)
To make the program more usable, the program should handle special cases such as an accidental invalid input from the user. If the user enters the wrong things, you should allow the user to re-enter a valid input. In whatever case, you should always try your best to ensure the program does not terminate unexpectedly. This may be hard to achieve sometime, but even if the program encounter a situation it cannot handle, it should at least display a warning message to the user and end itself graciously.
iii. Modularity
Each of your functions should NEVER be too long, always try to break down the problem into smaller functions with reasonable size. Of course, a function must form a logical processing unit that handles a single task with meaningful input and output.
Detailed Requirements:C++The objective of this assignment is to refresh and enhance the skills of the students in problem solving involving functions, arrays, classes and others using the C++ programming language. Students MUST use the inheritance and polymorphism concepts in the OOP. Students are required to design a “Financial Monitoring System†that can perform the following functions:See attachment
INSTRUCTIONS
i. Efficiency
You should always try your best to minimize computations as much as possible. If a result can be achieved using less computation (expression evaluation), then it is usually a better solution. However, you must also take into consideration of modular design, ease of debugging and flexibility for future improvement etc.
ii. Accuracy
You should always test your program with all possible scenarios of how the program would be used. You need to make sure errors will not occur when it is used, especially in the case when the user enter an invalid input, in which case, the user must be prompted to enter a valid input.
ii. Robustness (Error-free)
To make the program more usable, the program should handle special cases such as an accidental invalid input from the user. If the user enters the wrong things, you should allow the user to re-enter a valid input. In whatever case, you should always try your best to ensure the program does not terminate unexpectedly. This may be hard to achieve sometime, but even if the program encounter a situation it cannot handle, it should at least display a warning message to the user and end itself graciously.
iii. Modularity
Each of your functions should NEVER be too long, always try to break down the problem into smaller functions with reasonable size. Of course, a function must form a logical processing unit that handles a single task with meaningful input and output.
iv. Clarity and Style
Your program must be self-documented, with good, short but precise comments that help the reader to understand your program easier. It is possible, either you yourself or someone else may want to modify the program and add more functionality to it. A good style is also very important for program clarity.
Worker: On pay-for-deliverable
projects, all deliverables must be
uploaded to
vWorker.com before the
deadline(s)Â…with no exceptions. If
this contract makes it impossible
to do this (for example if it is
for a service that cannot be
uploaded), then do not start
this project. Otherwise, you
may find
yourself unprotected by the
payment guarantee.
Instead, ask the employer
to switch this project to
pay-for-time, so you are
guaranteed payment. If the
employer will not switch this, then
please alert us.
(Click here for more details...)
Example of unprotected/un-guaranteed work:
Imagine that this project is to
install something on the employers
website.
You do the work but upload nothing
to vWorker.com (because it takes too
long,
or you cannot). As long as there is
no dispute, you will not notice the
potential problem. But if the
employer disputes what you did then
we must make sure you delivered to the
triple-point-guarantee (100% to-contract: and
done in the industry exepcted manner, and
by the deadline). If the employer
does not allow us access to their
website, or accidentally/deliberately
changes the work you did on their
website, when we go to test it, we
will see that it does not work.
Then you would have no proof that
you delivered the final deliverables,
lose the arbitration, the escrowed
funds and receive a poor rating
(which will say “testing showed
the final deliverables did not
work”).
So for this reason,
you should have instead followed
the above instructions and
switched it to pay-for-time.
Had you done this, we would simply
have checked the Accutimcard to
make sure you punched-in the time
and were working on it. You would
have been paid for every hour
you worked.
Remember that contacting the other party outside of the site (by email, phone, etc.) on all outsourcing pay-for-deliverables projects violation of both the employer and worker agreements.
vWorker.com monitors all site activity for such violations and can instantly expel transgressors on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
Categories:
The categories were created by the employer, but sometimes mistakes occur.
If any of these categories are incorrect, please
report it and let us know.
Like everything else on this page, these categories are part of the original contract
for this project.
Technology, Software Development, Desktop applications
Additional Files:
This project includes IMPORTANT additional attached files. Please download and read fully before bidding.
15.96 kb
Legal:
1) I require complete and fully-functional working program(s) in executable form as well as complete source code of all work done (so that I may modify it in the future).
2) Deliverables must be in ready-to-run condition as follows (depending on the nature of the deliverables):
2b) Any website server-side deliverables must be installed in ready-to-run condition in the employer's environment (unless overridden otherwise by the employer elsewhere in this contract.
2c) If there are any server-side deliverables (intended to only exist in one place in the employer's environment) then they must be installed by the winning worker in ready-to-run condition (unless specified elsewhere by the employer).
2d) All other software (including but not limited to any desktop software or software the employer intends to distribute) must include a software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project (unless specified elsewhere by the employer).
3) Employer will receive exclusive and complete copyrights to all work paid for. All paid for deliverables will be considered 'work made for hire' under U.S. Copyright law.
3b) No part of the deliverable may contain any copyright restricted 3rd party components (including GPL, GNU, Copyleft, etc.) unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's 'Worker Legal Agreement'.
