Tag: programming

ASSESSMENT 2 BRIEF
Subject Code and Title MIS202 App, Web Design and Development
Assessment Frontend Programming Project
Individual/Group Individual
Length Not applicable
Learning Outcomes The Subject Learning Outcomes demonstrated by successful completion of the task below include:
a) Examine and apply web-based application architecture
b) Propose and communicate solutions using web-based design to meet organisational needs
c) Analyse organisational problems and develop solutions using frontend and backend technologies
d) Apply web-based programming concepts to solve organisational problems
Submission Due by 11:55pm AEST Sunday end of Module 4.2 (Week 8).
Weighting 30%
Total Marks 100 marks
Task Summary
In Assessments 2 and 3, you will turn the website prototype you developed in Assessment 1 into a working website. In this assessment, you will be developing the frontend of that website.
Please refer to the Task Instructions for details on how to complete this task.
Context
In this assessment, you will focus on frontend development. In particular, you will demonstrate your HTML, CSS and JavaScript programming skills and apply them in a close-to-real-life web development project.
Task Instructions
This assessment is based on the case study on Student Accommodation. You should first read the case in Assessment 1. You should also read the additional information for Assessment 2.
Additional information for the case
The website will support all the most recent several versions of mainstream browsers, including Safari, Chrome, IE, Edge and Firefox. Considering the popularity of mobile devices, this website should also be able to be viewed on a mobile device with a mobile browser, that is, the layout of the website shall be able to automatically adapt to various screen sizes and resolutions.
The company places a high standard on the usability of this website and requires you to develop a website that maximises usability. The following usability considerations must be implemented:
• contextual help tips provided to users when they mouse over a button or an input field;
• client-side validation must be implemented, e.g. prompt to user when their password and confirmed password do not match or if the input is invalid (e.g. a negative number for weekly rent).
All programming code must be well formatted, including appropriate indentation and spacing. Please refer to section 2.1, 2.2, 3.1, 3.2, 4.1 and 4.2 in Google HTML/CSS Style Guide available at https://google.github.io/styleguide/htmlcssguide.html#HTML_Formatting_Rules.
You must also provide sufficient comments in the code. In particular, comments must be provided to significant blocks of code that directly address the functional requirements of this system.
Assessment Task
You are now to develop a comprehensive frontend for the website in the case study using HTML, CSS and JavaScript. The frontend must comprehensively include all the functional requirements described in the case study and the requirements you identified in Task 1, 2 in Assessment 1 for each user either described in the case study, or that you identified in Task 3.1 in Assessment 1. The frontend must also satisfy all the requirements in the Additional Information for the case section in this Assessment.
There is NO minimum HTML page requirement nor maximum HMTL page requirement.
You may use frontend web development frameworks or libraries, including but not limited to, Bootstrap (https://getbootstrap.com) and JQuery (https://jquery.com).
General Assessment Requirement
Incomprehensible submissions – Assessments provide the opportunity for students to demonstrate their knowledge and skills to achieve the required standard. To do this, assessment responses need to be both clear and easy to understand. If not, the University cannot determine that students have demonstrated their knowledge and skills. Assessments will, therefore, be marked accordingly including the potential for 0 (zero) marks where relevant.
Case study: Assessment response must focus on the hypothetical case study given in the Task Instructions. Any assessment items that do not address the case study may be awarded 0 (zero) marks.
Track changes: If you use Track Changes when writing your assessment, you must ensure that the submitted document is the final and correct version of the document. That is, if your submitted report contains Track Changes or Comments or any other editing marks, it may be awarded 0 (zero) marks. It is your responsibility to submit the final and correct version of your report.
Check with marking criteria: Before submitting your assessment, you should check it against the assessment criteria and the marking rubric included in this specification to ensure that you have satisfactorily addressed all the criteria that will be used to mark your submission.
Academic language: All submissions should be thoroughly proofread for spelling, typographical or grammatical errors before being submitted. Do not reply on the ‘spell-check’ function in your word processing program. If, for example, ‘affect’ is substituted for ‘effect’, your program may not detect the error.
Referencing: No referencing required for this assessment.
Submission Instructions: ALL students must submit ONE ZIP file containing ALL HTML/CSS/JS files via the Assessment link in the main navigation menu in MIS202 App, Web Design and Development. Physical copies/email submissions are not accepted.
Complete and correct submission: Assessments, once submitted, are FINAL and therefore cannot be modified. The onus is on you to ensure that your submissions are final, correct (correct files in correct format) and complete before submitting to Blackboard.
You are expected to begin this assessment when you begin the trimester, especially as you relate the learning activities (formative assessment) in the modules to this and the other (summative) assessments. Be sure to keep several drafts of your work as well as your notes and any sources you used to draw on when preparing your report.
Extensions will be considered only in extenuating circumstances where the student has applied before the due date. At that point, students are required to provide the latest draft, in case the extension is not granted, and to demonstrate they have earnestly done everything to avoid lateness.
Students are responsible for keeping appropriate back-ups and drafts of their assignments and to submit the correct version.
Torrens University Australia’s policies apply to the preparation and submission of this assignment.
Assessment Rubric
Assessment Attributes Fail
(Yet to achieve minimum standard) 0-49% Pass
(Functional) 50-64% Credit
(Proficient)
65-74% Distinction
(Advanced)
75-84% High Distinction
(Exceptional) 85-100%
Overall
•
•
20% Web Page Layout And Styling
The overall web page design is professional and the layout is complete (e.g. clear navigation, footer).
The overall styling of the web pages is professional and is suitable for the case study. The website is poorly designed. The implementation demonstrates limited or no understanding of the basic web page structure.
The styling of the website does not look professional and may not be fit for purpose. The website is not very well designed and there is a noticeable lack of structural components in the web page.
The overall styling of the website is not very professional and there is significant room for improvement. The website is generally well designed and the layout structure is generally complete, but there is some room for improvement.
The overall styling of the website looks somewhat professional and generally fit for purpose, but there is some room for improvement. The website is excellently designed and the layout structure is generally complete.
The overall styling of the website looks professional and fit for purpose, but there is minor room for improvement. The website is expertly designed and the layout structure is complete.
The overall styling of the website looks extremely professional and fit for purpose.
Comple
•
•
20% teness and relevance
The front-end website covers all major functional requirements for all its users in the case study. All the website pages implemented in the submission are relevant to the case study. Many functional requirements are not implemented.
Many implemented
features are not relevant to the case study. Some of the major functional requirements are implemented.
Some of the implemented features are relevant to the case study. Most of the major functional requirements are implemented.
Most of the implemented features are relevant to the case study. All of the major functional requirements are implemented.
All of the
implemented features are relevant to the case study. All of the major functional requirements are implemented to a very high standard.
All implemented features are highly relevant to the case study.
Responsive web design and browser compatibility The implementation demonstrates limited or no understanding of The implementation demonstrates functional understanding of The implementation demonstrates sound understanding of The implementation demonstrates clear understanding of The implementation demonstrates thorough and in-
•
•
•
20% The frontend development correctly used responsive web design.
The web pages and their layout adjust to various screen sizes. The web pages and their layout look good in all mainstream browsers (Chrome, Edge, Safari and Firefox). responsive web design techniques.
The implementation demonstrates limited or no understanding of browser compatibility. responsive web design techniques.
The implementation demonstrates functional understanding of browser compatibility. responsive web design techniques.
The implementation demonstrates sound understanding of browser compatibility. responsive web design techniques.
The implementation demonstrates clear understanding of browser compatibility. depth understanding of responsive web design techniques.
The implementation demonstrates thorough and indepth understanding of browser compatibility.
Web form design
• Form widgets are selected appropriately, that is, the most appropriate form controls are selected for a given type of data.
• Appropriate HTML5 form
validation features are used.
20% The choice of form widgets demonstrates limited or no understanding of the function of commonly used web form widgets.
No HTML5 form validation is implemented. The choice of form widgets demonstrates functional understanding
of the function of commonly used web form widgets.
Some HTML5 form
validation is
implemented, but there is significant room for improvement. The choice of form widgets demonstrates sound understanding of the function of commonly used web form widgets.
HTML5 form validation is implemented, but there is some room for improvement. The choice of form widgets
demonstrates clear understanding of the function of commonly used web form widgets.
HTML5 form
validation is implemented, but there is minor room for improvement. The form widgets are selected appropriately, that is the most appropriate form controls are selected for a given type of data;
Appropriate HTML5 form validation features are correctly and thoroughly used.
Coding convention and quality of code
• The program follows a consistent naming convention.
• The program is well formatted, including appropriate spacing and indentation.
• The program contains sufficient comments; the implementation of major functions is commented. The code is formatted very little to not at all.
The naming of methods or variables is inconsistent. No naming convention is followed. The code is satisfactorily written, but there is substantial room for improvement.
There are significant errors in code format, and naming of methods or variables. The code is generally well written, but there is some room for improvement.
There are more than 5 errors, but less than 8 errors in terms of naming convention and code format. The code is generally well written.
There are more than
2 errors but less than 5 errors in terms of naming convention and code format. The code is expertly written.
There are no more than 2 errors in terms of naming convention and code format.
20% Little or no comments provided. There is a significant lack of useful comments. There is reasonable amount of useful comments. There is a sufficient amount of useful comments. There is a sufficient amount of useful comments

• WE HAVE DONE THIS ASSIGNMENT BEFORE, WE CAN ALSO DO IT FOR YOUGET SOLUTION FOR THIS ASSIGNMENT, Get Impressive Scores in Your ClassCLICK HERE TO MAKE YOUR ORDER on Web Design and Development Assessment Frontend Programming Project
• Are You looking for Assignment and Homework Writing help? We Provide High-Quality Academic Papers at Affordable Rates. No Plagiarism.

• TO BE RE-WRITTEN FROM THE SCRATCH