Write My Assignment FREE

BIT246: Object Oriented RAD

Assessment 2 – Software Application – Ruby Project

Due Date: Week 6, Week 7, Week 8 and Week 12

Date of Demonstration: Week 12

Assessment Weightage: 35%

Total Possible Marks:

Phase1-5 marks + Phase2 – 15marks + Phase3 – 15marks = 35 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

1. Text

2. Word (.doc or .docx)

3. Pdf

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 – Question Answer session for all phases– the task that must be passed in order to pass the whole assessment or phases of assessment.

The project is to be delivered in several phases:

Phase 1 (5 marks – due week 6)

Write Ruby code and answer following questions. Upload rb files (with comments) on Moodle:

1. Create a text file named Story1234.txt (1234 should replace by your student ID), type the following statements into the file and save it:

Once upon a time, there was a little boy who went on a great adventure.

Unfortunately, nothing happened.

The End

Next, create a Ruby program named Phase1Q11234.rb (1234 should replace by your student ID) and add the program logic needed to perform the following tasks:

• Verify that the file exists.
• If the file does not exist, display an error message.
• If the file exists, read it and test whether it contains the phrase “a little boy”
• If it does display the contents of the text file otherwise display phrase not found.
• Add appropriate comments e.g Name, Student ID, functionality of a variable, brief explanation of logic and flow of your program embeded inside the program code.

2. Create a Ruby program file named Phase1Q21234.rb (1234 should replace by your student ID) and add the program logic needed to perform the following tasks:

• Prompt the user to type the path and name of a folder whose contents will be displayed.
• Capture and analyze user input to determine whether the specified folder exists.
• Tell the user whether or not the folder exists.
• If the folder exists, prompt the user to press Enter in order to view the folder’s contents.
• If the folder does not exist, display an error message.
• Add appropriate comments e.g Name, Student ID, functionality of a variable, brief explanation of logic

Phase 2 (15 marks – due week 8)

1. Create a Ruby program file named Phase2Q11234.rb (1234 should replace by your student ID) and add the program logic needed to perform the following tasks:

1. Request two user inputs – a term/word/phrase and a directory from the user through command prompt.
2. Search for user input term/word/phrase in all text documents (.txt) in the specified directory and sub-directories (user input directory).
3. Output the list of names of the documents containing the user given term/word/phrase and portion of content of the text document. You can add information like total number of documents containing the term/phrase or total number of occurrence of the term/phrase in a specific document.
4. Display the appropriate message/information, if there is no match found for the given term/word/phrase in all text documents in the given directory.
5. Require no fancy user interface. User input will be provided through command prompt .It must implemented by using Ruby.
6. Implemented by using classes, objects, methods and constructor.
7. Add appropriate comments e.g Name, Student ID, functionality of a variable, brief explanation of logic

2. Create a Ruby program file named Phase2Q21234.rb (1234 should replace by your student ID) and add the program logic needed to perform the following tasks:

1. This phase extends Question 1 by adding the capacity to search term/word/phrase in word documents and pdf documents as well as text documents.
2. Ruby gems are required to implement Phase 3 (i.e. download from https://rubygems.org/, installing the gem, using ‘require’ in code and calling the appropriate method of the gem ). Hint: Read the related gem documentation to identify the parameters and output of different methods provided by the gem.
3. Add appropriate comments e.g Name, Student ID, functionality of a variable, brief explanation of logic

Phase 3 (15 marks – due week 12)

This prototype will then be transported to a rails framework with a user interface similar to the example below.

1. The user will provide the input through web page in rails. Web page should contain two text fields (1. Word/phrase and 2. Root directory) and a search button in an HTML form.
2. Search results will be display on web page (same or different) as well.
3. 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).
4. Add appropriate comments e.g Name, Student ID, functionality of a variable, brief explanation of logic

Plagiarism

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

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.

Extensions:

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.

Penalties:

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	GAs	Weight	Comments
Assessment 1 – Class Test – Written assessment of key concepts of object oriented programming and design, including syntax and semantics of the programming language. (30 minutes)	Week 4	a	A,D	10%	Individual
Assessment 2 – Software Application – Suggested topic: Development and demonstration of an original advance application system. This assessment may be undertaken as a group activity. (equivalent to 1,500 words)	Week 6, 8 and 10	a, b, c	A,C,D	35%	Individual
Report – Suggested topic: A report describing the quality assurance of the developed software through program testing and accurate documentation of the software application developed in this subject. (600 words)	Week 12	d	C	15%	Individual
Examination – Written assessment of knowledge and application of object orientated programming theory and application. (2 hours)	End of Semester	a, b, c, d	A,C,D	40%	Individual

Marking criteria for Phase 1

Marking Week	Possible marks
No Comments	-1
Q1	2.5
Verify that the file exists.	0.5
If the file does not exist, display an error message.	0.5
If the file exists, read it and test whether it contains the phrase “a little boy”	1
If it does display the contents of the text file otherwise display phrase not found	0.5
Q2	2.5
Prompt the user to type the path and name of a folder whose contents will be displayed.	0.5
Capture and analyze user input to determine whether the specified folder exists.	0.5
Tell the user whether or not the folder exists.	0.5
If the folder exists, prompt the user to press Enter in order to view the folder’s contents.	0.5
If the folder does not exist, display an error message.	0.5

Rubric for Phase 2

Marking Scheme	Approx. % of grade	Excellent	Good	Reasonable	Poor
Program specifications/ Correctness	60%	No errors, program always works correctly and meets the specification(s).	Minor details of the program specification are 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.
Documentation, style	20%	code is well‐commented 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 naming and styling conventions
Robustness	20%	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

Rubric for Phase 3

Marking Scheme	Approx % of grade	Excellent	Good	Reasonable	Poor
Program specifications/ Correctness	52%	No errors, program always works correctly and meets the specification(s).	Minor details of the program specification are 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.
Documentation, style	16%	code is well‐commented 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 naming and styling conventions
Robustness	16%	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	16%	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

The post BIT246: Object Oriented RAD appeared first on My Assignment Online.

Expert Help With This Assignment — On Your Terms