Scenario Brief – Royal Literary Fund – Content Management System (CMS)
You are required to build a CMS prototype Web Application called: RLF CMS an application that allows the RLF admin to create content for their website and hybrid apps.
Students using the website will not access the CMS. Instead, RLF admins will be able to update existing content
for
the website:
https://www.alexessaytool.com/
Your data model will
therefore
need to reflect the content structure of the existing app,
so that content updates map over to the live website and hybrid app suite. Take time to view the website and then draw a rough outline
for
the page structure. For example, there are 10 steps – and each step may have one or more pages within.
The CMS must be secured behind
an
login system. You can explore different
role based
access control features within Yii2 – but as a minimum, there will be one super admin role. A super admin could then register other users within the system, such a content editor.
YMD End Test 2002 AST 2017/18 – ICA ICA SPECIFICATION Module Title: Advanced Server-side Technologies Module Leader: Andrew Bingham Module Code: MUL3055-N Assignment Title: Royal Literary Fund – Content Management System (CMS) Deadline Date Deadline Time: 1.00 PM · Central Assignments Office (Middlesbrough Tower M2.08) Notes: · All work (including CDs etc) needs to be secured in a plastic envelope or a directory and clearly marked with the student name, number and module title. · An Assignment Front Sheet should be fully completed before the work is submitted. · When an extension has been granted, a fully completed and signed Extension form must be submitted to the SCM Reception. Online Submission Notes: · Please follow carefully the instructions given on the Assignment Specification · When an extension has been granted, a fully completed and signed Extension form must be submitted to the SCM Reception. FULL DETAILS OF THE ASSIGNMENT ARE ATTACHED INCLUDING MARKING & GRADING CRITERIA ICA - Individual Project The Individual Project will form 100% of the overall module mark. You are required to work on the project detailed below. Formative Feedback will be provided throughout during scheduled practical lab sessions. Scenario Brief – Royal Literary Fund – Content Management System (CMS) You are required to build a CMS prototype Web Application called: RLF CMS an application that allows the RLF admin to create content for their website and hybrid apps. Students using the website will not access the CMS. Instead, RLF admins will be able to update existing content for the website: https://www.alexessaytool.com/ Your data model will therefore need to reflect the content structure of the existing app, so that content updates map over to the live website and hybrid app suite. Take time to view the website and then draw a rough outline for the page structure. For example, there are 10 steps – and each step may have one or more pages within. The CMS must be secured behind an login system. You can explore different role based access control features within Yii2 – but as a minimum, there will be one super admin role. A super admin could then register other users within the system, such a content editor. Web Application Prototype (60% of marks): The proof on concept prototype will be a limited working version: Build application entirely within Yii, using the built in views – but change the standard template as appropriate. This is a brand new CMS based Web Application, but feel free to reuse assets from the live site such as logo’s and colour scheme’s via the CSS. We require an appropriate visual design, colour scheme, layout and navigation that is appropriate for the context in which the Web Application will be used. Please use no more than eight database tables in your data model. This ensures you focus on the core aspects of the web application. Objectives, Users, Tasks, Required Functional and non-functional requirements: - Define different users of the system. - Define the high level objectives of the CMS. - Define Tasks undertaken by the users. FRs: - Must allow a admin to login using their email address. - Should allow an super admin user to create more users, with less privileges than the super admin user. - Must allow the admin and any other users to create, read, update, and delete - text content, images and edit a path for each step video. Note :- create two admin user one of Super admin and Normal admin and divide admin role - A CMS dashboard should include functionality associated with the functions above. For further marks, the application could have the following additional functionality: · Explore delivery of text and video or Image via a PHP webservice in the JSON format, to be consumed by the decoupled website application and hybrid application suite. Note: this list is not exhaustive – please use eWURF (www.wurf.co.uk) to determine additional requirements as you see fit. Required Content Areas for the Prototype Web Application: Home Screen (not logged in), Dashboard Screen (logged in user) showing user details and access to the key functions of the system. Deliver a working prototype to the Open Source Web Server in a directory named AST_18. 1. Deployment Documentation (20%): You should detail how the application will be deployed and describe the approach taken in its development. Functional and Non-functional requirements should be included here (use eWURF).It will also outline key framework technologies, server environment, server requirements, how you might deploy to other server environments, load balancing, ways of enhancing performance further and SEO. Marks will be awarded for way the document communicates these aspects. Maximum 1000 words. Note :- this project can view from WAMP server and the godaddy server And install and uploading steps 3. Reflective Essay (20%): Please outline the approach taken in terms of development methodology, defence of the MVC framework, problems encountered and modifications taken. Please evaluate against the functional and non-functional user requirements. Marks will be awarded for the quality of the reflection and systematic use of criteria for the evaluation. Maximum 1000 words. Marking Criteria: Assignment Element Marks allocated for % of Total Prototype Web Application Clientside Development HTML5/CSS3. UI/UX A: The visual design is highly professional and responsive across multiple viewports. A responsive navigation is incorporated and thought has been put into how the user interacts with application to provide an excellent experience. HTML and CSS are well written. /20 B: The visual design is of a good standard and responsive across multiple viewports, with some minor issues. The navigation system is appropriate and interactions provide a good experience overall. HTML and CSS mostly well written. C: The visual design is of a satisfactory standard and responsive across two viewports, with some issues present. The navigation system is appropriate and interactions provide a satisfactory experience overall. HTML and CSS sometimes causes issues when rendering in the browser. D: The visual design is of a poor standard and can only be viewed in one viewport, with many issues present. The navigation system is poor and interactions provide a poor experience overall. HTML and CSS renders inappropriately in the browser. E: Some attempt made, but fall short of a pass without some additional work. F: Deficient in all aspects. Serverside Development PHP/MySQL A: The Web Application works without any major errors, and demonstrates multiple client server interactions appropriate to the scenario. Yii or alternative framework is used correctly. PHP is written and organised professionally and is fully commented. The data model includes more than four tables, but no more than eight. /40 B: The Web Application works with only minor errors, and demonstrates multiple client server interactions. Yii or alternative framework is mainly used correctly. PHP is written and organised appropriately and is mostly commented. The data model includes more than three tables, but no more than eight. C: The Web Application works with a few errors, and demonstrates at least one client server interaction. Yii or alternative framework or alternative framework is used, but some issues apparent .PHP is mostly written correctly, but a few minor issues are visible when it runs. The data model includes at least two tables, but no more than eight. D: The Web Application works with a number of errors. An attempt made at one client server interaction, which will partially work. Yii or alternative framework is not used correctly. PHP could be better written. The data model includes at least one table. E: Some attempt made, but fall short of a pass without some additional work. F: Deficient in all aspects. Sub Total: /60 Deployment Documentation Development Methods, Server, SEO. A: An excellent report, that clearly communicates the methods used in the production of the Web Application, along with how the Web Application would be visible to a search engine. 10 B: A good report that communicates the methods used in the production of the Web Application, along with how the Web Application would be visible to a search engine. C: A satisfactory report that communicates the methods used in the production of the Web Application, along with how the Web Application would be visible to a search engine. D: A poor report that communicates the methods used in the production of the Web Application, along with how the Web Application would be visible to a search engine. E: Some attempt made, but fall short of a pass without some additional work. F: Deficient in all aspects. Requirements Documentation A: eWURF fully utilised to explore actors, tasks, objectives and functional/non-functional requirements. A full and complete set of requirements produced at the end. 10 B: eWURF utilised to explore actors, tasks, objectives and functional/non-functional requirements. A mainly complete set of requirements produced at the end. C: eWURF partially utilised to explore actors, tasks, objectives and functional/non-functional requirements. A mainly complete set of requirements produced at the end, but some issues may be apparent. D: eWURF partially utilised to explore actors, tasks, objectives and functional/non-functional requirements. A mainly complete set of requirements produced at the end, but some significant issues may be apparent. E: Some attempt made, but fall short of a pass without some additional work. F: Deficient in all aspects. Sub Total: /20 Reflective Essay Reflection on process. A: An excellent reflective essay, providing the reader with insight into the main problems encountered and how these were resolved. Systematic evaluation against the functional and non-functional requirements. 20 B: A good reflective essay, providing the reader with insight into the some of the main problems encountered and how these were resolved. Systematic evaluation against the functional and non-functional requirements. C: A satisfactory reflective essay, providing the reader with insight into the some of the main problems encountered and how these were resolved. Evaluation against the functional and non-functional requirements, but some may be missing. D: A poor reflective essay. Does not provide the reader with insight into the problems encountered and how these were resolved. A poor evaluation against the functional and non-functional requirements. E: Some attempt made, but fall short of a pass without some additional work. F: Deficient in all aspects. Sub Total: /20 Total Mark: /100 Page 9 of 9