Recent Question/Assignment

CO4752 Web Development Assignment (2018)
Date issued: 18th, March, 2019 Date due: 17st, May, 2019
This assignment is worth 100% of the assessment for this module.
Learning Outcomes assessed
1. Understanding of multi-tier web application architecture and corresponded infrastructure setup. 2. Use of Servlets as a middle layer technology for web application development
3. Use of JavaScript and AJAX for web front development.
4. Use of JSON/XML as for exchanging messages between web portal and server application
5. Use of HTML/HTML 5 and CSS for web portal rendering.
6. Use of JDBC/Hibernate to operate Database (MySQL).
7. Understanding of how authorisations and authentications of web applications are conducted and are able to implement them for the web application.
Introduction
In this assignment, you are required to complete a simple online message management system which is composed of three tiers (web portal, middle layer and database). The basic requirement of the online message management is as the followings:
1. Users are able to Add/Remove/Update/Search/ their messages through a web portal. Messages are stored in the back end database.
2. Before they start performing any above actions, they will need to log into the system (therefore, you system should provide basic user registration/login/logout functions as well).
3. They can share their messages with other users by marking the message as public or private. If a message is marked as public, it can be seen by other users too. So a user can see both messages that are created by himself or messages that are marked as public by other users.
Task Details
Note: for guidelines what to hand in and what the marker will be looking for, see the marking scheme. Working INDIVIDUALLY:
1. Web portal: The architecture of the assignment needs to be strictly three tiers based. This means web portal is only used for rendering contents, taking inputs from users and feeding back results. The portal is not supposed to handle any business logics (PHP, Ruby on Rails, JSP style portal and things similar will not be accepted and marked). You will need to use javascript+HTML 5+CSS for your web portal development. Necessary third party libraries are allowed in the implementation. It should not point any specific backend server (bound with specific IP/hostname or etc.) but needs to be configurable using some configuration files
2. Middle Layer: A middle layer that talks to both database and web portal through message exchange. It should handle all business logics (how messages should be manipulated, how transaction is supported, authorisation and authentication and etc.). The middle layer needs to be implemented conforming to Java Servlet standard. It needs to be done in JAVA rather than any other programming languages. It should not point any specific backend database, but is configurable using web.xml configure file.
3. Database: MySQL database will be used to store data. You will need to define your database schema that support your application. For this assignment, you don’t need to worry too much about the DB normalisation rules and etc. You can use one table even as long as it satisfies your needs.
4. Message Exchange: The messages that are exchanged between the portal and middle layer need to be JSON. This leads the whole system to a completely decoupled manner. No portal will be relying on any specific middle layer’s implementation and vice versa. Both of them are only dependent on the contents of the messages exchanged and interpretations of those messages.
What You Should Submit:
You should submit a zip package and a source code text file via the links on Blackboard. Both files should follow the name convention: YourRegistrationNumber_(FirstName LastName).zip/txt.
• The zip file should contain the following contents:
a. Your web portal folder. This folder needs to be directly deployable and runnable on tomcat 6+ servers. Folder that fails to be deployed or run will be regarded as a failure, and you will lose half marks for web portal section.
b. A war file which can be directly deployed on tomcat 7+ servers. Failure on the deployment will lose you half marks for middle layer sections. You will need to be very careful with the all the libraries that you choose to use. Make sure you pack them up in the war file so when the war is deployed, the tomcat server will not complain about missing libraries.
c. A db.sql file that contains all the data you’ve created or used or tested for your project. It can be restored to MySQL database.
d. A report that explains your design, implementation details and any potential problems that you are aware of your development and potential improvement that can be done. Full lists of messages (syntax) that are exchanged between your Servlet service and portal. Explain how the http protocol is used in your implementation if any.
• The source code text file must contain all the source codes you implemented. The content of the file is copied and pasted from all your own *.java source files.
Failure to provide either of the above files will be considered as an incomplete submission and your work will not be marked until both files are submitted. (It can be treated as a late submission).
Assessment Criteria:
When I am marking this assignment, I will deploy your submission to my own environment. Please don’t assume that I will be in any of the computing labs or place similar. So please make sure your submission is going to work on any PC. Also, please make sure you web portal will work on google chrome browser (it has better support to 3rd party libs for javascript).
1.Web Portal Development 40%
Characteristics Mark Range
Has basic functions as specified in the requirements. User can do very basic operations through the portal. Pages are rendered using HTML only. CSS is not applied appropriately. Key interactions and communication with back end is handled by HTML form only. Implementation contains errors but doesn’t affect browsing rendering. Deployable on Tomcat server 6+ 0-15
Proper JavaScript is used and applied to all key operations/components in the portal. CSS is applied appropriately. Message exchange and handling is performed without major errors. Layout of portal is properly designed. HTML can pass W3C validator.
Exceptions returned from backend are handled properly using warning messages. 16-30
Excellent portal design with easy to use navigations. Authorisation and authentication are handled properly on the portal side. Have used local caching for data that need to be processed by users for better usability. Major PC browsers are supported (Chrome, Firefox, IE, for Internet Explorer, IE8+ is fine), as well as mobile devices browser with no issues. 31-40
2. Middle Layer 40%
Basic operations are handled properly using Java Servlet framework. Servlet concept is applied correctly (state and data driven, HTTP verbs are used are used correctly) from the implementation. Deployable on Tomcat server 6+. Can talk to DB and return results to the portal, but with major fault or exceptions. Some libraries required are missing. 0-15
No major exceptions or errors or they are handled properly. Transactions are handled correctly with database. Connections to DB are handled properly as well. (open/close). Sessions are implemented well. Use of web server context to exchange information if needed. Can handle all the messages that are passed in from the portal. Authorisation and authentication are implemented on service side. 16-30
Service lifecycle is handled well (activities when service is loaded, started, destroyed etc.) if needed. Necessary configures, such as DB connection information, are not hardcoded but are specified in configure file and is loaded into the application context. Concurrent control is implemented and implemented caching mechanism for better service performance. 31-40
3. Report 20%
Servlet APIs are specified. Problems, experiences while doing the assignment are summarised very briefly. Focused only on what you have done. 0-10
Deep analysis of your own implementation including the pros and cons. Possible improvement for the current implementation. Complete list of messages that are exchanged between server and portal as well as detailed comments (think it as a communication document between the service developer and portal developer). 11-20
Late work
Except where an extension of the hand-in deadline date has been approved (using extenuating circumstances forms), work that is handed in up to 5 days late will be capped to 50%. After this, it will receive a mark of 0%:

Looking for answers ?