SEMESTER 2 2019/20 COURSEWORK BRIEF: Module Code: MANG6180 Assessment: Individual Coursework Weighting: 30 Module Title: Web Applications Module Leader: Christophe Mues Submission Due Date: @ 16:00 Thursday 30 April 2020 Word Count: (see brief) Method of Submission: Electronic via Blackboard Turnitin ONLY (Please ensure that your name does not appear on any part of your work) Any submitted after 16:00 on the deadline date will be subject to the standard University late penalties (see below), unless an extension has been granted, in writing by the Senior Tutor, in advance of the deadline. University Working Days Late: Mark: 1 (final agreed mark) * 0.9 2 (final agreed mark) * 0.8 3 (final agreed mark) * 0.7 4 (final agreed mark) * 0.6 5 (final agreed mark) * 0.5 More than 5 0 This assessment relates to the following module learning outcomes: A. Knowledge and Understanding A1. Be able to identify and have a basic understanding of development and operational Internet/Web technologies; A2. Have gained an appreciation of a Web application development cycle. B. Subject Specific Intellectual and Research Skills B1. Have an appreciation of complexity in real-world systems; B3. Be able to apply basic programming skills to develop scripted Web pages. C. Transferable and Generic Skills C3. Report writing; C4. Programming skills 3 Coursework Brief: Activity Your task is to develop one or more scripted web pages that are meant to be part of a website of a small (fictitious) group of family portrait photographers in the South of England. These web pages should set out what they do (i.e. capture families either on location or in their photo studios), be appealing to their target market and list the photographers working in the group. Specifically, your solution should contain: HTML pages – an effective home page, or collection of navigable pages, with corresponding (example) content, that effectively showcases the group and presents its photography services to the intended target audience, including among other things testimonials, social media links (links only), etc.; Functionality/scripting – a script which fetches the list of photographers linked to the group, with their names and contact details, from a pre-specified MySQL database table (see database specifications below) and successfully displays this content on one of the pages. Styling (usability and visual aesthetics) – a user-friendly and visually appealing styling that are suitable for and well applied to the problem setting, and with appropriate positioning of all elements. Importantly, to avoid any possible confusion, every page you include in your solution must clearly include the following disclaimer: “Note that this is a fictitious website that was developed by a student as part of a programming assignment. None of the content on this page is meant to be genuine nor should it be taken as such”. Also, please do not make any attempt to submit your pages to a search index or to provide any external link to them. SEMESTER 2 2019/20 To develop your solution, you will need to use HTML and PHP server-side scripting. Use of CSS for styling is strongly encouraged; some may wish to use Bootstrap for this purpose. Importantly, your server-side script(s) must be designed to run under the existing Web server configuration used to host your personal web file store (www.southampton.ac.uk/~username/).1 Solutions that require different PHP versions, customised server configurations, etc. will attract low marks; you may wish to verify compatibility at the beginning stages of your work. Furthermore, you are asked to produce a written report (max. 1,000 words) which discusses and justifies your main design decisions (e.g. usability considerations taken into account, visual aesthetics, choice of framework/starting template, etc.). This report should also reference any sources of information or of existing code you used, and how you applied or further customised these. It should demonstrate how you reflected on the most relevant elements of your solution; you are encouraged to justify certain choices based on further research/reading. Database specifications For the purpose of this assignment, a MySQL database named “mgmt_webapp_msc” was created and stored on a University server (lamp.soton.ac.uk). This database contains a table named “photographers”, which was defined as follows: CREATE TABLE photographers ( photographer_id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, first_name VARCHAR(35), last_name VARCHAR(35), address VARCHAR(255), postcode VARCHAR(8), email VARCHAR(254), phone VARCHAR(11) ); You have been granted the necessary rights to select records from this table under the user name: MANG6180_student, password: tintin1830. You may assume the contents of this table will be maintained by the group of photographers; you are not given any user rights to insert, delete or update records in the table. Important note on academic integrity This is an individual assignment so your markup code and scripts, as well as your report, must be your own work: you are not allowed to copy from other students. You are of course encouraged to look for useful information sources to support your design choices and reference them. Also, you are allowed to make use of existing templates or frameworks and development environments to speed up development, or you may look for scripting code examples on the Web, in books, etc., and adapt and incorporate individual chunks of scripting code thus found. This is provided that you acknowledge their use and the source, both in code comments and in your written report. However, over- reliance on a single (or few of) such source(s), in so far that there would be little evidence of personal reflection about design and implementation decisions or further customisation to the task at hand, is discouraged, and marks will reflect this. The written report itself is subject to the same rules and guidelines regarding academic integrity as any other piece of coursework that you submit (e.g., it should be written in your own words and properly acknowledge any sources of information). 1 See Lab Session 2 for more details on how to upload and test your application. SEMESTER 2 2019/20 Submission Firstly, you must electronically submit your written report to Blackboard (Turnitin) so that it can be checked for plagiarism. Note that Turnitin will only accept MS Word or PDF documents (the preferred format is PDF) so do not attempt to also include your scripted web pages here. Make a note of your Turnitin submission ID. Secondly, include all your scripted web pages or program files (i.e., all HTML, PHP, CSS or other files required to run your application), together with the report that you submitted to Blackboard, into a zip file. Importantly, make sure this zip file contains your student number! (e.g. 26123456.zip) Open your browser and go to https://safesend.soton.ac.uk/. Log in. Click the “Drop-off” button. Check that your details are correct and click the “Next” button (as you do not have a request code). On the next page, check again that the email address in your “from” details is correct, leave the default options checked, and click on the “+” button to specify where you would like to send the file to. Then enter the module leader’s details: Name: Mues, C. Email: [email protected] Make sure these are correct! Fill in your name, student ID and Turnitin submission code in the “Short note to the Recipients” box. Have a final check everything is included. Click the “Drop-off Files” button. Your file should then be uploaded to the system, ready to be picked up. For your own records, print the “Drop-Off Summary” confirmation screen as proof of submission. Please note that, given the specific nature of this assignment, your Drop-off submission will be taken
as your main submission (including for the calculation of late submission penalties). You will get a confirmation (most likely the week following the submission deadline) when your file is picked up (if I have any problems downloading your submission I will contact you, so there is no need to send me an extra email, unless of course you are experiencing problems with the system). Assessment Marking criteria relate to the submitted Web application itself and the quality of your accompanying report. As for the former, we will evaluate the provided page(s), functionality/scripting and usability and visual aesthetics. Please carefully examine the grade descriptor document (provided separately) for more details and respective weights for each of the marking criteria. This assignment accounts for 30% of your overall module mark. SEMESTER 2 2019/20 Nature of Assessment: This is a SUMMATIVE ASSESSMENT. See ‘Weighting’ section above for the percentage that this assignment counts towards your final module mark. Word Limit: +/-10% either side of the word count (see above) is deemed to be acceptable. Any text that exceeds an additional 10% will not attract any marks. The relevant word count includes items such as cover page, executive summary, title page, table of contents, tables, figures, in-text citations and section headings, if used. The relevant word count excludes your list of references and any appendices at the end of your coursework submission. You should always include the word count (from Microsoft Word, not Turnitin), at the end of your coursework submission, before your list of references. Title/Cover Page: You must include a title/ cover page that includes: your Student ID, Module Code, Assignment Title, Word Count. This assignment will be marked anonymously, please ensure that your name does not appear on any part of your assignment. References: You should use the Harvard style to reference your assignment. The library provide guidance on how to reference in the Harvard style and this is available from: http://library.soton.ac.uk/sash/referencing Submission Deadline: Please note that the submission deadline for Southampton Business School is 16.00 for ALL assessments. Submission: The assignment MUST be submitted electronically, in part via Turnitin, which is accessed via the individual module on Blackboard, and through the University’s Drop-off system (details above). Further guidance on submitting assignments to Blackboard/Turnitin is available on the Blackboard support pages. It is important that you allow enough time prior to the submission deadline to ensure your submission is processed on time as all late submissions are subject to a late penalty. We would recommend you allow 30 minutes to upload your work and check the submission has been processed and is correct. Please make sure you submit to the correct assignment link. Turnitin Submission: You will know that your Turnitin submission has completed successfully when you see a message stating ‘Congratulations – your submission is complete…’. It is vital that you make a note of your Submission ID (Digital Receipt Number). This is a unique receipt number for your submission. You may be required to provide this number at a later date. We recommend that you take a screenshot of this page, or note the number down on a piece of paper. You should also receive an email receipt containing this number, and the number can be found after submitting by following this guide. This method of checking your submission is particularly useful in the event that you don’t receive an email receipt. You are allowed to test submit your assignment via Turnitin before the due date. You can use Turnitin to check your assignment for plagiarism before you submit your final version. See “Viewing Your Originality Report” for guidance. Please see the Module Leader/lecturer on your module if you would like advice on the Turnitin Originality report. The last submission prior to the deadline will be treated as the final submission and will be the copy that is assessed by the marker. It is your responsibility to ensure that the version received by the deadline is the final version, resubmissions after the deadline will not be accepted in any circumstances. Important: If you have any problems during the submission process you should contact ServiceLine immediately by email at [email protected] or by phone on +44 (0)23 8059 5656. Late Penalties: Further information on penalties for work submitted after the deadline can be found here. Special Considerations: If you believe that illness or other circumstances have adversely affected your academic performance, information regarding the regulations governing Special Considerations can be accessed via the Calendar: http://www.calendar.soton.ac.uk/sectionIV/special-considerations.html SEMESTER 2 2019/20 Extension Requests: : Extension requests along with supporting evidence should be submitted to the Student Office as soon as possible before the submission date. Information regarding the regulations governing extension requests can be accessed via the Calendar: http://www.calendar.soton.ac.uk/sectionIV/special-considerations.html Academic Integrity Policy: Please note that you can access Academic Integrity Guidance for Students via the Quality Handbook: http://www.southampton.ac.uk/quality/assessment/academic_integrity.page?. Please note any suspected cases of Academic Integrity will be notified to the Academic Integrity Officer for investigation. Feedback: Southampton Business School is committed to providing feedback within 4 weeks (University working days). Once the marks are released and you have received your feedback, you can meet with your Module Leader / Module Lecturer / Personal Academic Tutor to discuss the feedback within 4 weeks from the release of marks date. Any additional arrangements for feedback are listed in the Module Profile. Student Support: Study skills and language support for Southampton Business School students is available at: http://www.sbsaob.soton.ac.uk/study-skills-and-language-support/.
