HIT326 Project code (i.e. all application code including database scripts and data) - Marking Guide (35%)
HIT326 Project code (i.e. all application code including database scripts and data) - Marking Guide (35%)
Component Value Comment
The application is runnable 4
Installation of local web server applications accords with instructions in Report. 1
The database tables (with data) are appropriately and efficiently organised and tested. 4
The application is resistant to injection attacks (SQL, JS and HTML). 2
The working code is well organised and readable. 4
The working code accords with known design patterns (e.g.
MVC) 6
Passwords and other sensitive data are appropriately protected. 4
The application accords with statements made in the project proposal and associated progress report. 10
Team work (optional)
35
The assessor has flexibility to allocate bonus points where aspects of the project demonstrate exceptional skill and understanding of concepts in this unit. If students worked in teams then the final score will be factored into the 35%.
HIT 326 Project Report - Marking Guide (15 marks)
Component Value Comment
Overview
2
Installation related instructions
1
Database tests
1
Application Tests
1
Working code description
5
Security
2
Lessons learned
1
Conclusion
1
The report is well structured and readable.
1
Team work (Optional)
15
There is scope for bonus points (though with total project mark capped at 50) where novel and creative approaches apply, or the standard of the report is exceptionally high. Team scores are factored into the scope of the project and report. Please document team member contributions genuinely and clearly.
PROJECT PROPOSALHIT326 DATABASE -DRIVEN WEB APPLICATIONS
Contents
TOC o "1-3" h z u PROJECT PROPOSAL PAGEREF _Toc105181918 h 1The problem PAGEREF _Toc105181919 h 4Solution PAGEREF _Toc105181920 h 4Inclusions PAGEREF _Toc105181921 h 4Exclusions PAGEREF _Toc105181922 h 4The Plan PAGEREF _Toc105181923 h 6
Description
Todays word is conveniency, everybody wants things delivered quick to their door step, whether its food , clothes e.t.c, businesses and big organizations have changed their business model because of this. However, in this project the case is the same to where art is delivered to the community bought from an online platform.
The problemMost people today especially the youths have lost sense of their culture, the internet plays a huge role. People are experiencing things quick and at instance because information is travelling quicker and faster from music, pictures, and art .e.t.c However Art now on the internet is playing its effective role as far where cultural art is concerned, in that case people can reconnect to that from enjoying art and getting it from the internet.
Problem with the domain
Most likely to have SQL injections while building the website.
My domain might not hold information for a long period of time neither executing is time to live (TTL).
SolutionIam individually working on this Assignment project, I will constantly try out my codes which I believe will help me override my errors in this case , I have built a time line to follow until I arrive at a solution through a plan, I have organized my work and going through weekly tutorials as I continue with this project. I intend to use VSC I think its user friendly because I used it in the past and familiar with it .
InclusionsI have decided my website to have certain features because its an online Art selling website. The features or functions include.- Home page,
news and products items to be displayed for customer notification.
Purchased items to be stored in order tables
Customers selecting items using the shopping cart
Emailing items purchased details to customers
ExclusionsMy intensions is for the website to be simple, customers should be able to easily navigate and get confirmation details, which is why I intend to exclude certain things which are important but not exactly necessary but maybe included at some point in the project.
Payment Options
Full Customer information
All linked tabs
Full Content layout
Oversized images.
The PlanThis is my individual GANT chat on how I have been approaching this project
Defined the Project: That was my first step to the plan
Website Planning: The second step of the project was me planning my website using a prototype just to see how its going to work out and its layout.
Website Design: 3rd step to my project, which is my current stage right now. Involving codes and am creating my front end.
Below is My Gant Table.
Steps Start Date End Date
Define Project 04/05/2022 07/05/2022
Plan website 08/05/2022 13/05/2022
Design website (coding) 20/05/2022 3/6/2022
Create Content 3/06/2022 7/6/2022
Add Functionality 3/6/2022 7/6/2022
Testing 8/06/2022 9/06/2022
Lunch 10/06/2022 10/06/2022
center250002514600Project Title91700100000Project Titlecenter800007498080Your name(s)2019Lecturer: Luis Silva100000100000Your name(s)2019Lecturer: Luis Silva
Project TitleTable of Contents
TOC o "1-3" h z u Overview PAGEREF _Toc367706071 h 2About the project PAGEREF _Toc367706072 h 2Project Team PAGEREF _Toc367706073 h 2Business Requirements PAGEREF _Toc367706074 h 2Project Approach PAGEREF _Toc367706075 h 2Strategy PAGEREF _Toc367706076 h 2The online prototype PAGEREF _Toc367706077 h 2Installation instructions PAGEREF _Toc367706078 h 3Uninstalling PAGEREF _Toc367706079 h 3Database Tests PAGEREF _Toc367706080 h 3Application Tests PAGEREF _Toc367706081 h 3Working code description PAGEREF _Toc367706082 h 3Security PAGEREF _Toc367706083 h 4Licensing and copyright PAGEREF _Toc367706084 h 4Team work PAGEREF _Toc367706085 h 4Lessons Learned PAGEREF _Toc367706086 h 4Conclusion PAGEREF _Toc367706087 h 4References PAGEREF _Toc367706088 h 6Appendices PAGEREF _Toc367706089 h 7Appendix A PAGEREF _Toc367706090 h 8Appendix B PAGEREF _Toc367706091 h 9
OverviewAbout the projectIntroduce the focus of your project
Background you may wish to consult information from your project proposal and progress reports.
The overall goal of this project was/is to .
One or two paragraphs are all that is needed here.
Project Team
This is only relevant for team-based approaches. Outline the project team members, if any, and the roles and brief outline of responsibilities they assumed for the duration of the project. One paragraph is all that is needed here or a sentence and a table
Business RequirementsFrom the project brief and from any feedback from your client, outline the business requirements for your project.Specifically in this section outline:
What problem (or problems) does your application solve?
What were the final inclusions?
What were the final exclusions ?
Do the above points differ in any way to the final progress report?
Two or three paragraphs are all that is needed here. This information should be found in your original proposal and the subsequent progress reports.
Project ApproachOutline the approach that was used to develop the project write a paragraph describing this process and why it was used. Reference your writing in this section. One or two paragraphs are all that is needed here. Address this section by referring to the three-tiers and the tools you used.
Is it REST?
StrategyHow did you organize the project? How did you generally organise the application code? Did you use any design patterns (e.g. MVC)? One or two paragraphs are sufficient here. Details come later in the report.
The online prototypeProvide detailed information here on how the working prototype on Spinetail operates. Itemise examples of how it addresses the business requirements. List any features. You could also provide a test account for administrative functions e.g. signing in to your application. Note: sign in details to Spinetail itself should not be provided, only the administrative functions of your application are necessary.
Obviously, you must provide the URL to your application.
To what extent is the application mobile-ready?
You may provide screen captures in an appendix if you wish.
Installation instructionsThis section refers to instructions on how to install the web application on a local server i.e. WAMP/LAMP/MAMP. Remember, you must send the actual application as an archived (zipped) collection to the assessor through Learnline. The assessor will install it on a typical xampp server.
You should state the name of the expected database which must be created. You should clearly refer to the create and load files which create tables and load any data.
You should clearly state the relationship the files and folders have to each other and where they are placed in relation to the document root, and why.
Provide the SQL scripts required to create the tables and a separate script to load any initial data.
Make sure you mention the versions of the scripting (i.e. PHP) language and database applications required.
Also make sure you mention any program and database extensions required (e.g. php_mysqli).
You may assume the web server onto which the application is installed has HTTPS enabled, although you should still mention it if it is required.
You may include screen captures in an Appendix.
UninstallingProvide specific instructions on how to uninstall the application. This includes the application code as well as the database. You may provide a script to do so, but it is not essential.
Database TestsProvide special load and test scripts for testing all CRUD operations on all tables in the application. This load script is different to the one mentioned above. The assessor will test and exercise the database with these load and test scripts before the application is installed.
You may provide prints of tests in an Appendix.
Application TestsWhat tests should be carried out after the program is first installed. These tests should verify that all claimed features are working properly.
Provide advice to those installing the application of what to do if a key aspect of the application fails.
You may provide prints or screen captures as an Appendix.
Working code descriptionThis is where you get into the specifics of your code. Describe how it is organized. Use paths, file names and line numbers to highlight key aspects of your working code and how you solved problems associated with this project. For example, how does the program maintain state? How does the application work across the three tiers?
Demonstrate how your application accords with good programming practices such as DRYing up your code and re-usability. What makes this a good example of a database-driven web application.
Provide detailed examples of how the application code, database, and client-side code work together. Which database and techniques did you use prepared statements, Yanks method, MYSQLI, SQLite, PDO and so on. Which HTML doctype? Why? Did you include mobile readiness in any way?
This is a key part of the report.
SecurityOutline the key security features of the application. How does it protect data going into the database? How is the user protected from different kinds of code injection on input and output? How are user-names and passwords protected? Note that you should also mention how the database connection details are protected. How did you protect data going into the database? Which database and techniques did you use prepared statements, Yanks method, MYSQLI, SQLite, PDO and so on.
Use paths, file names, and line numbers to highlight examples.
Licensing and copyrightYou should briefly discuss the possible or preferred licensing arrangements for the application. This does not have to be a final decision. It is suggestive only. Provide advice on the possibilities, and one you are likely to prefer.
Team workThis section is for those who approached this project as a team.
Clearly outline how you approached the division of labour. Who did what? What worked? What did not?
Where there any advantages or disadvantages in taking a team approach?
What lessons were learned?
Lessons LearnedWhat worked ?
What didnt?
What would you change if you did this project again? i.e What would you do different?
How did the actual project timeline compare to that in the original proposal?
ConclusionUp to you summarise the key points you have made as you went through the report and make a final comment.
Dont forget to regenerate the Table of Contents before submitting the report
ReferencesFirst reference. The text begins at the left margin of the paper. Lines are double-spaced. When the entry is longer than one line, the second line is automatically indented.
Put these in alphabetical order
Use Harvard Style.
Additional references.
Appendices
Appendix A
Appendix B
