BIT246: Object Oriented RAD
Assessment 2 – Software Application – Ruby Project – Phase 3
Due Date: Week 12
Hurdle task: Week 12 Date of Demonstration: Week 12
Assessment 2 Weightage: 35%
Total Possible Marks: 15 marks
Phase3 – 15 marks out of 35 marks – 15% of 100 total marks
A company often needs to retrieve documents on its hard drive based on those documents containing words or phrases. It thus needs a system that allows the user to enter the required phrase or word and to then find the document/s containing that phrase and to print them to screen.
The type of documents that need to be accessed are
2. Word (.doc or .docx)
To shorten the search path, the user would also enter the root directory where the search begins. An example of the Ruby Rails implementation is shown below
This Assessment contains HURDLE TASK – Practical demonstration and Question Answer session about your submission– the hurdle task that must be passed to pass this phase of the assessment.
The project is to be delivered in several phases. This is the last phase of the assessment 2 and following are the specifications of Assessment 2 – Phase 3.
Phase 3 (15 marks – due week 12)
Extend the Phase 2 – Question 2 to be transported to a rails framework with a user interface similar to the example above.
1. The user provides the input through web page in rails. The web pages takes two user a term (or a word or a phrase) and a folder path. Web page should contain two text fields (1. Word/phrase and
2. Folder or directory path) and a search button in an HTML form.
2. Search results (output) must be display on web page (on same web page or different result page)
3. The rails application searches the Model first to find the search results for a given term and a folder path in the databases.
a. If search is successful, display the result(a) on the web page
b. If search is not successful, then the rails application searches the given term in the folder path on computer disk
i. If search is successful, the application adds the results in the database and displays the result on the web page.
ii. If search is not successful, the application does not add any record in the database and display an appropriate error message.
4. In this phase for every match found, the filename including the full path will be printed to the browser and a portion of content of the document will be printed into a text-area (these will be added dynamically according to the number of matches found).
5. Add appropriate comments e.g. Name, Student ID, functionality of a variable, brief explanation of logic
All used sources must be properly acknowledged with references and citations, if you did not create it. Quotations and paraphrasing are allowed but the sources must be acknowledged. Failure to do so is regarded as plagiarism and the minimum penalty for plagiarism is failure for the assignment. The act of given your assignment to another student is classified as a plagiarism offence. Copying large chucks and supplying a reference will result in zero marks as you have not contributed to the report. Copying from Youtube or other videos is also plagiarism (including transcripts). Citation in a video can be included as credits at the end.
Late submission of assignments will be penalised as follows:
• For assignments 1 to 10 days late, a penalty of 5% (of total available marks) per day.
• For assignments more than 10 days late, a penalty of 100% will apply. Which means, the assignment will not be marked and attract a fail grade.
Your submission must be compatible with the software (PDF/Word/Video/Zip) in Melbourne Polytechnic, Computer Laboratories/Classrooms.
Under normal circumstances, extensions will not be granted. In case of extenuating circumstances—such as illness—a Special Consideration form, accompanied by supporting documentation, must be received before 3 working days from the due date. If granted, an extension will be only granted only by the time period stated on the documentation; that is, if the illness medical certificate was for one day, an extension will be granted for one day only. Accordingly, the student must submit within that time limit.
Penalties may apply for late submission without an approved extension.
Academic misconduct such as cheating and plagiarism incur penalties ranging from a zero result to program exclusion.
All assessments (except for final examination) and feedback are provided via the Moodle site and in classes.
Assessment Tasks: Due Date SLOs CLOs Weight Comments
Class Test – Two written assessments of key concepts of object oriented programming and design, including syntax and semantics of the programming language. (30 minutes) Week 4 and Week 10 1,2,3,4 1 20% Individual
Software Application – Suggested topic: Development and demonstration of an original advanced application system based on. Suggested topic
Phase 1 (5%) : Working with Files and
Phase 2 (15%): Working with Files and folders by using Ruby gems Phase 1 – Week 6 Phase 2 – Week 8 and
Phase 3 – Week 12 1,2,3 1,3 35% Individual
Phase 3 (15%): Working with Files and
folders by using rails
Report and Oral Presentation - Suggested topic: A report and presentation to demonstrate an understanding of Ruby programming concept. Week 11 4 3 20% Individual
Software Application – Suggested topic: Development and demonstration of a web-based application using MVC for multiple CRUDs for multiple models Week 14 1,2,3 1,3 25% Individual
Rubric for Phase 3 (15 marks)
Following test cases will be executed to mark the assessment:
1. Given folder path does not exists
2. Given folder path exists but the given phrase or word does exist in any of the files
3. Given folder path exists and files found contains the given phrase or word.
This Assessment contains HURDLE TASK – Practical demonstration and Question Answer session about your submission– the hurdle task that must be passed to pass this phase of the assessment. NO demonstration – NO marks
Marking Scheme Approx
% of grade Excellent Good Reasonable Poor
specifications/ Correctness 65% No errors, program always works correctly and meets the specification(s) and test cases Minor details of the program specification is violated, program functions incorrectly for some inputs. Significant details of the specification are violated, program often exhibits incorrect behaviour. Program only functions correctly in very limited cases or not at all.
style 10% code is well-
and styling and naming conventions are well implemented comments are generally used when required
and naming and styling conventions are usually followed some comments are missing or naming and
styling conventions are not always followed Hardly any comments or adherence to
Robustness 10% The program catches all exceptions that can occur and provides all necessary information to the user when they occur The program catches most exceptions that can occur and provides reasonable information to the user when they occur The program catches some exceptions that can occur and provides some information to the user when they occur The program does not catch exceptions
User Interface 10% Interface is neat and well organized and uses rails capabilities extensively Interface is basically neat and well organized but does not make
full use of rails capabilities Interface is reasonable and makes some
use of rails capabilities Interface is untidy and not organized and does not use rails capabilities
Demonstration 5% Demonstration is given to show all test cases and prepared examples Demonstration is given to show some test cases Reasonable demonstration No
Demonstration is given