SQU Web Programming Worksheet

REQUIREMENTS

Student should be able to create a CRUD (Create Read Update and Delete) web application using HTML, CSS, Java Script and Python with Db connectivity. Web application should have responsive UI, LESP, system architecture needs to be clearly defined and implemented.

FINAL DELIVERABLES

• A Report in hard copy as per guidelines with Standard top sheet.
• Report will contain a CD which should have soft copy of the report along with complete code.

CD should contain the following:

1. An integrated web system with source code in ZIP file (using e.g., 7Zip). This should contain all the files and folders for the full working website. All programme files must have group ID and student name who has written the code.

2. Relevant Database (e.g. MySQL) dump.

3. A word document that includes names and student ids. This document should also provide a very basic guide (or instructions) about how to setup their website for testing including any test usernames and passwords. Suitable test data should also be provided to test the website functionality.

Design and Implementation requirements

Blood Bank Management System

Blood Bank Management system will contain some basic information related to Blood bank and CRUD operations need to apply by keeping in mind the following actors along with the types of action which they can perform.

The website MoSCoW requirements are identify using (M=Must, S=Should, C=Could, W= Would) below:

ADMIN:-

• Manage Registration for user [M]
• Manage Blood bank information like (update, delete) [M]
• Manage Donor Request for Donor [M]
• Manage patient Request for needy people [S]
• Manage Inquiry form for Appropriate Reply [C]
• Manage feedback for Appropriate Reply [C]
• Manage Donor information(profile) [M]
• Add new Donation for Blood [S]
• Manage patient information(profile)[M]
• Give the Request for patient for blood [S]

• Blood bank information view/update [S]
• View Donor information [M]
• Manage Patient Blood Request. [S]

DONOR:-

Manage Donor information(profile) [M]Add new Donation for Blood [S]

PATIENT:-

Manage patient information(profile)[M]Give the Request for patient for blood [S]

Bonus Task:

System is implemented with functionality of reports generation in a good format. Example of reports are as follow:

• Report of the requested blood according to blood groups
• Report of Donors with respect to different age groups
• Report of entertained requests with respect to blood bank
• Summary of pending requests

Check the attached file for more information

DEPARTMENT OF COMPUTING
ASSESSMENT COVER SHEET
Web Programming
Resit- Individual website code and written report
Resit Component B (Individual website code and written report)
REQUIREMENTS
Student should be able to create a CRUD (Create Read Update and Delete) web
application using HTML, CSS, Java Script and Python with Db connectivity. Web
application should have responsive UI, LESP, system architecture needs to be
clearly defined and implemented.
FINAL DELIVERABLES
•
•
A Report in hard copy as per guidelines with Standard top sheet.
Report will contain a CD which should have soft copy of the report
along with complete code.
CD should contain the following:
1. An integrated web system with source code in ZIP file (using e.g., 7Zip). This should
contain all the files and folders for the full working website. All programme files must have
group ID and student name who has written the code.
2. Relevant Database (e.g. MySQL) dump.
3. A word document that includes names and student ids. This document should also
provide a very basic guide (or instructions) about how to setup their website for testing
including any test usernames and passwords. Suitable test data should also be provided to
test the website functionality.
Design and Implementation requirements
Page 1 of 4
Blood Bank Management System
Blood Bank Management system will contain some basic information related to Blood
bank and CRUD operations need to apply by keeping in mind the following actors
along with the types of action which they can perform.
The website MoSCoW requirements are identify using (M=Must, S=Should, C=Could, W=
Would) below:
ADMIN:•
•
•
•
•
•
•
•
•
Manage Registration for user [M]
Manage Blood bank information like (update, delete) [M]
Manage Donor Request for Donor [M]
Manage patient Request for needy people [S]
Manage Inquiry form for Appropriate Reply [C]
Manage feedback for Appropriate Reply [C]
Blood bank information view/update [S]
View Donor information [M]
Manage Patient Blood Request. [S]
DONOR:•
•
Manage Donor information(profile) [M]
Add new Donation for Blood [S]
PATIENT:•
•
Manage patient information(profile) [M]
Give the Request for patient for blood [S]
Bonus Task:
System is implemented with functionality of reports generation in a good format. Example of
reports are as follow:
•
•
•
•
Report of the requested blood according to blood groups
Report of Donors with respect to different age groups
Report of entertained requests with respect to blood bank
Summary of pending requests
Page 2 of 4
Web Project Student Checklist (Tick the relevant option)
1. Navigation
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
Always
Compliance
Sometimes
Never
There is a clear indication of the current location
There is a clearly-identified link to the Home page
All major parts of the site are accessible from the Home page
Site structure is simple, with no unnecessary levels
If necessary an easy to use search function is available
2. Functionality
All functionality is clearly labelled
All necessary functionality is available without leaving the site
3. Control
The user can cancel all operations
There is a clear exit point on every page
All graphics links are available as textual links
The site support the user flows
The site support all browsers
Language
The language used is simple
4. Feedback
If necessary, online help is available
It is always clear what is happening on the site
Users can receive email feedback if necessary
Users can give feedback via email or a feedback form
5. Consistency
Only one word or term is used to describe any item
Links match titles of the pages to which they refer
Standard colours are used for links and visited links
Terminology is consistent with general web usage
6. Error prevention and correction
Errors do not occur unnecessarily
Error message is in plain language
Error messages describe what action is necessary
Error messages provide a clear exit point
Error messages provide contact details for assistance
7. Visual clarity
The layout is clear
All images have ALT text assigned
Unnecessary animation is avoided
Page 3 of 4
Grading Criteria
Page 4 of 4