Assessment Details

Assessment Task

Have you ever been unable to send an image because it was too large to export? In this assignment you will be reducing the size of colour images stored in PNG format. You will be implementing an adaptation of a compression technique called seam carving.

You will write a program in Java that reduces the size of an image horizontally by removing columns of pixels.

First the image will be read into the program using the method fromFileImage. You can query the image to get the Color of a given pixel using the getColorAt(int x, inty) method.  Each  pixel  should  be  represented  by a class  Pixel containing all salient information about each pixel in the image.

Specification

You must submit your work as a ZIP file to Gradescope. This file should:

●   Preserve the directory structure covered during the course (i.e., main, test, package)

●   The pom.xml with updated dependencies, where applicable.

●   Include all of the corresponding Java files that perform the tasks requested above, that is, not just the class containing the main method.

●   Comprise the image(s), in PNG format, involved in the project:

○ The original image

○   At least 1 image resulting from applying the bluest row to the original image.

○   At least 1 image resulting from applying the random row to the original image.

●   All Java files should be commented on by you.

Assessment Criteria

70  or higher There was evidence of the ability to perform all programming tasks correctly. The demonstration of the methods was excellent, coherent, well documented and clearly explained.

60-69              There  was  evidence  of ability  to perform some programming tasks

correctly. The demonstration of the methods is good, coherent and reasonably detailed and explained.

50-59              There  was  evidence  of ability  to perform some programming tasks

correctly,   but   the   demonstration   of   the   methods   was   limited, incoherent, not adequately documented and vaguely explained.

40-49              There was  limited evidence of ability to perform programming tasks.

The demonstration of the methods involved significant omissions and produced substantial inaccuracies.

39 or less       Failure to solve the  programming task  in assignment. Methods were

completely incorrect or absent. General grading criteria for Level 4 are described in Appendix B of the course syllabus.

Marking

The   University   uses   two   common   assessment   marking   schemes  –  one  for undergraduate and one for postgraduate - to mark all taught programmes leading to an award of the University.

More  detailed  information  on  the  common  assessment  marking  scheme  and the criteria can be found in the Course Syllabus, available on the University’s VLE.

Information for students on pathway and mobility programmes about conversion to Northeastern University grades is available in the relevant programme handbook

Learning Outcomes

This assessment will enable students to demonstrate in full or in part the learning outcomes identified in the Course Descriptor.

On successful completion of this assessment, students should be able to: Knowledge and Understanding

K1a         Demonstrate knowledge and understanding of basic design principles,    programming practices, tools, and techniques for software development.

K3a         Choose among basic design patterns and practices to design and implement small to moderately sized programs.

Subject Specific Skills

S1a         Evaluate the impact of program design decisions and implementations on the technical, social and management dimensions of software..

S2a         Demonstrate practical use of object-oriented design concepts, including encapsulation and inheritance, in software.

Transferable and Employability Skills

T1a         Write clear, concise, and well-documented code.

T3a         Display a developing technical proficiency in written English and an ability to communicate clearly and accurately in structured and coherent pieces of writing.

Accessing Feedback

Students  can  expect to  receive feedback on all summative coursework within 28 working days of the submission deadline. The 28 calendar day deadline does not apply to work submitted late. Feedback can be accessed through the Turnitin assessment link on the course page. Further instructions on submitting an assessment and accessing feedback can be found on the University’s VLE.

Late Submissions

Students are reminded to submit their assessment in the correct format and ahead of the published deadline. Deadlines are strict and Canvas uploads made remotely might not be immediate, we therefore strongly recommend that students upload their work to Canvas in goodtime before the deadline. If assessments are submitted late without approved Extenuating Circumstances, there are penalties:

●   For assessments submitted up to two days late: any mark of 40% or higher will be capped at 40% for undergraduate students. Any mark of 50% or higher will be capped at 50% for postgraduate students. Any mark below 40% for undergraduate students and below 50% for postgraduate students, will stand.

●   Students who do not submit their assessment within two days, and have no   approved extenuating circumstances, are deemed not to have submitted and to have failed that assessment element. The mark recorded will be 0%.

●   Late penalties are calculated differently for some types of portfolios. Please read the Assessment Brief of your portfolio carefully.

For further information, please refer to AQF7 Part C in the Academic Handbook.

Extenuating Circumstances

The University’s Extenuating Circumstances (ECs) procedure is in place if there are genuine circumstances that may prevent a student submitting an assessment. If the EC application is successful, there will be no academic penalty for missing the published submission deadline.

Students are normally expected to apply for ECs in advance of the assessment deadline. Students may apply for consideration of ECs retrospectively if they can  provide evidence that they could not have done so in advance of the deadline. All applications for ECs must be supported by independent evidence.

Students are reminded that the ECs procedure covers only short-term issues (within 21 days leading to the submission deadline) and that if they experience longer-term  matters that impact on learning then they must contact Student Support and

Development for advice.

Under the Extenuating Circumstances Policy, students may defer an assessed

element on only one occasion and may request an extension on a maximum of two occasions.

For further information, please refer to the Extenuating Circumstances Policy in the Academic Handbook.

Academic Misconduct

Any submission must be a student’s own work and, where facts or ideas have been used from other sources, these sources must be appropriately referenced. The

Academic Misconduct Policy includes the definitions of all practices that will be

deemed to constitute academic misconduct. This includes the use of artificial

intelligence (AI) where not expressly permitted within the assessment brief, or in a   manner other than specified. Students should check this policy before submitting their work. Students suspected of committing Academic Misconduct will face action under the Policy. Where students are found to have committed an offence they will  be subject to sanction, which may include failing an assessment, failing a course or being dismissed from the University depending upon the severity of the offence

committed. For further information, please refer to the Academic Misconduct Policy in the Academic Handbook.