Relational Database and Web Application CIS2360 Assignment 2 (50% of the overall assessment for this module) This document tells you: • What you need to hand in. • What criteria will be used to assess your work. • When the assignment will be handed out and when it will be submitted for marking You are reminded that it is your responsibility to read and understand the University regulations regarding assessment. Your attention is directed to the regulations regarding assessment in the Student’s Handbook of Regulations (available from the University website), and in particular to its guidance on academic misconduct and plagiarism. http://www.hud.ac.uk/registry/academicmisconduct/ http://www.hud.ac.uk/library/finding-info/apa-referencing/ Aims To develop skills in constructing a database driven web application. To critically analyze the implementation of a database driven web application constructed in PHP. Outcomes to be Assessed This assignment examines learning outcomes 1.4 to 1.5 and 2.4 to 2.5 Hand In • The assignment should be submitted via the designated turnitin links on UniLearn. All code should be added to a compressed zip folder and named in the following format firstname-lastname-userid. E.G. david-wilson-u1234567.zip. • A cover sheet, obtainable from http://ecover.hud.ac.uk/assignments/, which is to be prepended to your written component. • Each part of the assignment is to be submitted on a separate link. Hand Out Date January 17 2017 Hand In Date Part 1 – Friday 17 February 2017 (Written Report) Part 2 – Friday 7 April 2017 (Your Working Application and PHP Code) Resources Required An IDE of your choice, a Web Server and a database. Assessment Criteria Written Component – Approximately 1500 words (40%) 1. The report and evaluation of your application a. The design/modelling (UML) components for your application as derived from the assignment specification. (10%). Note: this is not the model solution for the database (provided) b. A discussion of the MVC architecture and how it applies to web application development (10%). c. A discussion of client and server interaction within web applications, discussing both client and server technology (10%). d. A discussion of alternative approaches to web application development and data interaction (10%). Note: Approximately 500 words each for question b – d. Web Component (60%) 2. PHP (Code) a. The application should be built using the MVC architecture 20% (Marks will be reduced for a non MVC implementation) b. The DAO Design Pattern 10% (Marks will be reduced for an implementation that does not conform to the parameters of the DAO design pattern) c. Fulfillment of Requirements (as per the problem statement) 20% 3. Demonstration of your working application 10% Problem Statement For this assignment you need to build a web interface for the Film Rental Service. The interface is for any one of the twelve shops in the company (You decide which shop you are going to develop for). Personnel who work in that shop can only update data records for that shop. That is, they can record when a film or films are loaned to a customer and when the film(s) is/are returned. Staff can only loan films to customers of the shop they work in. As such, you should: • Staff members should login to their shop interface. • Demonstrate film(s) being loaned to customers • Film(s) being returned by customers. • Calculate the daily sales figures for the shop and display them in a table on the web interface. • All input must be validated Note: There is no Registration requirement for this assignment. Notes: Note 1: The web interface is not being assessed; we are only concerned with the functionality of the application and its interaction with the database. Note 2: You must use the database provided. Note 3: The queries you make on the database should be made in respect of the functionality required in the problem statement. Note 4: You do not have to give a personal demonstration of your application but it should be hosted on the Selene web server within the School. As such, you must provide a URL for the address of the application. Failure to do this will result in 0 marks for the demonstration. Note 5: You may not use a Framework to develop your application. You must write your own code. Applications developed with a Framework, such as Codeigniter or other similar frameworks or a Content Management System, such as Drupal or similar will not be marked. Note 6: If in doubt, ask. Grade Indicators A. The report addresses all of the requirements, software is well structured, and the excellence of design is supported with an excellent evaluation, and a thorough but concise explanation of functionality. B. A very good attempt - addresses almost all of the report requirements. The software is well structured, a good design, a good evaluation and a good explanation of its functionality. C. A good attempt - addresses most of the report requirements, software is well structured, some features missing, a good evaluation and a reasonable explanation of its functionality. D. A reasonable attempt - addresses many of the report requirements, software will compile but is poorly structured, some features missing, not fully evaluated and functionality is not fully explained. E. Very poor but addresses a few of the report requirements, software attempted but does not compile, evaluation lacks any credibility; functionality not explained. F. Very poor, does not address the report requirements, no usable software, very little evaluation. G. Non-submission l .